[
https://jira.jboss.org/jira/browse/EJBTHREE-1834?page=com.atlassian.jira....
]
Jaizon F. Lubaton resolved EJBTHREE-1834.
-----------------------------------------
Resolution: Done
hi this problem is really not jboss4.2.3 bug it was only in my local an ejb3 jar file was
statically deployed in $JBOSS_HOME/server/default/lib. The ejb3 proxy that i created was
updated used by clients, but jboss reads the static and un updated ejb3 SLSB. and the
interface and ejb3 bean are not synchronized.
Deleting the ejb3custom.jar file in $JBOSS_HOME/server/default/lib resolves the problem
and the updated ejb3custom.jar is copied to $JBOSS_HOME/server/default/deploy instead. the
ejb proxy and bean are now synchronized. Thank!
java.lang.RuntimeException: Could not resolve beanClass method from
proxy call at
org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:274)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-1834
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1834
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Affects Versions: AS 4.2.3.GA
Environment: OS:Windows XP Pro, JDK1.6, JBoss4.2.3GA,CygWin
Reporter: Jaizon F. Lubaton
Priority: Minor
When i added a new ejb3 Stateless Session Bean method. Then access that method from a
java client it throws this RuntimeException.
Stack Trace:
Exception in thread "main" java.lang.RuntimeException: Could not resolve
beanClass method from proxy call
at
org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:274)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
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.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
at $Proxy0.findCCInfoByOid(Unknown Source)
at com.va2.client.CleanUpCC.cleanCCInfoTable(CleanUpCC.java:49)
at com.va2.client.CleanUpCC.main(CleanUpCC.java:24)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
I was able to resolve this temporarily :
1.)By uninstalling the entire jboss4.2.3GA
2.)Re-installation Jboss4.2.3Ga it again,
3.) then re-deploy the new ejb3 and client
4.) works ok but i dont want to reinstall everytime i will add a new ejb3 stateless
session bean method
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira