This discussion is archived
2 Replies Latest reply: Feb 20, 2013 5:16 AM by 834645 RSS

Weblogic server not starting

834645 Newbie
Currently Being Moderated
All of a sudden my weblogic server is giving error while I am trying to run startWeblogic.cmd

The admin server log trace is :

D:\Middleware\SOASuite11g\user_projects\domains\SOAOSBDevDomain\servers\AdminServer\data\ldap\XACMLRoleMappermyrealmInit.initialized, will load full LDIFT.>
####<Jan 31, 2013 5:04:00 AM GMT> <Info> <Security> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608640170> <BEA-090074> <Initializing RoleMapper provider using LDIF template file D:\Middleware\SOASuite11g\user_projects\domains\SOAOSBDevDomain\security\XACMLRoleMapperInit.ldift.>
####<Jan 31, 2013 5:04:00 AM GMT> <Info> <Security> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608640216> <BEA-090075> <The RoleMapper provider has had its LDIF information loaded from: D:\Middleware\SOASuite11g\user_projects\domains\SOAOSBDevDomain\security\XACMLRoleMapperInit.ldift>
####<Jan 31, 2013 5:04:00 AM GMT> <Info> <Security> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608640794> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm myrealm.>
####<Jan 31, 2013 5:04:00 AM GMT> <Notice> <Security> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608640794> <BEA-090082> <Security initializing using security realm myrealm.>
####<Jan 31, 2013 5:04:01 AM GMT> <Error> <JNDI> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608641326> <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:792)
     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:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
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.findOrCreateInternal(RJVMFinder.java:200)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:165)
     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
>
####<Jan 31, 2013 5:04:01 AM GMT> <Info> <Server> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608641763> <BEA-002622> <The protocol "[snmp, https, t3, cluster-broadcast-secure, ldaps, cluster-broadcast, ldap, http, iiop, admin, t3s, iiops]" is now configured.>
####<Jan 31, 2013 5:04:01 AM GMT> <Info> <XML> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608641794> <BEA-130036> <Initializing XMLRegistry.>
####<Jan 31, 2013 5:04:01 AM GMT> <Info> <messaging.interception> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608641810> <BEA-400000> <Initializing message interception service>
####<Jan 31, 2013 5:04:03 AM GMT> <Info> <Store> <siebel-crm> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1359608643013> <BEA-280008> <Opening the persistent file store "_WLS_AdminServer" for recovery: directory=D:\Middleware\SOASuite11g\user_projects\domains\SOAOSBDevDomain\servers\AdminServer\data\store\default requestedWritePolicy="Direct-Write" fileLockingEnabled=true driver="wlfileio3".>


Please help. Its urgent

Edited by: 831642 on Feb 20, 2013 5:13 AM

Edited by: 831642 on Feb 20, 2013 5:20 AM

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points