History | Log In     View a printable version of the current page. Get help!  
Issue Details (XML | Word)

Key: HJMS-155
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Colin Crist
Reporter: Christian Niehues
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
HermesJMS

Problems with JNDIQueueConnectionFactory and queue names

Created: 01/Aug/11 08:20 AM   Updated: 01/Aug/11 09:13 AM
Component/s: GUI
Affects Version/s: 1.14
Fix Version/s: 1.14

Environment:
WIndows Server 2003
JBoss 5.1.0.GA
Hermes 1.14


 Description  « Hide
With the current version of Hermes we discovered a problem how Hermes is handling queue names with the JNDIQueueConnectionFactory.
Hermes generates queue names like "queue/MY_QUEUE" but if you use JNDIQueueConnectionFactory you will get an error like

"javax.jms.JMSException: There is no administratively defined queue with name:queue/MY_QUEUE"

when sending a message. When you change the initialContextFactory to "JNDIQueueConnectionFactory" all works fine, but with the latest version of hermes this wasn't nescessary.
Did you any changes on hamdling queue names?


 All   Comments   Change History      Sort Order:
Colin Crist [01/Aug/11 09:13 AM]
Yes a bug was introduced, thanks for flagging it. I have updated the release on sourceforge.