Admin console unavailable when a managed server from domain get stuck

We have a weblogic 10.3.2 domain with an admin server and a managed server in two different virtual machines. When for some reason this managed server get stuck (e.g. cpu 100 %) admin consolo starts to go slow up to the point it´s impossible to get access to this.
Did anybody face to this problem before ?
Thanks.

Hi,
Try to find which object causing high cpu usage following Oracle Doc ID 779349.1.
by looking into the files then we can find what would be exact cause of this issue.
Regards,
Kalyan

Similar Messages

Getting error when starting managed server from administration server

          When i start one of my managed server in the cluster i get the following error
          The WebLogic Server did not start up properly.
          Exception raised: java.lang.ArrayIndexOutOfBoundsException
          java.lang.ArrayIndexOutOfBoundsException
          at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
          at com.bea.utils.misc.Process.validate(Process.java:1231)
          at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
          at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
          at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:278)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:335)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          Please tell if somebody know it


Do you have any other products from BEA other than WLS?
          I can't seem to find the following (com/bea/utils/misc) from WLS source
          line ?
          Kumar
          Ritesh Kapoor wrote:
          > When i start one of my managed server in the cluster i get the following error
          > The WebLogic Server did not start up properly.
          > Exception raised: java.lang.ArrayIndexOutOfBoundsException
          > java.lang.ArrayIndexOutOfBoundsException
          > at com.bea.utils.misc.ProcessUtil.base64ToBytes(ProcessUtil.java:552)
          > at com.bea.utils.misc.Process.validate(Process.java:1231)
          > at com.bea.utils.misc.Process.isValidSignature(Process.java:518)
          > at com.bea.utils.misc.ProcessManager.memCheck(ProcessManager.java:647)
          > at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:278)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:335)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
          > at weblogic.Server.main(Server.java:35)
          > Reason: Fatal initialization exception
          >
          > Please tell if somebody know it
          >
          >

Problems starting managed server from admin console WL70 portal

I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.

I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.

Configure Managed Server from Admin Console - Java arguments

