axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] Moved: (TRANSPORTS-18) JMS Transport Sender ignores connection factory settings from axis2.xml.
Date Wed, 22 Sep 2010 20:11:04 GMT


Andreas Veithen moved WSCOMMONS-521 to TRANSPORTS-18:

              Project: Axis2 Transports  (was: WS-Commons)
                  Key: TRANSPORTS-18  (was: WSCOMMONS-521)
    Affects Version/s:     (was: Transports 1.1)
          Component/s: JMS
                           (was: Transport)

> JMS Transport Sender ignores connection factory settings from axis2.xml.
> ------------------------------------------------------------------------
>                 Key: TRANSPORTS-18
>                 URL:
>             Project: Axis2 Transports
>          Issue Type: Bug
>          Components: JMS
>            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="" locked="false">XXX</parameter>
>         	<parameter name="" 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.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message