Thursday, 9 June 2016

nested exception is: java.rmi.ConnectException: This RJVM has already been shutdown

INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
<Jun 9, 2016 11:52:48 PM PDT> <Warning> <oracle.jbo.uicli.mom.JUApplicationDefImpl> <BEA-000000> <The definition at oracle.webcenter.webcenterapp.bindings.DataBindings.cpx, uses a pagemap pattern match that hides other cpx files.>
oracle.bpm.client.common.BPMServiceClientException: javax.naming.NamingException [Root exception is java.rmi.UnexpectedException: Marshalling: ; nested exception is:
        java.rmi.ConnectException: This RJVM has already been shutdown 4882431698259664306S:admvhn:[7001,-1,-1,-1,-1,-1,-1]:soadomain:AdminServer]
        at oracle.bpm.client.BPMServiceClientFactory.getBPMUserAuthenticationService(BPMServiceClientFactory.java:250)
        at oracle.bpm.web.security.AuthenticationUtil.initBPMContextInSession(AuthenticationUtil.java:117)
        at oracle.bpm.web.security.LoginBean.initSSOSession(LoginBean.java:105)
        at oracle.bpm.web.security.AuthenticationUtil.authenticateModule(AuthenticationUtil.java:206)
        at oracle.bpm.web.security.faces.AuthenticationPhaseListener.authenticate(AuthenticationPhaseListener.java:73)
        at oracle.bpm.web.security.faces.AuthenticationPhaseListener.authenticatePhase(AuthenticationPhaseListener.java:63)
        at oracle.bpm.web.security.faces.AuthenticationPhaseListener.afterPhase(AuthenticationPhaseListener.java:54)
        at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:520)
        at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:207)
        at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     
Solution:

Check the DNS names resolution and AdminServer listen address.
If you have enabled a cross domain trust then AdminServer listen address should not be same

Repalace the Listen Address with IP address for Admin and SOA server.    

2 comments:

  1. Hi Manoj,

    It was good to see your article. We are facing the same issue in our production environment at certain times during this time stuck thread comes and impacts critically. We have given admin server listen address as hostname in dns server. Do you want me to give ip there. Please advice.
    Thanks
    Srinivas

    ReplyDelete
    Replies
    1. Hi Srinivas,
      I was facing this issue while setting up new environment, In our case we have SOA integrated with webcenter portal ( Process Space) in a cross domain and the admin server listen address for SOA and Portal doamin was same.

      Delete