axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] Commented: (TRANSPORTS-12) Caching InitialContexts in JMS transport sender
Date Wed, 01 Dec 2010 07:08:11 GMT


Hiranya Jayathilaka commented on TRANSPORTS-12:

I believe the problem is with the InitialContext created in the JMSOutTransportInfo class.
This doesn't seem to get cleaned up ever. With certain JMS brokers this leads to catastrophic

Regarding your point 2 and 3, please note that JMSConnectionFactory will not come into the
picture unless the user has defined any in the Axis configuration under the JMS transport

I would like to spend some time on this issue and get it fixed properly. Will send in a patch

> Caching InitialContexts in JMS transport sender
> -----------------------------------------------
>                 Key: TRANSPORTS-12
>                 URL:
>             Project: Axis2 Transports
>          Issue Type: Improvement
>          Components: JMS
>            Reporter: Rajika Kumarasiri
>         Attachments: AXIS2-4658.patch, AXIS2-4658.patch
> When using the JMS transport sender for sending messages  to external broker it creates
InitialContext per message. This is actually unnecessary since we can cache and use the same
intialContext., and also some brokers behave strangely when re-creating the initialContext.
This patch cache the InitalContext using the EPR as the key. User can specify to use caching
using the property "transport.jms.CacheInitialContext" set to true. Synchronization has done
as required since creating InitialContext is not thread safe and also JNDI look up. 
> User has to define an Initial Context definition in the JMSTransport sender configuration
as follows. 
> <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender">
>         <parameter name="default" locked="false">
>         	<parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
>         	<parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter>
>         	<parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
> 		<parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
> 		<parameter name="transport.jms.CacheLevel">producer</parameter>
>                 <parameter name="transport.jms.CacheInitialContext">true</parameter>
>         </parameter>
> </transportSender> 
> A related discusstions also can be found here:
> Some of the improvements in this patch was suggested by Paul Inglis who also submitted
the patch for issue - 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message