Weblogic 6.0 Automatic startup of Managed Servers

Simple question -
Environ: Weblogic 6.0, NT/2K
Is there a way to start the managed servers under a given AdminServer
without configuring the individual managed servers as an NT Service?
I'd like the AdminServer be registered as a service, come up
automatically and then kick of its managed servers.
Thanks,
John

Is there a way to start the managed servers under a given
AdminServerwithout configuring the individual managed servers as an NT
Service?Nope
I'd like the AdminServer be registered as a service, come up
automatically and then kick of its managed servers.You will have to write a NT script for that. its not possible from within
the WLS infrastructure.
cheers,
Mihir

Similar Messages

Automatic startup of managed servers

hi all. i'm running wls 9.2, and i've got the node manager running as a windows service. i also created a managed server, and I would like it to start when windows starts. is this possible? Thanks.
qin_23

Hi there,
Using a WLST script, you should be able to do so.
More info available @ :
http://e-docs.bea.com/wls/docs92/config_scripting/manage_servers.html#wp1009240
Then just find some tools to generate a service for Windows (easily findable) and you're done !
Regards,
Maxence.

Automatically starting of Managed Servers

Hi, is it possible to start the managed servers without the use of WLST and the admin console automatically?
I want to make it such that when the Admin Server starts up, a service will run and automatically start the managed servers at a different host via the node manager?
Is it even possible? Please advise! Thanks!

Node Manager uses WLST so I'm not sure how else you would plan on using it?
Node Manager can start your machines in the last known state they were in on reboot using CrashRecoveryEnabled=true:
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Another option is to use the startup/services feature of your OS as Jay described. On *nix you could remotely login to another host and invoke the domain's bin/startManagedWebLogic script directly.

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

Weblogic.Admin command for stopping all Managed Servers in cluster

Hello All,
I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
I am looking for a way to do that using java weblogic.Admin utility
Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
Thanks
Weblogic Consultant

hi sir,
I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
If u want to use WLST for starting managed servers and clusters
check the follwing steps.
1. java weblogic.WLST
2. startNodeManager()
3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
4. TAKE ANOTHER COMMAND PROMPT
java weblogic.WLST
5. start('man1','Server') or start('man1','Server','localhost:7003')
6. start('mycluster','Cluster')
7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
8.shutdown('mycluster','Cluster')
regards
abhi
Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

Concurrent startup managed servers in a cluster

I'm using WLS 6.1 sp3 on Solaris 8. I configured 24 instances in a cluster.
          I tried to startup all managed servers at the same time. Some of the
          instance failed. Due to the WLS startup time (half hour to start an instance
          cause we have many ejbs), I didn't try to start servers one by one. Here is
          the log file I got from one of the failed servers. Any help will be
          appreciated.
          Thanks!
          Wenji
          /bea/jdk131/bin/java -server -ms512m -mx512m -XX:NewSize=128m -XX:MaxNewSize
          =128m -verbosegc -classpath
          .:/appdata/wls/cbfe1b/config/prod/properties:/appdata/wls/cbfe1b/config/prod
          /properties/srv34:/oracle/product/8.1.7/jdbc/lib/classes12.zip:/appdata/wls/
          cbfe1b/config/prod/lib/externalAPIs/iioprt.jar:/appdata/wls/cbfe1b/config/pr
          od/lib/externalAPIs/xerces.jar:/appdata/wls/cbfe1b/config/prod/lib/externalA
          PIs/jdom.jar:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/log4j-1.2.5.ja
          r:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/xalan.jar:/oracle/product
          /8.1.7/jdbc/lib/nls_charset12.zip:/bea/wlserver6.1:/bea/wlserver6.1/lib/webl
          ogic.jar:/appdata/wls/cbfe1b/config/prod/classes:/appdata/wls/cbfe1b/config/
          prod/lib/eontec/eontec_custom_user_realm.jar:/appdata/wls/cbfe1b/config/prod
          /lib/ibm/mqccf.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/ccf.jar:/appdata/
          wls/cbfe1b/config/prod/lib/ibm/eablib.jar:/appdata/wls/cbfe1b/config/prod/li
          b/ibm/imsconn.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/recjava.jar -Dwebl
          ogic.Domain=prod -Dweblogic.Name=prod-srv34 -Dbea.home=/bea -Dweblogic.manag
          ement.server=milkyway:8100 -Djava.security.policy=/bea/wlserver6.1/lib/weblo
          gic.policy -Dweblogic.management.password=eontec00 -Dweblogic.RootDirectory=
          /appdata/wls/cbfe1b weblogic.Server
          Starting WebLogic Server ....
          MBean Info preloading problem:
          java.lang.NullPointerException
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2266)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          at
          weblogic.management.tools.AttributeInfo.readObject(AttributeInfo.java:151)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2209)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1406)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1137)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2258)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1407)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
          at weblogic.management.internal.Helper.getMBeanInfo(Helper.java:205)
          at weblogic.management.internal.Helper.preloadMBeanInfos(Helper.java:232)
          at weblogic.management.Admin.initialize(Admin.java:226)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          at weblogic.Server.main(Server.java:35)
          Connecting to http://milkyway:8100...
          The WebLogic Server did not start up properly.
          Exception raised:
          java.lang.NullPointerException
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.management.configuration.ConfigurationException: connecting to
          http://milkyway:8100/wl_management_internal2/Bootstrap - with nested
          exception:
          [java.lang.NullPointerException]
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1164)
          at weblogic.management.Admin.initialize(Admin.java:340)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception


