[AXIS2-5523] JMSSender executes unnecessary JNDI lookups

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: JMS transport
• Assignee: Unassigned
• Reporter: Andreas Veithen
• Created: 10/May/09 17:39
• Updated: 20/Feb/16 20:20

Description

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.

Issue Links

• incorporates: AXIS2-5534 Caching InitialContexts in JMS transport sender