This exception has no message.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1409

  • via Terracotta by andrewm, 11 months ago
    This exception has no message.
  • via Terracotta by unimib, 11 months ago
    This exception has no message.
  • via Terracotta by lrohan, 2 weeks ago
    This exception has no message.
  • Stack trace

    • java.lang.reflect.UndeclaredThrowableException at at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke( at $Proxy155.onMessage(Unknown Source) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage( at org.jboss.jms.client.container.ClientConsumer.callOnMessageStatic( at org.jboss.jms.client.container.SessionAspect.handleRun( at at org.jboss.aop.joinpoint.MethodInvocation.invokeNext( at org.jboss.jms.client.container.ClosedInterceptor.invoke( at org.jboss.aop.advice.PerInstanceInterceptor.invoke( at org.jboss.aop.joinpoint.MethodInvocation.invokeNext( at at at at at at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( at java.util.concurrent.ThreadPoolExecutor$ at Caused by: org.jboss.aop.DispatcherConnectException: EJB container is not completely started, or is stopped. at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke( at org.jboss.aop.joinpoint.MethodInvocation.invokeNext( at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke( at org.jboss.aop.joinpoint.MethodInvocation.invokeNext( at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke( at org.jboss.aop.joinpoint.MethodInvocation.invokeNext( at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke( at org.jboss.aop.joinpoint.MethodInvocation.invokeNext( at org.jboss.ejb3.mdb.MessagingContainer.localInvoke( at ... 18 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.