Weblogic 8.1 managed server shuttdown problem
Hi Friends,
When we log in to Admin console and selecting servers in the left pane and right clicking a server instance and selecting start/stop server, it shows
start this server
resume this server
graceful shutdown of this server
force shutdown of this server
The problem is graceful shutdown of this server and force shutdown of this server links are not highliting for a perticular managed server and they are highlighting all remaining servers.
that means we are unable to shutdown the server from console. we are doing from command line.
can please respond where the problem is?
thanks for advance friends.
weblogic-admin
Hi,
I have been watching responses on this issue (that I have encountered too). I use IE6.0 and this does not happen always. I have seen it happen twice where the Graceful Shutdown and Forced Shutdown links are not highlighted for one managed server whereas for others it is highlighted. The only option then to shutdown/restart this is via the CLI. Please note that other times, these links are high-lighted for the same managed server that did not have these options high-lighted.
So I would like to know when and why this would happen?
Thanks.
Jay
Similar Messages
-
Manage Server Start Problem (weblogic.store.io.jdbc.JDBCStoreException)
I have a problem, when i start manage server.
Could you please help me about this problem?
Thanks
Orhan YENER
<Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "p13nJMSPersistenceStore" failed to open table "P13N_MESSAGING_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "p13nJMSPersistenceStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
weblogic.store.io.jdbc.JDBCStoreException: open failed
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSPersistenceStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Warning> <Store> <BEA-280076> <Database table "PF_PROLIFERATION_WLStore" for store "pfProliferationJMSStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102728280]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:57 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "pfProliferationJMSStore" in this server is not the owner of database table "PF_PROLIFERATION_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102748300]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=3276936988962983628:timestamp=1340102737578]".>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "pfProliferationJMSStore" failed to open table "PF_PROLIFERATION_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
weblogic.store.io.jdbc.JDBCStoreException: open failed
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "p13nJMSServer" due to weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist.
weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server p13nJMSServer: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <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:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <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:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'p13n-security-jms'.
weblogic.application.ModuleException: ERROR: Could not activate p13n-security-jms!p13n.security.RDBMSSecurityStoreTopic
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.backend.BETopicRuntimeDelegate.activate(BETopicRuntimeDelegate.java:100)
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)
Truncated. see log file for complete stacktrace
Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel p13nJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
at weblogic.messaging.kernel.internal.TopicImpl.activate(TopicImpl.java:97)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:627)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <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)
Truncated. see log file for complete stacktrace
Caused By: 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:280)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1696)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1872)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320400> <The log file /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log00054. Log messages will continue to be logged in /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log.>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerportal. Error - weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:133)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerportal' due to error weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:133)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerstaticweb. Error - weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerstaticweb' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
>
<Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 19, 2012 1:46:13 PM EEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jun 19, 2012 1:46:14 PM EEST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 172.25.23.238:80 was shutdown.>It's the first couple of bits that are key here
<Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
It looks to me that your stores are incorrectly configured, targetted or or just simply messed up. First thing I would do here is check the configuration and targetting of the JDBC Stores and make sure that each JMS server is using it own store and database tables. You may find that it's a really simple thing like creating two sets of tables on the same database, but making sure that they have different prefixes ... -
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 -
Hello,
After installing weblogic 6.1, I tried running a managed server. However, it
gave me the following error message:
<2001/11/1 譯觼04渀05禳49秮> <Notice> <WebLogicServer>
<Starting WebLogic Managed Server "SimsOneServer" for domain "mydomain">
<2001/11/1 譯觼04渀05禳56秮> <Emergency> <WebLogicServer>
<ListenThread.run() failed: java.lang.UnsatisfiedLinkError: no weblogicunix1 in
java.library.path
java.lang.UnsatisfiedLinkError: no weblogicunix1 in java.library.path
at java.lang.ClassLoader.loadLibrary ClassLoader.java:1312)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
at weblogic.platform.Unix.<init>(Unix.java:14)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.platform.OperatingSystem.getOS(OperatingSystem.java:75)
at weblogic.t3.srvr.T3Srvr$2.run(T3Srvr.java:1004)
at weblogic.t3.srvr.Callback.done(Callback.java:37)
at weblogic.t3.srvr.ListenThread.newServerSocket(ListenThread.java:186)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:223)
>
I am using the supplied script of the default domain, "mydomain".
I have no problem running weblogic as administration server.
Thanks.You need to have the directory where 'libweblogicunix1.so' resides in the LD_LIBRARY_PATH.
Depending on the platform you are using, LD_LIBRARY_PATH will be set by the
'startManagedWebLogic.sh' script in a case statement that figures out what platform you are
running on by using 'uname -s'. It then sets and exports LD_LIBRARY_PATH.
Look at your 'startManagedWebLogic.sh' script and make sure that this environment variable
is being set correctly and look in the directory that is being set to make sure that a copy
of 'libweblogicunix1.so' (.sl on HPUX) exists.
Bill Kemp
BEA Systems
Mark Liu wrote:
Hello,
After installing weblogic 6.1, I tried running a managed server. However, it
gave me the following error message:
<2001/11/1 譯觼04渀05禳49秮> <Notice> <WebLogicServer>
<Starting WebLogic Managed Server "SimsOneServer" for domain "mydomain">
<2001/11/1 譯觼04渀05禳56秮> <Emergency> <WebLogicServer>
<ListenThread.run() failed: java.lang.UnsatisfiedLinkError: no weblogicunix1 in
java.library.path
java.lang.UnsatisfiedLinkError: no weblogicunix1 in java.library.path
at java.lang.ClassLoader.loadLibrary ClassLoader.java:1312)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
at weblogic.platform.Unix.<init>(Unix.java:14)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.platform.OperatingSystem.getOS(OperatingSystem.java:75)
at weblogic.t3.srvr.T3Srvr$2.run(T3Srvr.java:1004)
at weblogic.t3.srvr.Callback.done(Callback.java:37)
at weblogic.t3.srvr.ListenThread.newServerSocket(ListenThread.java:186)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:223)
>
I am using the supplied script of the default domain, "mydomain".
I have no problem running weblogic as administration server.
Thanks. -
SOA managed server startup problem
Hi All,
I am facing an issue while starting the SOA Managed Server (soa_server1) using NodeManager.
Backgound:
I have setup a soa domain, started up NM and admin server using NM in solaris environemnt. All runs fine but when I start MS using NM for the first time it throws error. If I start the MS from the admin console it starts fine. The execution steps I have performed-
1. Started NodeManager - using script
2. Shutdown the NodeManager , changed the nodemanager.properties file to update parameter [startScriptEnabled=true] and start it again.
3. Started AS using NM [nmConnect(..) and nmStart('AdminServer')]
4. Enrolled the NM with the current machine [connect(..), nmEnroll(domain_dir, nodemanager_home)]
5. Copied the boot.properties to security/ dir of soa_server1
6. Started MS using NM - Throws error
Does it really mean I have to start the MS through admin console everytime I start MS first time in the machine? (I am working on automation on SOA env where everynight env wipes off and installs the SOA stack from scratch)
The soa-server1.out looks like:
<15-Mar-2012 10:26:41 o'clock GMT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<15-Mar-2012 10:26:41 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.1-b02 from Sun Microsystems Inc.>
<15-Mar-2012 10:26:42 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<15-Mar-2012 10:26:45 o'clock GMT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: Booting as admin server, but servername, soa_server1, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
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)
>
<15-Mar-2012 10:26:45 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<15-Mar-2012 10:26:45 o'clock GMT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<15-Mar-2012 10:26:45 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<15-Mar-2012 10:26:45> <FINEST> <NodeManager> <Waiting for the process to die: 20518>
<15-Mar-2012 10:26:45> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<15-Mar-2012 10:26:45> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Please help with your expertise.
Apologies if I have missed any info or posted in wrong forum, if you need more feel free to shout.
Thanks in advance.
Cheers,
BhaskarHi,
I have implemented the above mentioned suggestions. But seems to have no luck. I had
1. Copied startup.properties to ${DOMAIN_HOME}/servers/soa_server1/data/nodemanager
2. Copied the boot.properties to ${DOMAIN_HOME}/servers/soa_server1/security
These did not added any value, so I though of passing the parameters at nmStart() as WLST object;
arg="Arguments=\" -Dweblogic.management.server=localhost:8001\"" (My AS and MS runs on same machine)
prps=makePropertiesObject(arg)
nmStart('soa_server1',props=prps)
This started throwing Boot Identity file not valid.
I changed my way.
1. Connected to Admin Server using WLST
connect (username, password)
2. Start MS
start('soa_server1')
Its working fine now and under NM control. Not sure what more NM demands when starting without AS.
Regards,
Bhaskar -
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? -
Managed server discovery problem
I'm running WL 6.0 sp1 on Solaris 2.7.
I have my admin server discover=true. I start this up, with all my other servers in the domain
down, and get a bunch of can't-find-server warnings, which is fine. But then I get a null ptr
exception and the server shuts down!
If I manually cleaned up running-managed-servers.xml, then my admin server runs again, but obviously
I do not want to manually maintain this file!
<Mar 15, 2001 10:26:58 AM PST> <Notice> <Management> <Starting discovery of Managed Server...>
<Mar 15, 2001 10:26:58 AM PST> <Info> <Management> <Managed Server discovery, for server app03
running at 10.1.3.41:10085>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.3.41:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.3.41:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDe
legate.java:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app03
running on listen address 10.1.3.41 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No server found
at T3://10.1.3.41:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <Management> <Managed Server discovery, for server app02
running at 10.1.3.40:10085>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.3.40:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.3.40:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app02
running on listen address 10.1.3.40 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No server found
at T3://10.1.3.40:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <Management> <Managed Server discovery, for server app01
running at 10.1.1.22:10085>
<Mar 15, 2001 10:27:00 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.1.22:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.1.22:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app01
running on listen address 10.1.1.22 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No server found
at T3://10.1.1.22:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Info> <Management> <Managed Server discovery, for server web01
running at 10.1.1.22:10081>
<Mar 15, 2001 10:27:07 AM PST> <Emergency> <Server> <Unable to initialize the server: 'Fatal
initialization exception
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exceptiondone
"Viresh Garg" <[email protected]> wrote in message news:[email protected]...
Can you please follow up with [email protected], so that we can create a formal bug for this.
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
Gene Chuang wrote:
I'm running WL 6.0 sp1 on Solaris 2.7.
I have my admin server discover=true. I start this up, with all my other servers in the domain
down, and get a bunch of can't-find-server warnings, which is fine. But then I get a null ptr
exception and the server shuts down!
If I manually cleaned up running-managed-servers.xml, then my admin server runs again, but
obviously
I do not want to manually maintain this file!
<Mar 15, 2001 10:26:58 AM PST> <Notice> <Management> <Starting discovery of Managed Server...>
<Mar 15, 2001 10:26:58 AM PST> <Info> <Management> <Managed Server discovery, for server app03
running at 10.1.3.41:10085>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.3.41:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.3.41:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDe
legate.java:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app03
running on listen address 10.1.3.41 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No serverfound
at T3://10.1.3.41:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <Management> <Managed Server discovery, for server app02
running at 10.1.3.40:10085>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.3.40:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.3.40:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app02
running on listen address 10.1.3.40 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No serverfound
at T3://10.1.3.40:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:26:59 AM PST> <Info> <Management> <Managed Server discovery, for server app01
running at 10.1.1.22:10085>
<Mar 15, 2001 10:27:00 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a direct:
'Protocol: 't3''connection to: '0S:10.1.1.22:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1077)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:365)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Info> <ConnectionManager> <Bootstrap unable to get a routed:
'Protocol: 't3'' connection to: '0S:10.1.1.22:[10085,-1,-1,-1,-1,-1,-1]' on port: '10085'
java.rmi.ConnectException: No available router to destination
at weblogic.rjvm.ConnectionManager.findOrCreateRouter(ConnectionManager.java:1167)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:378)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:330)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:228)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:188)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Warning> <Management> <JNDI lookup for MBeanHome on server app01
running on listen address 10.1.1.22 listen port 10085 failed.
javax.naming.CommunicationException. Root exception is java.net.ConnectException: No serverfound
at T3://10.1.1.22:10085
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<Mar 15, 2001 10:27:00 AM PST> <Info> <Management> <Managed Server discovery, for server web01
running at 10.1.1.22:10081>
<Mar 15, 2001 10:27:07 AM PST> <Emergency> <Server> <Unable to initialize the server: 'Fatal
initialization exception
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:180)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:149)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:232)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.discoverManagedServer(Admin.java:1290)
at weblogic.management.Admin.discoverManagedServers(Admin.java:1182)
at weblogic.management.Admin.finish(Admin.java:489)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception -
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? -
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.
-
Remote Server Output of Weblogic 8.1 managed server.
Just have a quick question.
Where's the exact(default) location of the file that is showing on Server>Control>Remote Start Output>View Server Output.Thanks,
I found the file under user_projects/domains/mydomain/NodeManagerClientLogs/mydomain_someserver folder. But they were organized with the date and time as the file name. Can I configure the system to point to a file with fixed name so that I can view it from a servlet, for example. One of the reasons is the file may grow to big and it will take a long time to load up from console and check it from there. Second question is if it is possible to redirect both stdout and stderr to a single file. I can do it from the command line when starting weblogic (> a.out 2>1&). But I don't know how to do the same in Remote managed server startup. -
Cloud Control 12c identifies unused Weblogic version on Managed Server
I'm using Cloud Control to monitor our domain. In this case I upgraded from WebLogic 10.3.1 to Weblogic 12.1.2.0.0 by installing 12c on a separate Oracle/Middleware/Oracle_Home and updateing the startup script to use this new WL_Home location.
The Weblogic 10.3.1 installation is still there.
When I connect through Cloud Control to discover the Middleware Targets (WebLogic) it identifies my server as being 10.3.1
I checked the path and classpath in the startup script and there are no references to the 10.3 path. How is the cloud control agent finding the inactive one ?
any help is appreciatedFor the error messagee:
Shell path is incorrect or not defined.:/usr/local/bin/bash(SH_PATH),-c(SH_ARGS) on host XXX. Check the property values in the following files in this order, ssPaths_<plat>.properties or sPaths.properties or Paths.properties, in "/oracle/em12c/oms/oui/prov/resources" directory.For more details, refer to the Oracle Enterprise Manager Basic Installation Guide.
yes , you are suppose to change the shell patch as its at a different location.
The file where you have to chnage is: $<OMS_HOME>/oui/prov/resources/hpi.properties and change the variable: SH_PATH=
Try the agent deployment
On your another question: deploy manual agent , you have to get the em12c agent binaries usings elf update console. For information on Self Update and how you can use it to download the software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/self_update.htm#CACBHCBH -
9i Enterprise Management Server License problem
9i database standard edition can use Enterprise Managament Server?
Enterprise Management Server can send a alert e-mail then some tablespace have large than the setting size.Questions like this should be addressed to your Oracle sales representative. No one here can give you a reliable answer,which passes into law. In general Management Packs require Enterprise Edition.
Werner -
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.
-
Getting a perl error when trying to discover a Weblogic Managed Server
Hi,
Any help working this out would be greatly appreciated. I've searched Oracle Support and here without success so far.
I am trying to add a weblogic 10.3 manager server as a target for the agent on that host. Using Grid Control 10.2.0.5 patch 3 on both the OMS and the agent.
I get past the 2nd screen of the wizard then it fails. So far I've entered hostname, port, credentials for weblogic, then on the next page the credentials for the linux user on the host. Hitting next goes to a clock icon for a few seconds then it fails with:
Can't locate File/Find.pm in @INC (@INC contains: /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/5.8.3/i686-linux-thread-multi /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/5.8.3 /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl/5.8.3/i686-linux-thread-multi /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl/5.8.3 /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl .) at /app/oracle/agent10g/sysman/admin/scripts/weblogicdiscovery.pl line 2. BEGIN failed--compilation aborted at /app/oracle/agent10g/sysman/admin/scripts/weblogicdiscovery.pl line 2.
I understand that when the agent runs the perl script weblogicdiscovery.pl, perl cant find the Find module to include (as instructed on line 2). The file in question exists in /app/oracle/agent10g/perl/lib/5.8.3/File/Find.pm .
I've tried tweaking the PERL5LIB env variable in the shell before I start the agent, and also in the emctl script itself, but neither seems to have any effect on that error message. It at least should have the basic $ORACLE_HOME/perl/lib in the path which is doesn't.
Anywhere else I should look for this variable setting?
Edit: Next question. I've been wondering where those "/ade/smayer_perl58_main_linux/..." paths were coming from as they aren't going to work and I see them (or at least very similar paths) defined in /app/oracle/agent10g/perl/lib/5.8.3/i686-linux-thread-multi/Config.pm . I've checked another linux host with the agent installed and it is the same, so must be defaults from Oracle. Was I supposed to change these after the install? I didn't read that anywhere. Still if we can set PERL5LIB before running emctl this should prepend real paths, right?
Quick test:
export PERL5LIB=$ORACLE_HOME/perl/lib:$ORACLE_HOME/perl/lib/site_perl
perl -e 'print join "\n", @INC'
/perl/lib/5.8.3
/app/oracle/agent10g/perl/lib/5.8.3/i686-linux-thread-multi
/app/oracle/agent10g/perl/lib/5.8.3
/app/oracle/agent10g/perl/lib
/app/oracle/agent10g/perl/lib/site_perl/5.8.3/i686-linux-thread-multi
/app/oracle/agent10g/perl/lib/site_perl/5.8.3
/app/oracle/agent10g/perl/lib/site_perl
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/5.8.3/i686-linux-thread-multi
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/5.8.3
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl/5.8.3/i686-linux-thread-multi
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl/5.8.3
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl
Should $ORACLE_HOME/Perl be rebuilt during the agent install? I'm thinking it should because those details in the file point to someone with a username smayer configuring perl as per his environment.
Cheers,
Damian
Edited by: user11127564 on 29-Jun-2010 21:42
I've located something slightly useful on Metalink. Note ID 762125.1 particularly as we're using delegated privs and sudo.
However, this says this problem is fixed in 10.2.0.5. I'll prod my sysadmins some more on the sudoers configuration.
Edited by: user11127564 on 30-Jun-2010 16:55Right. If you are using delegated privs and sudo, make sure that sudo is configured to pass on the PERL5LIB and ORACLE_HOME environment variables at least.
-
Cannot start WebLogic Managed Server
Hi,
I have an weblogic domain on a physical machine with two servers (AdminServer and osb_server1 [Managed Server]). (Weblogic 10.3.6)
I started nodeManager and enrolled the domain using nmEnroll command through WLST.
I can start "AdminServer" thourgh nmStart('AdminServer') command. AdminServer starts successfully.
However, when I want to start managed server (osb_server1):
1. Through WebLogic administrator console it says:
(Warning) The user is not authorized to perform lifecycle operations on server osb_server1.
(Warning) All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
2. Using startManagedWebLogic.cmd script after entering username/password, it returns authentication denied.
Oct 22, 2012 10:31:21 AM EEST> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied>
<Oct 22, 2012 10:31:21 AM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
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)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
3. Using nmStart command on nodeManager, it is complaining about boot.properties file.
I can login AdminServer with same account without problems.
Best Regards,
Edited by: ToRRaDo on Oct 22, 2012 5:25 PMCopied boot.properties from AdminServer to osb_server1 and the error below occured. (I also with plain text passwords in boot.properties file but error did not change)
<Oct 23, 2012 8:03:59 AM EEST> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user weblogic starting the managed server. The reason for the error is .>
<Oct 23, 2012 8:03:59 AM EEST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:7001/.>
<Oct 23, 2012 8:03:59 AM EEST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Oct 23, 2012 8:03:59 AM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Oct 23, 2012 8:03:59 AM EEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Oct 23, 2012 8:04:00 AM EEST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\my_domain\servers\osb_server1\logs\osb_server1.log is opened. All server side log events will be written to this file.>
<Oct 23, 2012 8:04:19 AM EEST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Oct 23, 2012 8:04:19 AM EEST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid;
The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
<Oct 23, 2012 8:04:20 AM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password fromthe boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created.
Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:960)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
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)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace>
<Oct 23, 2012 8:04:20 AM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
Edited by: ToRRaDo on Oct 23, 2012 8:13 AM
Edited by: ToRRaDo on Oct 23, 2012 8:14 AM
Maybe you are looking for
-
Dear All, When im trying data imgration from legacy to oracle apps 12.1.3 version. Im trying to imgrate AR invoices. It give me the below error. Can any one pls help me As this is 1st time im doing this. Please suggest. Receivables: Version : 12.0.0
-
everything working find after the update to 10.2.1.537 expect the SMS. have no problem sending or getting sms/mms but nothing's visible within the "text messages" folder. new sms also not notified and asterick and sound (despite setting the sound on
-
SCUP update failure: Error and 0x800b0004 and 0x80246002
Hi, I'm trying to get Adobe products using SCCM2012R2 and SCUP 2011. The site server and distribution point are on the same machine, and the WSUS server sits on a different machine. We have a root CA which uses AD Certificate Services. My code sig
-
Need to know how to place a tiling image in the div tags
Let me see if I can explain what I want to do in a way that makes sense. I have created a box using the <div> I want a background image I made in photoshop that has rounded corners. I need this image to stretch or tile the length and width of the box
-
Multiple Licenses or Single Licenses of InDesign 6.0?
Can you buy one license of inDesign 6.0 for many computers or multiple licenses for many computers