|
If you were logged in you would be able to see more operations.
|
|
|
HermesJMS
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
WIndows Server 2003
JBoss 5.1.0.GA
Hermes 1.14
|
|
|
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?
|
|
Description
|
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?
|
Show » |
|
|
Bug
Resolved
Major
Problems with JNDIQueueConnectionFactory and queue names