[jboss-dev-forums] [Deployers on JBoss (Deployers/JBoss)] - Re: HOWTO: remove a deployment context that is in error?

adrian@jboss.org do-not-reply at jboss.com
Tue Dec 4 12:08:17 EST 2007


I just found one broken test org.jboss.test.mdb.test.MDBUnitTestCase.

JBoss Messaging is throwing all sorts of errors, but during teardown this leads
to

  |   <testcase classname="org.jboss.test.mdb.test.MDBUnitTestCase$1" name="unknown" time="0.0010">
  |     <error message="Cannot find durable subscription with name DurableSubscriberExample to unsubscribe" type="javax.jms.InvalidDestinationException">javax.jms.InvalidD
  | estinationException: Cannot find durable subscription with name DurableSubscriberExample to unsubscribe
  |         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.unsubscribe(ServerSessionEndpoint.java:812)
  |         at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$unsubscribe$aop(SessionAdvised.java:135)
  |         at org.jboss.jms.server.endpoint.advised.SessionAdvised$unsubscribe_8775578479443985821.invokeNext(SessionAdvised$unsubscribe_8775578479443985821.java)
  |         at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
  |         at org.jboss.jms.server.endpoint.advised.SessionAdvised$unsubscribe_8775578479443985821.invokeNext(SessionAdvised$unsubscribe_8775578479443985821.java)
  |         at org.jboss.jms.server.endpoint.advised.SessionAdvised.unsubscribe(SessionAdvised.java)
  |         at org.jboss.jms.wireformat.SessionUnsubscribeRequest.serverInvoke(SessionUnsubscribeRequest.java:74)
  |         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
  |         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:771)
  |         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
  |         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
  |         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
  |         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
  |         at org.jboss.remoting.Client.invoke(Client.java:1634)
  |         at org.jboss.remoting.Client.invoke(Client.java:548)
  |         at org.jboss.remoting.Client.invoke(Client.java:536)
  |         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:187)
  |         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:158)
  |         at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$unsubscribe$aop(ClientSessionDelegate.java:413)
  |         at org.jboss.jms.client.delegate.ClientSessionDelegate$unsubscribe_8775578479443985821.invokeNext(ClientSessionDelegate$unsubscribe_8775578479443985821.java)
  |         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
  |         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
  |         at org.jboss.jms.client.delegate.ClientSessionDelegate$unsubscribe_8775578479443985821.invokeNext(ClientSessionDelegate$unsubscribe_8775578479443985821.java)
  |         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
  |         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
  |         at org.jboss.jms.client.delegate.ClientSessionDelegate$unsubscribe_8775578479443985821.invokeNext(ClientSessionDelegate$unsubscribe_8775578479443985821.java)
  |         at org.jboss.jms.client.delegate.ClientSessionDelegate.unsubscribe(ClientSessionDelegate.java)
  |         at org.jboss.jms.client.JBossSession.unsubscribe(JBossSession.java:377)
  |         at org.jboss.test.mdb.test.MDBUnitTestCase$1.tearDown(MDBUnitTestCase.java:309)
  | 

and the test queues/topics were not getting undeployed.

I'm fixing it. So previous errors in the teardown don't stop other things
getting undeployed.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110263#4110263

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110263



More information about the jboss-dev-forums mailing list