Oracle Apps dbas,
We suddenly got the following error from our ipayment system batch job
[022807_083745962][EXCEPTION] [DEBUG] [sun.cpu.isalist]:
exception occured for (payee id=110485,account id=110485,batch id=2363) Communication error. The payment system, the processor, or iPayment electronic commerce servlet is not available/accessible. Please make sure you have the correct system set up and resubmit the request at a later time.
The Stack Trace is -
oracle.apps.iby.exception.PSException: Communication error. The payment system, the processor, or iPayment electronic commerce servlet is not available/accessible. Please make sure you have the correct system set up and resubmit the request at a later time.
It happened after I made some changes in jserv.properites based on the
Oracle Support solution plan to troubleshoot another workflow diagram issue.
I commented out the three in jserv.properities:
Is it any relationship between the two events?
iPayment Scheduler (IBYSCHEDULER) is a Java programs run as concurrent request which looks at the AF_CLASSPATH variable for classpath and does not look at jserv.properties file.
Have a look at Notes: 294084.1 & 376330.1, it may be helpful.
Thanks for the answer.
BTW, are there any good books about oracle applications fundamental which
introduce the basic architectures, how it works?
I am shifting from core dba to apps dba.
find out there is so many basics need to know.
E.g. what products/module in apps uses the real Java? what uses serviettes
What is AF_CLASSPATH…….
Interesting. Some nights the payment scheduler works some nights it doesn’t work with the same communication error.
All the real-time CC authorization work fine.
Is it possible that the paymentech server is too busy to handle this?
But the verified that they received the files.