Announcement Announcement Module
Collapse
No announcement yet.
Accessing Remote EJB 3 SLSB in JBoss 5.1.0 GA Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Accessing Remote EJB 3 SLSB in JBoss 5.1.0 GA

    Hi,

    I try to access an EJB3 component hosted in a JBoss 5.1.0GA app server. BTW I'm using the Mule 2.2.1 ESB for my client app on a separate VM. Here is a snapshot of my xml config:

    Code:
    		
    
    <jee:remote-slsb id="CommandServerEJB"
    			jndi-name="com.xxxxxxx.command.ejb.CommandServer"
    			business-interface="com.xxxxxx.command.ejb.CommandServerRemote">
    			<jee:environment>
    				java.naming.factory.initial=org.jboss.security.jndi.JndiLoginInitialContextFactory
    				java.naming.provider.url=jnp://localhost:1399
    				java.naming.security.principal=jboss
    				java.naming.security.credentials=jboss				
            	</jee:environment>
    		</jee:remote-slsb>
    An the following exception is generated when the EJB Component is accessed:

    Exception stack is:
    1. javax.naming.Reference.executeCommand(com.xxxxxxxx .util.command.Command) java.lang.NoSuchMethodException)
    java.lang.Class:1605 (null)
    2. No matching RMI stub method found for: public abstract void com.xxxxxxxx.command.ejb.CommandServerRemote.execu teCommand(com.fedextnc.util.command.Command) throws com.xxxxxxxx.util.command.CommandException,java.rm i.RemoteException; nested exception is java.lang.NoSuchMethodException: javax.naming.Reference.executeCommand(com.xxxxxxxx .util.command.Command)
    (org.springframework.remoting.RemoteProxyFailureEx ception)
    org.springframework.remoting.rmi.RmiClientIntercep torUtils:120 (null)
    The spring version is 2.5.6
    I try to debug the RmiClientInterceptorUtils and the stub I received is an instance of javax.naming.Reference. There used to be a resourceRef=true property on the jee:remote-slsb component but it's not there anymore...
    Any help would be greatly appreciated. Thanks,

  • #2
    Problem found

    The version on the client side weren't the right one..... After pointing to jbossall-client.5.1.0.GA the message disappear.

    Comment

    Working...
    X