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

Similar Messages

  • 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

  • How to start Weblogic 10.3.5 managed server on port 80

    Hello,
    We're trying to understand how to start Weblogic as root so we can start on port 80 on Linux. We understand that we'll use the post bind UID to run as a non-priv user. Right now in the Admin console under the managed server, Server Start properties (node manager) we have the weblogic user as the user to start the server, which works. Is this where we'd put the root user? We tried that but it fails complaining about root user didn't have permission to start the server. Can someone shed some light?
    Thanks

    Hi
    1. You are asking for 2 things here:
    a) Start Weblogic as root user ?
    Before I answer this question, who (Which User) installed Weblogic Software and who created Domain. I hope its NOT root user. Usually its not preferable to use root account for this. Instead create a new user account like for example oracle or some xyz. Then login with that account. Install Weblogic and create any Domain. I would NOT prefer/recommend using root account to install weblogic. This means, I would not recommend/support to start weblogic as root user. The thing is when you install weblogic, it stores/creates lots of files/scripts. Now when you start, it has to be same user. Because at the startup, we need to read files and also CREATE lots of temp files under domain root folder. So on unix, this becomes very complex. Simple answer is if you install weblogic and domain with user say "xyz" and try to start domain with "root", you corrupted your entire domain. Some files gets changed to root user and some files just FAIL saying you do not have permissions. So its just gone. If you are a Unix Geek, do some magic and restore all permissions back.
    b) Start Weblogic at Port 80
    Very Simple. Forget about above thing. Install Weblogic and create domain say with user "xyz". Just go to domain root folder, open config/config.xml file and edit the localport to 80. By default at time of domain creation if you used all the defaults like port 7001, then you will NOT see this entry in config.xml file. But still you can edit config.xml file manually. Stop the servers. Add a section with listen-port as 80. Just refer docs for the steps. After this change, your weblogic server is now running at port 80. NOW, the main precautions is make sure that you do NOT have any other stuff running at the same port 80. Otherwise, Weblogic server startup will fail saying port 80 is already is in use.
    Now if you want both a) and b), still it is possible. But I would NOT want/recommend a), which is use "root" account to install weblogic server and create and start the Domain. Nope, totally not recommending and supporting this. Yes, port 80 can be used, but not the "root" account.
    Thanks
    Ravi Jegga

  • Manage Server Start Problem (weblogic.store.io.jdbc.JDBCStoreException)

    I have a problem, when i start manage server.
    Could you please help me about this problem?
    Thanks
    Orhan YENER
    <Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
    <Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
    <Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "p13nJMSPersistenceStore" failed to open table "P13N_MESSAGING_WLStore".
    weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "p13nJMSPersistenceStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
    weblogic.store.io.jdbc.JDBCStoreException: open failed
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
            at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:37 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSPersistenceStore failed.
    weblogic.management.DeploymentException:
            at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
            at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:37 PM EEST> <Warning> <Store> <BEA-280076> <Database table "PF_PROLIFERATION_WLStore" for store "pfProliferationJMSStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102728280]". Trying to wait for ownership.>
    <Jun 19, 2012 1:45:57 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "pfProliferationJMSStore" in this server is not the owner of database table "PF_PROLIFERATION_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102748300]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=3276936988962983628:timestamp=1340102737578]".>
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "pfProliferationJMSStore" failed to open table "PF_PROLIFERATION_WLStore".
    weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
    weblogic.store.io.jdbc.JDBCStoreException: open failed
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
            at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
    weblogic.management.DeploymentException:
            at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
            at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
            at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
            at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
            at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
            at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
            at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "p13nJMSServer" due to weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist.
    weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSServer failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server p13nJMSServer: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
    weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfJMSServer failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
            at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
            at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
            at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
            at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
            at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'p13n-security-jms'.
    weblogic.application.ModuleException: ERROR: Could not activate p13n-security-jms!p13n.security.RDBMSSecurityStoreTopic
            at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
            at weblogic.jms.backend.BETopicRuntimeDelegate.activate(BETopicRuntimeDelegate.java:100)
            at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
            at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
            at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel p13nJMSServer has not yet been opened
            at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
            at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
            at weblogic.messaging.kernel.internal.TopicImpl.activate(TopicImpl.java:97)
            at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
            at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:627)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
    weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
            at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
            at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
            at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
            at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
            at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
            at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
            at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
            at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1696)
            at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
            at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1872)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320400> <The log file /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log00054. Log messages will continue to be logged in /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log.>
    <Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerportal. Error - weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
    weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
            at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
            at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
            Truncated. see log file for complete stacktrace
    Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
            at java.util.zip.ZipFile.open(Native Method)
            at java.util.zip.ZipFile.<init>(ZipFile.java:114)
            at java.util.jar.JarFile.<init>(JarFile.java:133)
            at java.util.jar.JarFile.<init>(JarFile.java:97)
            at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerportal' due to error weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
    weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
            at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
            at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
            Truncated. see log file for complete stacktrace
    Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
            at java.util.zip.ZipFile.open(Native Method)
            at java.util.zip.ZipFile.<init>(ZipFile.java:114)
            at java.util.jar.JarFile.<init>(JarFile.java:133)
            at java.util.jar.JarFile.<init>(JarFile.java:97)
            at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerstaticweb. Error - weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
            at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
            at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
            Truncated. see log file for complete stacktrace
    Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
            at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
            at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
            at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            Truncated. see log file for complete stacktrace
    >
    <Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerstaticweb' due to error weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
            at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
            at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
            Truncated. see log file for complete stacktrace
    Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
            at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
            at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
            at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
            at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
            at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
            Truncated. see log file for complete stacktrace
    >
    >
    <Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jun 19, 2012 1:46:13 PM EEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <Jun 19, 2012 1:46:14 PM EEST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 172.25.23.238:80 was shutdown.>

    It's the first couple of bits that are key here
    <Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
    <Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
    It looks to me that your stores are incorrectly configured, targetted or or just simply messed up. First thing I would do here is check the configuration and targetting of the JDBC Stores and make sure that each JMS server is using it own store and database tables. You may find that it's a really simple thing like creating two sets of tables on the same database, but making sure that they have different prefixes ...

  • Weblogic Admin and Managed Server start using boot.properties and LDAP Acc.

    Hello - Can any one please tell me if Weblogic 10.3.x can be started using boot.properties file and by using a user account from the External LDAP (OID) server?
    I have configured the Weblogic server and have added a LDAP authenticator.
    The Group in OID is mapped to the Admin role in Weblogic so that the user can start and stop the server.
    LDAP users can successfully authenticate and access WLS console.
    We would like to remove Default Authenticator (Embeded LDAP) from the list of available providers for our security releam.
    Thank you.

    Tested and got it worked.

  • Re: How to start Weblogic 10.3.5 managed server on port 80

    I can start managed server at port 80 but root permission make some deployments of managed server cannot cooperate with adminserver which is run by oracle user, in my case is oam_server1. Server is run but access server is down.

    I can start managed server at port 80 but root permission make some deployments of managed server cannot cooperate with adminserver which is run by oracle user, in my case is oam_server1. Server is run but access server is down.

  • 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

  • Weblogic 10.3.0 managed server + Spring Framework slow startup

    Hello
    Iam running weblogic 10.3.0 plus an application using spring framework on this:
    java.runtime.name = Java(TM) SE Runtime Environment
    java.runtime.version = 1.6.0_20-b02
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Sun Microsystems Inc.
    java.specification.version = 1.6
    java.vendor = Oracle Corporation
    java.version = 1.6.0_20
    java.vm.info = compiled mode
    java.vm.name = Oracle JRockit(R)
    os.arch = amd64
    os.name = Windows 2003
    os.version = 5.2
    sun.arch.data.model = 64
    sun.io.unicode.encoding = UnicodeLittle
    sun.jnu.encoding = Cp1252
    sun.management.compiler = Oracle JRockit(R) Optimizing Compiler
    sun.os.patch.level = Service Pack 2
    Problem Description: A weblogic managed server is taking more than an hour to start, the delay is due to the deployments during startup, passing from STATE_PREPARED to STATE_ADMIN and to the initialization of the Spring root WebApplicationContex, which takes an avg of 7 mins per module deployed.
    I have a development server with the same application which starts in a few minutes, the only difference between the environments are tha the development server runs in 32bits.
    Any help will be appreciated
    -luis
    Server log file:
    ####<Feb 17, 2011 5:09:06 PM VET> <Info> <ServletContext-/Micropago/ServiciosOperacionTransferencia> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1297978746371> <BEA-000000> <Initializing Spring root WebApplicationContext>
    ####<Feb 17, 2011 5:19:16 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297979356364> <BEA-149059> <Module operaciondispatcher-ws-1.0-SNAPSHOT.war of application operaciondispatcher-ws-1 is transitioning from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
    ####<Feb 17, 2011 5:19:16 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297979356411> <BEA-149060> <Module operaciondispatcher-ws-1.0-SNAPSHOT.war of application operaciondispatcher-ws-1 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
    ####<Feb 17, 2011 5:19:24 PM VET> <Info> <ServletContext-/Micropago/ServiciosOperacionD> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1297979364083> <BEA-000000> <Initializing Spring root WebApplicationContext>
    ####<Feb 17, 2011 5:23:35 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297979615333> <BEA-149059> <Module operacionutil-ws-1.0-SNAPSHOT.war of application operacionutil-ws-1 is transitioning from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
    ####<Feb 17, 2011 5:23:35 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297979615333> <BEA-149060> <Module operacionutil-ws-1.0-SNAPSHOT.war of application operacionutil-ws-1 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
    ####<Feb 17, 2011 5:23:40 PM VET> <Info> <ServletContext-/Micropago/ServiciosUtilidad> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1297979620318> <BEA-000000> <Initializing Spring root WebApplicationContext>
    ####<Feb 17, 2011 5:30:10 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297980010468> <BEA-149059> <Module securitymanager-ws-1.0-SNAPSHOT.war of application securitymanager-ws-1 is transitioning from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
    ####<Feb 17, 2011 5:30:10 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297980010515> <BEA-149060> <Module securitymanager-ws-1.0-SNAPSHOT.war of application securitymanager-ws-1 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server micropago_server.>

    Hi, thanks for your answer.
    How can I do a Thread Dump snapshot in a windows server starting as a service (no console)?
    Admin_server Thread Stack Trace
    Dump 1/3
    "Main Thread" waiting for lock weblogic.t3.srvr.T3Srvr@f14693 WAITING
         java.lang.Object.wait(Native Method)
         java.lang.Object.wait(Object.java:485)
         weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:811)
         weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:459)
         weblogic.Server.main(Server.java:67)
    "(Signal Handler)" RUNNABLE
    null
    "(OC Main Thread)" RUNNABLE
    null
    "(Code Generation Thread 1)" RUNNABLE
    null
    "(Code Optimization Thread 1)" RUNNABLE
    null
    "(VM Periodic Task)" RUNNABLE
    null
    "(Attach Listener)" RUNNABLE
    null
    "Finalizer" RUNNABLE
         jrockit.memory.Finalizer.waitForFinalizees(Native Method)
         jrockit.memory.Finalizer.access$700(Finalizer.java:12)
         jrockit.memory.Finalizer$4.run(Finalizer.java:189)
         java.lang.Thread.run(Thread.java:619)
    "Reference Handler" RUNNABLE
         java.lang.ref.Reference.waitForActivatedQueue(Native Method)
         java.lang.ref.Reference.access$100(Reference.java:11)
         java.lang.ref.Reference$ReferenceHandler.run(Reference.java:82)
    "(Sensor Event Thread)" RUNNABLE
    null
    "VM JFR Buffer Thread" RUNNABLE native
    null
    "Timer-0" waiting for lock java.util.TaskQueue@e259a7 WAITING
         java.lang.Object.wait(Native Method)
         java.lang.Object.wait(Object.java:485)
         java.util.TimerThread.mainLoop(Timer.java:483)
         java.util.TimerThread.run(Timer.java:462)
    "Timer-1" waiting for lock java.util.TaskQueue@10ad080 TIMED_WAITING
         java.lang.Object.wait(Native Method)
         java.util.TimerThread.mainLoop(Timer.java:509)
         java.util.TimerThread.run(Timer.java:462)
    "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE
    DUMP 2/3
    "Main Thread" waiting for lock weblogic.t3.srvr.T3Srvr@f14693 WAITING
         java.lang.Object.wait(Native Method)
         java.lang.Object.wait(Object.java:485)
         weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:811)
         weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:459)
         weblogic.Server.main(Server.java:67)
    "(Signal Handler)" RUNNABLE
    null
    "(OC Main Thread)" RUNNABLE
    null
    "(Code Generation Thread 1)" RUNNABLE
    null
    "(Code Optimization Thread 1)" RUNNABLE
    null
    "(VM Periodic Task)" RUNNABLE
    null
    "(Attach Listener)" RUNNABLE
    null
    "Finalizer" RUNNABLE
         jrockit.memory.Finalizer.waitForFinalizees(Native Method)
         jrockit.memory.Finalizer.access$700(Finalizer.java:12)
         jrockit.memory.Finalizer$4.run(Finalizer.java:189)
         java.lang.Thread.run(Thread.java:619)
    "Reference Handler" RUNNABLE
         java.lang.ref.Reference.waitForActivatedQueue(Native Method)
         java.lang.ref.Reference.access$100(Reference.java:11)
         java.lang.ref.Reference$ReferenceHandler.run(Reference.java:82)
    "(Sensor Event Thread)" RUNNABLE
    null
    "VM JFR Buffer Thread" RUNNABLE native
    null
    "Timer-0" waiting for lock java.util.TaskQueue@e259a7 WAITING
         java.lang.Object.wait(Native Method)
         java.lang.Object.wait(Object.java:485)
         java.util.TimerThread.mainLoop(Timer.java:483)
         java.util.TimerThread.run(Timer.java:462)
    "Timer-1" waiting for lock java.util.TaskQueue@10ad080 TIMED_WAITING
         java.lang.Object.wait(Native Method)
         java.util.TimerThread.mainLoop(Timer.java:509)
         java.util.TimerThread.run(Timer.java:462)
    "[STANDBY] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@10ad1bd WAITING
         java.lang.Object.wait(Object.java:485)
         weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    "weblogic.time.TimeEventGenerator" waiting for lock weblogic.time.common.internal.TimeTable@10aff60 TIMED_WAITING
         weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:286)
         weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:117)
         java.lang.Thread.run(Thread.java:619)
    "weblogic.timers.TimerThread" waiting for lock weblogic.timers.internal.TimerThread@11216cb TIMED_WAITING
         java.lang.Object.wait(Native Method)
         weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:267)
    "[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@10ad3e0 WAITING
         java.lang.Object.wait(Object.java:485)
         weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    "Thread-7" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@10ad595 WAITING
         sun.misc.Unsafe.park(Native Method)
         java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
         java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
         java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
         weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
         weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
         weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:615)
         weblogic.store.internal.PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
    "ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
         weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
         weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
         weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    "ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
         weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
         weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
         weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    "ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
         weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
         weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
         weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    "VDE Transaction Processor Thread" waiting for lock [email protected] WAITING
         java.lang.Object.wait(Native Method)
         java.lang.Object.wait(Object.java:485)
         com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:367)
         com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:212)
    "VDE Replication Thread" waiting for lock com.octetstring.vde.replication.Replication@10ad426 TIMED_WAITING
         com.octetstring.vde.replication.Replication.wait30sec(Replication.java:384)
         com.octetstring.vde.replication.Replication.run(Replication.java:350)
    "DoSManager" TIMED_WAITING
         java.lang.Thread.sleep(Native Method)
         com.octetstring.vde.DoSManager.run(DoSManager.java:433)
    "Thread-11" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4f576f WAITING
         sun.misc.Unsafe.park(Native Method)
    DUMP 3/3
    "Main Thread" waiting for lock weblogic.t3.srvr.T3Srvr@f14693 WAITING
         java.lang.Object.wait(Native Method)
         java.lang.Object.wait(Object.java:485)
         weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:811)
         weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:459)
         weblogic.Server.main(Server.java:67)
    "(Signal Handler)" RUNNABLE
    null
    "(OC Main Thread)" RUNNABLE
    null
    "(Code Generation Thread 1)" RUNNABLE
    null
    "(Code Optimization Thread 1)" RUNNABLE
    null
    "(VM Periodic Task)" RUNNABLE
    null
    "(Attach Listener)" RUNNABLE
    null
    "Finalizer" RUNNABLE
         jrockit.memory.Finalizer.waitForFinalizees(Native Method)
         jrockit.memory.Finalizer.access$700(Finalizer.java:12)
         jrockit.memory.Finalizer$4.run(Finalizer.java:189)
         java.lang.Thread.run(Thread.java:619)
    "Reference Handler" RUNNABLE
         java.lang.ref.Reference.waitForActivatedQueue(Native Method)
         java.lang.ref.Reference.access$100(Reference.java:11)
         java.lang.ref.Reference$ReferenceHandler.run(Reference.java:82)
    "(Sensor Event Thread)" RUNNABLE
    null
    "VM JFR Buffer Thread" RUNNABLE native
    null
    "Timer-0" waiting for lock java.util.TaskQueue@e259a7 WAITING
         java.lang.Object.wait(Native Method)
         java.lang.Object.wait(Object.java:485)
         java.util.TimerThread.mainLoop(Timer.java:483)
         java.util.TimerThread.run(Timer.java:462)
    "Timer-1" waiting for lock java.util.TaskQueue@10ad080 TIMED_WAITING
         java.lang.Object.wait(Native Method)
         java.util.TimerThread.mainLoop(Timer.java:509)
         java.util.TimerThread.run(Timer.java:462)
    "[STANDBY] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@10ad1bd WAITING
         java.lang.Object.wait(Object.java:485)
         weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    "weblogic.time.TimeEventGenerator" waiting for lock weblogic.time.common.internal.TimeTable@10aff60 TIMED_WAITING
         weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:286)
         weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:117)
         java.lang.Thread.run(Thread.java:619)
    "weblogic.timers.TimerThread" waiting for lock weblogic.timers.internal.TimerThread@11216cb TIMED_WAITING
         java.lang.Object.wait(Native Method)
         weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:267)
    "[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@10ad3e0 WAITING
         java.lang.Object.wait(Object.java:485)
         weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    "Thread-7" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@10ad595 WAITING
         sun.misc.Unsafe.park(Native Method)
         java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
         java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
         java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
         weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
         weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
         weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:615)
         weblogic.store.internal.PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
    "ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
         weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
         weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
         weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    "ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
         weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
         weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
         weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    "ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
         weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
         weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
         weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    "VDE Transaction Processor Thread" waiting for lock [email protected] WAITING
         java.lang.Object.wait(Native Method)
         java.lang.Object.wait(Object.java:485)
         com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:367)
         com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:212)
    "VDE Replication Thread" waiting for lock com.octetstring.vde.replication.Replication@10ad426 TIMED_WAITING
         com.octetstring.vde.replication.Replication.wait30sec(Replication.java:384)
         com.octetstring.vde.replication.Replication.run(Replication.java:350)
    "DoSManager" TIMED_WAITING
         java.lang.Thread.sleep(Native Method)
         com.octetstring.vde.DoSManager.run(DoSManager.java:433)
    "Thread-11" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4f576f WAITING
         sun.misc.Unsafe.park(Native Method)

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

    Dears: I ran my managed server using script but failed , the weblogic version is 10.3.2 (11g R1) , on Solaris 10 sparc 64bit.:
    ports=( 7001 7003 7005 7007 )
    instances=( instance1 instance2 instance3 )
    adminip=192.168.11.174
    "startManagedWebLogic.sh ${instances[1]} http://$adminip:${ports[0]}"&
    Does anyone get jammed into this situation?
    The Managed Server instance2 is going to running
    JAVA Memory arguments: -Xms768m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=6 -XX:+DisableExplicitGC -XX:MaxPermSize=2048m
    WLS Start Mode=Production
    CLASSPATH=/wls11g/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/wls11g/jdk1.6.0_18/lib/tools.jar:/wls11g/utils/config/10.3/config-launch.jar:/wls11g/wlserver_10.3/server/lib/weblogic_sp.jar:/wls11g/wlserver_10.3/server/lib/weblogic.jar:/wls11g/modules/features/weblogic.server.modules_10.3.2.0.jar:/wls11g/wlserver_10.3/server/lib/webservices.jar:/wls11g/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/wls11g/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/wls11g/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/wls11g/wlserver_10.3/server/lib/xqrl.jar
    PATH=/wls11g/wlserver_10.3/server/bin:/wls11g/modules/org.apache.ant_1.7.0/bin:/wls11g/jdk1.6.0_18/jre/bin:/wls11g/jdk1.6.0_18/bin:/wls11g/user_projects/domains/base_domain:/wls11g/user_projects/domains/base_domain/bin:/wls11g/wlserver_10.3/server/bin:/wls11g/user_projects/domains/base_domain:/wls11g/user_projects/domains/base_domain/bin:/wls11g/wlserver_10.3/server/bin:/usr/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    -bash-3.00$ java version "1.6.0_18-ea"
    Java(TM) SE Runtime Environment (build 1.6.0_18-ea-b05)
    Java HotSpot(TM) 64-Bit Server VM (build 16.0-b12, mixed mode)
    Starting WLS with line:
    /wls11g/jdk1.6.0_18/bin/java -server -d64 -Xms768m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=6 -XX:+DisableExplicitGC -XX:MaxPermSize=2048m -Dweblogic.Name=instance2 -Djava.security.policy=/wls11g/wlserver_10.3/server/lib/weblogic.policy -da -Dplatform.home=/wls11g/wlserver_10.3 -Dwls.home=/wls11g/wlserver_10.3/server -Dweblogic.home=/wls11g/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=http://140.126.24.25:6001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/wls11g/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
    <Jan 20, 2010 6:02:46 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 16.0-b12 from Sun Microsystems Inc.>
    <Jan 20, 2010 6:02:49 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
    <Jan 20, 2010 6:03:00 PM CST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://140.126.24.25:6001.>
    <Jan 20, 2010 6:03:00 PM CST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Jan 20, 2010 6:03:00 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jan 20, 2010 6:03:00 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jan 20, 2010 6:03:01 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jan 20, 2010 6:03:01 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log00026. Log messages will continue to be logged in /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log.>
    <Jan 20, 2010 6:03:01 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log is opened. All server side log events will be written to this file.>
    <Jan 20, 2010 6:03:16 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jan 20, 2010 6:03:19 PM CST> <Error> <Configuration Management> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://140.126.24.25:6001 during startup. Since bootstrap succeeded check that t3://140.126.24.25:6001 uniquely identifies the administration server.
    javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:430)
    at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
    Truncated. see log file for complete stacktrace
    Caused By: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
    at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
    at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:429)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:426)
    Truncated. see log file for complete stacktrace
    >
    <Jan 20, 2010 6:03:19 PM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:430)
    at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
    at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:173)
    at weblogic.server.channels.RemoteChannelServiceImpl.registerForever(RemoteChannelServiceImpl.java:146)
    at weblogic.protocol.ConnectMonitorFactory.registerForever(ConnectMonitorFactory.java:88)
    at weblogic.management.provider.MSIService.registerForReconnectToAdminServer(MSIService.java:174)
    at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.start(CompatibilityMBeanServerService.java:154)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
    at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
    at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:429)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:426)
    ... 9 more
    >
    <Jan 20, 2010 6:03:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jan 20, 2010 6:03:19 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jan 20, 2010 6:03:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    -bash-3.00$
    Edited by: user7322888 on 2010/2/4 下午 11:41

    Hi,
    Reproducing this issue is very easy.....
    1). Just Create a Admin and Managed Server
    2). Start AdminServer then from Admin Console Disable the normal listen-port for admin Server (suppose it was 7001 disable it)....AND enable only the SSL port for Admin Server (example 7002).
    Managed Server (Listen Port=7003 and SSL ListenPort=7004)
    3). Now Try Start Managed Server.
    you wil get the Exact same exception
    <Jan 20, 2010 6:03:19 PM CST> <Error> <Configuration Management> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://140.126.24.25:6001 during startup. Since bootstrap succeeded check that t3://140.126.24.25:6001 uniquely identifies the administration server.
    javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.]
    And
    <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://140.126.24.25:6001.>
    Now it will be easy for us to find out where is the issue actually.
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
    Edited by: Jay SenSharma on Feb 24, 2010 4:15 PM

  • 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

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

  • Weblogic deployment ( admin and managed server)

    I have one AdminServer and One ManageServer running on the same IP Address with
    different ports,
    AdminServer and ManagedServer is coming up without any errors, I able to access
    the index.jsp using the following URLs
    http://hostname:7001/index.jsp (Admin Server)
    http://hostname:8001/index.jsp (Managed Server)
    my index.jsp I have several other hperlinks ( say contacts, help etc)
    Once my servers ( admin and managed ) are started successfully, I'm able to browse
    thru my application using the first URL.
    but if I accessed the application using the second URL the index.jsp is coming
    from port no (8001), which I observed thru the access.log and if I click any other
    links(contacts, help) in the index.jsp, it is access the jsps from (7001) instead
    of 8001.
    I think in my Jsp I'm using a wrong mechanism to read the URL, what is the proper
    way to read the correct URL?
    Please help me to sort out this issue

    Tested and got it worked.

  • Null argument for startup classes when managered server starts

    Hi Everyone,
    We have a Weblogic 10.3.5 clustering environment. the environment seems to work fine. I am able to have the servers (both Admin and Managed) and deployed applications running without any problems. However, I just notice that, every time when I start the Managered servers, I got the following information in the system log. It appears that they are start-up classes, but with null argument. Are they normal or not?
    Thanks in advance,
    John
    ####<Feb 22, 2012 11:28:27 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928107258> <BEA-000256> <Invoking oracle.dms.wls.DMSShutdown.main(null)>
    ####<Feb 22, 2012 11:28:27 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928107769> <BEA-000256> <Invoking oracle.ias.cache.Shutdown.main(null)>
    ####<Feb 22, 2012 11:40:08 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928808600> <BEA-000256> <Invoking oracle.jrf.wls.JRFStartup.main(null)>
    ####<Feb 22, 2012 11:40:08 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928808682> <BEA-000256> <Invoking oracle.security.jps.wls.JpsWlsStartupClass.main(null)>
    ####<Feb 22, 2012 11:40:08 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928808790> <BEA-000256> <Invoking oracle.core.ojdl.weblogic.ODLConfiguration.main(null)>
    ####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817314> <BEA-000256> <Invoking oracle.jrf.AppContextStartup.main(null)>
    ####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817318> <BEA-000256> <Invoking oracle.as.jmx.framework.wls.spi.StartupListener.main(null)>
    ####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817432> <BEA-000256> <Invoking oracle.j2ee.ws.server.WebServiceServerStartup.main(null)>
    ####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817492> <BEA-000256> <Invoking oracle.ias.cache.Startup.main(null)>
    ####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817493> <BEA-000256> <Invoking oracle.dms.wls.DMSStartup.main(null)>
    ####<Feb 22, 2012 11:40:18 AM EST> <Info> <Management> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928818207> <BEA-141278> <Java entropy configuration is: System property "java.security.egd= null"; JRE's java.security file property "securerandom.source= file:/dev/urandom"; Blocking Config= false; JDK version= 1.6.0_26; Operating System= Linux.>
    ####<Feb 22, 2012 11:40:48 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928848987> <BEA-000256> <Invoking oracle.security.audit.ajl.loader.JEEAuditLoader.main(null)>

    Hi John,
    This is Ok. Those are just info messages. Thery are not warnings or errors, so nothing to worry about.
    If the classes are invoked with null arguments and no exception is thrown, then is means that the class is able to have a null argument, so nothing to worry about again.
    Regards,
    Cris

  • Warning message at managed server start up for an EAR application

    Hi all, I have an wli <b>cluster 8.1 sp3 running on AIX</b> machines. When i deploy an <u>webservice application</u> (ear) i get an exception in the node which does not host admin server. The strange thing is that the application seems to be deployed correctly. My suspicion, about the exception, is the it's caused by the different directory structure of the two nodes. As you can see at bold words, weblogic tries to create ear at a directory that does not exist at this node. It finds the latter webbus from the path of admin server at the other machine. My question is straightforwad, Can we have different paths at cluster nodes ? In this case, Should we deploy ear (webservice application) in a different way ? <Feb 22, 2005 12:33:26 PM EET> <Info> <Deployer> <BEA-149060> <Module faxManWeb of application faxManAppl successfully transitioned from prepared to active on server wliBusServerPatmosDevel.> <b>javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear</b> at weblogic.management.internal.BootStrap.apply(BootStrap.java:580) at weblogic.management.internal.BootStrap.apply(BootStrap.java:474) at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3476) at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code)) at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code)) at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code)) at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543) at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71) at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999) at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290) at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721) at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094) at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976) at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751) at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359) at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361) at weblogic.Server.main(Server.java:32) --------------- nested within: ------------------ weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception: [javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear] at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3479) at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code)) at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code)) at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code)) at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543) at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71) at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999) at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290) at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721) at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094) at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976) at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751) at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359) at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361) at weblogic.Server.main(Server.java:32)

    Hi,
    The problem is that the <b>directory /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/</b> does not exist at the node, because we have move it to <b>/appl/webdbus/</b> instead of <b>/appl/webbus/</b>. The question is why applications need to create adminServerDevel/upload directory and how can override it.
    Thanks in advanced

  • Weblogic 6.0 SP1 default server starting problem

    Hi
    After I successfully installed WLS6.0SP1 on solaris, I was trying to run the default
    server as mentioned in your post-installation tasks. I am getting the following
    error:
    <Apr 11, 2001 12:11:33 PM PDT> <Error> <HTTP> <[Default WebApp] failure extracting
    WAR classes java.io.FileNotFoundException: /var/tmp/WEB-INF/_tmp_war_myserver_myserver_wl_ma
    nagement_internal2/weblogic/management/servlet/BootstrapServlet.class (Permission
    denied)
    at java.io.FileOutputStream.open(Native Method)
    However I can see the index page at port 7001 and also see the console thro' the
    browser.
    So I am not sure if or not I should ignore the above problem
    Please let me know
    thanx

    This solution was emailed to me by WebLogic and it works.
    Yes, I do have a fix for your issue. You received that
    exception because there was an attempt to run multiple
    instances in a single machine.
    By default, WLS 6.0 creates some temporary files
    in system swap space at /tmp/WEB-INF. The becomes
    a conflict if multiple users try to fire up WLS instances.
    Please add the following parameters into your startup
    script.
    Example:
    -Djava.io.tmpdir=/var/tmp/userid property
    java -ms64.... -classpath $CLASSPATH ..... -Djava.io.tmpdir=/export/home/chunan/tmp....
    For production, please keep the default.
    If you still need to run multiple instances for production,
    you may point it back to /tmp (system swap) to reduce
    hard disk delay.
    Chunan
    BEA Support Team
    "Santosh Joglekar" <[email protected]> wrote:
    >
    Hi
    After I successfully installed WLS6.0SP1 on solaris, I was trying to
    run the default
    server as mentioned in your post-installation tasks. I am getting the
    following
    error:
    <Apr 11, 2001 12:11:33 PM PDT> <Error> <HTTP> <[Default WebApp] failure
    extracting
    WAR classes java.io.FileNotFoundException: /var/tmp/WEB-INF/_tmp_war_myserver_myserver_wl_ma
    nagement_internal2/weblogic/management/servlet/BootstrapServlet.class
    (Permission
    denied)
    at java.io.FileOutputStream.open(Native Method)
    However I can see the index page at port 7001 and also see the console
    thro' the
    browser.
    So I am not sure if or not I should ignore the above problem
    Please let me know
    thanx

Maybe you are looking for