Shutdown(block='false') only works via Admin Server, not managed servers

Hello,
We want to shut down all 10 managed servers in our domain gracefully, and in parallel. 5 of those managed servers are on the same OS/host as the AdminServer, the other 5 are on a separate OS/host (i.e. we have 5 x 2-node clusters).
I'm writing scripts to gracefully shut down all of our servers upon an OS reboot command. On the OS with the AdminServer (and 5 managed servers), I can simply do this:
connect(user, pwd, http://localhost:7001)
shutdown('myserver1', 'Server', block='false')
shutdown('myserver3', 'Server', block='false')
shutdown('myserver5', 'Server', block='false')
shutdown('myserver7', 'Server', block='false')
shutdown('myserver9', 'Server', block='false')
All 5 servers will be shutting down at the same time. If they each took 2 minutes to shut down, the whole shutdown process would take 2 minutes.
However, on the OS running the other managed servers, I cannot assume that the AdminServer [on the other OS] will be online. Hence, I would like to gracefully shut down each server locally like this:
connect(user, pwd, url='t3://localhost:8001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:9001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:10001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:11001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:12001')
shutdown(block='false')
disconnect()
NOTE that the ports are different (i.e. I connect via WLST to the managed servers themselves rather than to the AdminServer).
Unfortunately, in this scenario, the block='false' does not work. WLST waits until the managed server is shut down before proceeding to the next connect() command. So if each server took 2 minutes to shut down, the whole shutdown process now takes 10 minutes.
We don't want to use the nmKill() command on the local Node Manager because we want a graceful shutdown.
What options do we have to issue a graceful shutdown command either to a local Node Manager or to the managed servers themselves (since we can't expect the AdminServer to be online when our script runs)?
Best regards,
Michael

Hi Mike,
WLST will create it temp directory with /var/tmp/wlstTemp which is shared by all users. Since we cannot differentiated by different users which cause block on particular user at that time.
One solution is to grant write access to all users to the directory where the WLST temporary directory is created (e.g. on Solaris /var/tmp; you can verify the default on your system by executing java utils.getProperty and search for java.io.tmpdir).
If for whatever reason you cannot grant these access modes on the temporary directory, then you can create a directory somewhere on the file system where every user has the correct permissions.
Start the scripting tool with one the following options to redirect the cache files to the specified directory. Dependent on your environment one or the other will apply.
java -Djava.io.tmpdir=<path-to-tmpDir> weblogic.WLST
or
java -Dpython.cachedir=<path-to-tmpDir> weblogic.WLST
This will be useful to make shutdown of servers without any problem.
Note: block=false will always works it should not be the problem.
Regards,
Kal

Similar Messages

  • Creating Weblogic domain with Admin Server and managed servers on different

    I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.

    Whilst the method that Lawrence gives can result in a domain that is perfectly functional, it is a method that can result in errors as you are having to enter the same information twice. Also you will create two admin servers, as the second domain creation will have the console added to it on the renamed admin server and this will give issues.
    The best method to create a domain spamming multiple physical machines, is to create the domain with all the components on the first machine. This means planning the domain and making sure all components are added once; so having the information about the domain written out is wise. Ensure that the WLS software is installed in the same path on each machine before starting.
    Then copy the domain that you have created from one machine to the other, keeping the same paths. You can simply copy (I've used this method multiple times without issue) but the supported way would be to use the WLST PACK and UNPACK methods. These create and extract domains from templates. Some more information on these is given here -> http://docs.oracle.com/cd/E13179_01/common/docs100/pack/intro.html#wp1069056

  • Admin server looses managed servers

    we hava 2 clusters of 2 wls 6.1 sp2 instances each on 2 hpux 11 boxes. The wls console
    shows all the instances when booted up. But suddenly, after a period( and this random
    without a pattern), the admin seems to loose some of the managed servers. The console
    does not show them running but if I ping the server it is there and applications
    on those 'lost' instances are responding. We are not able to predict this beheaviour.
    We are still trying to device a way to identify when it happens. When this happens
    applications work properly but new deployments are not possible and we have to recycle
    the 'lost' managed instances. Obvoiusly we are not able to look at any stats for
    monitoring from the console.
    Has anybody experienced something like this.
    thanks
    Devaraju, Sushant

    I was just getting ready to post for an exact same symptom (scary).
    Only difference is that I am running WLS 6.1 on Compaq Tru64 (unix).
    Appreciate any help on where to start.
    Sushant: Pls post (or email) any responses or resolution.
    Thanks-
    Rama
    "sushant" <[email protected]> wrote:
    >
    we hava 2 clusters of 2 wls 6.1 sp2 instances each on 2 hpux 11 boxes. The
    wls console
    shows all the instances when booted up. But suddenly, after a period( and
    this random
    without a pattern), the admin seems to loose some of the managed servers.
    The console
    does not show them running but if I ping the server it is there and applications
    on those 'lost' instances are responding. We are not able to predict this
    beheaviour.
    We are still trying to device a way to identify when it happens. When this
    happens
    applications work properly but new deployments are not possible and we have
    to recycle
    the 'lost' managed instances. Obvoiusly we are not able to look at any stats
    for
    monitoring from the console.
    Has anybody experienced something like this.
    thanks
    Devaraju, Sushant

  • Nano only works via mains charger then freezes when unplugged....

    Could use someones wise advice please!
    My nano is just over 1yr old, worked fine until recently. I have tried the 5 r's, software is upto date, battery is fully charged, only works via mains charger but when i disconnect it, it freezes with a line through the screen. Connect it to charger, it is fine again.
    Via pc usb, the apple logo comes on then it goes black then logo then black screen etc seems it almost boots up but just quite doesnt.
    I have found if you hold ccentre button & left scroll button you access an engineers menu, been through all this and it seems fine. Any help would be cool

    If the iPod functions normally while plugged into an external power source of some sort (either USB port on your PC or Mac OR while plugged into a wall adapter), but doesn't when running on battery power, it's likely that the iPod's battery is shot.
    You can have Apple or a third party repair center replace the battery for a flat fee. Otherwise, it's time to start saving for a new iPod or replacement.
    B-rock

  • Cloned OMS - WebLogic Admin Server not available....

    Greetings,
    We are working our way through an active active R4 OMS setup, and we just successfully cloned oms1 to oms2 via cloud control, and executed the post install steps. We now need to access each of the OMSs WebLogic Admin Server Console to confirm LDAP settings, and the oms2 WebLogic Admin Server Console is unavailable. The oms2 clone has the same WebLogic Admin Server details as oms1 (see below).
    Is that by design, i.e. only one WebLogic Admin Server Console with two load balanced OMSs?
    Which files do we need to edit on oms2 to get oms2's WebLogic Admin Server on-line?
    oms1:
    /u01/app/oracle/product/middleware_r4/oms/bin/emctl status oms -details
    WLS Domain Information
    Domain Name            : GCDomain
    Admin Server Host      : oms1.mastec.com
    Admin Server HTTPS Port: 7102
    Admin Server is RUNNING
    oms2:
    WLS Domain Information
    Domain Name            : GCDomain
    Admin Server Host      : oms1.mastec.com
    Admin Server HTTPS Port: 7102
    Thank you,

    The WLS admin server only exists on the first OMS host. Usually an SLB is used for load balancing.
    For information on HA (High Availability) solutions, see:
    http://docs.oracle.com/cd/E24628_01/install.121/e24089/ha_intro.htm#EMADV9611
    Regards,
    - Loc

  • Different service packs in admin server and managed server

    Hi,
    Has anybody successfully used a WebLogic 6.1 SP1 managed server that
    connects to a WebLogic 6.1 SP 2 admin server?
    BEA's docs claim:
    "The Administration Server must be running the same version of
    WebLogic Server as the Managed Servers in its domain. The
    Administration Server must also have the same or later service pack
    installed as the Managed Servers in its domain. For example, the
    Administration Server could be running version 6.1, Service Pack 2
    while the Managed Servers are running version 6.1, Service Pack 1."
    This is precisely what we want to do, but it's not working. In this
    case, we need to run the admin server and managed server on the same
    machine, but we need the managed server to run SP 1 to work around a
    bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
    where I run the admin server, I added a second installation, this time
    WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
    managed server from this second installation, I can see from the logs
    that it is starting up correctly as 6.1 SP 1. But then it fails with
    a ClassCastException when connecting to the admin server (I have
    included the stack trace below). This seems typical of version
    compatibility problems I've had when I've tried connecting to a server
    with a client of a different version.
    But in this case, you are supposed to be able to have the managed
    server with a lower service pack. Does this work for anybody? Has
    anybody encountered the problem I'm having? Note that the servers are
    not clustered, if that makes any difference, and we have a custom
    security realm in addition to the default file realm (though "system"
    of course is in the default file realm).
    Thanks in advance for any help,
    Jim Doyle
    [email protected]
    ####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
    <chile.iso-ne.com> <webui
    server> <main> <system> <> <000000> <Unable to initialize the server:
    'Fatal ini
    tialization exception
    Throwable: java.lang.ClassCastException:
    weblogic.security.acl.DefaultUserInfoImpl
    Start server side stack trace:
    java.lang.ClassCastException:
    weblogic.security.acl.DefaultUserInfoImpl
    at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
    at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
    at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
    at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace

    Hi,
    Has anybody successfully used a WebLogic 6.1 SP1 managed server that
    connects to a WebLogic 6.1 SP 2 admin server?
    BEA's docs claim:
    "The Administration Server must be running the same version of
    WebLogic Server as the Managed Servers in its domain. The
    Administration Server must also have the same or later service pack
    installed as the Managed Servers in its domain. For example, the
    Administration Server could be running version 6.1, Service Pack 2
    while the Managed Servers are running version 6.1, Service Pack 1."
    This is precisely what we want to do, but it's not working. In this
    case, we need to run the admin server and managed server on the same
    machine, but we need the managed server to run SP 1 to work around a
    bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
    where I run the admin server, I added a second installation, this time
    WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
    managed server from this second installation, I can see from the logs
    that it is starting up correctly as 6.1 SP 1. But then it fails with
    a ClassCastException when connecting to the admin server (I have
    included the stack trace below). This seems typical of version
    compatibility problems I've had when I've tried connecting to a server
    with a client of a different version.
    But in this case, you are supposed to be able to have the managed
    server with a lower service pack. Does this work for anybody? Has
    anybody encountered the problem I'm having? Note that the servers are
    not clustered, if that makes any difference, and we have a custom
    security realm in addition to the default file realm (though "system"
    of course is in the default file realm).
    Thanks in advance for any help,
    Jim Doyle
    [email protected]
    ####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
    <chile.iso-ne.com> <webui
    server> <main> <system> <> <000000> <Unable to initialize the server:
    'Fatal ini
    tialization exception
    Throwable: java.lang.ClassCastException:
    weblogic.security.acl.DefaultUserInfoImpl
    Start server side stack trace:
    java.lang.ClassCastException:
    weblogic.security.acl.DefaultUserInfoImpl
    at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
    at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
    at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
    at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace

  • Admin Server and Managed server startup problem

    Hi,
    My weblogic server version is 11g and OS is Linux.
    When i am trying to start the admin server a frer i created the domain i am getting following exceptions in the server log and server is shutting down.
    FPR6 4008000000000000 (f: 0.000000, d: 3.000000e+00)
    FPR7 4010000000000000 (f: 0.000000, d: 4.000000e+00)
    FPR8 006f007300690078 (f: 6881400.000000, d: 1.379624e-306)
    FPR9 0053006f0063006b (f: 6488171.000000, d: 4.228017e-307)
    FPR10 00650074004d0075 (f: 5046389.000000, d: 9.346098e-307)
    FPR11 0078006500720024 (f: 7471140.000000, d: 2.136208e-306)
    FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
    FPR13 4068000000000000 (f: 0.000000, d: 1.920000e+02)
    FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    Module=/usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so
    Module_base_address=0800000000003000
    Target=2_40_20090409_033254_BHdSMr (AIX 5.3)
    CPU=ppc64 (4 logical CPUs) (0x220000000 RAM)
    - Stack Backtrace -
    /usr/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64/libmuxer.so:0x000046F4 [0x00003000 +0x000016F4]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005F7088 [0x005AF000 +0x00048088]
    /usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB8228 [0x00FAB000 +0x0000D228]
    /usr/java6_64/jre/lib/ppc64/default/libjclscar_24.so:0x00FB884C [0x00FAB000 +0x0000D84C]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EDE08 [0x005AF000 +0x0003EE08]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF600 [0x005AF000 +0x00040600]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EF3A8 [0x005AF000 +0x000403A8]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005EC1A0 [0x005AF000 +0x0003D1A0]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB5B4 [0x005AF000 +0x0000C5B4]
    /usr/java6_64/jre/lib/ppc64/default/libj9prt24.so:0x0064C21C [0x00649000 +0x0000321C]
    /usr/java6_64/jre/lib/ppc64/default/libj9vm24.so:0x005BB4D0 [0x005AF000 +0x0000C4D0]
    /usr/java6_64/jre/lib/ppc64/default/libj9thr24.so:0x006375F0 [0x00635000 +0x000025F0]
    /usr/lib/libpthreads.a:0x005084F0 [0x00505000 +0x000034F0]
    0x00000000
    JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
    JVMDUMP007I JVM Requesting System dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp'
    JVMDUMP010I System dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/core.20100513.125306.852102.0001.dmp
    JVMDUMP007I JVM Requesting Snap dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc'
    UTE105: Error writing header to tracefile: /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
    JVMDUMP010I Snap dump written to /usr/Oracle/Middleware/user_projects/domains/test_domain/Snap.20100513.125306.852102.0002.trc
    JVMDUMP007I JVM Requesting Java dump using '/usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt'
    JVMDUMP012E Error in Java dump: /usr/Oracle/Middleware/user_projects/domains/test_domain/javacore.20100513.125306.852102.0003.txt
    JVMDUMP013I Processed dump event "gpf", detail "".
    After adding "<native-io-enabled>false</native-io-enabled>" in cofig.xml as shown below , i am able to start the admin server.
    <server>
    <name>AdminServer</name>
    <native-io-enabled>false</native-io-enabled>     
    <listen-port>9595</listen-port>
    <listen-address>10.10.15.16</listen-address>
    </server>
    i did the same thing for managed servers to start the server.
    My Question is:
    Are we missing any configurations/settings while creating domain?
    Is there any other option to start the server without adding <native-io-enabled>false</native-io-enabled>?
    Regards,
    Naga

    Hi,
    my managed server heap size properties are
    -XX:PermSize=256m -XX:MaxPermSize=256m -Xms256M -Xmx512M
    But the error with Admin server also and we are not providing any heap size properties to admin server. Becuase while creating the domain, i haven't got any
    option to set the heap size for Admin server. Am i required to set heap size properties in Admin server by following this path "Summary of Servers >AdminServer->Server start->"Arguements"?
    Sorry, i am not able to find activity.log. Can you please tell me the location where i can find acivity.log. If i am not wrong, are you taling about serverOut.log? If that is serverOut.log, please tell me which log you require? is it admin server or managed server?

  • Creative SB0410 digital out only works for dd/dts, not for stereo or web videos...

    Creative SB0410 digital out only works for dd/dts, not for stereo or web videos...
    Hi all,
    Need some suggestions here.
    I have an old Creative sb0410 7.1 channel card and after reading few long threads, I am able to output dd/dts via 3.5mm to rca connector.
    However, the problem is I only hear sound if the video has dd or dts sound. When I play normal MP3 or youtube videos, there is no sound.
    Is there a way to configure the digital out so it sends all sound to the receiver whether it's dd or dts or regular stereo?
    Thanks

    As a workaround, I used another 3.5mm stereo to RCA adapter on stereo LR output of sound card and hooked to a different input in my receiver.
    Problem, is I have to switch input in receiver for non DTS/DD sounds.
    It's disappointing that my upscaling dvd player sends all sound signals via coax but this card does not.
    Isn't it supposed to send all sound signals via coax regardless whether it is DTS/DD or normal stereo/mono etc?

  • 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 admin server not starting.

    Hi all,
    I have a problem with my WebLogic Admin server not starting. Following a VM reboot last week our admin servers are no longer starting. On this particular server we have 3 admin servers serving 3 separate environments.
    Theserver seems to be getting stuck right at the very start. I have tried removing tmp, cache and ldap directories. Searched for and removed all .lok files. I have manually turned on full debug to try and flush some extra information through standard out but no luck. It is very peculiar. When we have exported the domain to another box and started the admin server it has come up successfully.
    This is the output from the logs - this is literally as far as it get before it hangs and does nothing. As far as I know the next thing WebLogic is doing is checking the version. Has anyone any ideas what the problem could be? It is server wide as all 3 admin servers on the same box are suffering the same problem.
    This is Weblogic 10.3.2 on a Solaris vm
    JAVA Memory arguments: -Xms256m -Xmx512m
    WLS Start Mode=Development
    CLASSPATH=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/lib/tools.jar:/apps/Oracle/Middleware64/utils/config/10.3/config-launch.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic_sp.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.jar:/apps/Oracle/Middleware64/modules/features/weblogic.server.modules_10.3.2.0.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/webservices.jar:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/apps/Oracle/Middleware64/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/apps/Oracle/Middleware64/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/xqrl.jar
    PATH=/apps/Oracle/Middleware64/wlserver_10.3/server/bin:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/jre/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin:/usr/bin:/usr/sfw/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:
    Starting WLS with line:
    /apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.policy -Xverify:none -da -Dplatform.home=/apps/Oracle/Middleware64/wlserver_10.3 -Dwls.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
    <09-Jan-2013 18:32:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.1-21-133393-1.6.0_20-20100512-2127-solaris-sparcv9 from Oracle Corporation>

    Just a wild guess (as you have restarted the physical servers), it could be related to the entropy of the machine.
    What you can try to do is edit the java.security file in the $JAVA_HOME/jre/lib/security directory.
    Find the entry securerandom.source and edit the value to file:/dev/./urandom (instead of file:/dev/urandom)

  • Why is my airportxpr only working with Itunes and not with another music program

    why is my airportxpr only working with Itunes and not with another music program??
    I can not select/see other outputs in my sound selector.

    You have not indicated which OS or which music program you have so I have listed a program called Airfoil to try for both Windows and Mac - it may work for you
    for Windows - http://rogueamoeba.com/airfoil/windows/
    for Mac - http://rogueamoeba.com/airfoil/mac/

  • I have CS6 and CC installed on my mac when I'm using CS6 and use bridge CC activates how can I set this to only work on one and not the other

    I have CS6 and CC installed on my mac when I'm using CS6 and use bridge CC activates how can I set this to only work on one and not the other

    If you want Bridge CS6 to open when using Photoshop CS6, you must quit Bridge CC.
    Then File menu > Browse in Bridge will bring up Bridge CS6.
    If Bridge CC is already open, The File > Browse in Bridge for Photoshop CS6 will use Bridge CC and Bridge CS6 will not open.
    I hope that's the answer you were looking for.
    Gene

  • Communication protocol between Admin Server and Managed Server

    Hello - I am hoping someone can help me here to understand the communication protocols used in my setup.
    Here is my understanding of the protocol that are used between each component.
    End User <--->HTTPS<--->LoadBalancer Device<--->HTTPS<--->Web Server<---->HTTPS<--->WebLogic Server(Managed Server)<--->LDAP/JDBC<-->Data tier components
    AdminServer<--->T3<--->Managed Server i.e. The communication protocol between Admin Server and Managed server is T3
    The communication protocol between Managed Servers running in one cluster on two seperate machine is What?
    Thank you.

    Hello, interesting question.
    In the documentation " [cluster multicast communication|http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001] " don't specify the used protocol to pack the information for example in a session replication.
    Although in a session replication all objects must be serializable i don't think rmi protocol is used.
    I hope some expert give us some light in this issue :-)
    http://download.oracle.com/docs/cd/E13222_01/wls/docs90/cluster/features.html#1007001

  • How to access JNDI tree of Admin Server from Managed Server

    Hello,
    I created Managed and Admin Server for Domain.
    On Managed Server I use:
    InitialContext con = new InitialContext()
    It points to Managed Server local JNDI tree and
    Managed Server can't find JNDI tree of Admin Server.
    Looks like Managed Server is regular remote client of Admin Server.
    How to access JNDI tree of Admin Server from Managed Server?
    Thanks.
    Oleg.

    Hello,
    I created Managed and Admin Server for Domain.
    On Managed Server I use:
    InitialContext con = new InitialContext()
    It points to Managed Server local JNDI tree and
    Managed Server can't find JNDI tree of Admin Server.
    Looks like Managed Server is regular remote client of Admin Server.
    How to access JNDI tree of Admin Server from Managed Server?
    Thanks.
    Oleg.

  • Strange WLS6.sp2 Oracle DB Reconnect issue in a Cluster but ONLY on the Admin server

    Any Ideas? ->
    I am having a issue when our oracle db server goes down and when we try
    to reconnect the Pool via weblogic I am getting this error. This only
    happens on the Admin server for the cluster, none of the managed servers get
    this and they all seem to be ok. Any ideas?
    -Pete
    **** Below is the stack trace:
    java.sql.SQLException: Io exception: Broken pipe
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
    at
    oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1329
    at
    oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
    at
    oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1
    353)
    at
    oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1760)
    at
    oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
    :1805)
    at
    oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
    ment.java:322)
    at
    oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.j
    ava:366)
    at
    weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:45)
    at
    weblogic.jdbc.rmi.internal.PreparedStatementImpl.execute(PreparedStatementIm
    pl.java:289)
    at
    weblogic.jdbc.rmi.SerialPreparedStatement.execute(SerialPreparedStatement.ja
    va:398)

    Hi,
    As i understand is OS is clustered not the db. Better is to manually shutdown the db clean and then start it.
    TO start login through sqlplus sys as sysdba
    1. startup
    2. Once its done, start the listener
    3. Start the application
    Anand

Maybe you are looking for