Thank you very much for your replies. Matching them to IBM's statement about the AMI's future, I think I will steer my customer towards Scott's path: native Java classes and/or JMS.
Cheers.
Heinz
Ruzi R wrote:
Hi Heinz,
You are having a lot of problems with PeopleSOft using AMI, and currently in the process of dealing with them (with lost of frustration). The problem seems to happen for sending messages over about 500K. Yesterday, it took over an hour to put a 1.8 MB message, and the process was still hanging as it did not get the confirmation (I think it is the return code from AMI). I could browse the message (so it was committed). After an hour it put the same message again ! 3 minutes after that it put it for the third time. So the same message got put 3 times ( with Retry count =3)!!!. Retry count is not supposed to work like this. We are trying to determine the exact pattern, which seems to be very hard to do Sometimes we get the AMI return code 49 -- for no justifiable reason. I will put the AMI trace on and see if we can come up with anything.
Best regards,
Ruzi
--- Scott Gray <[EMAIL PROTECTED]> wrote:
Heinz,
We had all sorts of problems running AMI under WAS 3.5 ranging from lockups to coredumps...worked with support for weeks but got the run around between the WAS and MQ support teams...we finally gave up and rewrote our app using the base mq java classes. The best answer we got was that there was some issue with threading and the way AMI used JNI, but we never got real closure.
Good luck.
Scott
-----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Heinz Klein Sent: Tuesday, May 04, 2004 4:44 PM To: [EMAIL PROTECTED] Subject: AMI and Application Servers
Hello everyone.
We have a customer using the AMI (yes we - and they - know AMI is 'out' but they need time to adjust) for file transfer operations.
The applications have been running quite well, but lately they created a new version that runs over the Web. The Java/AMI code on the server side runs under JBoss as application server, and they are having many very strange problems, like lock-ups and the AMI repository file not being found. All these problems happen randomly, apparently when the load rises.
Question: is there any known limitation for the use of the AMI in an Application Server environment, particularly JBoss?
TIA.
Heinz Klein
OLTP Tecnologia & Solucoes Ltda. Sao Paulo/SP - Brasil
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
