<Feb 4, 2003 11:45:48 AM PST> <Warning> <RJVM> <000519> <Unable to connect to
a
remote server on address 10.3.21.6 and port 7001 with protocol t3. The Except
ion is java.net.ConnectException: Operation timed out: connect>
javax.naming.CommunicationException. Root exception is java.net.ConnectExceptio
n: t3://10.3.21.6:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Operation timed out: connect; No available
ro
uter to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:173)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:262)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:323)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:221)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
60)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241
)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at jsp_servlet.__jndi._jspService(__jndi.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:401)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:5412)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:744)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3086)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
t3 is the protocol BEA uses for RMI.
You probably have a network device that is filtering the traffic on the
port (7001). You can verify this if you try to connect with a web
browser to the same port via HTTP (http://xxx:7001/console/).
Try setting the port of your server to one that is not filtered ( 80 or
8080 might be a good choice for an experiment) and see if it helps.
Regards,
Dejan
<ExecuteThread: '9' for queue: 'default'> <kernel identity> <> <080003> <RuntimeException
thrown by rmi server: com.ebal.LoginSupport_eufzwc_EOImpl.idString()
java.lang.SecurityException: Invalid Subject: principals=[clientuser]>
java.lang.SecurityException: Invalid Subject: principals=[clientuser]
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)
I didn't set any security when deploy the ejb. And I viewed the jndi policy for
the bean, it's all default to "everyone" group.
Why I got SecurityException?
Look at the procedure in this link:
http://edocs.bea.com/wls/docs70/adminguide/managetx.html#1050458 .
I'd guess that your two servers are in different domains and the above
link shows how to make the two domains accept the others' Subjects.
Dejan
Dejan
And that security context is actually the Subject of the currently
executing user. If you did not associate a security context yourself
then it's the anonymous user Subject, but there is one always.
And those Subjects are signed (validated) by the different WLS domains
with a different key, unless you define your own that makes them
"portable" from one domain to another.
Dejan