Admin server is not a member of a cluster.
          Wenji
          Wenji Tong wrote:
          > I'm using WLS 6.1 sp3 on Solaris 8. I configured 24 instances in a cluster.
          > I tried to startup all managed servers at the same time. Some of the
          > instance failed. Due to the WLS startup time (half hour to start an instance
          > cause we have many ejbs), I didn't try to start servers one by one. Here is
          > the log file I got from one of the failed servers. Any help will be
          > appreciated.
          >
          > Thanks!
          > Wenji
          >
          >
          >
          > /bea/jdk131/bin/java -server -ms512m -mx512m -XX:NewSize=128m -XX:MaxNewSize
          > =128m -verbosegc -classpath
          > .:/appdata/wls/cbfe1b/config/prod/properties:/appdata/wls/cbfe1b/config/prod
          > /properties/srv34:/oracle/product/8.1.7/jdbc/lib/classes12.zip:/appdata/wls/
          > cbfe1b/config/prod/lib/externalAPIs/iioprt.jar:/appdata/wls/cbfe1b/config/pr
          > od/lib/externalAPIs/xerces.jar:/appdata/wls/cbfe1b/config/prod/lib/externalA
          > PIs/jdom.jar:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/log4j-1.2.5.ja
          > r:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/xalan.jar:/oracle/product
          > /8.1.7/jdbc/lib/nls_charset12.zip:/bea/wlserver6.1:/bea/wlserver6.1/lib/webl
          > ogic.jar:/appdata/wls/cbfe1b/config/prod/classes:/appdata/wls/cbfe1b/config/
          > prod/lib/eontec/eontec_custom_user_realm.jar:/appdata/wls/cbfe1b/config/prod
          > /lib/ibm/mqccf.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/ccf.jar:/appdata/
          > wls/cbfe1b/config/prod/lib/ibm/eablib.jar:/appdata/wls/cbfe1b/config/prod/li
          > b/ibm/imsconn.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/recjava.jar -Dwebl
          > ogic.Domain=prod -Dweblogic.Name=prod-srv34 -Dbea.home=/bea -Dweblogic.manag
          > ement.server=milkyway:8100 -Djava.security.policy=/bea/wlserver6.1/lib/weblo
          > gic.policy -Dweblogic.management.password=eontec00 -Dweblogic.RootDirectory=
          > /appdata/wls/cbfe1b weblogic.Server
          > Starting WebLogic Server ....
          > MBean Info preloading problem:
          > java.lang.NullPointerException
          > at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2266)
          > at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          > at
          > weblogic.management.tools.AttributeInfo.readObject(AttributeInfo.java:151)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at
          > java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2209)
          > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1406)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          > at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1137)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
          > at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2258)
          > at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1407)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
          > at weblogic.management.internal.Helper.getMBeanInfo(Helper.java:205)
          > at weblogic.management.internal.Helper.preloadMBeanInfos(Helper.java:232)
          > at weblogic.management.Admin.initialize(Admin.java:226)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          > at weblogic.Server.main(Server.java:35)
          > Connecting to http://milkyway:8100...
          > ***************************************************************************
          > The WebLogic Server did not start up properly.
          > Exception raised:
          > java.lang.NullPointerException
          > <<no stack trace available>>
          > --------------- nested within: ------------------
          > weblogic.management.configuration.ConfigurationException: connecting to
          > http://milkyway:8100/wl_management_internal2/Bootstrap - with nested
          > exception:
          > [java.lang.NullPointerException]
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1164)
          > at weblogic.management.Admin.initialize(Admin.java:340)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          > at weblogic.Server.main(Server.java:35)
          > Reason: Fatal initialization exception
          > ***************************************************************************
          >
          >
          >

Best way to make managed servers start up on machine startup?

I had thought that if I used NodeManager to start servers from the admin console, if I rebooted the computer, and my RC scripts brought up the NodeManager (and AdminServer), that the NodeManager would note that the managed server had been in a running state before, and that it should be automatically restarted.
In my testing, it doesn't do that. I filed a support case to ask about this, and they concurred, saying that the NodeManager won't do that for me.
So, is the best strategy for starting up managed servers at system startup to write a wlst script that runs after NodeManager startup that tells the NodeManager to start the managed servers? Or is there a way to make the NodeManager automatically start the managed servers?

If it matters to anyone, I tried writing a WLST script taken directly from examples that connects to the NodeManager and starts up a managed server, but it didn't work (I don't have the text of the error anymore). However, a similar version that connects to the AdminServer worked perfectly fine.
At this point, however, I'm not sure that I want to do this anyway. After a server restart, it's good to have the NodeManager and AdminServer automatically start, but I'm examining whether the ManagedServer startup should be automatic. I'll have to think about it.

Managed servers are started/stopped from admin console using NodeManager

Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
Ajmal

Hi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody

Transaction span two WLS managed servers (non-clustering)

(Weblogic 6.1 - non-clustering version)
I have two managed servers configured on a single machine on different
ports, and I am not using clustering weblogic. Assuming I have EJB A
deployed on managed server 1, and EJB B deployed on managed server 2.
I want to have EJB A to invoke EJB B. In EJB A, I guess I will
probably create the InitialContext with the URL of managed server 2,
then do the JNDI look up and call EJB B.
My questions are:
- Can weblogic handle transaction that spans two managed servers
(non-clustering setting)?
- Does weblogic use XA to handle transaction between managed servers?
- Do I need to do any JTA code in order to achieve that (instead of
just letting the EJB container to handle the transaction for me)?
Thanks in advance!
B.L.

Hi,
"benson" <[email protected]> wrote in message
news:[email protected]..
(Weblogic 6.1 - non-clustering version)
I have two managed servers configured on a single machine on different
ports, and I am not using clustering weblogic. Assuming I have EJB A
deployed on managed server 1, and EJB B deployed on managed server 2.
I want to have EJB A to invoke EJB B. In EJB A, I guess I will
probably create the InitialContext with the URL of managed server 2,
then do the JNDI look up and call EJB B.
My questions are:
- Can weblogic handle transaction that spans two managed servers
(non-clustering setting)?Yes, it can.
- Does weblogic use XA to handle transaction between managed servers?Yes, it does. Make sure you use TX DataSources. If the servers are connected
to different databases, TX DataSources should be based on connection pools
used XA drivers.
- Do I need to do any JTA code in order to achieve that (instead of
just letting the EJB container to handle the transaction for me)?No, you don't. WebLogic will take care about handling
distributed TXs.
Regards,
Slava Imeshev

JMS topic-cache topic is not getting broadcasting in other managed servers

Hi All,
Please give me some idea in fixing the issue that im facing.
I have created the JMS topic in my weblogic console server which has 2 managed servers.
I have a feature in my application which is kept in a cache that will be used by my JMS topic. If my request hits managed 1 server im able to see the newly created feature.
But the same feature is not working when i make the request hit managed 2 server.
It means the JMS topic is not getting broadcasted properly in other managed server. I dont want to go for a server recycle which will resolve the issue.
Please let me know if im not clear enough.
Below is the description provided by my partner on the same issue in his words..
"The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.
The same problem is observed in Production as well. Let us know if there is anything wrong in the way the JMS Topic is created or any other configuration is missing, that is not allowing the proper functioning of the Topic."
fyi...i have all my firewall enabled between the managed servers.And multicast property is also declared correctly only.

Please let me know if im not clear enough.No. Please explain again.
The JMS Topic - 'CacheTopic' is not broadcasting messages created on one managed server to the remaining managed servers.Is it a distributed topic? Or does it mean a topic message doesnt get delivered to all subscribers?
ram.

Automatic startup of admin server + managed server on Windws

Hello,
I have installed/configured WLS 10.3.6 + Forms/Reports 11.1.2.1 on Windows 2008 R2. All this went ok with no errors.
The NodeManager is installed as a service and runs happily after every reboot of the server. OPMN does it as well.
I can connect to the NodeManager with WLST and start/stop/status the Admin Server and the managed servers (WLS_FORMS,WLS_REPORTS) created during the
the installation/configuration step. Each server has the username/password defined (and already encrypted).
However, when I restart the Windows Server, neither the Admin Server nor the WLS_x servers are started during the boot.
I thought that the configuration process was in charge of setting all this, that was my experience with the previous version Oracle Internet Application Server (iAS) 10.1.2.x (opmn running as a service started them all).
I have run through the installation/configuration docs, and found nothing that says that Oracle will configure (or not) the automatic startup.
1) Is the Oracle configuration process (the one that creates the ClassicDomain) supposed to configure the automatic startup of the admin server + managed servers in this setup ? Am I missing perhaps some extra steps ?
or
2) Do I have to create WLST scripts (that connect to the NodeManager and start the admin server + managed servers) and deploy them as Windows Services myself ?
regards.

Hi,
During weblogic installation in window server, node manager will be automatically registered as window services. But for admin and managed servers, you need to register it manually after succesful installation and configuration for automatic startup during machine reboot.
Please refer the metaliknk id for register as window services:1060058.1.
If this helps please mark.
Regards,
Kishore

I am unable to start Managed Servers through Weblogic AdminConsole

