9 Replies Latest reply on Jul 26, 2011 10:35 AM by 750029

    WebLogic 10.3.2  managed server startup failed : ''31' could not be found'

    Jay user7322888
      Dears: I ran my managed server using script but failed , the weblogic version is 10.3.2 (11g R1) , on Solaris 10 sparc 64bit.:
      ports=( 7001 7003 7005 7007 )
      instances=( instance1 instance2 instance3 )
      adminip=192.168.11.174
      "startManagedWebLogic.sh ${instances[1]} http://$adminip:${ports[0]}"&

      Does anyone get jammed into this situation?
      -------------------------------------------------------------------------------------------

      The Managed Server instance2 is going to running

      .
      .
      JAVA Memory arguments: -Xms768m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=6 -XX:+DisableExplicitGC -XX:MaxPermSize=2048m
      .
      WLS Start Mode=Production
      .
      CLASSPATH=/wls11g/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/wls11g/jdk1.6.0_18/lib/tools.jar:/wls11g/utils/config/10.3/config-launch.jar:/wls11g/wlserver_10.3/server/lib/weblogic_sp.jar:/wls11g/wlserver_10.3/server/lib/weblogic.jar:/wls11g/modules/features/weblogic.server.modules_10.3.2.0.jar:/wls11g/wlserver_10.3/server/lib/webservices.jar:/wls11g/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/wls11g/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/wls11g/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/wls11g/wlserver_10.3/server/lib/xqrl.jar
      .
      PATH=/wls11g/wlserver_10.3/server/bin:/wls11g/modules/org.apache.ant_1.7.0/bin:/wls11g/jdk1.6.0_18/jre/bin:/wls11g/jdk1.6.0_18/bin:/wls11g/user_projects/domains/base_domain:/wls11g/user_projects/domains/base_domain/bin:/wls11g/wlserver_10.3/server/bin:/wls11g/user_projects/domains/base_domain:/wls11g/user_projects/domains/base_domain/bin:/wls11g/wlserver_10.3/server/bin:/usr/bin
      .
      ***************************************************
      * To start WebLogic Server, use a username and *
      * password assigned to an admin-level user. For *
      * server administration, use the WebLogic Server *
      * console at http://hostname:port/console *
      ***************************************************
      starting weblogic with Java version:
      -bash-3.00$ java version "1.6.0_18-ea"
      Java(TM) SE Runtime Environment (build 1.6.0_18-ea-b05)
      Java HotSpot(TM) 64-Bit Server VM (build 16.0-b12, mixed mode)
      Starting WLS with line:
      /wls11g/jdk1.6.0_18/bin/java -server -d64 -Xms768m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=6 -XX:+DisableExplicitGC -XX:MaxPermSize=2048m -Dweblogic.Name=instance2 -Djava.security.policy=/wls11g/wlserver_10.3/server/lib/weblogic.policy -da -Dplatform.home=/wls11g/wlserver_10.3 -Dwls.home=/wls11g/wlserver_10.3/server -Dweblogic.home=/wls11g/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=http://140.126.24.25:6001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/wls11g/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
      <Jan 20, 2010 6:02:46 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 16.0-b12 from Sun Microsystems Inc.>
      <Jan 20, 2010 6:02:49 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
      <Jan 20, 2010 6:03:00 PM CST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://140.126.24.25:6001.>
      <Jan 20, 2010 6:03:00 PM CST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
      <Jan 20, 2010 6:03:00 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
      <Jan 20, 2010 6:03:00 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
      <Jan 20, 2010 6:03:01 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
      <Jan 20, 2010 6:03:01 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log00026. Log messages will continue to be logged in /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log.>
      <Jan 20, 2010 6:03:01 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log is opened. All server side log events will be written to this file.>
      <Jan 20, 2010 6:03:16 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
      <Jan 20, 2010 6:03:19 PM CST> <Error> <Configuration Management> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://140.126.24.25:6001 during startup. Since bootstrap succeeded check that t3://140.126.24.25:6001 uniquely identifies the administration server.
      javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.]
      at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
      at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
      at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
      at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:430)
      at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
      Truncated. see log file for complete stacktrace

      Caused By: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
      at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
      at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:429)
      at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
      at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
      at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:426)
      Truncated. see log file for complete stacktrace
      >
      <Jan 20, 2010 6:03:19 PM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

      There are 1 nested errors:

      javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.]
      at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
      at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
      at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
      at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:430)
      at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
      at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:173)
      at weblogic.server.channels.RemoteChannelServiceImpl.registerForever(RemoteChannelServiceImpl.java:146)
      at weblogic.protocol.ConnectMonitorFactory.registerForever(ConnectMonitorFactory.java:88)
      at weblogic.management.provider.MSIService.registerForReconnectToAdminServer(MSIService.java:174)
      at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.start(CompatibilityMBeanServerService.java:154)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
      Caused by: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
      at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
      at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:429)
      at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
      at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
      at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:426)
      ... 9 more

      >
      <Jan 20, 2010 6:03:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
      <Jan 20, 2010 6:03:19 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
      <Jan 20, 2010 6:03:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

      -bash-3.00$

      Edited by: user7322888 on 2010/2/4 下午 11:41