Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

calling EJB on WL61 from an EJB on WL61

0 views
Skip to first unread message

Tor Mala

unread,
Apr 3, 2002, 10:13:43 AM4/3/02
to
I'm experiencing a problem.

I can connect over T3 to a server B from a regular java-application. When I
do the same from an EJB on server A I get an authentication-error:

Code used to create the InitialContext is:
-----------------------------------------
// Create the context
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
weblogic.jndi.WLInitialContextFactory.class.getName());
p.put(Context.PROVIDER_URL, "MY_URL");
p.put(Context.SECURITY_PRINCIPAL, "MY_USERNAME");
p.put(Context.SECURITY_CREDENTIALS, "MY_PASSWORD");
InitialContext ctx = new InitialContext(p); // throws an
AuthenticationException here when in EJB on server A
// Get remote object
MyHome home = (MyHome)ctx.lookup("MY_JNDI_NAME");
MyRemote remote = home.create();
// Call methods on remote object
remote.myMethod();
-----------------------------------------

Both server A and B are WL6.1 SP2 and they have the same system-password.
Any ideas why the code works nice from a normal javaprogram, but not from a
EJB running on Server A?

The calling EJB gets the following Exception:
javax.naming.AuthenticationException. Root exception is
java.lang.SecurityException: Authentication for user myuser denied in realm
weblogic
Start server side stack trace:
java.lang.SecurityException: Authentication for user myuser denied in realm
weblogic
at weblogic.security.acl.Realm.authenticate(Realm.java:212)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:119)
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:210)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:638)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace


Mala
--


Przemyslaw Rychlewski

unread,
Apr 4, 2002, 7:55:56 AM4/4/02
to
hi,

maybe a different realm configuration of servers A and B causes the problem.

regards,
przemek

Tor Mala schrieb:

Yeshwant

unread,
Apr 5, 2002, 7:21:20 PM4/5/02
to

This should work if both the servers have the same system password.
I have been able to get this to work .
can you set the Trans-attribute to NotSupported for all the methodsof the bean
and try ?
0 new messages