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.

Similar Messages

  • Error in Admin and manager server startup - BEA-149205-  due to error weblogic.security.internal.encryption.EncryptionServiceException

    Hi -
    I have installed OIM 11g r2 ps2, I an tring to start my Admin and SOA server :
    1. Though my admin server is coming up fine, but I am getting the following error when I am trying to start Admin server.
    ####<Apr 22, 2015 12:22:27 AM PDT> <Error> <Deployer> <devoimx003> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS
    Kernel>> <> <> <1429687347654> <BEA-149205> <Failed to initialize the application 'opss-DBDS' due to error weblogic.security.internal.encryption.EncryptionServiceException.
    weblogic.security.internal.encryption.EncryptionServiceException
            at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
            at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
            at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
            at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
            at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
            at weblogic.j2ee.descriptor.wl.JDBCDriverParamsBeanImpl.getPassword(JDBCDriverParamsBeanImpl.java:337)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.getDriverProperties(DataSourceConnectionPoolConfig.java:368)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig$2.run(DataSourceConnectionPoolConfig.java:304)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.initJDBCParameters(DataSourceConnectionPoolConfig.java:300)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.access$000(DataSourceConnectionPoolConfig.java:24)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig$1.run(DataSourceConnectionPoolConfig.java:78)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.getPoolProperties(DataSourceConnectionPoolConfig.java:75)
            at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1329)
            at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:176)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:507)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:428)
            at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:280)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
            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:45)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
            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.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
            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:180)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
            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.security.internal.encryption.EncryptionServiceException
            at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
            at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
            at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
            at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
            at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
            at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
            at weblogic.j2ee.descriptor.wl.JDBCDriverParamsBeanImpl.getPassword(JDBCDriverParamsBeanImpl.java:337)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.getDriverProperties(DataSourceConnectionPoolConfig.java:368)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig$2.run(DataSourceConnectionPoolConfig.java:304)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.initJDBCParameters(DataSourceConnectionPoolConfig.java:300)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.access$000(DataSourceConnectionPoolConfig.java:24)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig$1.run(DataSourceConnectionPoolConfig.java:78)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jdbc.common.internal.DataSourceConnectionPoolConfig.getPoolProperties(DataSourceConnectionPoolConfig.java:75)
            at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1329)
            at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:176)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:507)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:428)
            at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:280)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
            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:45)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
            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.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
            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:180)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
            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)
    2. My SOA server is coming up but in admin mode and giving OPSS connections errors.
    Any help is really appreciated!
    Thanks,
    SK

    Hi Faisal -
    is your domain in development mode or production mode?
         - While configuring my domian , I had selected Prod Mode, but pon start up when I see in admin server console, it is starting in developement mode already ?
    Any idea how, why ?
    if its production mode you can switch to development mode, change all the credentials in the config.xml and configurations under sub folders to cleartext and start the server..
    - Let me still try these and get back to you.
    Thanks,
    SK

  • WebService URL in Admin and Managed Server????

    All,
    WLS configuration:
    Admin Server:7001
    Managed Server:7003
    Both Admin and Managed Servers reside in the same machine.
    Which is the correct URL for accessing the webservice?
    http://localhost:7001/test/testWebService?WSDL
              OR
    http://localhost:7003/test/testWebService?WSDL
    WLS configuration:
    Admin Server:7001
    Managed Server:7003
    Managed Server:7004
    Both Admin and the 2 Managed Servers reside in the same machine.
    Two managed Servers form the cluster.
    What will be the correct URL to access the webservice
    http://loclahost:XXXX/test/testWebService?WSDL
    what is XXXX???
    Thanks
    Jay

    Services will be deployed in managed servers only.
    Then in the first case it will be
    http://localhost:7003/test/testWebService?WSDL
    In the second case, wherein 2 Managed servers are there.
    What will be the accesing webservice URL?? when the services are deployed in both.
    Will the admin server redirect the requests to the managed servers??
    How do I access???
    Thanks
    Jay

  • WLS Admin and managed server startup issue

    Hi ,
    In one of WLS Domain both the Admin Server and Managed Server startup is just hanging at the below mentioned point :
    <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    After this there are no error messages or logs being generated and the server start up is not proceeding .
    Only message shown a while after this is :
    Warning : domain runtime mbean server has not been found after trying for 600 seconds
    Please provide some inputs on how to troubleshoot this issue .
    Checked the AdminServer.log and there are no errors reported there as well .
    Some more data from AdminServer.log :
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448845368> <BEA-090516> <The Authenticator provider has preexisting LDAP data.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448845632> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846193> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846208> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846433> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm myrealm.>
    <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846433> <BEA-090082> <Security initializing using security realm myrealm.>
    Thanks
    Srinath
    Edited by: Srinath Menon on May 8, 2012 9:36 AM

    Hi Ashish ,
    Thanks for the inputs.
    Tried the same steps as mentioned but the issue still remains like that .
    Posting the thread dump collected for AdminServer:
    ===== FULL THREAD DUMP ===============
    Tue May 8 10:04:58 2012
    Oracle JRockit(R) R28.1.3-11-141760-1.6.0_24-20110301-1430-linux-ia32
    "Main Thread" id=1 idx=0x4 tid=9341 prio=5 alive, waiting, native_blocked
    -- Waiting for notification on: weblogic/t3/srvr/SubsystemRequest@0x9f81d3c0[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
    at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
    at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at weblogic/t3/srvr/SubsystemRequest.rendezvouz(SubsystemRequest.java:100)
    ^-- Lock released while waiting: weblogic/t3/srvr/SubsystemRequest@0x9f81d3c0[fat lock]
    at weblogic/t3/srvr/SubsystemRequest.action(SubsystemRequest.java:81)
    at weblogic/t3/srvr/SubsystemRequest.start(SubsystemRequest.java:51)
    at weblogic/t3/srvr/ServerServicesManager.startService(ServerServicesManager.java:459)
    at weblogic/t3/srvr/ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    ^-- Holding lock: java/lang/Class@0x9fa95598[biased lock]
    at weblogic/t3/srvr/T3Srvr.initializeStandby(T3Srvr.java:879)
    at weblogic/t3/srvr/T3Srvr.startup(T3Srvr.java:566)
    at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:467)
    at weblogic/Server.main(Server.java:71)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "(Signal Handler)" id=2 idx=0x8 tid=9342 prio=5 alive, native_blocked, daemon
    at <unknown>(???.c)@0xb7fe9410
    at sigiSignalHandlerThread+135(signalhandler.c:131)@0xb7ec2fd8
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(OC Main Thread)" id=3 idx=0xc tid=9343 prio=5 alive, native_waiting, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
    at nativeWait+71(nativelock.c:721)@0xb7e79008
    at ocMainThread+663(gcthreads.c:581)@0xb7d8a098
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(GC Worker Thread 1)" id=? idx=0x10 tid=9344 prio=5 alive, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
    at eventWaitNoTransition+32(event.c:62)@0xb7d6bc31
    at mmGCWorkerThread+134(gcthreads.c:797)@0xb7d89d67
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(GC Worker Thread 2)" id=? idx=0x14 tid=9345 prio=5 alive, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
    at eventWaitNoTransition+32(event.c:62)@0xb7d6bc31
    at mmGCWorkerThread+134(gcthreads.c:797)@0xb7d89d67
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(Code Generation Thread 1)" id=4 idx=0x18 tid=9348 prio=5 alive, native_waiting, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
    at nativeWait+71(nativelock.c:721)@0xb7e79008
    at cg_thread+380(compilerqueue.c:203)@0xb7d4be5d
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(Code Optimization Thread 1)" id=5 idx=0x1c tid=9349 prio=5 alive, native_waiting, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
    at nativeWait+71(nativelock.c:721)@0xb7e79008
    at cg_thread+380(compilerqueue.c:203)@0xb7d4be5d
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "(VM Periodic Task)" id=6 idx=0x20 tid=9350 prio=10 alive, native_blocked, daemon
    at <unknown>(???.c)@0xb7fe9410
    at block_for_safepoint+106(safepoint.c:34)@0xb7ebad5b
    at eventTimedWait+239(event.c:83)@0xb7d6bd30
    at periodic_task_thread+627(periodictask.c:367)@0xb7e90dd4
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "Finalizer" id=7 idx=0x24 tid=9351 prio=8 alive, native_waiting, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
    at nativeWait+71(nativelock.c:721)@0xb7e79008
    at RJNI_jrockit_memory_Finalizer_waitForFinalizees+211(finalhandles.c:1007)@0xb7d751f4
    at jrockit/memory/Finalizer.waitForFinalizees(J[Ljava/lang/Object;)I(Native Method)
        at jrockit/memory/Finalizer.access$700(Finalizer.java:12)
        at jrockit/memory/Finalizer$4.run(Finalizer.java:189)
        at java/lang/Thread.run(Thread.java:662)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        -- end of trace
    "Reference Handler" id=8 idx=0x28 tid=9352 prio=10 alive, native_waiting, daemon
        at <unknown>(???.c)@0xb7fe9410
        at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
        at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
        at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
        at nativeUnlockAndWait+71(nativelock.c:686)@0xb7e790a8
        at RJNI_java_lang_ref_Reference_waitForActivatedQueue+38(semiref.c:342)@0xb7ebd9b7
        at java/lang/ref/Reference.waitForActivatedQueue(J)Ljava/lang/ref/Reference;(Native Method)
        at java/lang/ref/Reference.access$100(Reference.java:11)
        at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:82)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        -- end of trace
    "(Sensor Event Thread)" id=9 idx=0x2c tid=9353 prio=5 alive, native_blocked, daemon
        at <unknown>(???.c)@0xb7fe9410
        at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
        at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
        at eventTimedWait+138(event.c:56)@0xb7d6bccb
        at eventWait+32(event.c:50)@0xb7d6bd81
        at sensor_event_loop+37(sensor.c:68)@0xb7ebfda6
        at thread_stub+146(lifecycle.c:808)@0xb7e2c333
        at start_thread+225(:0)@0x515832
        at __clone+93(:0)@0x46ae0e
    "VM JFR Buffer Thread" id=10 idx=0x30 tid=9354 prio=5 alive, in native, daemon
        at <unknown>(???.c)@0xb7fe9410
        at bufferthread+2135(vmjfr.c:1008)@0xb71744b8
        at run_agent_thread+128(jvmtithreads.c:524)@0xb7e1f361
        at thread_stub+146(lifecycle.c:808)@0xb7e2c333
        at start_thread+225(:0)@0x515832
        at __clone+93(:0)@0x46ae0e
    "Timer-0" id=13 idx=0x34 tid=9358 prio=5 alive, waiting, native_blocked, daemon
        -- Waiting for notification on: java/util/TaskQueue@0x9f9fc350[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
    at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
    at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at java/util/TimerThread.mainLoop(Timer.java:483)
    ^-- Lock released while waiting: java/util/TaskQueue@0x9f9fc350[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "Timer-1" id=14 idx=0x38 tid=9363 prio=5 alive, waiting, native_blocked, daemon
    -- Waiting for notification on: java/util/TaskQueue@0xa20ee240[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/util/TimerThread.mainLoop(Timer.java:509)
    ^-- Lock released while waiting: java/util/TaskQueue@0xa20ee240[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=15 idx=0x3c tid=9364 prio=5 alive, waiting, native_blocked, daemon
    -- Waiting for notification on: netscape/ldap/LDAPResponseListener@0x9724f0c8[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
    at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
    at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at netscape/ldap/LDAPMessageQueue.waitForMessage(LDAPMessageQueue.java:200)
    ^-- Lock released while waiting: netscape/ldap/LDAPResponseListener@0x9724f0c8[recursive]
    at netscape/ldap/LDAPMessageQueue.waitFirstMessage(LDAPMessageQueue.java:101)
    ^-- Lock released while waiting: netscape/ldap/LDAPResponseListener@0x9724f0c8[fat lock]
    at netscape/ldap/LDAPConnection.sendRequest(LDAPConnection.java:1796)
    ^-- Holding lock: netscape/ldap/LDAPConnection@0x9721f310[biased lock]
    at netscape/ldap/LDAPConnection.simpleBind(LDAPConnection.java:1763)
    at netscape/ldap/LDAPConnection.authenticate(LDAPConnection.java:1264)
    at netscape/ldap/LDAPConnection.authenticate(LDAPConnection.java:1273)
    at netscape/ldap/LDAPConnection.bind(LDAPConnection.java:1562)
    at weblogic/security/providers/authentication/LDAPAtnDelegate$LDAPFactory.newInstance(LDAPAtnDelegate.java:4134)
    at weblogic/security/utils/Pool.newInstance(Pool.java:37)
    at weblogic/security/utils/Pool.getInstance(Pool.java:33)
    at weblogic/security/providers/authentication/LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3478)
    at weblogic/security/providers/authentication/LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3470)
    at weblogic/security/providers/authentication/LDAPAtnDelegate.authenticate(LDAPAtnDelegate.java:3522)
    at weblogic/security/providers/authentication/LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:227)
    at com/bea/common/security/internal/service/LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
    at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)
    at jrockit/vm/AccessController.doPrivileged(AccessController.java:268)
    at com/bea/common/security/internal/service/LoginModuleWrapper.login(LoginModuleWrapper.java:106)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java/lang/reflect/Method.invoke(Method.java:597)
        at javax/security/auth/login/LoginContext.invoke(LoginContext.java:769)
        at javax/security/auth/login/LoginContext.access$000(LoginContext.java:186)
        at javax/security/auth/login/LoginContext$4.run(LoginContext.java:683)
        at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)
        at jrockit/vm/AccessController.doPrivileged(AccessController.java:268)
        at javax/security/auth/login/LoginContext.invokePriv(LoginContext.java:680)
        at javax/security/auth/login/LoginContext.login(LoginContext.java:579)
        at com/bea/common/security/internal/service/JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java/lang/reflect/Method.invoke(Method.java:597)
        at com/bea/common/security/internal/utils/Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
        at $Proxy28.login(Ljava/lang/String;Ljavax/security/auth/callback/CallbackHandler;Lweblogic/security/service/ContextHandler;)Lcom/bea/common/security/service/Identity;(Unknown Source)
        at weblogic/security/service/internal/WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
        at com/bea/common/security/internal/service/JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
        at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java/lang/reflect/Method.invoke(Method.java:597)
        at com/bea/common/security/internal/utils/Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
        at $Proxy46.authenticate(Ljavax/security/auth/callback/CallbackHandler;Lweblogic/security/service/ContextHandler;)Lcom/bea/common/security/service/Identity;(Unknown Source)
        at weblogic/security/service/WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
        at weblogic/security/service/PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:348)
        at weblogic/security/service/CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
        at weblogic/security/service/CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
        at weblogic/security/service/SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic/security/SecurityService.start(SecurityService.java:141)
        at weblogic/t3/srvr/SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic/work/ExecuteThread.execute(ExecuteThread.java:207)
        at weblogic/work/ExecuteThread.run(ExecuteThread.java:176)
        at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
        -- end of trace
    "JFR request timer" id=16 idx=0x40 tid=9365 prio=5 alive, waiting, native_blocked, daemon
        -- Waiting for notification on: java/util/TaskQueue@0xa2049280[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
    at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
    at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:485)
    at java/util/TimerThread.mainLoop(Timer.java:483)
    ^-- Lock released while waiting: java/util/TaskQueue@0xa2049280[fat lock]
    at java/util/TimerThread.run(Timer.java:462)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "weblogic.time.TimeEventGenerator" id=18 idx=0x44 tid=9366 prio=9 alive, waiting, native_blocked, daemon
    -- Waiting for notification on: weblogic/time/common/internal/TimeTable@0xa2089c70[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
    ^-- Lock released while waiting: weblogic/time/common/internal/TimeTable@0xa2089c70[fat lock]
    at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)
    at java/lang/Thread.run(Thread.java:662)
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace
    "JMAPI event thread" id=19 idx=0x48 tid=9367 prio=5 alive, in native, daemon
    at <unknown>(???.c)@0xb7fe9410
    at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
    at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
    at innerNativeDoWait+526(nativelock.c:614)@0xb7e78b3f
    at nlMonitorWaitInner+79(nativelock.c:1112)@0xb7e78df0
    at nlMonitorWaitNoTransition+38(nativelock.c:1132)@0xb7e78e47
    at nativeRawMonitorWait+78(rawmonitor.c:161)@0xb7ea8caf
    at jvmti_RawMonitorWait+111(jvmtirawmonitors.c:95)@0xb7e1b420
    at threadProc+291(jmapi.c:305)@0x90452bd4
    at run_agent_thread+128(jvmtithreads.c:524)@0xb7e1f361
    at thread_stub+146(lifecycle.c:808)@0xb7e2c333
    at start_thread+225(:0)@0x515832
    at __clone+93(:0)@0x46ae0e
    "weblogic.timers.TimerThread" id=20 idx=0x4c tid=9368 prio=9 alive, waiting, native_blocked, daemon
    -- Waiting for notification on: weblogic/timers/internal/TimerThread@0xa203dbf0[fat lock]
    at <unknown>(???.c)@0xb7fe9410
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)
    at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:262)
    ^-- Lock released while waiting: weblogic/timers/internal/TimerThread@0xa203dbf0[fat lock]
    at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
    -- end of trace

  • Where to increase Java Heap settings for Admin and Managed Server.

    Hello Experts
    I am having issue with increasing the JVM memory arguments for the Admin and Managed Servers. I have tried in a couple of places to increase the memory arguments (Xms and Xmx to 1024m)but its not taking effect. When I start the Admin Server and Managed server , I do not see the increased Heap settings. Here is what I see -
    "Starting WLS with line : /oracle/app/bi/Oracle_BI1/jdk/java -server - Xms256m -Xmx512m -XX:MaxPermSize=512m"
    I have the following memory arguments in the setDomainEnv.sh located in <DOMAIN_HOME>/bin
    XMS_SUN_64BIT ="2048"
    export XMS_SUN_64BIT
    XMX_SUN_64BIT="2048"
    export XMX_SUN_64BIT
    Looks like this did not work , so I added an entry in the setOBIDomainEnv.sh file hoping to increase the Java memory , but that does not work either. Below is from setOBIDomainEnv.sh file -
    Really, trying to understand where/how the JVM settings are controlled from. Please guide me.
    Appreciate your time.
    Rakesh

    Under setobidomainenv.sh you will also find the admin server tag's so you need to increase the jvm parameters in there too. Depending upon your java vendor and bit version(Sun/Oracle/IBM/HP and 32-bit vs 64-bit ) So change accordingly
    eg:
    if server group is not obi then we can assume that it is Admin Server
      if [ "${JAVA_VENDOR}" = "Sun" ] ; then
      # -UseSSE42Intrinsics required for server running EM
      if [ "${JAVA_USE_64BIT}" = "true" ] ; then
      # Admin Server memory args for 64-bit Sun JVM
      SERVER_MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:-UseSSE42Intrinsics"
      export SERVER_MEM_ARGS
    similarly in setdomain.sh you will find the args as below:
    XMX_SUN_64BIT="512"
    export XMX_SUN_64BIT
    XMS_SUN_64BIT="256"
    export XMS_SUN_64BIT
    if [ "${JAVA_VENDOR}" = "Sun" ] ; then
      WLS_MEM_ARGS_64BIT="-Xms256m -Xmx512m"
      export WLS_MEM_ARGS_64BIT
      WLS_MEM_ARGS_32BIT="-Xms256m -Xmx512m"
      export WLS_MEM_ARGS_32BIT
    after setting them just execute them ./setdomain.sh and ./setobidomainenv.sh and then try to start the admin and managed servers and see the process running with the updated values.

  • Race condition between admin and managed server?

    When I start my managed server, my admin server gets the following complaint
    in its log file:
    Jun 20, 2001 4:39:37 PM PDT Critical Log Management Unable to
    contact managed server - rat5, at 172.16.1.26:7027
    . Domain
    logfile will not contain messages from this server.
    java.lang.IllegalArgumentException: Invalid user name or password
         at
    weblogic.management.logging.DomainLogHandler.getMBeanHome(DomainLogHandler.j
    ava:281)
         at
    weblogic.management.logging.DomainLogHandler.subscribeToServer(DomainLogHand
    ler.java:243)
         at
    weblogic.management.logging.DomainLogHandler.registerToMe(DomainLogHandler.j
    ava:183)
         at java.lang.reflect.Method.invoke(Native Method)
         at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:562)
         at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    48)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at
    weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBean
    ServerImpl_WLSkel.java:382)
         at
    weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at
    weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at
    weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
    java:118)
         at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    7)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    This happens while my managed server is still booting. It isn't listening on
    port 7027 until a few seconds later. In the managed server rat5's log file
    is
    Jun 20, 2001 4:39:58 PM PDT Notice WebLogicServer WebLogic
    Server started
    Jun 20, 2001 4:39:58 PM PDT Notice WebLogicServer ListenThread
    listening on port 7027
    which is 21 seconds after the message in the admin log file. What do I have
    to do to have the admin server wait until the managed server is up before
    contacting it? Am I assessing the problem correctly?

    nope
    a server can be either Admin or Managed, there is no such thing as a Admin+Managed server.
    A domain expects you to specify which instance is an Admin, in config.xml you find
    <admin-server-name>AdminServer</admin-server-name>
    But this is not a problem for you, to all effects a domain without any managed servers and with only 1 Admin is a perfectly legal environment,
    you can deploy your applications to the Admin and be happy.
    Actually this is a common setup for Development environments.
    Of course in production you want to set up a proper environment with cluster etc....

  • Starting Admin and Managed Server on Same Machine

    Has anyone come across a method of running both their admin server and managed
    servers as a Service and on the same machine. As you can see, when the OS comes
    up both Services for the servers will be started. I can put in a dependency on
    the managed server saying that the admin server needs to be started but that doesn't
    guarantee that admin server will be ready for "prime time."
    I have seen somewhere in a support message something about a "depend" and "delay"
    flag for the beasvc.exe program but the one I'm using doesn't seem to support
    this.
    Here is my setup:
    Windows 2000 Pro
    Weblogic Server 6.1 SP1
    Any assistance is appreciated,
    Rich

    John Hufnagle wrote:
              > Is it possible to run cluster admin server and one of the managed servers on the
              > same machine...(just preserving machine resources for in-house testing).
              As Kumar said, it is possible to run the admin server and one (or more) managed servers
              on the same machine.
              >
              >
              > If the admin listens on 7001/7002 can I just set up the managed server to 7003/7004
              > or will I also run into problems with the multicast address?
              Since the admin server is not part of the cluster, it is perfectly fine to use a
              different set of ports for the managed servers as long as all servers in the same
              cluster use the same ports...
              Hope this helps,
              Robert
              

  • Admin and Managed Server on same machine

              Is it possible to run cluster admin server and one of the managed servers on the
              same machine...(just preserving machine resources for in-house testing).
              If the admin listens on 7001/7002 can I just set up the managed server to 7003/7004
              or will I also run into problems with the multicast address?
              

    John Hufnagle wrote:
              > Is it possible to run cluster admin server and one of the managed servers on the
              > same machine...(just preserving machine resources for in-house testing).
              As Kumar said, it is possible to run the admin server and one (or more) managed servers
              on the same machine.
              >
              >
              > If the admin listens on 7001/7002 can I just set up the managed server to 7003/7004
              > or will I also run into problems with the multicast address?
              Since the admin server is not part of the cluster, it is perfectly fine to use a
              different set of ports for the managed servers as long as all servers in the same
              cluster use the same ports...
              Hope this helps,
              Robert
              

  • 10.3 registering Admin and Managed server as windows service.

    I have not found anything in the new documentation on how to do this which left me wondering if there is a reason it was omitted? I found procedures from the 8.1 docs but would rather have something more up to date. I'm installing on win 2003 server. Thank you.
    Edit: I found the installSvc.cmd script in the %wlshome%\server\bin directory and tried it. According to instructions you set SERVER_NAME and then call the script. It seems to install the services ok but when I start them they stop immediately with no specific errors in event viewer.

    Dear,
    I assume you now have at least 3 windows services:
    -node manager service
    -adminserver service
    -1 or more service for your managed servers (which start after adminserver service)
    All of them start on system startup.
    My question: If let's say one managed server crashes, is it then automatically restarted by the nodemanager? Since the managed server is not started by node manager itself, I guess the answer is no. If so, what is the usage of having nodemanager running as a service?
    Thanks.

  • How to start admin and manage server

    I can able to start admin server but I want to start admin & manage both the server . Please tell me the solution for this problem .
              

    Your managed Server must have a different listen Port than the admin
              instance.
              "prashant parab" <[email protected]> a écrit dans le message news:
              3bca85c2$[email protected]..
              > I can able to start admin server but I want to start admin & manage both
              the server . Please tell me the solution for this problem .
              

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

  • How to setup WebLogic Admin Server and Managed Server

    Hi,
    I working to setup a Weblogic admin and managed server but fail.
    May i know the correct steps to setup the system ?
    Tx.

    TX. I will proceed to upload more logs here later.
    Anyway I notice that after i follow the guide to setup the admin and managed server, I only able to access the web apps on admin server. I can not access web apps for managed server.
    I setup the admin server using port 7001 and managed server using port 7003 based on oracle guide.
    I found weird here. when I browse to http://adminserver:7001/apps, it works. But when i browse to http://managedserver:7003/apps it does not work.
    But funny thing is when i browse to http://adminserver:7003/apps, it works.
    I confuse that which configuration I have done is incorrect and have this result???
    besides that I notice that in the nodemanager setting...the listening address is set to localhost and it works. If i configure it to IP address, it will give me errors.
    Edited by: Wilson78 on Dec 22, 2008 12:29 PM

  • Problem creating a domain w/ one Admin Server and Managed Server

    I went through the config wizard (Weblogic 10.2) and set up a domain w/ 1 Admin Server and Managed Server. When I start the Admin server I get the following error:
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Store> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
    weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:105)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
    weblogic.management.DeploymentException:
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:60)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <JMS> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
    weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-141197> <The deployment of pfJMSServer failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:198)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Deployer> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328461> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
    weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
         at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
         at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
         at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
         at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
         at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
         at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
         at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1633)
         at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
         at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1809)
         at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:609)
         at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
         at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
         at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
         at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >

    I am using the default db the installation uses which is PointBase. I am not using any specific db, JDBC Datasource/Connection pool Configuration.
    Just to try something different, I tried creating a domain w/ one Admin and Managed Server which uses a Cluster and I did not get any errors. From what I read, a cluster is not necessary but not sure why it works without errors w/ a cluster.
    I will try commenting out the datasource from the config and see what happens and will let you know.

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

  • Deploy to single managed server checked and greyed out while performing upgrade to EPM 11.1.2.4

    Hi Gurus,
    We are trying to upgrade EPM from 11.1.2.2 to EPM 11.1.2.4 and have applied the maintenance release successfully.
    Issue:
    When we are trying to configure EPM 11.1.2.4 and are providing the same Shared Service database details, at the summary screen, we are not able to uncheck the option "Deploy to Single Managed server" which is checked and is greyed out.
    We have tried the following:
    1. We updated the HSS_COMPONENT_PROPERTY_VALUE table  and updated the PROPERTY_NAME "isCompact" to false.
    2. Modified the config.xml file located at EPMSystem/config and epmsystem1/config to remove the property for compactState.
    We are still having the issue where we are not able to uncheck the option for Compact Deployment. Any help would be appreciated.
    Thanks in advance.

    As it is a maintenance release and it deployed as a single managed server then you will not be able to change the deployment type when applying the maintenance release.
    There is a procedure to change a deployment type from compact to single managed server that I created as an internal document.
    you may want to give it a go but you would need to test this first as this was an in house test that I carried out.
    Hyperion Planning - Version 11.1.2.2.300 and later
    Information in this document applies to any platform.
    Goal
    The scenario:
    EPM system 11.1.2.3 was configured and deployed as a single managed server compact deployment so that only one JVM was used for all products EPMServer0.
    Later on, due to performance issues, the decision was made to go for using a JVM for each product and get rid of the compact deployment.
    The administrator went ahead and redeployed the application servers individually into their own JVM.
    However everytime the webserver is reconfigured, the weblogicCluster entry in the OHS file mod_wl_ohs has 2 servers, one for EPMSserver running on port 9000 and another server running on the product default port (as if it was being load balanced)
    The aim:
    It is clear that initial compact deployment has not been cleared from the EPM environment and the aim in this exercise is to clear the registry and the file system so that the compact deployment is removed fromthe EPMenvironment and we are left with the desired configuration Single JVM deployment for earch web application.
    Solution
    Caution:
    Make sure that you take a backup of the following:
    - TheFoundation Services database schema backup
    - Take a backup of the following folders:
    \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
    \Oracle\Middleware\user_projects\domains\EPMSystem\servers
    \Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
    Disclaimer:
    This was tested in House and it worked for this specific environment and it may not work for your environment. So the suggestion is to test first in a development environment and make sure that you take the appropriate backups in case it does not go according to plan.
    Use at your own discretion.
    Procedure:
    1- Run the epmsys_registry to generate the Registry report
    2- Search through the report for the word applicationServerDeployment with a corresponding value of configured and take the ObjectID number down for any entry of applicationServerDeployment that has a value of Configured
    i.e:
    Instance Tasks Configuration (INSTANCE_TASKS_CONFIGURATION)
    Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7adf
    3- use the object ID of each entry you have taken down throughout the Registry HTML Report to manually set it back to Pending using the following procedure:
                    Start a command prompt and set the working directory to
                     \Oracle\Middleware\user_projects\epmsystem1\bin
                    run the command:
                     epmsys_registry.bat updateproperty #e4b3a86a82c26941S32ef81a1455fe48473S7adf/@applicationServerDeployment=Pending
                    Repeat this command for each ObjectID that has its applicationServerDeployment
                     property set to Configured
    4- rerun the epmsys_registry.bat to generate the Registry HTML report and search for applicationServerDeployment in the newly generated report to make sure that they are all set to Pending and there none missed (very Important).
    5- Search the registry HTML report this time for EPMServer0 which is the default serverName given to the single managed server deployment (there will be multiple entries)
    Take note of the first ObjectID entry in the section header: for example
    WORKSPACE_WEBAPP (WORKSPACE_WEBAPP)
    Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Start a command prompt and set the working directory to
                     \Oracle\Middleware\user_projects\epmsystem1\bin
    - run the command:
                     epmsys_registry.bat view #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    -Note the Parents ID in the output:
    For example:
    Parent 1
    NAME -  WORKSPACE_LWA
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    TYPE -  LOGICAL_WEB_APP
    Parent 2
    NAME -  HOST:BACHVMPS3TR
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7ffe
    TYPE -  HOST
    - Note the single child ID:
    For Example:
    Child 1
    NAME -  WebLogic 10
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7fd6
    TYPE -  APP_SERVER
    Now run the following command to remove the Link between Parent and child:
    epmsys_registry removelink #parentObjectID #childObjectID
    In this example that would translate to:
    To remove the single child1 link to the WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ):
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd3 #e4b3a86a82c26941S32ef81a1455fe48473S7fd6
    And do the following To remove the link between WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ) and Parent1 and Parent2:
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7ffe
    #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Now that the link has been removed, delete the WORKSPACE_WEBAPP component using its ObjectID :
    epmsys_registry deletecomponent #parentObjectID
    In this example:
    epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Delete also the Parent representing the WORKSPACE_LWA
    epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    Note:So we have now deleted the WEBAPP and LWA for workspace.
    6- Repeat steps in section No 5 for every WEBAPP with EPMServer0
    7- Start the Weblogic admin console and login
    Then go to the left panel and Expand Environment -> Server
    Click on Lock & Edit -> Select EPMServer0 -> click on Delete and confirm
    Activate Changes and Log off
    8- Stop the weblogic admin console server
    9- Go to the following location and delete the folder EPMServer0:
    \Oracle\Middleware\user_projects\domains\EPMSystem\servers
    Delete also EPMServer0 from the following location:
    \Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
    10- Start a command prompt and delete the Windows service that was created for EPMServer0 (if using Microsoft Windows Operating System):
    Right click on the service 'OracleHyperion EPM Server - Java Web Application (epmssystem1)' and get its service name i.e: HyS9EPMServer_FOUNDATION1
    Run the following command: sc delete HyS9EPMServer_FOUNDATION1
    11- Launch the EPMSystem configurator and redeploy the web application server to their own JVM
    12- Go to the following location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component and rename the file mod_wl_ohs.conf to mod_wl_ohs.conf.old.
    13- Copy the unconfigured mod_wl_ohs.conf file from the location C:\Oracle\Middleware\ohs\ohs\conf to the location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
    14- Run the EPM System Configurator again and configure the WebServer to reconfigure the OHS configuration file mod_wl_ohs.conf.
    Once done then open the mod_wl_ohs.conf file and make sure that there are no servers configured with Port 9000.
    15- Start the services and test the workspace