Hi There;
I am configuring a managed server from the admin console and the one item that me up is when I add the following into the Arguments sections:
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol'|'oracle.fabric.common.classloaderurl.handler'|'oracle.fabric.common.uddiurl.handler'|'oracle.bpm.io.fs.protocol.
Note The command line script used double quotes (") but the console gave an error - Arguments may not contain '"' This sounded reasonable so I switched the double quotes to single quotes.
Switching to single quotes allowed me to bypass the error.
The managed server fails when I start it from the console:
Error message:
oracle.fabric.common.classloaderurl.handler ' is not recognized as an internal or external command, operable program or batch file.- it is like it ignores the values after the single quotes and fials.
How can I configure this parameter?
note: I am running weblogic 10.3.6 on widows 2008. it is a SOA Managed Server I am trying to setup to run from the Admin Console.
J

Try leaving out the quotes
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol
See also the documentation: URL (Java Platform SE 7 ) "interpreted as a list of packages separated by a vertical slash character |"

Error start managed server from admin console in SSL mode

I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
<Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
<Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
<Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
<Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
<Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
<Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
<Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
<Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
I am running everything on IBM UNIX server.
I appriciate your help.
Thanks & regards,
Laxman.

Hi
From the admin console ... Are you able to check the status of Node Manager ?
If yes ... please check the SSL configuration of managed servers ...
Check the domain administration port also.
Jin

Starting Managed Server from Administration Console

Hi
I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
java.lang.ClassNotFoundException
Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
java.lang.ClassNotFoundException
I start the services in below order
Weblogic Server
node Manager
and
soa_server
Thanks
Hari

you must set to true the StartScriptEnabled property in nodemanager.properties

How to start managed server from admin server both running

I have an admin server on one machine and created a managed server on different
machine, I am not able to start managed server from either machine. When I used
the admin server machine to start the managed server remotely I got this message
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server (running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
ed during initialization. Exception:java.lang.SecurityException: Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
<Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Thanks.

"fkeita" <[email protected]> wrote in message
news:[email protected]...
>
I have an admin server on one machine and created a managed server ondifferent
machine, I am not able to start managed server from either machine. When Iused
the admin server machine to start the managed server remotely I got thismessage
>
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Securityinitializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328><Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350><Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port:8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhapsthe
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port8002.>
>
Try running netstat to see whether another process is actually running at
the given address/port.
Also check using ifconfig/ipconfig or directly checking /etc/hosts file of
the box to see whether the ips addreses are correct.
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Serverfailed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342><Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server(running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Securityinitializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364><Server fail
ed during initialization. Exception:java.lang.SecurityException:Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
atweblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
atweblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>Seems to be some issue with security credentials.
Try running the manageed server directly (as sort of admin) by not passing
the admin server url and bringing it just like an admin server.
See if this works. If it works, then soemthing wrong in the way the admin
server is receiving the request/security credentials from managed server.
Also make sure both managed and admin servers are on the same patch/service
pack level.
-Sabha

How to start managed server from admin server both running on separate machines

          I have an admin server on one machine and created a managed server on different
          machine, I am not able to start managed server from either machine. When I used
          the admin server machine to start the managed server remotely I got this message
          Connecting to http://fkeita:7001...
          <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
          ng using realm myrealm.>
          <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
          ogic Managed Server "managedserver3" for domain "admindomain">
          <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
          create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
          java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
          a
          ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
          <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
          to
          bind to any port such that it is not reachable from the console.>
          <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
          initialize the server: Fatal initialization exception>
          When I tried to connect managed server from its machine to admin server (running
          on separate machine ) I got this error
          Starting WebLogic Server...
          Connecting to http://fkeita:7001...
          <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
          ng using realm myrealm.>
          <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
          ed during initialization. Exception:java.lang.SecurityException: Authentication
          for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          >
          <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
          initialize the server: Fatal initialization exception
          Throwable: java.lang.SecurityException: Authentication for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          >
          The WebLogic Server did not start up properly.
          Exception raised:
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          Reason: Fatal initialization exception
          Throwable: java.lang.SecurityException: Authentication for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          Thanks.


          I used startmanagedweblogic managedserver1 http://fkeita:7001 to try to start managed
          server, but it did not work, and got error messages. Error messages are posted
          on my first posting.
          "pankaj" <[email protected]> wrote:
          >Use the startManagedWeblogic.cmd / .sh script to start your
          >Managed/Clustered servers
          >
          >
          >"fkeita" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> I have an admin server on one machine and created a managed server
          >on
          >different
          >> machine, I am not able to start managed server from either machine.
          >When I
          >used
          >> the admin server machine to start the managed server remotely I got
          >this
          >message
          >>
          >> Connecting to http://fkeita:7001...
          >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security
          >initializi
          >> ng using realm myrealm.>
          >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328>
          ><Starting WebL
          >> ogic Managed Server "managedserver3" for domain "admindomain">
          >> <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350>
          ><Unable to
          >> create a server socket on Channel Default for: BFINKELMAN/90.0.0.25,
          >port:
          >8002.
          >> java.net.BindException: Cannot assign requested address: JVM_Bind
          >Perhaps
          >the
          >> a
          >> ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using
          >port
          >8002.>
          >>
          >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server
          >failed
          >> to
          >> bind to any port such that it is not reachable from the console.>
          >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342>
          ><Unable to
          >> initialize the server: Fatal initialization exception>
          >>
          >> When I tried to connect managed server from its machine to admin server
          >(running
          >> on separate machine ) I got this error
          >>
          >> Starting WebLogic Server...
          >> Connecting to http://fkeita:7001...
          >> <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security
          >initializi
          >> ng using realm myrealm.>
          >> <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364>
          ><Server fail
          >> ed during initialization. Exception:java.lang.SecurityException:
          >Authentication
          >> for user system denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> >
          >> <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342>
          ><Unable to
          >> initialize the server: Fatal initialization exception
          >> Throwable: java.lang.SecurityException: Authentication for user system
          >denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> >
          >>
          >***************************************************************************
          >> The WebLogic Server did not start up properly.
          >> Exception raised:
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> Reason: Fatal initialization exception
          >> Throwable: java.lang.SecurityException: Authentication for user system
          >denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >>
          >> Thanks.
          >
          >

Error when trying to start managed server from node manager

I have a managed server which is authenticated through a WeblogicAuthenticProvider. When starting the managed server from command line I need to setup certain jars in the classpath in order to start it successfully. However when I try and start the managed server from a node manager, I receive the following error.
Any ideas as to what is going on are appreciated. Is there any way to force Weblogic Node manager to invoke the actual startManagedWeblogic.cmd when bringing up the managed server
Thanks
<Jun 5, 2006 9:21:05 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server TweCluster::TaxwareServer1 ...>
<Jun 5, 2006 9:21:07 AM EDT> <Info> <NodeManager@*.*:5555> <Server TweCluster::TaxwareServer1 started, process id = 3,012>
<Jun 5, 2006 9:21:11 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://zeus3dev:7001 to check if there exists a running admin server at this URL.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://zeus3dev:7001 to retrieve the initial configuration.>
<Jun 5, 2006 9:21:16 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file E:\bea8.1\weblogic81\common\nodemanager\TaxwareServer1\TaxwareServer1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
java.lang.NoClassDefFoundError: com/taxware/twe/util/crypto/CryptoUtil
at com.taxware.twe.auth.server.GenericPrincipalValidator.<init>()V(GenericPrincipalValidator.java:41)
at com.taxware.twe.auth.server.WeblogicPrincipalValidator.<init>()V(WeblogicPrincipalValidator.java:38)
at com.taxware.twe.auth.server.WeblogicAuthenticationProvider.getPrincipalValidator()Lweblogic.security.spi.PrincipalValidator;(WeblogicAuthenticationProvider.java:188)
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:154)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
Reason: com/taxware/twe/util/crypto/CryptoUtil

Found a workaround:
Manually, add PATH (and probably the other environment variables also) to
${WLS_HOME}/common/bin/commEnv.sh.

How to start managed server from console?

Hi,
After several unsuccesful attempts to start a managed server from admin console,
which starts fine by script and stops by console, can somebody please mail me
what to enter in the "remote start" tab!
The documentation is very uncertain if the path have to be absolute or not. It
seems to be a problem with the classpath.
thanks in advance
Kai

The ServerStart element should look like below (WLS6.1sp1+). Using absolute
path is definitely OK. Please provide us more info if you still have this
problem such as files under WL_HOME\NodeManagerLogs\<mgr'ed servername>
especially config and <mgr'ed server name>_error.log
<ServerStart Arguments="-mx64m -ms64m" BeaHome="d:\bea"
ClassPath="d:\bea\load1;d:\bea\load1\lib\weblogic_sp.jar;d:\bea\load1\lib\we
blogic.jar"
Name="Server-1005280911753"
OutputFile="d:\bea\load1\config\NodeManagerClientLogs\managed1\startserver_1
005280991998.log"
RootDirectory="d:\bea\load1"
SecurityPolicyFile="d:/bea/load1/lib/weblogic.policy"/>
"Kai" <[email protected]> wrote in message news:3bea490f$[email protected]..
>
Hi,
After several unsuccesful attempts to start a managed server from adminconsole,
which starts fine by script and stops by console, can somebody please mailme
what to enter in the "remote start" tab!
The documentation is very uncertain if the path have to be absolute ornot. It
seems to be a problem with the classpath.
thanks in advance
Kai

Start managed server from console?

If I try to start a new weblogic 10.3 managed server from the console then i get this error:
"The server myserver does not have a machine associated with it.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed."
Starting the same managed server from the dos prompt "bin/startManagedServer.bat myserver" works, so why is the weblogic console not working?

Hi,
To start any managed servers from Admin Console you need to have a Machine associated with that Managed server and have to start nodemanager, then only you can start a managed server from console.
Following are the steps:
1) Create a Managed Server (MS-1)
2) Create a Machines (MachineA)
3) In the above created MachineA add the MS-1 which can be done from the below console path
Console Path:
Machines --> MachineA --> Configuration [Tab] --> Servers [Sub-Tab]
4) Now start nodemanager using the startNodeManager.sh script which can be found in the below path
Path:
wlserver_10.3/server/bin/
5) Now you can try to start your MS-1 using the Admin Console.
Note: If you still cannot start the your managed servers then would suggest you to have a look at the below post
Topic: NodeManager is not reachable
http://middlewaremagic.com/weblogic/?p=5205
Topic: Common NodeManager Issues in WebLogic
http://middlewaremagic.com/weblogic/?p=2887
Regards,
Ravish Mody

