JMS Transport Sender ignores connection factory settings from axis2.xml.
------------------------------------------------------------------------
Key: WSCOMMONS-521
URL: https://issues.apache.org/jira/browse/WSCOMMONS-521
Project: WS-Commons
Issue Type: Bug
Components: Transport
Affects Versions: Transports 1.1
Reporter: Gabor Herr
Properties from an axis2 jms connection factory are not used when referring to
indirectly from the EPR like this
jms:/servicequeue?transport.jms.ConnectionFactory=default:
where axis2.xml contains the following definition:
<!-- JMS Transport -->
<transportSender name="jms"
class="org.apache.axis2.transport.jms.JMSSender">
<parameter name="default" locked="false">
<parameter name="java.naming.factory.initial"
locked="false">com.tibco.tibjms.naming.TibjmsInitialContextFactory</parameter>
<parameter name="java.naming.provider.url"
locked="false">tibjmsnaming://HOST:PORT</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName"
locked="false">QueueConnectionFactory</parameter>
<parameter name="java.naming.security.principal"
locked="false">XXX</parameter>
<parameter name="java.naming.security.credentials"
locked="false">XXX</parameter>
<parameter name="transport.jms.UserName"
locked="false">XXX</parameter>
<parameter name="transport.jms.Password"
locked="false">XXX</parameter>
</parameter>
</transportSender>
Using the above EPR will fail with a javax.naming.NoInitialContextException due
to the missing JNDI factory definition.
The problem seems to be that getJMSConnectionFactory in JMSSender is called too
late in sendMessage, when JMSOutTransportInfo constructor had already made some
JNDI calls.
According to the documentation this should be possible:
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
