java.net.ConnectException: t3://someip:7001: Bootstrap to: 'someip/someip:7001' over: 't3' got an error or timed out
Steve C
I'm having the following problem with WebLogic 7 running under Redhat: 7.2,
Linux Kernel: 2.4.7, Java: 1.3.1
Looks like weblogic was installed from wls7001_36_COMP_linux.jar
The WebLogic build has been stable since build (about a month ago). We've
been using it as our test server and deploying an EJB app to it without
problems, but this week it started throwing the following exception when
navigating to some of the apps JSPs. The EJB works fine when run locally on
the development PCs. I think this is a WebLogic configuration problem, but
am at a loss as to where to start "tweaking" . Any help will be gratefully
received.
Regards,
Steve
(I've had to replace the real ip for "someip" and also some of the debug
data values in the stack trace for privacy reasons)
2002.10.16 03:30:38 custcareServlet: Calling registration.getUsers:
1,90,null,null,null,null,cms_id_01,abc.co.uk,abc.co.uk,null,null
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ bootstrapping
through loopback ]
at weblogic.utils.Debug.assertion(Debug.java:84)
at
weblogic.rjvm.ConnectionManagerServer.handleIdentifyResponse(ConnectionManag
erServer.java:391)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:691)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:488)
at
weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:507)
at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:429)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
<16-Oct-02 15:30:38 BST> <Error> <socket> <000405> <Uncaught Throwable in
processSockets
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ bootstrapping
through loopback ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ bootstrapping
through loopback ]
at weblogic.utils.Debug.assertion(Debug.java:84)
at
weblogic.rjvm.ConnectionManagerServer.handleIdentifyResponse(ConnectionManag
erServer.java:391)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:691)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:488)
at
weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:507)
at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:429)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)>
2002-10-16 15:31:38,782 [ExecuteThread: '9' for queue: 'default'] ERROR
com.abc.registration.phase2.exception.RegistrationException -
NamingException in registrationBean.ejbActivate()
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://someip:7001: Bootstrap to:
'someip/someip:7001' over: 't3' got an error or timed out at
weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:173)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:262)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:324)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:222)
at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
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
com.abc.registration.phase2.util.ServiceLocator.<init>(ServiceLocator.java:5
0)
at
com.abc.registration.phase2.util.ServiceLocator.getInstance(ServiceLocator.j
ava:64)
at
com.abc.registration.master.RegistrationBean.ejbCreate(RegistrationBean.java
:854)
at
com.abc.registration.master.RegistrationBean_cdn3rr_Impl.ejbCreate(Registrat
ionBean_cdn3rr_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.jav
a:148)
at
weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:9
8)
at
weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:154)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:126)
at
weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java
:61)
at
com.abc.registration.master.RegistrationBean_cdn3rr_EOImpl.getUsers(Registra
tionBean_cdn3rr_EOImpl.java:1327)
at
com.abc.registration.servlets.CustCareServlet.doActionSearch(CustCareServlet
.java:718)
at
com.abc.registration.servlets.CustCareServlet.chooseRoute(CustCareServlet.ja
va:481)
at
com.abc.registration.servlets.CustCareServlet.doPost(CustCareServlet.java:25
1)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:945)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:332)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:242)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5360)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:721)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3043)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2468)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
2002.10.16 03:31:38 custcareServlet: registration.getUsers returns
exception: java.rmi.RemoteException: EJB Exception: ; nested exception is:
java.lang.NullPointerException
2002.10.16 03:31:38 custcareServlet: Forwarding to /UserSearch.jsp
2002.10.16 03:31:38 custcareServlet: ^^--doPost ends--^^
2002.10.16 03:30:38 custcareServlet: Calling registration.getUsers:
1,90,null,null,null,null,cms_id_01,abc.co.uk,abc.co.uk,null,null
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ bootstrapping
through loopback ]
at weblogic.utils.Debug.assertion(Debug.java:84)
at
weblogic.rjvm.ConnectionManagerServer.handleIdentifyResponse(ConnectionManag
erServer.java:391)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:691)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:488)
at
weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:507)
at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:429)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
<16-Oct-02 15:30:38 BST> <Error> <socket> <000405> <Uncaught Throwable in
processSockets
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ bootstrapping
through loopback ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ bootstrapping
through loopback ]
at weblogic.utils.Debug.assertion(Debug.java:84)
at
weblogic.rjvm.ConnectionManagerServer.handleIdentifyResponse(ConnectionManag
erServer.java:391)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:691)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:488)
at
weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:507)
at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:429)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)>
2002-10-16 15:31:38,782 [ExecuteThread: '9' for queue: 'default'] ERROR
com.abc.registration.phase2.exception.RegistrationException -
NamingException in RegistrationBean.ejbActivate()
Steve C
We have a properties file for the jndi service locator. I'd set the
properties file to the IP address of the server, rather than to localhost. I
don't see that this should have made a difference, except that I think our
systest machine has recently changed IP.
"Steve C" <scres...@smart421.com> wrote in message
news:3dae...@newsgroups.bea.com...