weblogic.jms.common.JMSException: Subscription - Topic is in use
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   anwar_sadat
Posted On:   Tuesday, July 3, 2007 05:25 AM

weblogic.jms.common.JMSException: Subscription - Topic is in use Hi, I am getting the following exception "weblogic.jms.common.JMSException: Subscription - Topic is in use". If anyone has encountered with similar problems or know the root cause problem, kindly share the solution. Following is the log snippet INFO: Trying to get BEA JMS queue Connection for t3://iam.store.in:7962 INFO: BEA JMS queue Connection for t3://iam.store.in:7962 - Completed INFO: Trying to get BEA JMS queue for MyMessageQueue INFO: BEA JMS queue for MyMessageQueue - Created INFO: Trying to get BEA JMS queue for MyR   More>>

weblogic.jms.common.JMSException: Subscription - Topic is in use


Hi,
I am getting the following exception

"weblogic.jms.common.JMSException: Subscription - Topic is in use".



If anyone has encountered with similar problems or know the root cause problem, kindly share the solution.



Following is the log snippet



INFO: Trying to get BEA JMS queue Connection for t3://iam.store.in:7962

INFO: BEA JMS queue Connection for t3://iam.store.in:7962 - Completed

INFO: Trying to get BEA JMS queue for MyMessageQueue

INFO: BEA JMS queue for MyMessageQueue - Created

INFO: Trying to get BEA JMS queue for MyReplyQueue

INFO: BEA JMS queue for MyReplyQueue - Created

INFO: Trying to get BEA JMS queue for MyShutdownQueue

INFO: BEA JMS queue for MyShutdownQueue - Created



INFO: Trying to get BEA JMS topic Connection for t3://iam.store.in:7962

INFO: BEA JMS topic Connection for t3://iam.store.in:7962 - Completed

INFO: Trying to get BEA JMS Topic for MyEventTopic

INFO: BEA JMS Topic for MyEventTopic - Created



JMSExceptionweblogic.jms.common.JMSException: Subscription MyEventTopic is in use




Thanks in advance.

   <<Less

Re: weblogic.jms.common.JMSException: Subscription - Topic is in use

Posted By:   anwar_sadat  
Posted On:   Tuesday, July 3, 2007 06:07 AM

Some more stack trace which might be useful



Adapter AL Manager started at Tue Apr 17 15:06:30 2007

Starting Adapter...

INFO: Trying to get BEA JMS queue Connection for t3://myserver.in:7963

INFO: BEA JMS queue Connection for t3://myserver.in:7963 Completed

INFO: Trying to get BEA JMS queue for MessageQueue

INFO: BEA JMS queue for MessageQueue Created

INFO: Trying to get BEA JMS queue for ReplyQueue

INFO: BEA JMS queue for ReplyQueue Created

INFO: Trying to get BEA JMS queue for ShutdownQueue

INFO: BEA JMS queue for ShutdownQueue Created

INFO: Trying to get BEA JMS topic Connection for t3://myserver.in:7963

INFO: BEA JMS topic Connection for t3://myserver.in:7963 Completed

INFO: Trying to get BEA JMS Topic for EventTopic

INFO: BEA JMS Topic for EventTopic Created

Adapter up and running

>
count = 0, total = 120

-----------------------------------------------------------------------


Adapter AL Manager started at Tue Apr 17 15:33:12 2007

Starting Adapter...

INFO: Trying to get BEA JMS queue Connection for t3://myserver.in:7963

INFO: BEA JMS queue Connection for t3://myserver.in:7963 Completed

INFO: Trying to get BEA JMS queue for MessageQueue

INFO: BEA JMS queue for MessageQueue Created

INFO: Trying to get BEA JMS queue for ReplyQueue

INFO: BEA JMS queue for ReplyQueue Created

INFO: Trying to get BEA JMS queue for ShutdownQueue

INFO: BEA JMS queue for ShutdownQueue Created

INFO: Trying to get BEA JMS topic Connection for t3://myserver.in:7963

INFO: BEA JMS topic Connection for t3://myserver.in:7963 Completed

INFO: Trying to get BEA JMS Topic for EventTopic

INFO: BEA JMS Topic for EventTopic Created

Adapter up and running

in PublisherManager publish(Object data,PublisherInfo mPublisherInfo) Exception

weblogic.jms.common.JMSException: java.io.IOException: JMS JDBC store, connection pool = , prefix = : flush failed

java.io.IOException: JMS JDBC store, connection pool = , prefix = : SQL exception

weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:Could not create pool connection. The DBMS driver exception was: Io exception: The Network Adapter could not establish the connection

at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(Ljava/lang/Exception;Ljava/lang/String;)V(JDBCUtil.java:203)

at weblogic.jdbc.pool.Driver.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;(Driver.java:161)

at weblogic.jms.store.JDBCIOStream.opendb()V(JDBCIOStream.java:2204)

at weblogic.jms.store.JDBCIOStream.flush()V(JDBCIOStream.java:777)

at weblogic.jms.store.JMSStore.execute(Lweblogic/kernel/ExecuteThread;)V(JMSStore.java:502)

at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)

at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)

at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)


at weblogic.jms.store.JDBCIOStream.throwIOException(Ljava/lang/String;Ljava/lang/Exception;)V(JDBCIOStream.java:498)

at weblogic.jms.store.JDBCIOStream.opendb()V(JDBCIOStream.java:2287)

at weblogic.jms.store.JDBCIOStream.flush()V(JDBCIOStream.java:777)