Hi,
We are using Weblogic 10.3.1.0 version.
Totaly 4 Managed Severs
1 Admin Server
with Nodemanger.
In Admin Console When ever we going to Stop the Manged Servers.
1. Environment ----- > Servers ---- > Control ----------- > Mananged Server 1 -----------> Force shutdown
2. Then click refresh button ---- showing "FAILED_NOT_RESTARTABLE"
3. after that when ever we going to start the Managed Server in Admin console
First its Showing ----- Starting
and next its showing ----- FAILED_NOT_RESTARTABLE
4. its not coming to Running State.
In Logs
Domain log
-----------> <1273141345460> <BEA-000450> <Socket 8 internal data record unavailable (probable closure due idle timeout), event received 17>
####<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280738> <BEA-000396> <Server shutdown has been requested by weblogic>
####<06-May-2010 11:54:40 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280771> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
####<06-May-2010 11:54:40 o'clock BST> <Notice> <Cluster> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280844> <BEA-000163> <Stopping "async" replication service>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281061> <BEA-000365> <Server state changed to ADMIN>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281064> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <Server> <ukirt156> <twpserver1> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <1273143281113> <BEA-002607> <Channel "Default" listening on 172.21.149.168:7003 was shutdown.>
####<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <ukirt156> <AdminServer> <[ACTIVE] ExecuteThread: '45' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273143390016> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
AdminServer log
<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
<06-May-2010 11:57:33 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
<06-May-2010 12:07:02 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
ManagedServer Log
<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler pause
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
<06-May-2010 11:54:54> <Debug> <NodeManager> <Waiting for the process to die: 19316>
<06-May-2010 11:54:54> <Info> <NodeManager> <Server was shut down normally>
<06-May-2010 11:54:54> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
NodeManager Log
<06-May-2010 11:54:54> <Info> <twp_domain> <twpserver1> <Server was shut down normally>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Boot identity properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Startup configuration properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/startup.properties">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00020">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Starting WebLogic server with command line: /appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/bin/java -Dweblogic.Name=twpserver1 -Djava.security.policy=/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.management.server=http://ukirt156:7001 -Djava.library.path="/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386/jrockit:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/../lib/i386::/appl/nsm/CA/UnicenterNSM/lib:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386/client:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386:/appl/nsm/CA/SharedComponents/ccs/dia/dna/lib:/appl/nsm/CA/SharedComponents/ccs/dia/lib:/usr/lib:/opt/CA/CAlib:/appl/nsm/CA/SharedComponents/lib:/appl/nsm/CA/SharedComponents/Csam/SockAdapter/lib:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/data/share/package/twp/WEB-INF/lib/ojdbc14.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.jar -Dweblogic.system.BootIdentityFile=/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xmanagement:port=7091,ssl=false,authenticate=false -Xms=1200m -Xmx=1200m -Xverbose:gc,gcpause -Dreflexis.scheduler=true -Dreflexis.server=twpserver1 -Djava.awt.headless=true -Dclient.encoding.override=UTF-8 -Doracle.jdbc.V8Compatible=true weblogic.Server >
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Working directory is "/appl/weblogic/scripts">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00021">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
<06-May-2010 11:56:29> <Info> <twp_domain> <twpserver1> <Server failed during startup so will not be restarted>
<06-May-2010 11:56:29> <Warning> <Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:332)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Server logs
<06-May-2010 12:06:57> <Info> <NodeManager> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
[JRockit] Management server started on port 7091, ssl=false, authenticate=false.
<06-May-2010 12:06:59 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.2-20_o-108500-1.6.0_05-20090120-1115-linux-ia32 from BEA Systems, Inc.>
<06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {AES}xvFgPysVi5b89pYwaAppoqPXQ5wFVW13yoFhzhKmuQo= from the file /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception <06-May-2010 12:07:01 o'clock BST> <Info> <Management> <BEA-141223> <The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the
<06-May-2010 12:07:01 o'clock BST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<06-May-2010 12:07:01 o'clock BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<06-May-2010 12:07:02> <Debug> <NodeManager> <Waiting for the process to die: 19443>
<06-May-2010 12:07:02> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<06-May-2010 12:07:02> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Note: if i start the manged servers through WLST script its working fine.
[twpuser@ukirt156 /appl/weblogic/scripts]$ java weblogic.WLST
nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
nmStart('twpserver1')
Please provide the solution, how to solve this issue.
Thanks
SRK

Just at first glance, it seems as though you have one or more configuration issues, perhaps inconsistencies between the node manager server configuration files and the domain's config.xml
nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
nmStart('twpserver1')
implies that tmp_domain is configured in /appl/weblogic/oracle/middleware/user_projects/domains, (which is the default from the configuration wizard). However, the node manager and server output logs make it seem like it's trying to use a domain in the directory /appl/weblogic/scripts. Not sure how that happened, perhaps you had two domains? Perhaps copied or moved the domain files? Something else?
In any case, start by checking out your nodemanager.domains file and ensure that it reflects your intended domain directory.

Startup.properties settings for managed servers