How to control managed server from alternate admin ?

Hi All,
We have two managed servers m1 and m2 in ip1 and ip2 and the admin adm1 is in ip3. We have a scenario where there is a problem with the admin server and it regularly goes down in ip3. All the servers are in individual filesystem. To avoid the loss of control we have already packed and unpacked the admin from ip3 into ip4. When we start the admin in ip4 we dont see the managed servers as running instead we see them as shutdown. Is it possible to control the managed servers from the alternate admin server in ip3 without restarting the managed servers ?.
Regards
Kiran

Managed servers ping the admin URL every 10 seconds until it comes back up. When the admin server's IP has changed
you need a way for the admin URL to allow the managed server to find the restarted admin server on the IP address.
A way to achieve this is by using a DNS name that maps to both IP addresses.

Acl.NotOwnerException when starting managed server

I have installed the evaluation version of WL 6.0 and sp1 on Solaris and can run
applications
using the administration server.
I created a new server with the WL console, and then tried to start it as a managed
server,
but I get a java.security.acl.notOwnerException. I start the admin server and
the managed
server using the same user account. When prompted for the boot password, I use
the same
password to start each server.
Is there anything I can change in my setup to get around this problem?
This is the trace of the error:
startManagedWebLogic.sh myserver2 http://localhost:7501
p1= myserver2
p2= http://localhost:7501
LD_LIBRARY_PATH=/private/weblogic/weblogic6.0/wlserver6.0/lib/solaris
<Mar 29, 2001 2:31:16 PM PST> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:systempswd
Starting WebLogic Server ....
Connecting to http://localhost:7501...
log file: /private/weblogic/weblogic6.0/wlserver6.0/./myserver2.log
<Mar 29, 2001 2:31:26 PM PST> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers> myserver2> Logging> General> Stdout severity threshold>
<Mar 29, 2001 2:31:26 PM PST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance for any help.
Joan

