[jira] Created: (AXIS-1375) Exception when using JMS URL endpoint address to drive the JMS transport

[ji...@apache.org]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1375

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1375
    Summary: Exception when using JMS URL endpoint address to drive the JMS transport
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Aleksandrs Hristoforovs

    Created: Mon, 31 May 2004 7:17 AM
    Updated: Mon, 31 May 2004 7:17 AM
Environment: Win2000
jdk 1.4.1 03
Weblogic 8.1.1
JMS/JNDI provided with weblogic 8.1.1


Description:
When running ..\samples\jms\dii\JMSURLTest.java with url:

	static String sampleJmsUrl = "jms:/MyQueue?" +
	 "vendor=JNDI" +
	 "&java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory" +
	 "&java.naming.provider.url=t3://localhost:8080" +
	 "&ConnectionFactoryJNDIName=MyCF" +
	 "&java.naming.context.principal=username" +
	 "&java.naming.context.credentials=password" +
	 "&deliveryMode=persistent" +
	 "&priority=5" +
	 "&ttl=10000" +
	 "&debug=true";

we are getting exception:
javax.naming.ConfigurationException.  Root exception is java.rmi.MarshalException: failed to marshal lookup(Ljava.lang.String;Ljava.util.Hashtable;); nested exception is: 
	java.io.NotSerializableException: org.apache.axis.transport.jms.JMSURLHelper
	at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:86)
	at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:278)
	at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
	at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
	at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
	at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
	at javax.naming.InitialContext.lookup(InitialContext.java:347)
	at org.apache.axis.components.jms.JNDIVendorAdapter.getConnectionFactory(JNDIVendorAdapter.java:87)
	at org.apache.axis.components.jms.JNDIVendorAdapter.getQueueConnectionFactory(JNDIVendorAdapter.java:55)
	at org.apache.axis.transport.jms.JMSConnectorFactory.createConnector(JMSConnectorFactory.java:227)
	at org.apache.axis.transport.jms.JMSConnectorFactory.createClientConnector(JMSConnectorFactory.java:178)
	at org.apache.axis.transport.jms.JMSConnectorManager.getConnector(JMSConnectorManager.java:107)
	at org.apache.axis.transport.jms.JMSTransport.setupMessageContextImpl(JMSTransport.java:163)
	at org.apache.axis.client.Transport.setupMessageContext(Transport.java:46)
	at org.apache.axis.client.Call.invoke(Call.java:2649)
	at org.apache.axis.client.Call.invoke(Call.java:2357)
	at org.apache.axis.client.Call.invoke(Call.java:2280)
	at org.apache.axis.client.Call.invoke(Call.java:1741)
	at JMSURLTest.getQuote(JMSURLTest.java:131)

This is caused because JMSURLHelper is in environment variable passed to InitialContext:
(code from JNDIVendorAdapter.getConnectionFactory() )
<..>
        context = new InitialContext(environment);
<..>

JMSURLHelper is put in cfProps in following method:
JMSVendorAdapter.getJMSConnectionFactoryProperties()

Affter commenting folowing line in JMSVendorAdapter.getJMSConnectionFactoryProperties() everything works fine:
        // cfProps.put(JMSConstants.JMS_URL, jmsurl);

JMSURLHelper is used in method isMatchingConnectionFactory 
which uses only _CONNECTION_FACTORY_JNDI_NAME property of JMSURLHelper to match connection factory.
Because of this JMSVendorAdapter.getJMSConnectionFactoryProperties()
could put only jmsurl.getPropertyValue(_CONNECTION_FACTORY_JNDI_NAME)
in cfProps hashmap.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira