JMSSender executes unnecessary JNDI lookups
-------------------------------------------
Key: WSCOMMONS-467
URL: https://issues.apache.org/jira/browse/WSCOMMONS-467
Project: WS-Commons
Issue Type: Bug
Components: Transport
Reporter: Andreas Veithen
Priority: Minor
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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