Hi Joan
Go to the Managedserver Confiuration and give the Correct listen Port and SSL.I hope this will help you.
Nagesh Rao
Joan Silverman wrote:
I have installed the evaluation version of WL 6.0 and sp1 on Solaris and can run
applications
using the administration server.
I created a new server with the WL console, and then tried to start it as a managed
server,
but I get a java.security.acl.notOwnerException. I start the admin server and
the managed
server using the same user account. When prompted for the boot password, I use
the same
password to start each server.
Is there anything I can change in my setup to get around this problem?
This is the trace of the error:
startManagedWebLogic.sh myserver2 http://localhost:7501
p1= myserver2
p2= http://localhost:7501
LD_LIBRARY_PATH=/private/weblogic/weblogic6.0/wlserver6.0/lib/solaris
<Mar 29, 2001 2:31:16 PM PST> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:systempswd
Starting WebLogic Server ....
Connecting to http://localhost:7501...
log file: /private/weblogic/weblogic6.0/wlserver6.0/./myserver2.log
<Mar 29, 2001 2:31:26 PM PST> <Info> <Logging> <Only log messages of severity
"Error" or worse will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers> myserver2> Logging> General> Stdout severity threshold>
<Mar 29, 2001 2:31:26 PM PST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance for any help.
Joan

Facing error in starting managed server from nodemanager

Hi All,
I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
<11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
Can anyone please tell me what could be the issue. It is really urgent. Please help!!

Hi Roshni,
It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
3. Save and close the file.
4. Restart the Node Manager
If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
Thanks,
Scott (PITSS)
http://pitss.com/us

Deployment of Web Application when the managed Server is down .....

Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

This is currently being fixed in 7.0 line, contact [email protected] and reference
CR110687
Cheers
mbg
"Selvamohan Neethiraj" <[email protected]> wrote in message news:[email protected]..
Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

Admin console unavailable when a managed server from domain get stuck

Similar Messages

Maybe you are looking for