Maybe you are looking for

  • Send remittance advice by email to vendors

    When automatic payment (F110) run is done to make payment to vendors,it generates a PAYEXT IDOC to be send to bank for payments. Print output program is RFFOEDI1 Remittance advice standard SAP script is F110_IN_AVIS. What are the ways to send email i

  • How to create hyperlinks in Acrobat 9 Pro?

    Hi everyone, Is there a way to create hyperlinks from within Acrobat 9 Pro? If so, can you let me know how? I am having a hard time finding out how to do so. Thank you in advance for your help:) Christine

  • Inner thread question

    class A { getName(){} setName(){} class B extends A{ private class innerClass extends Thread{ run(){ getName() setName() The problem is that calling getName from inner class will use the getName from Thread beacuse that is it's super. How do I specif

  • Mac Mail crashing after Mavericks upgrade

    My Macbook Pro 15 Retina, mail keeps crashing and I am unable to open any mail from my inbox. No sooner, I click a message the following error is thrown, and even cannot open Appstore or Terminal. Any help is much appreciated. =========== Process:   

  • What happens if i sync two desktop firefoxes? Will my bookmarks be organised by computer or will there be duplicates?

    How to set up firefox sync is well described, but there is hardly any information on what happens after setup. I have two computers with different bookmarks and settings and i want to keep it that way, but i would still like to have access to the oth