[jboss-jira] [JBoss JIRA] Created: (JBAS-5242) NoSuchObjectException on Server Restart Using RMI Transport & Unified Invoker

[John Reynolds (JIRA)]

NoSuchObjectException on Server Restart Using RMI Transport & Unified Invoker
-----------------------------------------------------------------------------

                 Key: JBAS-5242
                 URL: http://jira.jboss.com/jira/browse/JBAS-5242
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.0.CR1
         Environment: Server Running Windows XP or Redhat - Swing Client on Windows XP
            Reporter: John Reynolds


Using a Swing client to connect to the JBoss server, configured with RMI Transport Connector and Unified Invoker, I receive the following StackTrace when, after successfully connecting to the server and executing a few EJB transactions, I shut the server down and then bring it back up. Upon attempting to do any further invocations, it appears cached information is causing the client to fail. 

------------- 
(rmi.RMIClientInvoker 272 ) java.rmi.NoSuchObjectException: no such object in table 
galaxy.framework.model.domain.services.util.SLCommunicationException: Error making invocation in RMI client invoker. 
at galaxy.framework.model.domain.services.util.ServiceLocator.authenticateUser(ServiceLocator.java:738) 
at galaxy.framework.model.domain.services.util.ServiceLocator.initializeWithLDAP(ServiceLocator.java:435) 
at galaxy.application.view.swing.presentation.util.ClientConnectionManager$1.run(ClientConnectionManager.java:51) 
Caused by: org.jboss.remoting.CannotConnectException: Error making invocation in RMI client invoker. 
at org.jboss.remoting.transport.rmi.RMIClientInvoker.transport(RMIClientInvoker.java:273) 
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) 
at org.jboss.remoting.Client.invoke(Client.java:1550) 
at org.jboss.remoting.Client.invoke(Client.java:530) 
at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:183) 
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) 
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) 
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61) 
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) 
at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:112) 
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) 
at $Proxy1.authenticateSwingUserWithLDAP(Unknown Source) 
at galaxy.framework.model.domain.services.util.ServiceLocator.authenticateUser(ServiceLocator.java:725) 
... 2 more 
Caused by: java.rmi.NoSuchObjectException: no such object in table 
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) 
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) 
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) 
at org.jboss.remoting.transport.rmi.RMIServerInvoker_Stub.transport(Unknown Source) 
at org.jboss.remoting.transport.rmi.RMIClientInvoker.transport(RMIClientInvoker.java:238) 
... 14 more 

------------ 

Seems potentially similar to this issue fixed in 4.0.5 in non-remoting-RMI code (see discussion thread): 
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116027 


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira