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

Key: HJMS-154
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Colin Crist
Reporter: Wayne Zhang
Votes: 0
Watchers: 0
Operations

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

Connect to Weblogic JMS Server Queue Failed

Created: 29/Jul/11 03:56 AM   Updated: 10/Aug/11 06:20 AM
Component/s: None
Affects Version/s: 1.14
Fix Version/s: 1.14

Environment:
OS: Windows XP SP3
Java: 1.6.0 Update 26
WebLogic Server: 10.3.3.0


 Description  « Hide
Connect to WebLogic Server JMS Queue failed. (It works in HermesJMS 1.3 and a 1.4 dev build released last year). Exception:

weblogic.jms.common.JMSException: [JMSExceptions:045101]The destination name passed to createTopic or createQueue "WapsImsInQueue" is invalid. If the destination name does not contain a "/" character then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character then the string before the "/" must be the name of a JMSServer or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WLS server will be returned.
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:202)
at weblogic.jms.frontend.FEManager.invoke(FEManager.java:548)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

1.14 uses sessions created by previous version. Is there any destination name change in the latest version?


 All   Comments   Change History      Sort Order:
Colin Crist [01/Aug/11 09:16 AM]
Are you using the Hermes JNIDQueueConectionFactory in your configuration?

If so I've updated the release with a fix which I think is the same as what you are seeing. Please try the updated version on sourceforge.

Wayne Zhang [10/Aug/11 12:52 AM]
Yes, this issue has been fixed by your latest update.

Thanks!