|
Home > Archive > WebSphere Application Server > March 2004 > Urgent: dumpNameSpace error on WAS 406
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Urgent: dumpNameSpace error on WAS 406
|
|
|
| All,
I was getting a "Could not find datasource: jdbc/MyDatasource" in my app
server's stdout log , so I tried to run the dumpNameSpace.sh script to see
if my datasource name was in the JNDI namespace. However, when I did so, I
got the following error. Please help!!!!!!
/opt/WebSphere/AppServer/bin >./dumpNameSpace.sh
Getting the initial context
ERROR: Could not get the initial context or unable to look up the starting
context. Exiting.
Exception received: javax.naming.CommunicationException: Caught
CORBA.COMM_FAILURE when resolving initial reference=WsnNameService [Root
exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No]
javax.naming.CommunicationException: Caught CORBA.COMM_FAILURE when
resolving initial reference=WsnNameService. Root exception is
org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No
at com.ibm.CORBA.iiop.HTTPConnection.send(HTTPConnection.java:447)
at com.ibm.CORBA.iiop.HTTPConnection.locate(HTTPConnection.java:679)
at com.ibm.CORBA.iiop.GIOPImpl.locate(GIOPImpl.java:197)
at
com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1098)
at
com.ibm.CORBA.iiop.InitialNamingClient.resolve(InitialNamingClient.java:372)
at
com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_references(InitialNam
ingClient.java:551)
at
com.ibm.CORBA.iiop.ORB.resolve_initial_references_remote(ORB.java:2014)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFact
ory.java:594)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactor
y.java:354)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCt
xFactory.java:229)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)
at com.ibm.ws.naming.util.WsnInitCtx.<init>(WsnInitCtx.java:79)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory
..java:137)
at
com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnIniti
alContextFactory.java:80)
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.ibm.websphere.naming.DumpNameSpace.getStartingContext(DumpNameSpace.java
:247)
at
com.ibm.websphere.naming.DumpNameSpace.main(DumpNameSpace.java:208)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
| |
| Ken Hygh 2004-03-30, 1:34 pm |
| prem wrote:
>All,
>
>I was getting a "Could not find datasource: jdbc/MyDatasource" in my app
>server's stdout log , so I tried to run the dumpNameSpace.sh script to see
>if my datasource name was in the JNDI namespace. However, when I did so, I
>got the following error. Please help!!!!!!
>
>/opt/WebSphere/AppServer/bin >./dumpNameSpace.sh
>
>Getting the initial context
>ERROR: Could not get the initial context or unable to look up the starting
>context. Exiting.
>Exception received: javax.naming.CommunicationException: Caught
>CORBA.COMM_FAILURE when resolving initial reference=WsnNameService [Root
>exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No]
>javax.naming.CommunicationException: Caught CORBA.COMM_FAILURE when
>resolving initial reference=WsnNameService. Root exception is
>org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No
> at com.ibm.CORBA.iiop.HTTPConnection.send(HTTPConnection.java:447)
>
>
[snip]
You probably aren't using the default port. dumpNameSpace takes a port
parameter.
Ken
|
|
|
|
|