java.lang.SecurityException

**[Security:090398]**Invalid Subject: principals=[weblogic, Administrators, super_users]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web971

  • via mzan.com by Unknown author, 10 months ago
    **[Security:090398]**Invalid Subject: principals=[weblogic, Administrators, super_users]
  • [Security:090398]Invalid Subject: principals=[weblogic, Administrators, super_users]
  • via Oracle Community by Mohan Basavarajappa, 1 year ago
    [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
  • Stack trace

    • java.lang.SecurityException: **[Security:090398]**Invalid Subject: principals=[weblogic, Administrators, super_users] at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259) at weblogic.jms.frontend.FEConnectionFactoryImpl_1034_WLStub.connectionCreateRequest(Unknown Source) at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:224) at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285) at weblogic.jms.client.JMSConnectionFactory.createConnection(JMSConnectionFactory.java:191) at org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:184) at org.springframework.jms.listener.AbstractJmsListeningContainer.createSharedConnection(AbstractJmsListeningContainer.java:405) at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:390) at org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:885) at org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:861) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1012) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, super_users] at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:833) at weblogic.security.service.SecurityServiceManager.getSealedSubjectFromWire(SecurityServiceManager.java:522) at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:349) at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:953) at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:351) at weblogic.rmi.cluster.ClusterableServerRef.dispatch(ClusterableServerRef.java:243) at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1141) at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1023) at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:240) at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:888) at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:512) at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:330) at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:298) at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:950) at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:898) at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:215) at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:177) at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29) at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:43) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    3 more bugmates