Destination jms/Topic-test not found

One Star

Destination jms/Topic-test not found

Hello
The tjmsimout and tjmsoutput can connect to jmsserver now,but there can't find destination, the configuration of TOS
and weblogic refer to attachment please,what should I do next ,thank you!
?15:18 09/07/2012????Copy_of_test_a.

connecting to socket on port 3881
connected
Exception in component tJMSInput_1
weblogic.jms.common.JMSException: Destination jms/Topic-test not found
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3133)
at weblogic.jms.client.JMSSession.createTopic(JMSSession.java:2419)
at weblogic.jms.client.WLSessionImpl.createTopic(WLSessionImpl.java:1123)
at talenddemosjava.copy_of_test_a_0_1.Copy_of_test_a.tJMSInput_1Process(Copy_of_test_a.java:467)
at talenddemosjava.copy_of_test_a_0_1.Copy_of_test_a.runJobInTOS(Copy_of_test_a.java:1325)
at talenddemosjava.copy_of_test_a_0_1.Copy_of_test_a.main(Copy_of_test_a.java:1193)
Caused by: weblogic.jms.common.JMSException: Destination jms/Topic-test not found
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
at weblogic.jms.dispatcher.Request.useChildResult(Request.java:69)
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:339)
at weblogic.jms.frontend.FEManager.invoke(FEManager.java:544)
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)
Caused by: weblogic.jms.common.JMSException: Destination jms/Topic-test not found
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:1124)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsyncInternal(DispatcherImpl.java:139)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:115)
at weblogic.messaging.dispatcher.Request.dispatchAsync(Request.java:1295)
at weblogic.jms.dispatcher.Request.dispatchAsync(Request.java:96)
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:324)
... 8 more
Caused by: weblogic.jms.common.JMSException: Destination jms/Topic-test not found
at weblogic.jms.backend.BackEnd.findDestination(BackEnd.java:1604)
at weblogic.jms.backend.BackEnd.invoke(BackEnd.java:2175)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
... 13 more
Exception in component tJMSOutput_1
weblogic.jms.common.JMSException: Destination jms/Topic-test not found
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3133)
at weblogic.jms.client.JMSSession.createTopic(JMSSession.java:2419)
at weblogic.jms.client.WLSessionImpl.createTopic(WLSessionImpl.java:1123)
at talenddemosjava.copy_of_test_a_0_1.Copy_of_test_a.tRowGenerator_1Process(Copy_of_test_a.java:917)
at talenddemosjava.copy_of_test_a_0_1.Copy_of_test_a.runJobInTOS(Copy_of_test_a.java:1338)
at talenddemosjava.copy_of_test_a_0_1.Copy_of_test_a.main(Copy_of_test_a.java:1193)
Caused by: weblogic.jms.common.JMSException: Destination jms/Topic-test not found
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
at weblogic.jms.dispatcher.Request.useChildResult(Request.java:69)
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:339)
at weblogic.jms.frontend.FEManager.invoke(FEManager.java:544)
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)
Caused by: weblogic.jms.common.JMSException: Destination jms/Topic-test not found
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:1124)
disconnected
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsyncInternal(DispatcherImpl.java:139)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:115)
at weblogic.messaging.dispatcher.Request.dispatchAsync(Request.java:1295)
at weblogic.jms.dispatcher.Request.dispatchAsync(Request.java:96)
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:324)
... 8 more
Caused by: weblogic.jms.common.JMSException: Destination jms/Topic-test not found
at weblogic.jms.backend.BackEnd.findDestination(BackEnd.java:1604)
at weblogic.jms.backend.BackEnd.invoke(BackEnd.java:2175)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
... 13 more
?15:19 09/07/2012????Copy_of_test_a?
One Star

Re: Destination jms/Topic-test not found

Hi
Because you have gotten a lot of issues about JMS component recently, I think you'd better report it on BugTracker.
This would give you an chance to have a talk with development team. Maybe some underlying bugs weren't found before.
Regards,
Pedro