[jboss-user] [JBoss Seam] - Re: @Asynchronous / Dispatcher not bound
m_hess
do-not-reply at jboss.com
Mon Dec 11 11:27:22 EST 2006
Hmmm.... OK. So maybe anybody else also experienced this errormessage?
| [17:24:37] [admin1] [ERROR] [...erceptors.ExceptionInterceptor:370 ] >> redirecting to debug page
| javax.ejb.EJBTransactionRolledbackException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.core.dispatcher
| at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:93)
| at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
| at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:201)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| [...]
|
| Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.core.dispatcher
| at org.jboss.seam.Component.newInstance(Component.java:1724)
| at org.jboss.seam.Component.getInstance(Component.java:1627)
| at org.jboss.seam.Component.getInstance(Component.java:1594)
| at org.jboss.seam.Component.getInstance(Component.java:1573)
| at org.jboss.seam.Component.getInstance(Component.java:1568)
| at org.jboss.seam.core.Dispatcher.instance(Dispatcher.java:237)
| at org.jboss.seam.interceptors.AsynchronousInterceptor.invokeAsynchronouslyIfNecessary(AsynchronousInterceptor.java:24)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| [...]
|
| Caused by: javax.naming.NameNotFoundException: Dispatcher not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:626)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:588)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.jboss.seam.Component.instantiateSessionBean(Component.java:1029)
| at org.jboss.seam.Component.instantiate(Component.java:1015)
| at org.jboss.seam.Component.newInstance(Component.java:1720)
| ... 170 more
| [...]
|
The Dispatcher components gets installed on startup:
| [16:55:06] [] [INFO ] [...org.jboss.seam.Component :245 ] >> Component: org.jboss.seam.core.dispatcher, scope: STATELESS, type: STATELESS_SESSION_BEAN, class: org.jboss.seam.core.Dispatcher, JNDI: Dispatcher/local
And we do have the local interface annotated (not the implementing classes method).
Any ideas or insights?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992809#3992809
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992809
More information about the jboss-user
mailing list