Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 187C211389 for ; Fri, 10 May 2013 10:49:20 +0000 (UTC) Received: (qmail 84713 invoked by uid 500); 10 May 2013 10:49:18 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 84443 invoked by uid 500); 10 May 2013 10:49:18 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 84143 invoked by uid 99); 10 May 2013 10:49:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 May 2013 10:49:17 +0000 Date: Fri, 10 May 2013 10:49:17 +0000 (UTC) From: "Andreas Veithen (JIRA)" To: java-dev@axis.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Moved] (AXIS2-5534) Caching InitialContexts in JMS transport sender MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AXIS2-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-12 to AXIS2-5534: -------------------------------------------------- Component/s: (was: JMS) JMS Key: AXIS2-5534 (was: TRANSPORTS-12) Project: Axis2 (was: Axis2 Transports) > Caching InitialContexts in JMS transport sender > ----------------------------------------------- > > Key: AXIS2-5534 > URL: https://issues.apache.org/jira/browse/AXIS2-5534 > Project: Axis2 > Issue Type: Improvement > Components: JMS > Reporter: Rajika Kumarasiri > Labels: JMS, transport > 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. > > > org.apache.activemq.jndi.ActiveMQInitialContextFactory > tcp://localhost:61616 > QueueConnectionFactory > queue > producer > true > > > A related discusstions also can be found here: http://wso2.org/forum/thread/9281 > Some of the improvements in this patch was suggested by Paul Inglis who also submitted the patch for issue - https://issues.apache.org/jira/browse/AXIS2-4625 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org