Anyone worked with Verisign's Payflow Pro object in ASP? We've had it
up and running for weeks without a problem and recently we've started
to get some undesirable behavior: at the point where the component
sends the transaction data, about 1 in 4 times it will go through, but
otherwise it will sit and spin until the script or the browser session
times out. may or may not be related to a server maintenance change.
I'm not a server admin guy, so I don't know specifically what to look
for, but can anyone tell me what I should ask our server admin guy to
look for? Could there be something with COM threading or other issues
where multiple instances of this object are being run? Is there a
place on the server where a person can look and see what's going on
with this object?
Here's the code with some info removed... I've marked where it usually
locks or spins:
***************************
Set client = Server.CreateObject("PFProCOMControl.PFProCOMControl.1")
'Transaction through Verisign
parmList = "TRXTYPE=S&TENDER=C&PARTNER=VeriSign&VENDOR=XXXXXXX&USER=XXXXXXX&PWD=XXXXXXX&ACCT=4111111111111111&EXPDATE=0405&AMT=0.01"
Ctx1 = client.CreateContext("test-payflow.verisign.com", 443, 30, "",
0, "", "")
'this next line is what locks up the object or goes into a loop
curString = client.SubmitTransaction(Ctx1, parmList, Len(parmList))
client.DestroyContext (Ctx1)
set Ctx1 = nothing
set client = nothing
***************************
Thanks for your help.