"[EMAIL PROTECTED]" wrote :
|
| What does the logged exception look like?
Well, the patch is out already so I'll have to fat-finger in what I have from a
hard copy. I suspect you'll actually need more than this, but here is the
first bit:
2005-02-13 14:28:54,660 TRACE [org.jboss.mq.Connection] DeleteDestination
dest=TOPIC.JMS_TT3 [EMAIL PROTECTED]:ID:8/50a5cd14262170cc7fd80d5d5edf8b36
rcvstate=STOPPED]
2005-02-13 14:28:54,660 TRACE [org.jboss.mq.TracingInterceptor] CALLED :
deleteTemporaryDestination
2005-02-13 14:28:54,660 TRACE [org.jboss.mq.server.TracingInterceptor] ARG :
TOPIC_JMS_TT3
2005-02-13 14:28:54,661 TRACE [org.jboss.mq.TracingInterceptor] EXCEPTION :
deleteTemporaryDestination:
javax.jms.InvalidDestinationException: That destination does not exist! null
at
org.jboss.mq.server.JMSDestinationManager.deleteTemporaryDestination(JMSDestinationManager.java:724)
at
org.jboss.mq.server.JMSServerInterceptorSupport.deleteTemporaryDestination(JMSServerInterceptorSupport.java:174)
at
org.jboss.mq.security.ServerSecurityInterceptor.deleteTemporaryDestination(ServerSecurityInterceptor.java:217)
at
org.jboss.mq.server.TracingInterceptor.deleteTemporaryDestination(TracingInterceptor.java:405)
at
org.jboss.mq.server.JMSServerInvoker.deleteTemporaryDestination(JMSServerInvoker.java:174)
at
org.jboss.mq.il.jvm.JVMServerIL.deleteTemporaryDestination(JVMServerIL.java:177)
at
org.jboss.mq.Connection.deleteTemporaryDestination(Connection.java:490)
at org.jboss.mq.SpyTemporaryTopic.delete(SpyTemporaryTopic.java:69)
at
org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.close(JmsSessionFactoryImpl.java:300)
anonymous wrote :
| What does your code look like for the deletes?
|
| Are you sure you are not trying to delete the temporary before
| you closed the consumer that was trying to receive from it?
Well, my SessionBean creates the conection and then the session, and passes the
session to a helper object (POJO). This object essentially does the following:
| TemporaryTopic replyTopic = null;
| TopicSubscriber replyReceiver = null;
| try {
| replyTopic = topicSession.createTemporaryTopic();
| replyReceiver = topicSession.createSubscriber(replyTopic);
|
| // Set replyTopic as the JMSReplyTo for the original message
| // and publish it to the main topic (code not shown)
|
| // Wait for the first reply
| Message replyMsg = replyReceiver.receive(timeout1);
| // Process first reply
|
| // Assuming first reply was ok, wait for the second reply
| replyMsg = replyReceiver.receive(timeout2);
| // Process second reply
|
| } catch (...) {
| } finally {
| try {
| if (replyReceiver != null) {
| replyreceiver.close();
| }
| if (replyTopic != null) {
| replyTopic.delete();
| }
| } catch (JMSException e) {
| // log, etc.
| throw e;
| }
| }
|
Once this method completes, we close the publisher (for the main topic) and
then close the session and finally the connection, all in my SLSB. Does this
seem reasonable?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866863#3866863
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866863
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
