axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Turner (JIRA)" <>
Subject [jira] Commented: (AXIS2-2030) jms destination name error in j2ee container
Date Wed, 28 Feb 2007 14:11:56 GMT


John Turner commented on AXIS2-2030:

In addition, the JMSConnectionfactory contains a mapping between the attribute 'transport.jms.Destination'
(in service.xml) and the service name.  This attribute  contains a JNDI name which is not
always equal to the javax.jms.Queue.getQueueName or javax.jms.Topic.getTopicName as these
are both vendor specific representations of the destination.

The JMSMessageReceiver uses the Destination Name to determine which service to call and so
in the case were the destination name is not equal to the JNDI name it will not be able to
resolve the service name.

I have worked around this by maintaining two distinct mappings within the JMSConnectionFactory.
 One which maps the JNDI Name and Service Name and another that maps the Destination Name
and the Service Name.  This also required a change to the JMSMessageReceiver.  I'm not familiar
enough with Axis2 to know if there are any knock-on effects but I have not come across any
so far.  I implemented the work around on 1.1.1 and can post the source if you would find
it helpful?

> jms destination name error in j2ee container
> --------------------------------------------
>                 Key: AXIS2-2030
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1
>         Environment: Axis2 1.1, Geronimo1.1.1, windows XP professional
>            Reporter: falom
>         Assigned To: Sanka Samaranayake
> if axis2 jmslistner trys to listen to an available destination in a j2ee container, i.e.
one queue in activemq in 
> geronimo, then axis2 jmslistner can connect to it only through java:comp/env/jms/testQueue,
but axis2 also register the destination name as java:comp/env/jms/testQueue, not testQueue
instead, so when a axis2  client send message to the queue, the axis2 engine can not find
the service to call. JMSConnectionFactory can be enhanced to handle this problem. falom

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