Application Development Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Can't Start a Local Weblogic server.

1031354Aug 7 2013

I have been trying for over a week now to figure this out. I have found no information on this issue and I don't know enough about WebLogic to find out what is going on.

I have a local weblogic 10.3.5 server on my work laptop that I need to use to be able to debug in eclipse. The problem is when I try to start the server I get these odd errors, pasted below. I have no idea what the server is attempting to do when it gets this error. How I've gotten along so far, is I found a way to get around this, but only from the command line, which won't work in eclipse. If I open up oracle quickstart, create a new domain, have quickstart start the admin server on the new domain, the server starts up, then I kill the server in the same command prompt, and go to the first domain and start it, it starts. But if I just go straight to the main domain and try to start it I get the below errors. Does anyone know, or could point me in the right direction, on what could be causing this or what I need to do to fix it? Thanks.

<Aug 7, 2013 6:54:20 AM EDT> <Error> <JNDI> <BEA-050003> <Cannot create Initial Context. Reason: javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']

at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)

at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)

at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)

at weblogic.jndi.Environment.getContext(Environment.java:315)

at weblogic.jndi.Environment.getContext(Environment.java:285)

at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)

at javax.naming.InitialContext.init(InitialContext.java:223)

at javax.naming.InitialContext.<init>(InitialContext.java:197)

at weblogic.jndi.internal.ForeignJNDIManager.<init>(ForeignJNDIManager.java:45)

at weblogic.jndi.internal.ForeignJNDIManager.initialize(ForeignJNDIManager.java:53)

at weblogic.jndi.internal.ForeignJNDIManagerService.start(ForeignJNDIManagerService.java:36)

at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'

at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)

at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)

at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)

at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:316)

at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:205)

at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)

at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)

at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)

at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)

... 13 more

<Aug 7, 2013 6:54:22 AM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

java.io.IOException: Cannot bind to URL [weblogic.management.mbeanservers.runtime]: javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']

at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804)

at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417)

at weblogic.management.mbeanservers.internal.MBeanServerServiceBase.start(MBeanServerServiceBase.java:208)

at weblogic.management.mbeanservers.runtime.internal.RuntimeServerService.start(RuntimeServerService.java:172)

at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Caused by: javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']