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 ...

Similar Messages

  • Weblogic SIP Server start problem

    I installed the evaluation version of the Welogic SIP server 2.2.0. When I start the server, I get the following error message:
    "...failed to bind socket to host 192.168.1.1 and port 5060..."
    "...failed to start the sip service, shutting down..."
    When I try to open the the server admin concole at http://localhost:7001, I get the 404 message.
    I uninstalled and reinstalled the server, but the same problem exists.
    Any help from anyone is greatly appreciated.
    Thank you very much.

    Double-check the weblogic.policy file in your WLS 5.1 installation directory. My codeBase and
    FilePermission for my WinNT installation looks like this:
    grant codeBase "file:C:/wls/-" {
    permission java.io.FilePermission "C:${/}wls${/}-", "read,write,delete,execute";
    Niall wrote:
    Hello,
    When I try to start the Weblogic Commerce server 3.2,
    I get the error message:
    The WebLogic Server did not start up properly.
    Exception raised: java.security.AccessControlException: access denied (java.util.PropertyPermission
    weblogic.management.password read)
    java.security.AccessControlException: access denied (java.util.PropertyPermission
    weblogic.management.password read)
    I have changed the property weblogic.password.system in the weblogic.properties file
    to the system password for Weblogic.
    Any ideas?--
    Ture Hoefner
    BEA Systems, Inc.
    2590 Pearl St.
    Suite 110
    Boulder, CO 80302
    www.bea.com
    [att1.html]

  • 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

  • Weblogic 10.3.5 Managed Server 추가 후 start 할 때 에러 나요...

    Windows 7(로컬 환경)에서 weblogic 10.3.5를 사용하고 있고, 관리자 콘솔(http://localhost:7001/)에서 Managed Server(서버 이름 :test_server)를 등록해주었습니다.
    그리고 배치에 디플로이 할 소스 경로를 체크하고 test_server targetting 한 후 start 했는데 에러가 납니다...ㅠㅠ
    두 가지 방법으로 start 했었는데..
    1. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin>startManagedWebLogic.cmd  test_server http://localhost:8001
    이렇게 입력하면, 로그가 잘 찍히다가
    Enter username to boot WebLogic server: test_name
    이게 표시됩니다. weblogic 처음 설치 할 때 설정한 username(어드민 콘솔 아이디)를 입력하니 password를 입력하라고 나오는게 아니라 아래와 같이 에러가 납니다. ㅠㅠ
    *<Error> <Security> <BEA-090783> <Server is Running in Development Mode and Native Library(terminalio) to read the password securely from commandline is not found.>*
    *<Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>*
    *<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>*
    두번 째 방법은
    2. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin\*startManagedWebLogic.cmd*
    여기서 startManagedWebLogic.cmd 를 카피하여 startManagedWebLogic_test.cmd 를 만든 후 if "%1"=="" ( 바로 아래
    set SERVER_NAME=test
    set ADMIN_URL=http://localhost:8001
    set WLS_USER=test_name
    set WLS_PW=test_password
    이렇게 만든 후 2. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin\*startManagedWebLogic_test.cmd* 로 Start 하였습니다.
    그러니 아주 크리티컬한 에러가............... ㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠ
    <Critical> <WebLogicServer> <BEA-000362> *<Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: The provider Provider already* exists>
    <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    저 에러로그로 구글링을 엄청나게 해봤는데 별다른 성과가 없습니다..
    제발 아시는 분 도와주세요..ㅠㅠ
    글 수정: 889513

  • Weblogic Server does not show managed server started when I used the Windows service to start it.

    I created a windows service to start a managed server and the services was created successfully and stated.  WHen I go to the Weblogic Server Admn console, the server is still showing shutdown.  Whenm I try to start it, it returns with error that the the service is not able to start.  Has anyone ran into anything similar.  I am running on Windows Server 2008R2 and running Weblogic Server 10.3.6 and Fusion Middleware 11.1.6.
    C

    Hi,
    For starting managed server as windows service there is no need of nodemanager .
    Please follow the steps given in the below doc:
    How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)
    Thanks,
    Sharmela

  • Weblogic commerce server  start problem

    Hello,
    When I try to start the Weblogic Commerce server 3.2,
    I get the error message:
    The WebLogic Server did not start up properly.
    Exception raised: java.security.AccessControlException: access denied (java.util.PropertyPermission
    weblogic.management.password read)
    java.security.AccessControlException: access denied (java.util.PropertyPermission
    weblogic.management.password read)
    I have changed the property weblogic.password.system in the weblogic.properties file
    to the system password for Weblogic.
    Any ideas?

    Double-check the weblogic.policy file in your WLS 5.1 installation directory. My codeBase and
    FilePermission for my WinNT installation looks like this:
    grant codeBase "file:C:/wls/-" {
    permission java.io.FilePermission "C:${/}wls${/}-", "read,write,delete,execute";
    Niall wrote:
    Hello,
    When I try to start the Weblogic Commerce server 3.2,
    I get the error message:
    The WebLogic Server did not start up properly.
    Exception raised: java.security.AccessControlException: access denied (java.util.PropertyPermission
    weblogic.management.password read)
    java.security.AccessControlException: access denied (java.util.PropertyPermission
    weblogic.management.password read)
    I have changed the property weblogic.password.system in the weblogic.properties file
    to the system password for Weblogic.
    Any ideas?--
    Ture Hoefner
    BEA Systems, Inc.
    2590 Pearl St.
    Suite 110
    Boulder, CO 80302
    www.bea.com
    [att1.html]

  • WSM Managed server starts in ADMIN Mode after upgrade to 11.1.1.7

    We have just upgraded our 11g SOA Cluster environment from 11.1.1.4 to 11.1.1.7. The issue is after the upgrade, our WSM servers are starting to ADMIN state with following error.
    <Sep 25, 2013 7:14:35 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@381802823[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
    at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
    Our cluster environment has one Admin Server, and two of each OSB, WSM and SOA managed servers. As our WSM servers are not coming up, we are not able to start our SOA servers too.
    Thank You

    Same issue here :-)), Just playing around with policies configuration, the server was running just fine, I wanted to check if the policies are applicable during runtime even the WSM managed server is down. After restart, it started in ADMIN mode, well the solution is straight. It is exactly telling that the dms application is missing the jstl library reference
    <Error> <Deployer> <iwpdcdevsoaa.iwater.ie> <WLS_WSM1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <bcfaf10ec8fbdfc2:-26d85d29:1429ffae24c:-8000-0000000000000003> <1385663491675> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
    weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@384044243[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
            at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
            at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494)
            at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
            at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
            at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
            at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    >
    So search for "jstl" within the weblogic console in search bar, it is type of library, click on it and target it to the managed server where OWSM is running as weel. It was root cause in my case, somehow the library was not targeted to our WLS_WMS1 managed server. Now the server is back in RUNNING mode. Of course apply this in case of problem with SOA servers, target it to the cluster or exact nodes and it should work.
    Still I don't know how the issue has been crated, I don't think that somebody removed it from deployment. Rather I think that somebody was applying patch or some artifacts to OSB or SOA managed server and this library was required as well, but as soon as we have separated WSM cluster, it was maybe assuming that it is running within OSB or SOA clusters and therefore didn't target the WSM cluster automatically. But this is just the idea :-))
    Ladislav

  • Managed server start very slowly

    Hi All,
    We are currently facing issues in starting a managed weblogic server.
    We have 2 machines, say MAC1 and MAC2.
    MAC1 contains the admin server and 5 managed servers.
    MAC2 contains only 5 managed servers with the same name as that of the 5 managed servers which are on MAC1.
    We faced some issues starting the managed servers on MAC2.
    So we decided to use pack and unpack.
    We were able to start the managed servers on MAC2 however each server tooks about 25 minutes to start.
    This is some what unexpected behaviour.
    I had a look at the logs of one of the managed server.
    It appears that its waits most of its time on :
    <Log Management> <BEA-170019> <The server log file xyz.log is opened. All server side log events will be written to this file.>
    The next log after this appears after about 20 minutes.
    So i feel that its stuck reading or writing the logs.
    Any pointers!!
    Regards,
    Stacey.

    Hi All,
    After taking the thread dumps , I am suspecting the following two threads which might be causing the issue :
    "Thread-3" daemon prio=10 tid=0x73939800 nid=0x6784 waiting on condition [0x72530000]
    java.lang.Thread.State: WAITING (parking)
         at sun.misc.Unsafe.park(Native Method)
         - parking to wait for <0x76610450> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
         at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
         at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1735)
         at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:452)
         at weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:19)
         at weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
         at weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:175)
         at weblogic.store.internal.PersistentStoreImpl$2.run(PersistentStoreImpl.java233)
    "ExecuteThread: '7' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=0x7391ec00 nid=0x6789 waiting for monitor entry [0x73344000]
    java.lang.Thread.State: BLOCKED (on object monitor)
         at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:95)
         - waiting to lock <0x765902f0> (a weblogic.socket.PosixSocketMuxer$1)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    Any pointers !!
    Regards,
    Stacey.

  • 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,
    Bhaskar

    Hi,
    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

  • 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 exception

    done
    "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,
    Naga

    Hi,
    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?

  • Managed Server started but reflected as Shutdown in Admin Console

    Hi,
    Our managed server is running as service (but the error log shows it is unable to contact the Admin server, thus running in independence mode). On our admin console, it shows the managed server as shutdown. How can we resolve this issue?
    We have tried to clear all the folders under \servers\<managedserver> except the security folder containing boot.properties. However it kept prompting that invalid username/password has been entered. If we restore the original folders, the managed server was able to startup, although in independence mode. Is it because of some ldap ldift file which we find in the managed server's subfolder? How can we resolve this??
    Please help, as this is a production environment and this issue just suddenly happened. It was running fine earlier

    Hi
    1) 10gR3
    2) The log for managed server shows it is started and running. However, it has the following lines of error:
    ####<Dec 28, 2012 6:43:42 PM SGT> <Emergency> <Management> <KIMPRDDMAPP> <> <main> <> <> <> <1356691422536> <BEA-141151> <The admin server could not be reached at https://kimprddmapp:9002.>
    ####<Dec 28, 2012 6:43:42 PM SGT> <Info> <Configuration Management> <KIMPRDDMAPP> <> <main> <> <> <> <1356691422552> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    It is also unable to deploy our application:
    ####<Dec 28, 2012 6:43:51 PM SGT> <Error> <Deployer> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356691431398> <BEA-149205> <Failed to initialize the application 'da' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
    weblogic.management.DeploymentException: Exception occured while downloading files
         at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
         at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
         at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
         at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
         at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.net.SocketException: Network is unreachable: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
         at java.net.Socket.connect(Socket.java:525)
         at java.net.Socket.connect(Socket.java:475)
         at java.net.Socket.<init>(Socket.java:372)
         at java.net.Socket.<init>(Socket.java:273)
         at javax.net.ssl.SSLSocket.<init>(SSLSocket.java:195)
         at javax.net.ssl.impl.SSLSocketImpl.<init>(Unknown Source)
         at javax.net.ssl.impl.SSLSocketFactoryImpl.createSocket(Unknown Source)
         at weblogic.socket.ChannelSSLSocketFactory.createSocket(ChannelSSLSocketFactory.java:78)
         at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:274)
         at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:502)
         at weblogic.net.http.HttpsClient.New(HttpsClient.java:566)
         at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:242)
         at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:75)
         at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
         at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
         at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
         at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
         at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
         at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Dec 28, 2012 6:43:51 PM SGT> <Info> <WebService> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1356691431991> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Dec 28, 2012 6:43:52 PM SGT> <Info> <WebService> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1356691432085> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    Noticed that on my Admin Server, it has the following error message, could this be the cause? How can I fix it?
    ####<Dec 28, 2012 6:35:45 PM SGT> <Warning> <Security> <KIMPRDDMAPP> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356690945499> <BEA-090482> <BAD_CERTIFICATE alert was received from KIMPRDDMAPP.pubnet.sg - 10.206.12.30. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    ####<Dec 28, 2012 6:35:45 PM SGT> <Error> <Console> <KIMPRDDMAPP> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <kimdmweblogic> <> <> <1356690945499> <BEA-240003> <Console encountered the following error javax.help.HelpSetException: Could not parse
    Got an IOException ([Security:090477]Certificate chain received from docs.kim.pubnet.sg - 10.206.12.30 was not trusted causing SSL handshake failure.)
    Parsing failed for null
         at javax.help.HelpSet.<init>(HelpSet.java:146)
         at com.bea.help.utils.HelpSetHelper.getExtensionHelpSetMap(Unknown Source)
         at com.bea.help.utils.HelpSetHelper.mergeExtensionHelpSet(Unknown Source)
         at com.bea.help.utils.HelpSetHelper.createHelpSet(Unknown Source)
         at com.bea.help.utils.HelpSetHelper.getHelpSet(Unknown Source)
         at com.bea.help.utils.HelpSetHelper.ensureHelpSet(Unknown Source)
         at jsp_servlet._jsp.__tocview._jspService(__tocview.java:110)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
         at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:552)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
         at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
         at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
         at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
         at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
         at jsp_servlet._framework._skeletons._console.__nolayout._jspService(__nolayout.java:119)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
         at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
         at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
         at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
         at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
         at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
         at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
         at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
         at jsp_servlet._framework._skeletons._console.__twocollayout._jspService(__twocollayout.java:246)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
         at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
         at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
         at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
         at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
         at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
         at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
         at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:211)
         at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:196)
         at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
         at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    3) Both Admin and managed servers are running on same host

  • How to find manage server name in weblogic server?

    I have two managed server in weblogic server. I need to find out which managed server serving my request. Please let me know if any body knows about this.

    You do not need to do anything, if your Report server is on the same machine as the Forms server (which is usually the case) you simply use the url as
    /reports/rwservlet?report=myreport' and the server will automatically use the default report server.
    then you simply use
    web.show_document('/reports/rwservlet?userid=scott/tiger@orcl&report=myreport&desformat=htmlcss&desname=test.html'Tony
    Try it now
    Edited by: Tony Garabedian on Nov 5, 2008 2:00 PM

  • WebSphere Default Server Starting Problem

    I am using WebSphere AS and facing a strange problem at the time of starting the default server.
    I had to change the user name & password of the XADataSource of the Server. On applying this, and starting the Default server, the server started and application worked fine. However, the next day, when I restarted the machine & started the Server, the server is not starting.
    I checked the connection using the Test Connection button. The connection is ok.
    I am getting the following error at the Default Server start up in the Default_Server_stdout.log:
    [4/18/03 14:28:38:219 GMT+05:30] 3cce5e54 Server U Build number: ptf30217.01
    [4/18/03 14:29:21:962 GMT+05:30] 3cce5e54 XARminst W WTRN0017W: Encountered an error in XA recover operation: -3
    [4/18/03 14:29:21:982 GMT+05:30] 3cce5e54 XARminst X Error to recover XAResource:
    In the log, the above two lines are repeated in a seemingly infinite loop. (I have to Force Stop the Default Server.)
    I suspect that there is some problem while reading the Default ServerXAResources properties file. I tried deleting this file so that it will be created, replacing it with that from another machine, but these things didn't work.
    (The classes12.zip is present in the classpath. )
    Please let me know if I have to do any more settings whenever I change the dastasource user/password.
    Thanks,
    JRahul.

    The following steps should fix your environment problem.
    1) Delete the log files under <WAS_HOME>\tranlog folder.
    This will allow you to start the server.
    2) Also make sure that your user id has SELECT privilege on
    "DBA_PENDING_TRANSACTIONS" table. I guess your id doesn't have that
    privilege.
    To grant the SELECT privilege on the system view
    "DBA_PENDING_TRANSACTIONS", you must logon to Oracle as "SYS" user using
    Oracle's tool likes SQL*Plus and issue the following command (Note: the
    default password for "SYS" user is "CHANGE_ON_INSTALL")
    sqlplus sys/change_on_install
    SQL> GRANT SELECT ON dba_pending_transactions to myuserid ;
    Sanjeevnagpal1

  • 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

Maybe you are looking for

  • 24" imac goes into sleep mode and lights on circuit flicker

    Hi -   I have a 24" imac and have found that when the display goes into sleep mode the lights on the circuit flicker.   I have searched the web and other users have complained of the same issue with no resolution.     Here is a similiar post - https:

  • In need of help to get music off my ipod back onto new computer

    the problem i have is before i had chance to set my ipod up 2 get it ready to transfer my music to another comp the comp went caput.i have disk use enabled but now i have a new comp i cant get my music onto it as i couldnt set it up before my other c

  • How to add custom feild in std report 2kee

    Hi, How we can add custom field in standard report 2kee. I need one extra field to add in 2kee report for the same is there any customization req. Regards Ravi

  • Crawler setting

    how do we set the crawler to crawle only internal web sites no external links are desired if we crawle www.oracle.com only pages in www.oracle.com web site get indexed. Regards and many thanks. Zakaria Ben-Salem

  • HT201386 I want my money back !

    I Paid good money for iPhoto on my iPad. Now because Apple has released IOS 8 iPhoto no longer works. Don't bother saying it's not supported, it worked fine in IOS 7 so your IOS 8 is at fault. If you can't make an operating system that works with you