While using JMS enabled Axis2 web services in a Websphere MQ
environment, I encountered a bug with JNDI resource leakage when using
the Axis 2 JMS Sender to post to WebSphere MQ - the bug causes the Axis
2 client to use up all of the WebSphere MQ servers client connections,
and after a while nothing can connect to it anymore.
If anyone else is having similar issues with Axis 2 over WebSphere MQ,
I've created a patch/fix for Axis 2 version 1.3 that cleans up the JNDI
contexts correctly when sending messages. The patch and details are
at:
http://thejavamonkey.blogspot.com/2008/08/modding-axis-2-jms-transportweb-sphere.html
cheers,
Ants.
--
Anthony
-------------------------------------
Anthony Bull
Senior Developer
Black Coffee Software Ltd
PO Box 10-192 The Terrace
Wellington, New Zealand
[EMAIL PROTECTED]
Ph +64 4 472 8818
Fax +64 4 472 8811
-------------------------------------
www.bcsoft.co.nz
---------------------------------------------------------------
This email may contain confidential or privileged information,
and is intended for use only by the addressee, or addressees.
If you are not the intended recipient please advise the sender
immediately and do not copy, use or disclose the contents to
any other person or organisation.
Black Coffee Software Ltd accepts no responsibility for viruses
received with this email, or to any changes made to the original
content. Any views or opinions expressed in this email may be
personal to the sender and are not necessarily those of Black
Coffee Software Ltd.
---------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
