axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AXIS2-5523) JMSSender executes unnecessary JNDI lookups
Date Sun, 24 Jan 2016 15:34:40 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Veithen updated AXIS2-5523:
-----------------------------------
    Fix Version/s:     (was: 1.7.0)
                   1.7.1

> JMSSender executes unnecessary JNDI lookups
> -------------------------------------------
>
>                 Key: AXIS2-5523
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5523
>             Project: Axis2
>          Issue Type: Bug
>          Components: JMS transport
>            Reporter: Andreas Veithen
>            Priority: Minor
>             Fix For: 1.7.1
>
>         Attachments: TRANSPORTS-1-update1.patch, TRANSPORTS-1.patch
>
>
> JMSSender contains the following code:
> jmsOut = new JMSOutTransportInfo(targetAddress);
> // do we have a definition for a connection factory to use for this address?
> jmsConnectionFactory = getJMSConnectionFactory(jmsOut);     
> if (jmsConnectionFactory != null) {
>     messageSender = new JMSMessageSender(jmsConnectionFactory, targetAddress);
> } else {
>     ...
> }
> The constructor of JMSOutTransportInfo will create a new InitialContext and lookup the
destination from JNDI. If a connection factory definition is found (jmsConnectionFactory !=
null), this is unnecessary because the JMSMessageSender constructor will also create a new
InitialContext (or reuse a cached one) and carry out the JNDI lookup again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message