Hi,
We have been deploying Axis2 1.3 on WAS 6.1.0.9. We are using SOAP over JMS and are using Websphere MQ 6.0. This deployment has worked fine for us. However, we have recently upgraded to Axis2 1.4. The same deployment is now behaving unusually. When sending a message which contains a binary attachment using MTOM the client places two identical messages on the queue instead of the expected one message. Our test cases have narrowed this down to the MQ Queue object being used and more importantly how that object is obtained. When the MQ Queue object is obtained by performing a JNDI lookup on WAS the unusal behaviour of two messages is the result. When the MQ Queue object is obtained by performing a JNDI lookup of an alternative JNDI server (e.g a file system context) the behaviour is as expected i.e one message is placed on the queue. Question: Why is the MQ Queue object returned via a WAS JNDI lookup causing two messages to be placed on the queue? Thanks, Cathal -- View this message in context: http://www.nabble.com/MTOM---duplicate-message-on-queue-tp17804361p17804361.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