at weblogic.jms.store.JMSStore.execute(Lweblogic/kernel/ExecuteThread;)V(JMSStore.java:502)

at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)

at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)

at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)


at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)

at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)

at weblogic.jms.dispatcher.DispatcherImpl_815_WLStub.dispatchSyncTranFuture(Unknown Source)

at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:408)

at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:383)

at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)

at com.jmscommunicator.PublisherManager.publish(Unknown Source)

at com.jmscommunicator.JMSCommunicator.publish(Unknown Source)

at com.applayer.RequestProcessor.sendMessageOverMOM(Unknown Source)

at com.applayer.RequestProcessor.create(Unknown Source)

at com.applayer.RequestProcessor.run(Unknown Source)

at com.applayer.WorkerThread.run(Unknown Source)

Caused by: weblogic.jms.common.JMSException: java.io.IOException: JMS JDBC store, connection pool = , prefix = : flush failed
java.io.IOException: JMS JDBC store, connection pool = , prefix = : SQL exception

weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:Could not create pool connection. The DBMS driver exception was: Io exception: The Network Adapter could not establish the connection

at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(Ljava/lang/Exception;Ljava/lang/String;)V(JDBCUtil.java:203)

at weblogic.jdbc.pool.Driver.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;(Driver.java:161)

at weblogic.jms.store.JDBCIOStream.opendb()V(JDBCIOStream.java:2204)

at weblogic.jms.store.JDBCIOStream.flush()V(JDBCIOStream.java:777)

at weblogic.jms.store.JMSStore.execute(Lweblogic/kernel/ExecuteThread;)V(JMSStore.java:502)

at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)

at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)

at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)


at weblogic.jms.store.JDBCIOStream.throwIOException(Ljava/lang/String;Ljava/lang/Exception;)V(JDBCIOStream.java:498)

at weblogic.jms.store.JDBCIOStream.opendb()V(JDBCIOStream.java:2287)

at weblogic.jms.store.JDBCIOStream.flush()V(JDBCIOStream.java:777)

at weblogic.jms.store.JMSStore.execute(Lweblogic/kernel/ExecuteThread;)V(JMSStore.java:502)

at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)

at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)

at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)


at weblogic.jms.backend.BEMessageWriteListener.storeIOComplete(BEMessageWriteListener.java:104)

at weblogic.jms.store.StoreRequest.execute(StoreRequest.java:422)

at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java)

at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

at java.lang.Thread.startThreadFromVM(Unknown Source)

Caused by: java.io.IOException: JMS JDBC store, connection pool = , prefix = : flush failed
java.io.IOException: JMS JDBC store, connection pool = , prefix = : SQL exception

weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:Could not create pool connection. The DBMS driver exception was: Io exception: The Network Adapter could not establish the connection

at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(Ljava/lang/Exception;Ljava/lang/String;)V(JDBCUtil.java:203)

at weblogic.jdbc.pool.Driver.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;(Driver.java:161)

at weblogic.jms.store.JDBCIOStream.opendb()V(JDBCIOStream.java:2204)

at weblogic.jms.store.JDBCIOStream.flush()V(JDBCIOStream.java:777)

at weblogic.jms.store.JMSStore.execute(Lweblogic/kernel/ExecuteThread;)V(JMSStore.java:502)

at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)

at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)

at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)


at weblogic.jms.store.JDBCIOStream.throwIOException(Ljava/lang/String;Ljava/lang/Exception;)V(JDBCIOStream.java:498)

at weblogic.jms.store.JDBCIOStream.opendb()V(JDBCIOStream.java:2287)

at weblogic.jms.store.JDBCIOStream.flush()V(JDBCIOStream.java:777)

at weblogic.jms.store.JMSStore.execute(Lweblogic/kernel/ExecuteThread;)V(JMSStore.java:502)

at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)

at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)

at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)


at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:498)

at weblogic.jms.store.JDBCIOStream.flush(JDBCIOStream.java:809)

at weblogic.jms.store.JMSStore.execute(JMSStore.java:502)

... 3 more

>
INFO: Trying to get BEA JMS queue Connection for t3://myserver.in:7963

INFO: BEA JMS queue Connection for t3://myserver.in:7963 Completed

INFO: Trying to get BEA JMS queue for MessageQueue

INFO: BEA JMS queue for MessageQueue Created

INFO: Trying to get BEA JMS queue for ReplyQueue

INFO: BEA JMS queue for ReplyQueue Created

INFO: Trying to get BEA JMS queue for ShutdownQueue

INFO: BEA JMS queue for ShutdownQueue Created

INFO: Trying to get BEA JMS topic Connection for t3://myserver.in:7963

INFO: BEA JMS topic Connection for t3://myserver.in:7963Completed

INFO: Trying to get BEA JMS Topic for EventTopic

INFO: BEA JMS Topic for EventTopicCreated

INFO: Trying to get BEA JMS queue for MessageQueue

INFO: BEA JMS queue for MessageQueue Created

INFO: Trying to get BEA JMS queue for ReplyQueue

INFO: BEA JMS queue for ReplyQueue Created

INFO: Trying to get BEA JMS queue for ShutdownQueue

INFO: BEA JMS queue for ShutdownQueue Created

INFO: Trying to get BEA JMS Topic for EventTopic

INFO: BEA JMS Topic for EventTopic Created

JMSException - weblogic.jms.common.JMSException: Subscription EventTopic is in use
About | Sitemap | Contact