New JMS Implementation - ConnectionFactory cache for client -----------------------------------------------------------
Key: AXIS2-869 URL: http://issues.apache.org/jira/browse/AXIS2-869 Project: Apache Axis 2.0 (Axis2) Type: New Feature Components: transports Reporter: Ali Sadik Kumlali Priority: Minor I'm creating this issue regarding discussion found at http://www.mail-archive.com/axis-dev@ws.apache.org/msg18547.html Following is the related excerpt from the mentioned discussion: [Ali Sadik Kumlali] - In SonicMQ, if ConnectionFactory is retrieved from the JNDI for each connection, very high memory usage which prevents access to admin console occurs during high message traffic. And sometimes the server crashes. - AFAIK, old JMS implementation uses connectors to achive this. [Asankha] The JMS listener focuses on listening for JMS messages - and I believe that the optimization that one could perform on outgoing JMS is limited - as different messages may be destined for different JMS destinations. However, I also think that we could use the "default" connection factory (if one is defined) for outgoing messages with a minor patch.. Will this be ok? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]