Weblogic Admin and Managed Server start using boot.properties and LDAP Acc.
Hello - Can any one please tell me if Weblogic 10.3.x can be started using boot.properties file and by using a user account from the External LDAP (OID) server?
I have configured the Weblogic server and have added a LDAP authenticator.
The Group in OID is mapped to the Admin role in Weblogic so that the user can start and stop the server.
LDAP users can successfully authenticate and access WLS console.
We would like to remove Default Authenticator (Embeded LDAP) from the list of available providers for our security releam.
Thank you.
Tested and got it worked.
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. -
Weblogic deployment ( admin and managed server)
I have one AdminServer and One ManageServer running on the same IP Address with
different ports,
AdminServer and ManagedServer is coming up without any errors, I able to access
the index.jsp using the following URLs
http://hostname:7001/index.jsp (Admin Server)
http://hostname:8001/index.jsp (Managed Server)
my index.jsp I have several other hperlinks ( say contacts, help etc)
Once my servers ( admin and managed ) are started successfully, I'm able to browse
thru my application using the first URL.
but if I accessed the application using the second URL the index.jsp is coming
from port no (8001), which I observed thru the access.log and if I click any other
links(contacts, help) in the index.jsp, it is access the jsps from (7001) instead
of 8001.
I think in my Jsp I'm using a wrong mechanism to read the URL, what is the proper
way to read the correct URL?
Please help me to sort out this issueTested and got it worked.
-
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 -
How to use boot.properties to bypass username and password entry in WLST while connecting to server?
I'm currently writing a script that starts managed servers through WLST and I want it to avoid having the user enter their username and password similar to how startManagedWebLogic.sh does when a boot.properties file exists in the security directory of the server.
Currently, the way my script is set up is that it starts up WLST and enters the connect command, where it requests the username and password. The admin server URL is pulled from a config file used for the script.
Does anyone know how to supply the boot.properties file into WLST to have it automatically use the values in there? I do not want to have to save the values in plain text, nor do I want to have to create a new file to store them if it isn't necessary. I've read this thread weblogic.system.BootIdentityFile not working with WLST and tried copying boot.properties to domain home but didn't have any luck and still had to enter username and password. I have also tried looking into how startManagedWebLogic.sh pulls the values from the boot.properties but was unable to clearly identify how this is done. Any help would be much appreciated.
Thanks,
BrianExamples are presented here: Middleware Snippets: Starting and Stopping a Java EE Environment when using WebLogic
The examples use the Node Manager and Admin Server to start the managed server. To start the AdminServer nmStart is used. Note that boot.properties (in ${DOMAIN_HOME}/servers/${ADMIN_SERVER_NAME}/security) must exist in order to start a server with nmStart.
Next you can use, for example, the ServerLifeCycleRuntimeMBean to start the managed server (in this case the Node Manager and the Admin Server will make sure a boot.properties and startup.properties are propagated to the right directory ${DOMAIN_HOME}/servers/${SERVER_NAME}/data/nodemanager.
When the Admin Server is not available you can also use nmStart for the managed server. In this case you have to create boot.properties and startup.properties yourself by using nmGenBootStartupProps and copy them to the ${DOMAIN_HOME}/servers/${SERVER_NAME}/data/nodemanager directory. -
Weblogic 8.1 managed server unable to contact Admin server
I have a strange issue here.
I have admin server on Linux Machine A
Managed server on Linux Machine B.
When i try to start managed server on Machine B, i get the following error.
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150001]An error occurred while connecting to the admin server to bootstrap through URL: http://MachineA:7100/wl_management_internal2/Bootstrap, user: system
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readFully(ObjectInputStream.java:2571)
at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:1990)
The error suggests that managed server on machine B, is unable to contact Admin server on Machine A.
But i know for sure that Admin server is running on that port 7100 for sure.
It has been for the last 3 years.
To see if Machine B and Machine A have network issues, i did telnet.
From Machine B: i typed the following
telnet MachineA 7100
Connected to MachineA.
Escape character is '^]'
The above telnet command tells us that no network issues exist.
After a few tries, the managed server contacts to admin server and comes up.
This is not a one time thing.
I saw this behavior many times.
How should i resolve this?
Edited by: gvamsius on Feb 12, 2009 1:23 PMEvery thing is configured fine.
Nothing wrong with Configuration.
This domain has been running for the past 3 years.
Recently, i found something interesting in admin server logs, when i try to start the managed servers.
I realized there will be some amount of hand shake that happens during managed server startup, when it tries to communicate with admin server.
Here is the log snippet when managed server A contacts Admin server and starts up successfully.
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server A.>
####<Mar 10, 2009 12:11:46 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> <*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Here is the log snippet when managed server B contacts Admin server and does not start.
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server B.>
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server B.>
####<Mar 10, 2009 12:07:08 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server B.>
The difference as you can see here is that managed server starts up only when Admin Server does the following
<*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Does any one knows why Admin server would not send the above bootstrap configuation all the times for the managed servers? -
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 -
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.... -
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 -
WebLogic 9.2 Managed Server Is not starting
I have WebLogic 9.2 Application Server installed on Solaris Box and have deployed some ear and war files.
If I try to start the managed server its getting the following exception leading to FORCE_SHUTDOWN of the server.
Please help me if any one know the solution for this.
The Exception is
<Jan 5, 2009 4:46:12 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Ve
rsion 1.5.0_10-b03 from Sun Microsystems Inc.>
java.io.IOException: Error while downloading files from admin server. Undelying error is : null
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:7
1)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandl
erManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doDownload(ConfigDataUpdate.java:75)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.downloadFiles(RuntimeAccessDeploymentR
eceiverService.java:892)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateFiles(RuntimeAccessDeploymentRec
eiverService.java:851)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleRegistrationResponse(RuntimeAcce
ssDeploymentReceiverService.java:706)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.registerHandler(RuntimeAccessDeploymen
tReceiverService.java:677)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.start(RuntimeAccessDeploymentReceiverS
ervice.java:169)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:67)
<Jan 5, 2009 4:46:19 AM CST> <Error> <Management> <BEA-141196> <The managed server could not update the configuration files du
ring the registration with the deployment service. The update failed due to an exception:
weblogic.management.DeploymentException: Exception occured while downloading files
at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doDownload(ConfigDataUpdate.java:83)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.downloadFiles(RuntimeAccessDeploymentR
eceiverService.java:892)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateFiles(RuntimeAccessDeploymentRec
eiverService.java:851)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleRegistrationResponse(RuntimeAcce
ssDeploymentReceiverService.java:706)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.registerHandler(RuntimeAccessDeploymen
tReceiverService.java:677)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.start(RuntimeAccessDeploymentReceiverS
ervice.java:169)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:67)
java.io.IOException: Error while downloading files from admin server. Undelying error is : null
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:7
1)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandl
erManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doDownload(ConfigDataUpdate.java:75)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.downloadFiles(RuntimeAccessDeploymentR
eceiverService.java:892)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateFiles(RuntimeAccessDeploymentRec
eiverService.java:851)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleRegistrationResponse(RuntimeAcce
ssDeploymentReceiverService.java:706)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.registerHandler(RuntimeAccessDeploymen
tReceiverService.java:677)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.start(RuntimeAccessDeploymentReceiverS
ervice.java:169)
Thanks
Shailesh
Edited by: user6488619 on Jan 5, 2009 6:48 PMI'd say it's time to file a support case. Go to [https://support.bea.com] for this. You'll have to register if you haven't before. Note that this portal is going away at the end of this month.
-
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 -
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. -
I installed windows 7 using Boot camp, Then i wanted to install the support software using boot camp and it always stops at 50% i tried installing the software using internet it always gives me error when i start installing it on windows, What to do?
What is the error? Are you following the Bootcamp instructions? Where on the "internet" are you trying to install from? Did you try downloading from here http://www.apple.com/support/bootcamp/downloads/?
-
Weblogic Installation gets managed server of old installation
Hi. In my CentOS I had a weblogic 10.3.3.0 with three managed servers, then I unistalled it, delete the folder of installation manually for the files that the uninstaller didn't erase and then I installed again weblogic (jdevstudio11113install.bin) with new managed servers and when I want to start them up it tells me that it doesn't exist that the only ones that exist are the old ones I had in the previous installation. So I assume they are in a hidden file that I had to remove or update with new managed servers, which sounds strange because that should be deleted during uninstall process. Anyway any hint would be highly appreciated. Greetings.
From what I understand about your problem you have a domain - Admin server running on one physical machine and Managed server running on another physical machine, when stopping the Managed server its getting hung at suspending state, which in turn is causing Admin server slow down in response or hang.
Please confirm on this how are you stopping and starting your managed server
make sure that you do not use localhost when creating domains which spread across more than one physical machine.
Make sure that your Adminserver & Managed server have address as hostname's of physical server instead of Localhost
You should be starting / stopping Managed server something like this
startManagedWeblogic.sh -url t3://AdminserverHostName:PortNo <servername>
stopManagedWeblogic.sh -url t3://AdminserverHostName:PortNo <servername>
Let me know if you still have the problem.
Weblogic Consultant -
i am a final cut pro user and i recently started using adobe premiere pro. for anyone firmiliar with fcp, there are interesting ways of doing introductions on it and im wondering if anyone could tell me if premiere pro has preset introductions i can use.
Singenu wrote:
I tought about looking in Monitor Activity to see what happens...
Well, when I start working (should I say try to work with FCPX, activity monitor in the %processor column for FCPX jumps rapidly over 100% and reaches more than 200% ??? What the **** is that ?
200% or more is not strange. Remember that your mac has 4 cores (you say it's 3 months old, so I assume it is a new model), so 200% amounts to using 2 of these 4 cores to the max.
Regarding the question of creating a new admin user: while it sits in the same system, it may help if the problem is caused by some user-specific preferences or settings. Not likely in your case, since you seem to have reinstalled from scratch, but still it is worth a try. It takes 5 minutes and may help pinpoint the problem.
Maybe you are looking for
-
My music is all in a folder in D drive and the folder is called I tunes Music. When I open the I Tunes program it gives me the option to go to library and then to add files. I want to add the entire folder as there are too many individual files(son
-
How to upload image to the progrogram...
I am trying to upload the image to the function module but it says the "sunset.jpg" is feild unkonwn it is not defined by the data... and when i am passing this image stuff at the runtime... it gives me the memory dum.. would you like to help me... i
-
Adobe flash player update will not install and Ican not run and video on computer from internet expl
Internet explorer asks to upgrade flashplayer and it will not install,now I have no streaming video .
-
Okay, I have a macbook running 10.5.8 with a Matshita DVD drive. There are 2 accounts on this macbook. The primary user of this macbook told me that the DVD drive is not working. Any CD she puts in the drive tells her that it's an invalid disc and ej
-
I'm trying to figure out how I to get a Mac running OS X 10.9, with iCloud Keychain enabled, to *not* automatically connect to WiFi, even if the WiFi radio is turned on and a known network is reachable. The lack of a simple 'disconnect' feature in OS