Foo_1_EJB deployed on one server(S1) calls Foo_2_EJB on another server(S2).
(S1 and S2 is NOT simply two different domains running on the same server. It
is actually two different weblogic servers listening on different ports).
S2 gets a db-connection from a pool. When running a web-solution deployed on S2,
EVERYTHING works fine and has done so for several months.
But when I connect from S1 I get this error:
java.lang.SecurityException: Invalid Subject: principals=[someuser]
Via the home-interface-object S1 DOES get a reference to Foo_2_EJB deployed on
S2, but when I refer to the functionality on Foo_2_EJB (the functionality that
needs to use the db-connection) I get the exception mentioned above.
Foo_2_EJB DOES get myDataSource-object, but myDataSource.getConnection() fails,
and that's when I get the Exception.
!!!see stack trace below!!!
By the way: "someuser" HAS been created and works, all right.
Any kind af help is appreciated :-)
Cheers,
Michel
Start server side stack trace:
java.lang.SecurityException: Invalid Subject: principals=[someuser]
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:943)
at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:309)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End server side stack trace
Dejan