We are using WLS 9.2 MP3 on Solaris 10 (SPARC).
I have built a few test systems in an attempt to document configurations and noticed my managed servers on the systems start up with a different "weblogic.management.server" setting in the log files. This setting appears in the <domain>/servers/<server name>/data/nodemanager/start.properties file as "AdminURL=http:\://xxx.xxx.xxx.xxx\:7001"
Each system was built and rebuilt using the same settings. Each system has multiple interfaces. One system has an entry of AdminURL=http:\://192.168.100.100\:7001 and another system has an entry of AdminURL=http:\://10.10.10.100\:7001 even though each system was built just like the other.
Every time I manually change the adminURL setting it gets reset on each server restart (which I expected). I have not specified (that I know of) the IP address or interface of the admin server anywhere in the "server start" settings. I also notice the admin server is starting on all interfaces on the system (not sure if this is good/bad/indifferent).
Can anyone tell me where the startup.properties file entries are pulled from?
As a followup: I just noticed (after my post) a slight difference between my systems. One has a fiber connection whereas the others do not. When I execute 'ifconfig -a' I see the interfaces/IP's in different orders (because the interfaces are named differently). I also noticed a wlsifconfig.sh script in one of the startup files. It almost appears as though the wlsifconfig.sh script is setting the AdminURL value and is pulling it from the last interface it finds in the ifconfig listing?????
Thanks for any assistance

To diagnose problems with Thunderbird, try one of the following:
*Restart Thunderbird with add-ons disabled (Thunderbird Safe Mode). On the Help menu, click on "Restart with Add-ons Disabled". If Thunderbird works like normal, there is an Add-on or Theme interfering with normal operations. You will need to re-enable add-ons one at a time until you locate the offender.
*Restart the operating system in '''[http://en.wikipedia.org/wiki/Safe_mode safe mode with Networking]'''. This loads only the very basics needed to start your computer while enabling an Internet connection. Click on your operating system for instructions on how to start in safe mode: [http://windows.microsoft.com/en-us/windows-8/windows-startup-settings-including-safe-mode Windows 8], [http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-7 Windows 7], [http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-vista Windows Vista], [http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/boot_failsafe.mspx?mfr=true" Windows XP], [http://support.apple.com/kb/ht1564 OSX]
; If safe mode for the operating system fixes the issue, there's other software in your computer that's causing problems. Possibilities include but not limited to: AV scanning, virus/malware, background downloads such as program updates.

SAML2 between Managed Servers in same Weblogic

Hi,
I need to configure SAML V2 between 2 or more applications deployed in WebLogic 10.3.6 server.
My problem occurs when I try to use application in same weblogic, different managed server.
* App1 call App2 within an iframe.
* When I access App1, logon page works.
* When I access App2 within iframe, credentials was transfered perfectly from App1 to App2.
* When I return to App1, session is ended.
Deploying apps on diferent weblogic all works fine and I can access App1 and App2 normally.
Deploying apps on same weblogic, same managed server, credentials are sharing automatically even SAML not configured.
I can't understand why App1's session was killed when I access App2 in same weblogic and different managed servers.
Does someone can help me?
Regards

I am setting a different cookie for each application. First app show login form and authenticate correctly but when I open second app, credentials was not recnognized.

Weblogic 10.3.6 managed servers are not working properly

Hi,
i am using weblogic 10.3.6. I have 6 managed server and one Admin server. I observed one thing that when i up Managed6 and run my application. In one of the java file i am using one jar file to fetch one class(Bussiness Object instance). For managed 6 the code is working fine. it gives me the same class file. but if i up any other managed server then i am getting the Impl of that class.
can anyone help me out. Thanks in advance.

Hi,
You shouldn't have to edit the startup.properties manually.
Try the following sequence:
1. Shut down all managed servers;
2. Change the property in the Admin Console;
3. Restart the AdminServer;
4. Start the managed servers and check the property;
Make sure the managed server do not start in Independence Mode

Weblogic 6.0 Automatic startup of Managed Servers

Similar Messages

Maybe you are looking for