Visibroker and Managed Server problem
Hi,
I have a webapp that connects to a Visibroker (3.4) server for getting some information.
When the application is deployed on the admin server itself everything runs fine. I'm not modifying any of the scripts for this.
But when I deploy the application on the managed server that are part of the cluster it's not working. It's giving me an exception that should go away if I put my vbjorb.jar in the endorsed folder. (that's how it worked in tomcat) but here in WLS if I do that the server's itself are not coming up. They are throwing an exception.
The exceptions are pasted below:
<b>(managed server's exception.)</b>
java.lang.VerifyError: class org.omg.PortableServer.AdapterActivatorPOA overrides final method .
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at com.inprise.vbroker.orb.ORB.adapterManager(ORB.java:939)
at com.inprise.vbroker.ds.DSUser.(DSUser.java:270)
at com.inprise.vbroker.ds.Init.init(Init.java:20)
at com.inprise.vbroker.orb.ORB.installServices(ORB.java:767)
at com.inprise.vbroker.orb.ORB.initialize(ORB.java:708)
at com.inprise.vbroker.orb.ORB.set_parameters(ORB.java:788)
at org.omg.CORBA.ORB.init(ORB.java:337)
at com.qwest.drp.vconsoles.ConsolesConstants.InitOrb_V(ConsolesConstants.java:79)
at com.qwest.drp.vconsoles.JobFactory.BindToJobFactoryServer(JobFactory.java:145)
at com.qwest.drp.vconsoles.JobFactory.GetCurrentJobs(JobFactory.java:54)
at com.qwest.med.portal.backend.bo.MonitoringBO.getDrpJobInfo(MonitoringBO.java:181)
at com.qwest.med.portal.backend.appService.ProdMonitoringService.getDrpJobInfo(ProdMonitoringService.java:83)
at com.qwest.med.portal.backend.POJOFacade.getDrpJobInfo(POJOFacade.java:448)
at com.qwest.med.portal.web.service.MedPortalServiceImpl.getDrpJobInfo(MedPortalServiceImpl.java:219)
at com.qwest.med.portal.web.prodMon.ProdMonFwdAction.execute(ProdMonFwdAction.java:95)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at org.displaytag.filter.ResponseOverrideFilter.doFilter(ResponseOverrideFilter.java:125)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
<b>(all server exception)</b>
The WebLogic Server did not start up properly.
java.lang.ExceptionInInitializerError
at weblogic.iiop.Utils.<clinit>(Utils.java:128)
at weblogic.corba.utils.RepositoryId.getIDFromValueType(RepositoryId.java:149)
at weblogic.corba.utils.RepositoryId.<init>(RepositoryId.java:95)
at weblogic.corba.utils.ClassInfo.<init>(ClassInfo.java:78)
at weblogic.corba.utils.ClassInfo.putClassInfo(ClassInfo.java:281)
at weblogic.corba.utils.ClassInfo.<clinit>(ClassInfo.java:60)
at weblogic.iiop.IIOPService.resumeClient(IIOPService.java:205)
at weblogic.iiop.IIOPService.initialize(IIOPService.java:145)
at weblogic.t3.srvr.SubsystemManager.initialize(SubsystemManager.java:118)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:895)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
Caused by: java.lang.RuntimeException: Unable to load javax.rmi.CORBA.Util implementation weblogic.iiop.UtilDelegateImpl
at javax.rmi.CORBA.Util.<clinit>(Util.java:29)
... 13 more
Any help would be appreciated.
Kind Rgds,
Amarendra.
Amarendra Mishra <> writes:
3.4 does not support JDK 1.4 (I assume you are using WLS 8.1?) You
need to use a later version of Visi. Alternatively don't use the
client ORB at all but use the WLS ORB.
andy
Hi,
I have a webapp that connects to a Visibroker (3.4) server for getting some information.
When the application is deployed on the admin server itself everything runs fine. I'm not modifying any of the scripts for this.
But when I deploy the application on the managed server that are part of the cluster it's not working. It's giving me an exception that should go away if I put my vbjorb.jar in the endorsed folder. (that's how it worked in tomcat) but here in WLS if I do that the server's itself are not coming up. They are throwing an exception.
The exceptions are pasted below:
<b>(managed server's exception.)</b>
java.lang.VerifyError: class org.omg.PortableServer.AdapterActivatorPOA overrides final method .
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at com.inprise.vbroker.orb.ORB.adapterManager(ORB.java:939)
at com.inprise.vbroker.ds.DSUser.(DSUser.java:270)
at com.inprise.vbroker.ds.Init.init(Init.java:20)
at com.inprise.vbroker.orb.ORB.installServices(ORB.java:767)
at com.inprise.vbroker.orb.ORB.initialize(ORB.java:708)
at com.inprise.vbroker.orb.ORB.set_parameters(ORB.java:788)
at org.omg.CORBA.ORB.init(ORB.java:337)
at com.qwest.drp.vconsoles.ConsolesConstants.InitOrb_V(ConsolesConstants.java:79)
at com.qwest.drp.vconsoles.JobFactory.BindToJobFactoryServer(JobFactory.java:145)
at com.qwest.drp.vconsoles.JobFactory.GetCurrentJobs(JobFactory.java:54)
at com.qwest.med.portal.backend.bo.MonitoringBO.getDrpJobInfo(MonitoringBO.java:181)
at com.qwest.med.portal.backend.appService.ProdMonitoringService.getDrpJobInfo(ProdMonitoringService.java:83)
at com.qwest.med.portal.backend.POJOFacade.getDrpJobInfo(POJOFacade.java:448)
at com.qwest.med.portal.web.service.MedPortalServiceImpl.getDrpJobInfo(MedPortalServiceImpl.java:219)
at com.qwest.med.portal.web.prodMon.ProdMonFwdAction.execute(ProdMonFwdAction.java:95)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at org.displaytag.filter.ResponseOverrideFilter.doFilter(ResponseOverrideFilter.java:125)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
<b>(all server exception)</b>
The WebLogic Server did not start up properly.
java.lang.ExceptionInInitializerError
at weblogic.iiop.Utils.<clinit>(Utils.java:128)
at weblogic.corba.utils.RepositoryId.getIDFromValueType(RepositoryId.java:149)
at weblogic.corba.utils.RepositoryId.<init>(RepositoryId.java:95)
at weblogic.corba.utils.ClassInfo.<init>(ClassInfo.java:78)
at weblogic.corba.utils.ClassInfo.putClassInfo(ClassInfo.java:281)
at weblogic.corba.utils.ClassInfo.<clinit>(ClassInfo.java:60)
at weblogic.iiop.IIOPService.resumeClient(IIOPService.java:205)
at weblogic.iiop.IIOPService.initialize(IIOPService.java:145)
at weblogic.t3.srvr.SubsystemManager.initialize(SubsystemManager.java:118)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:895)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
Caused by: java.lang.RuntimeException: Unable to load javax.rmi.CORBA.Util implementation weblogic.iiop.UtilDelegateImpl
at javax.rmi.CORBA.Util.<clinit>(Util.java:29)
... 13 more
Any help would be appreciated.
Kind Rgds,
Amarendra.--
Similar Messages
-
Problem creating a domain w/ one Admin Server and Managed Server
I went through the config wizard (Weblogic 10.2) and set up a domain w/ 1 Admin Server and Managed Server. When I start the Admin server I get the following error:
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Store> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:105)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:60)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <JMS> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-141197> <The deployment of pfJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:198)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Deployer> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328461> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1633)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1809)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:609)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>I am using the default db the installation uses which is PointBase. I am not using any specific db, JDBC Datasource/Connection pool Configuration.
Just to try something different, I tried creating a domain w/ one Admin and Managed Server which uses a Cluster and I did not get any errors. From what I read, a cluster is not necessary but not sure why it works without errors w/ a cluster.
I will try commenting out the datasource from the config and see what happens and will let you know. -
[Fwd: Starting Managed server problem ......]
Forwarding to the security news group...
-------- Original Message --------
Subject: Starting Managed server problem ......
Date: 1 Jun 2004 23:02:53 -0700
From: Sameer <barsatkiraat2001>
Newsgroups: weblogic.developer.interest.management
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and
installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one
unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager
and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
<BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check
the peer to determine why it rejected the certificate chain (trusted CA
configuration, hostname verification). SSL debug tracing may be required
to determine the exact reason the certificate was rejected.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
<Certificate chain received from PortalQA - 10.12.10.94 failed hostname
verification check. Certificate contained AdminQA but check expected
PortalQA>
The WebLogic Server did not start up properly.
Exception raised:
'weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
<The node manager is unable to monitor this server. Could not create an
SSL connection to the node manager. Reason :
[Security:090504]Certificate chain received from PortalQA - 10.12.10.94
failed hostname verification check. Certificate contained AdminQA but
check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due to
faulty SSL configuration, this server is unable to establish a
connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server:
weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer.Hello Satya/All,
I'm also experiencing the exact problem you are facing. It would be great if
somebody could help in this regard at the earliest.
Thanks, senthil
Satya Ghattu <[email protected]> wrote:
Forwarding to the security news group...
-------- Original Message --------
Subject: Starting Managed server problem ......
Date: 1 Jun 2004 23:02:53 -0700
From: Sameer <barsatkiraat2001>
Newsgroups: weblogic.developer.interest.management
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and
installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one
unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager
and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
<BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check
the peer to determine why it rejected the certificate chain (trusted
CA
configuration, hostname verification). SSL debug tracing may be required
to determine the exact reason the certificate was rejected.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
<Certificate chain received from PortalQA - 10.12.10.94 failed hostname
verification check. Certificate contained AdminQA but check expected
PortalQA>
The WebLogic Server did not start up properly.
Exception raised:
'weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
<The node manager is unable to monitor this server. Could not create
an
SSL connection to the node manager. Reason :
[Security:090504]Certificate chain received from PortalQA - 10.12.10.94
failed hostname verification check. Certificate contained AdminQA but
check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due
to
faulty SSL configuration, this server is unable to establish a
connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server:
weblogic.management.configuration.ConfigurationException: Due to faulty
SSL configuration, this server is unable to establish a connection to
the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer. -
Starting Managed server problem ......
Hi All,
I need you guy's help in this regard, that I am using solaris 8 and installed Weblogic8.1 Server.
My Scenario is;
Have configured Admin Server and Managed server with nodemanager on one unix machine.
So, what am facing the problem;
I am not able to get run Managed server after starting the nodemanager and admin server, getting the error in nodemanager logs that is :
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482> <BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
And in Admin Server logs it's saying;
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504> <Certificate chain received from PortalQA - 10.12.10.94 failed hostname verification check. Certificate contained AdminQA but check expected PortalQA>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : [Security:090504]Certificate chain received from PortalQA - 10.12.10.94 failed hostname verification check. Certificate contained AdminQA but check expected PortalQA>
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
<Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
If some one can help me, I do appreciate in all due respect.
Sameer.Hello,
NodeManager requires proper SSL configuration. Are you sure you are using the right certificates?
Try running AS with following option
-Dweblogic.security.SSL.ignoreHostnameVerification=true
Ali -
Different service packs in admin server and managed server
Hi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack traceHi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace -
Hi,
I did create Admin server and Managed server on the same host. I have set Managed server (Name, Machine, Listen Address, Listen port enabled, Listen port, SSL listen port enebled, SSL listen port and java compiler) with these parameters. and i ran Admin server and Node manager (Admin server, node manager, managed server all on same host). When i was trying to run managed server from Admin server console the following error occured. Hwt is the solution for this. I am doing it in development mode
error is
<May 2, 2006 1:38:26 PM CDT> <Info> <NodeManager@*.*:5555> <Starting Server testDomain::managedServer1 ...>
<May 2, 2006 1:38:28 PM CDT> <Info> <NodeManager@*.*:5555> <Server testDomain::managedServer1 started, process id = 1,480>
<May 2, 2006 1:38:28 PM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
<May 2, 2006 1:38:29 PM CDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://10.8.85.103:7001 to check if there exists a running admin server at this URL.>
<May 2, 2006 1:38:29 PM CDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<May 2, 2006 1:38:29 PM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<May 2, 2006 1:38:29 PM CDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://10.8.85.103:7001 to retrieve the initial configuration.>
<May 2, 2006 1:38:31 PM CDT> <Notice> <Log Management> <BEA-170019> <The server log file D:\apps\bea\weblogic81\common\nodemanager\managedServer1\managedServer1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
java.lang.NoClassDefFoundError: com/bea/wsrp/util/debug/Debug
at com.bea.wsrp.security.WSRPIdentityAsserterProviderImpl.<clinit>()V(WSRPIdentityAsserterProviderImpl.java:45)
at jrockit.vm.Reflect$IClass.runClinit(I)V(Unknown Source)
at jrockit.vm.Reflect$IClass.ensureInitialized(Ljava.lang.Class;)V(Unknown Source)
at java.lang.Class.newInstanceCached(I)Ljava.lang.Object;(Unknown Source)
at java.lang.Class.newInstance(I)Ljava.lang.Object;(Unknown Source)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.createSecurityProvider(Lweblogic.management.security.ProviderMBean;Lweblogic.security.service.Auditor;)Lweblogic.security.spi.SecurityProvider;(SecurityServiceManagerDelegateImpl.java:232)
at weblogic.security.service.SecurityServiceManager.createSecurityProvider(Lweblogic.management.security.ProviderMBean;Lweblogic.security.service.Auditor;)Lweblogic.security.spi.SecurityProvider;(SecurityServiceManager.java:957)
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:152)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
Reason: com/bea/wsrp/util/debug/Debug
***************************************************************************Hi,
I'm also having the same problem with a clean installation of 8.1 SP3. If I start the managed server manually using startManagerServer.cmd, it starts up fine.
Does anyone have any idea what is causing this?
Thanks,
Jim -
Where to increase Java Heap settings for Admin and Managed Server.
Hello Experts
I am having issue with increasing the JVM memory arguments for the Admin and Managed Servers. I have tried in a couple of places to increase the memory arguments (Xms and Xmx to 1024m)but its not taking effect. When I start the Admin Server and Managed server , I do not see the increased Heap settings. Here is what I see -
"Starting WLS with line : /oracle/app/bi/Oracle_BI1/jdk/java -server - Xms256m -Xmx512m -XX:MaxPermSize=512m"
I have the following memory arguments in the setDomainEnv.sh located in <DOMAIN_HOME>/bin
XMS_SUN_64BIT ="2048"
export XMS_SUN_64BIT
XMX_SUN_64BIT="2048"
export XMX_SUN_64BIT
Looks like this did not work , so I added an entry in the setOBIDomainEnv.sh file hoping to increase the Java memory , but that does not work either. Below is from setOBIDomainEnv.sh file -
Really, trying to understand where/how the JVM settings are controlled from. Please guide me.
Appreciate your time.
RakeshUnder setobidomainenv.sh you will also find the admin server tag's so you need to increase the jvm parameters in there too. Depending upon your java vendor and bit version(Sun/Oracle/IBM/HP and 32-bit vs 64-bit ) So change accordingly
eg:
if server group is not obi then we can assume that it is Admin Server
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
# -UseSSE42Intrinsics required for server running EM
if [ "${JAVA_USE_64BIT}" = "true" ] ; then
# Admin Server memory args for 64-bit Sun JVM
SERVER_MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:-UseSSE42Intrinsics"
export SERVER_MEM_ARGS
similarly in setdomain.sh you will find the args as below:
XMX_SUN_64BIT="512"
export XMX_SUN_64BIT
XMS_SUN_64BIT="256"
export XMS_SUN_64BIT
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
WLS_MEM_ARGS_64BIT="-Xms256m -Xmx512m"
export WLS_MEM_ARGS_64BIT
WLS_MEM_ARGS_32BIT="-Xms256m -Xmx512m"
export WLS_MEM_ARGS_32BIT
after setting them just execute them ./setdomain.sh and ./setobidomainenv.sh and then try to start the admin and managed servers and see the process running with the updated values. -
WLS Admin and managed server startup issue
Hi ,
In one of WLS Domain both the Admin Server and Managed Server startup is just hanging at the below mentioned point :
<Security> <BEA-090082> <Security initializing using security realm myrealm.>
After this there are no error messages or logs being generated and the server start up is not proceeding .
Only message shown a while after this is :
Warning : domain runtime mbean server has not been found after trying for 600 seconds
Please provide some inputs on how to troubleshoot this issue .
Checked the AdminServer.log and there are no errors reported there as well .
Some more data from AdminServer.log :
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448845368> <BEA-090516> <The Authenticator provider has preexisting LDAP data.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448845632> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846193> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846208> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846433> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm myrealm.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846433> <BEA-090082> <Security initializing using security realm myrealm.>
Thanks
Srinath
Edited by: Srinath Menon on May 8, 2012 9:36 AMHi Ashish ,
Thanks for the inputs.
Tried the same steps as mentioned but the issue still remains like that .
Posting the thread dump collected for AdminServer:
===== FULL THREAD DUMP ===============
Tue May 8 10:04:58 2012
Oracle JRockit(R) R28.1.3-11-141760-1.6.0_24-20110301-1430-linux-ia32
"Main Thread" id=1 idx=0x4 tid=9341 prio=5 alive, waiting, native_blocked
-- Waiting for notification on: weblogic/t3/srvr/SubsystemRequest@0x9f81d3c0[fat lock]
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/t3/srvr/SubsystemRequest.rendezvouz(SubsystemRequest.java:100)
^-- Lock released while waiting: weblogic/t3/srvr/SubsystemRequest@0x9f81d3c0[fat lock]
at weblogic/t3/srvr/SubsystemRequest.action(SubsystemRequest.java:81)
at weblogic/t3/srvr/SubsystemRequest.start(SubsystemRequest.java:51)
at weblogic/t3/srvr/ServerServicesManager.startService(ServerServicesManager.java:459)
at weblogic/t3/srvr/ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
^-- Holding lock: java/lang/Class@0x9fa95598[biased lock]
at weblogic/t3/srvr/T3Srvr.initializeStandby(T3Srvr.java:879)
at weblogic/t3/srvr/T3Srvr.startup(T3Srvr.java:566)
at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:467)
at weblogic/Server.main(Server.java:71)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"(Signal Handler)" id=2 idx=0x8 tid=9342 prio=5 alive, native_blocked, daemon
at <unknown>(???.c)@0xb7fe9410
at sigiSignalHandlerThread+135(signalhandler.c:131)@0xb7ec2fd8
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(OC Main Thread)" id=3 idx=0xc tid=9343 prio=5 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeWait+71(nativelock.c:721)@0xb7e79008
at ocMainThread+663(gcthreads.c:581)@0xb7d8a098
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(GC Worker Thread 1)" id=? idx=0x10 tid=9344 prio=5 alive, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
at eventWaitNoTransition+32(event.c:62)@0xb7d6bc31
at mmGCWorkerThread+134(gcthreads.c:797)@0xb7d89d67
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(GC Worker Thread 2)" id=? idx=0x14 tid=9345 prio=5 alive, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
at eventWaitNoTransition+32(event.c:62)@0xb7d6bc31
at mmGCWorkerThread+134(gcthreads.c:797)@0xb7d89d67
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(Code Generation Thread 1)" id=4 idx=0x18 tid=9348 prio=5 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeWait+71(nativelock.c:721)@0xb7e79008
at cg_thread+380(compilerqueue.c:203)@0xb7d4be5d
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(Code Optimization Thread 1)" id=5 idx=0x1c tid=9349 prio=5 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeWait+71(nativelock.c:721)@0xb7e79008
at cg_thread+380(compilerqueue.c:203)@0xb7d4be5d
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(VM Periodic Task)" id=6 idx=0x20 tid=9350 prio=10 alive, native_blocked, daemon
at <unknown>(???.c)@0xb7fe9410
at block_for_safepoint+106(safepoint.c:34)@0xb7ebad5b
at eventTimedWait+239(event.c:83)@0xb7d6bd30
at periodic_task_thread+627(periodictask.c:367)@0xb7e90dd4
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"Finalizer" id=7 idx=0x24 tid=9351 prio=8 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeWait+71(nativelock.c:721)@0xb7e79008
at RJNI_jrockit_memory_Finalizer_waitForFinalizees+211(finalhandles.c:1007)@0xb7d751f4
at jrockit/memory/Finalizer.waitForFinalizees(J[Ljava/lang/Object;)I(Native Method)
at jrockit/memory/Finalizer.access$700(Finalizer.java:12)
at jrockit/memory/Finalizer$4.run(Finalizer.java:189)
at java/lang/Thread.run(Thread.java:662)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Reference Handler" id=8 idx=0x28 tid=9352 prio=10 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeUnlockAndWait+71(nativelock.c:686)@0xb7e790a8
at RJNI_java_lang_ref_Reference_waitForActivatedQueue+38(semiref.c:342)@0xb7ebd9b7
at java/lang/ref/Reference.waitForActivatedQueue(J)Ljava/lang/ref/Reference;(Native Method)
at java/lang/ref/Reference.access$100(Reference.java:11)
at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:82)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"(Sensor Event Thread)" id=9 idx=0x2c tid=9353 prio=5 alive, native_blocked, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
at eventTimedWait+138(event.c:56)@0xb7d6bccb
at eventWait+32(event.c:50)@0xb7d6bd81
at sensor_event_loop+37(sensor.c:68)@0xb7ebfda6
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"VM JFR Buffer Thread" id=10 idx=0x30 tid=9354 prio=5 alive, in native, daemon
at <unknown>(???.c)@0xb7fe9410
at bufferthread+2135(vmjfr.c:1008)@0xb71744b8
at run_agent_thread+128(jvmtithreads.c:524)@0xb7e1f361
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"Timer-0" id=13 idx=0x34 tid=9358 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: java/util/TaskQueue@0x9f9fc350[fat lock]
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at java/util/TimerThread.mainLoop(Timer.java:483)
^-- Lock released while waiting: java/util/TaskQueue@0x9f9fc350[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Timer-1" id=14 idx=0x38 tid=9363 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: java/util/TaskQueue@0xa20ee240[fat lock]
at <unknown>(???.c)@0xb7fe9410
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/util/TimerThread.mainLoop(Timer.java:509)
^-- Lock released while waiting: java/util/TaskQueue@0xa20ee240[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=15 idx=0x3c tid=9364 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: netscape/ldap/LDAPResponseListener@0x9724f0c8[fat lock]
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at netscape/ldap/LDAPMessageQueue.waitForMessage(LDAPMessageQueue.java:200)
^-- Lock released while waiting: netscape/ldap/LDAPResponseListener@0x9724f0c8[recursive]
at netscape/ldap/LDAPMessageQueue.waitFirstMessage(LDAPMessageQueue.java:101)
^-- Lock released while waiting: netscape/ldap/LDAPResponseListener@0x9724f0c8[fat lock]
at netscape/ldap/LDAPConnection.sendRequest(LDAPConnection.java:1796)
^-- Holding lock: netscape/ldap/LDAPConnection@0x9721f310[biased lock]
at netscape/ldap/LDAPConnection.simpleBind(LDAPConnection.java:1763)
at netscape/ldap/LDAPConnection.authenticate(LDAPConnection.java:1264)
at netscape/ldap/LDAPConnection.authenticate(LDAPConnection.java:1273)
at netscape/ldap/LDAPConnection.bind(LDAPConnection.java:1562)
at weblogic/security/providers/authentication/LDAPAtnDelegate$LDAPFactory.newInstance(LDAPAtnDelegate.java:4134)
at weblogic/security/utils/Pool.newInstance(Pool.java:37)
at weblogic/security/utils/Pool.getInstance(Pool.java:33)
at weblogic/security/providers/authentication/LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3478)
at weblogic/security/providers/authentication/LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3470)
at weblogic/security/providers/authentication/LDAPAtnDelegate.authenticate(LDAPAtnDelegate.java:3522)
at weblogic/security/providers/authentication/LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:227)
at com/bea/common/security/internal/service/LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)
at jrockit/vm/AccessController.doPrivileged(AccessController.java:268)
at com/bea/common/security/internal/service/LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java/lang/reflect/Method.invoke(Method.java:597)
at javax/security/auth/login/LoginContext.invoke(LoginContext.java:769)
at javax/security/auth/login/LoginContext.access$000(LoginContext.java:186)
at javax/security/auth/login/LoginContext$4.run(LoginContext.java:683)
at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)
at jrockit/vm/AccessController.doPrivileged(AccessController.java:268)
at javax/security/auth/login/LoginContext.invokePriv(LoginContext.java:680)
at javax/security/auth/login/LoginContext.login(LoginContext.java:579)
at com/bea/common/security/internal/service/JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java/lang/reflect/Method.invoke(Method.java:597)
at com/bea/common/security/internal/utils/Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at $Proxy28.login(Ljava/lang/String;Ljavax/security/auth/callback/CallbackHandler;Lweblogic/security/service/ContextHandler;)Lcom/bea/common/security/service/Identity;(Unknown Source)
at weblogic/security/service/internal/WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
at com/bea/common/security/internal/service/JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java/lang/reflect/Method.invoke(Method.java:597)
at com/bea/common/security/internal/utils/Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at $Proxy46.authenticate(Ljavax/security/auth/callback/CallbackHandler;Lweblogic/security/service/ContextHandler;)Lcom/bea/common/security/service/Identity;(Unknown Source)
at weblogic/security/service/WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
at weblogic/security/service/PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:348)
at weblogic/security/service/CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
at weblogic/security/service/CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic/security/service/SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic/security/SecurityService.start(SecurityService.java:141)
at weblogic/t3/srvr/SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:207)
at weblogic/work/ExecuteThread.run(ExecuteThread.java:176)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"JFR request timer" id=16 idx=0x40 tid=9365 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: java/util/TaskQueue@0xa2049280[fat lock]
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at java/util/TimerThread.mainLoop(Timer.java:483)
^-- Lock released while waiting: java/util/TaskQueue@0xa2049280[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"weblogic.time.TimeEventGenerator" id=18 idx=0x44 tid=9366 prio=9 alive, waiting, native_blocked, daemon
-- Waiting for notification on: weblogic/time/common/internal/TimeTable@0xa2089c70[fat lock]
at <unknown>(???.c)@0xb7fe9410
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
^-- Lock released while waiting: weblogic/time/common/internal/TimeTable@0xa2089c70[fat lock]
at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)
at java/lang/Thread.run(Thread.java:662)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"JMAPI event thread" id=19 idx=0x48 tid=9367 prio=5 alive, in native, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+526(nativelock.c:614)@0xb7e78b3f
at nlMonitorWaitInner+79(nativelock.c:1112)@0xb7e78df0
at nlMonitorWaitNoTransition+38(nativelock.c:1132)@0xb7e78e47
at nativeRawMonitorWait+78(rawmonitor.c:161)@0xb7ea8caf
at jvmti_RawMonitorWait+111(jvmtirawmonitors.c:95)@0xb7e1b420
at threadProc+291(jmapi.c:305)@0x90452bd4
at run_agent_thread+128(jvmtithreads.c:524)@0xb7e1f361
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"weblogic.timers.TimerThread" id=20 idx=0x4c tid=9368 prio=9 alive, waiting, native_blocked, daemon
-- Waiting for notification on: weblogic/timers/internal/TimerThread@0xa203dbf0[fat lock]
at <unknown>(???.c)@0xb7fe9410
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:262)
^-- Lock released while waiting: weblogic/timers/internal/TimerThread@0xa203dbf0[fat lock]
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace -
How to setup WebLogic Admin Server and Managed Server
Hi,
I working to setup a Weblogic admin and managed server but fail.
May i know the correct steps to setup the system ?
Tx.TX. I will proceed to upload more logs here later.
Anyway I notice that after i follow the guide to setup the admin and managed server, I only able to access the web apps on admin server. I can not access web apps for managed server.
I setup the admin server using port 7001 and managed server using port 7003 based on oracle guide.
I found weird here. when I browse to http://adminserver:7001/apps, it works. But when i browse to http://managedserver:7003/apps it does not work.
But funny thing is when i browse to http://adminserver:7003/apps, it works.
I confuse that which configuration I have done is incorrect and have this result???
besides that I notice that in the nodemanager setting...the listening address is set to localhost and it works. If i configure it to IP address, it will give me errors.
Edited by: Wilson78 on Dec 22, 2008 12:29 PM -
Communication protocol between Admin Server and Managed Server
Hello - I am hoping someone can help me here to understand the communication protocols used in my setup.
Here is my understanding of the protocol that are used between each component.
End User <--->HTTPS<--->LoadBalancer Device<--->HTTPS<--->Web Server<---->HTTPS<--->WebLogic Server(Managed Server)<--->LDAP/JDBC<-->Data tier components
AdminServer<--->T3<--->Managed Server i.e. The communication protocol between Admin Server and Managed server is T3
The communication protocol between Managed Servers running in one cluster on two seperate machine is What?
Thank you.Hello, interesting question.
In the documentation " [cluster multicast communication|http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001] " don't specify the used protocol to pack the information for example in a session replication.
Although in a session replication all objects must be serializable i don't think rmi protocol is used.
I hope some expert give us some light in this issue :-)
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001 -
Gateway server and Management server in SCOM 2012
What are the main Different between Gateway server and Management server in SCOM 2012?
I have referred this , is there anything ?
http://blogs.technet.com/b/momteam/archive/2008/02/19/10-reasons-to-use-a-gateway-server.aspx1) Management server can write data , gathered from agent, directly into operations manager database. Gateway server should forward data, collected from managed agent to management server.
2) In a unturst environment for example workgroup or untrust domain, and you do not want to deploy a certificate to every monitored agent, you should deploy gateway server rather than managment server.
Roger -
Move SCOM agent between gateway server and management server ?
Dear all,
IN SCOM 2012 R2 is it possible to move SCOM agent between gateway server and management server ? I mean if one agent is reporting to Gateway server , in case if i want to shutdown that Gateway server , can i move to another Management server and
Vice versa ?
Thanks,
SengoHi,
http://blogs.catapultsystems.com/cfuller/archive/2012/06/05/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr.aspx
and links at the bottom of
the article -
Admin Server and Managed server startup problem
Hi,
My weblogic server version is 11g and OS is Linux.
When i am trying to start the admin server a frer i created the domain i am getting following exceptions in the server log and server is shutting down.
FPR6 4008000000000000 (f: 0.000000, d: 3.000000e+00)
FPR7 4010000000000000 (f: 0.000000, d: 4.000000e+00)
FPR8 006f007300690078 (f: 6881400.000000, d: 1.379624e-306)
FPR9 0053006f0063006b (f: 6488171.000000, d: 4.228017e-307)
FPR10 00650074004d0075 (f: 5046389.000000, d: 9.346098e-307)
FPR11 0078006500720024 (f: 7471140.000000, d: 2.136208e-306)
FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR13 4068000000000000 (f: 0.000000, d: 1.920000e+02)
FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so
Module_base_address=0800000000003000
Target=2_40_20090409_033254_BHdSMr (AIX 5.3)
CPU=ppc64 (4 logical CPUs) (0x220000000 RAM)
- Stack Backtrace -
/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so:0x000046F4 [0x00003000 +0x000016F4]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005F7088 [0x005AF000 +0x00048088]
/usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB8228 [0x00FAB000 +0x0000D228]
/usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB884C [0x00FAB000 +0x0000D84C]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EDE08 [0x005AF000 +0x0003EE08]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF600 [0x005AF000 +0x00040600]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF3A8 [0x005AF000 +0x000403A8]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EC1A0 [0x005AF000 +0x0003D1A0]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB5B4 [0x005AF000 +0x0000C5B4]
/usr/java6_64/jre/lib/ppc64/default/libj9prt24.so:0x0064C21C [0x00649000 +0x0000321C]
/usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB4D0 [0x005AF000 +0x0000C4D0]
/usr/java6_64/jre/lib/ppc64/default/libj9thr24.so:0x006375F0 [0x00635000 +0x000025F0]
/usr/lib/libpthreads.a:0x005084F0 [0x00505000 +0x000034F0]
0x00000000
JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
JVMDUMP007I JVM Requesting System dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp'
JVMDUMP010I System dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp
JVMDUMP007I JVM Requesting Snap dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc'
UTE105: Error writing header to tracefile: /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
JVMDUMP010I Snap dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
JVMDUMP007I JVM Requesting Java dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt'
JVMDUMP012E Error in Java dump: /usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt
JVMDUMP013I Processed dump event "gpf", detail "".
After adding "<native-io-enabled>false</native-io-enabled>" in cofig.xml as shown below , i am able to start the admin server.
<server>
<name>AdminServer</name>
<native-io-enabled>false</native-io-enabled>
<listen-port>9595</listen-port>
<listen-address>10.10.15.16</listen-address>
</server>
i did the same thing for managed servers to start the server.
My Question is:
Are we missing any configurations/settings while creating domain?
Is there any other option to start the server without adding <native-io-enabled>false</native-io-enabled>?
Regards,
NagaHi,
my managed server heap size properties are
-XX:PermSize=256m -XX:MaxPermSize=256m -Xms256M -Xmx512M
But the error with Admin server also and we are not providing any heap size properties to admin server. Becuase while creating the domain, i haven't got any
option to set the heap size for Admin server. Am i required to set heap size properties in Admin server by following this path "Summary of Servers >AdminServer->Server start->"Arguements"?
Sorry, i am not able to find activity.log. Can you please tell me the location where i can find acivity.log. If i am not wrong, are you taling about serverOut.log? If that is serverOut.log, please tell me which log you require? is it admin server or managed server? -
Starting Admin and Managed Server on Same Machine
Has anyone come across a method of running both their admin server and managed
servers as a Service and on the same machine. As you can see, when the OS comes
up both Services for the servers will be started. I can put in a dependency on
the managed server saying that the admin server needs to be started but that doesn't
guarantee that admin server will be ready for "prime time."
I have seen somewhere in a support message something about a "depend" and "delay"
flag for the beasvc.exe program but the one I'm using doesn't seem to support
this.
Here is my setup:
Windows 2000 Pro
Weblogic Server 6.1 SP1
Any assistance is appreciated,
RichJohn Hufnagle wrote:
> Is it possible to run cluster admin server and one of the managed servers on the
> same machine...(just preserving machine resources for in-house testing).
As Kumar said, it is possible to run the admin server and one (or more) managed servers
on the same machine.
>
>
> If the admin listens on 7001/7002 can I just set up the managed server to 7003/7004
> or will I also run into problems with the multicast address?
Since the admin server is not part of the cluster, it is perfectly fine to use a
different set of ports for the managed servers as long as all servers in the same
cluster use the same ports...
Hope this helps,
Robert
-
Race condition between admin and managed server?
When I start my managed server, my admin server gets the following complaint
in its log file:
Jun 20, 2001 4:39:37 PM PDT Critical Log Management Unable to
contact managed server - rat5, at 172.16.1.26:7027
. Domain
logfile will not contain messages from this server.
java.lang.IllegalArgumentException: Invalid user name or password
at
weblogic.management.logging.DomainLogHandler.getMBeanHome(DomainLogHandler.j
ava:281)
at
weblogic.management.logging.DomainLogHandler.subscribeToServer(DomainLogHand
ler.java:243)
at
weblogic.management.logging.DomainLogHandler.registerToMe(DomainLogHandler.j
ava:183)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:562)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
48)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBean
ServerImpl_WLSkel.java:382)
at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at
weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
java:118)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
7)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
This happens while my managed server is still booting. It isn't listening on
port 7027 until a few seconds later. In the managed server rat5's log file
is
Jun 20, 2001 4:39:58 PM PDT Notice WebLogicServer WebLogic
Server started
Jun 20, 2001 4:39:58 PM PDT Notice WebLogicServer ListenThread
listening on port 7027
which is 21 seconds after the message in the admin log file. What do I have
to do to have the admin server wait until the managed server is up before
contacting it? Am I assessing the problem correctly?nope
a server can be either Admin or Managed, there is no such thing as a Admin+Managed server.
A domain expects you to specify which instance is an Admin, in config.xml you find
<admin-server-name>AdminServer</admin-server-name>
But this is not a problem for you, to all effects a domain without any managed servers and with only 1 Admin is a perfectly legal environment,
you can deploy your applications to the Admin and be happy.
Actually this is a common setup for Development environments.
Of course in production you want to set up a proper environment with cluster etc....
Maybe you are looking for
-
I'd love to buy Lightroom but I can't cause I'm now living in Australia but I create my account when I was living in Belgium so it says that I can't buy with this account cause I'm not in Belgium. How can I change my country??
-
I installed the Progress OpenEdge ODBC driver for 32 bit database on my win7 workstation -- I used odbcad32.exe located at C:\Windows\SysWOW64 to configure the driver for 32 bit applications -- per the screen Shots here and I am able to connect to th
-
Bluetooth streaming issues iOS 8.1.2
I have been seeing issues with Bluetooth audio streaming on my iPhone 5c, when connected to Harman/Kardon Soundsticks III BT. Initially I thought it was an issue with the speakers, but changed my mind when my friend's Nexus 4 was able to stream audio
-
Several messages popped up on screen while I was on the internet using Safari yesterday. They look to me to be some sort of trick to get me to download a program or just to sell me something useless. The Safari logo looks authentic, but the grammar i
-
Dear Sir or Madam: This is a fundamental requirement needed by us. I am running SAP Business One version 2005 Patch Level 39 When we do the delivery of a particular consignment we right click the delivery and choose the packaging option. On the packa