Issues Migrating Custom UserManager from OC4J 9.0.4 to 10.1.3

(Doc ID 396650.1)

Last updated on DECEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version: 10.1.3
This problem can occur on any platform.

Symptoms

Various errors when migrating J2EE application from OC4J 9.0.4 to new version 10.1.3.0.0 on the
usage of a UserManager that was working without issues on the old version.

1) Initial warning message was

    06/10/12 11:04:25 Unable to register security provider MBean for Spider
    06/10/12 11:04:25 User Manager not of required type for this application

2) After changing some of the configuration got errors from user manager code

        06/10/18 13:40:43 2006-10-18|13:40:43|se.cambiosys.spider.SpiderException|1|
        java.lang.NullPointerException|SpiderException: DataService(0): java.lang.NullPointerException
        06/10/18 13:40:43 2006-10-18|13:40:43|se.cambiosys.spider.SpiderException|2|
        java.lang.NullPointerException|
        java.lang.NullPointerException~
        at se.cambiosys.spider.UserService.UserToolkit.isSpiderUser(UserToolkit.java:428)~
        at se.cambiosys.spider.UserService.UserToolkit.getCurrentUser(UserToolkit.java:154)~
        at se.cambiosys.spider.UserService.UserToolkit.getCurrentUser(UserToolkit.java:123)~
        at
    se.cambiosys.spider.DataService.VersionedObjectToolkit.create(VersionedObjectToolkit.java:408)~


3) Then got RMI connection rejected from the server

        Connecting ...
        javax.naming.NoPermissionException: Not allowed to look up UserService/UserManager, check the
        namespace-access tag setting in orion-application.xml for details
          at
    com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:110)
          at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:92)
          at
    com.evermind.server.rmi.RMIClientConnection.waitForJndiResponse(RMIClientConnection.java:326)
          at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:137)
          at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:249)
          at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:50)
          at javax.naming.InitialContext.lookup(Unknown Source)


4) And finally the RMI client throws errors that indicate some wrong implementation on the
UserManager

        java.lang.IllegalArgumentException: El rol especificado ya existe en el sistema.
          (in english "The specified role already exists in the system")
          at
    com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:110)
          at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
          at

com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
          at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
          at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
          atcom.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
          at __Proxy0.create(Unknown Source)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms