Admin Server Funcationality in a WebLogic Cluster

Is this a correct statement of how the Admin Server is handled in WebLogic Cluster:
"If you have a two node WebLogic 10.3 Cluster then you will have the Admin Server for the domain running on node1. The managed server within the domain will run on both node1 and node2. The managed server services your application(s).
If node1 fails then the managed server running on node2 will continue to operate, thus meeting your high availability requirement.
If you need to administer your WebLogic installation you will first have to restore node1 to an operational state so that you can access the Admin Server."
Thank you

Answers :-
Q>"If you have a two node WebLogic 10.3 Cluster then you will have the Admin Server for the domain running on node1. The managed server within the domain will run on both node1 and node2. The managed server services your application(s).
A>Admin server can be running on any node(Physical machine). One Managed server(say MS1) can run only on one node. Two nodes can host two different managed servers. Yes, managed servers services your applications.
Q>If node1 fails then the managed server running on node2 will continue to operate, thus meeting your high availability requirement.
A> Yes, that is the reason of using clustering : Load balancing and failover.
Q>If you need to administer your WebLogic installation you will first have to restore node1 to an operational state so that you can access the Admin Server."
Yes, if admin server was running on node1, then it needs to be up and running to administer the domain.

Similar Messages

Monitoring Managed servers if Admin server is unavailable in Weblogic

Is it possible to find managed servers state ( example: RUNNING, FAILED, UNKNOWN etc..) if Admin server is unavailable( may be down) in Weblogic.
We can search the state of managed server using keywords in managed server logs. But we don't want to do that.
Is there any other way to find the managed servers state.
Thanks,
Venkat

WLST and connecting to managed servers is one option.
Another one is using a RESTful approach: the one that comes with WLS12c in centrally located on the admin server and therefore not really helpful in your case
You might try OpenSource Jolokia ( Overview ) which is a nifty little tool.
Some more infos about Jolokia and WebLogic:
RESTful WebLogic Monitoring of Servers, Applications, JDBC and JMS with Jolokia — munz & more
best regards!

ORACLE WEBLogic 12C Clustering of Admin Server ?

Hi ,
I have setup WebLogic Server 12c on solaris 10 u11, as cluster.
For cluster of managed servers, it works fine.
My Question is, can we run Admin Server from two nodes of cluster?
example: Node 1, created Admin Server, Cluster (F-End1/F-End2) Managed Servers
F-End1 on node1, and F-End2 on node2.
Now for some reason, Node1 has some hardware problem, can i run Admin Server from Node2 ?
I have followed the setup from this website<>
http://www.oracle-base.com/articles/11g/weblogic-11g-clustered-domains.php
Followed Same, Pack/Unpack, Enroll.
Now from Node 1, i can run, Node Manager, ./startweblogic.sh   and it takes me to the Admin Server.
from there i can manage every thing.
Question is, can i run Admin Server form Node2? if yes, how?

Node1: 10.0.1.179     Admin Server :7001      F-End-1 7003 B-End1   7020
Node2: 10.0.1.177                                       F-End-2   7003 B-End2   7020
when i try to run the Admin Server from the Node2, i get error (By 1st running the Node Manager)
<Sep 5, 2013 10:34:03 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<Sep 5, 2013 10:34:03 AM GST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
<Sep 5, 2013 10:34:03 AM GST> <Notice> <Log Management> <BEA-170019> <The server log file /u02/Oracle/Middleware/user_projects/domains/bust_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
<Sep 5, 2013 10:34:17 AM GST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 5, 2013 10:34:31 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY.>
<Sep 5, 2013 10:34:31 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<Sep 5, 2013 10:34:49 AM GST> <Notice> <Log Management> <BEA-170027> <The server has successfully established a connection with the Domain level Diagnostic Service.>
<Sep 5, 2013 10:34:49 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN.>
<Sep 5, 2013 10:34:49 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING.>
<Sep 5, 2013 10:34:49 AM GST> <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
<Sep 5, 2013 10:34:49 AM GST> <Error> <Server> <BEA-002606> <The server is unable to create a server socket for listening on channel "Default". The address 10.0.1.179 might be incorrect or another process is using port 7001: java.net.BindException: Cannot assign requested address>
<Sep 5, 2013 10:34:49 AM GST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
<Sep 5, 2013 10:34:49 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<Sep 5, 2013 10:34:49 AM GST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
<Sep 5, 2013 10:34:49 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
Any Suggestions?

6.0 cluster startup without the admin server...

Is it possible to start a WL6.0 cluster without the admin server being up
          and running? If not, are there any workarounds that eliminate the admin
          server as a single point of failure?


          I have same questions.
          1.The admin server's primary task is up the cluster?And if admin server is down
          that can't affect the cluster running.
          2.Is it right when the cluster is working,the useful ip is admin server's ip?For
          example,admin 10.10.10.1,cluster1 10.10.10.2,cluster2 10.10.10.3,the only useful
          ip is 10.10.10.1 in the cluster.
          3.Is it correct that because the only useful ip is 10.10.10.1,therefor my client
          access the cluster from 10.10.10.1?
          When my admin server is down,then my system will be down.
          4.which is the dispatch in the cluster system ?
          my step of configuration of th cluster:
          1.add two managed servers to admin server and edit startweblogic.cmd;
          2.config cluster.(admin server address 10.10.10.1:8168,cluster address 10.10.10.2:7001,10.10.10.3:7001),multicast(237.0.0.1)
          please help explain these questions!thanks a lot!
          2.
          Kumar Allamraju <[email protected]> wrote:
          >Sorry if i wasn't clear, what i mean to say is
          >
          >When you first start the managed server's you have to have admin server
          >up &
          >running.
          >Admin server can go down when cluster is running, but then you can't
          >add servers
          >to cluster
          >and I think its ok to have it that way from administration point of view.
          >
          >Yes, there's no facility to achieve single point of failure for admin
          >servers.
          >
          >--
          >Kumar
          >
          >
          >
          >William Wallace wrote:
          >
          >> I may be misreading that page, but it doesn't really tell me how to
          >> successfully start to start a managed server is the admin server is
          >down. If
          >> you run the managed server script you get an "cannot connect to admin
          >> server" exception if the admin server is not running. Now, I imagine
          >that I
          >> could script something up to restart the admin server if it's down,
          >but that
          >> doesn't protect me from hardware failure.
          >>
          >> "Kumar Allamraju" <[email protected]> wrote in message
          >> news:[email protected]...
          >> > http://e-docs.bea.com/wls/docs60/adminguide/startstop.html#1035064
          >> >
          >> > --
          >> > Kumar
          >> >
          >> >
          >> > William Wallace wrote:
          >> >
          >> > > Is it possible to start a WL6.0 cluster without the admin server
          >being
          >> up
          >> > > and running? If not, are there any workarounds that eliminate the
          >admin
          >> > > server as a single point of failure?
          >> >
          >

Can Admin Server in primary domain be used to control managed server in secondary domain?

Hi Experts,
I have 2 unix boxes, and I have 1 installation of weblogic on each (one in primary and one in secondary site).
The set up is as listed below::
PrimarySite
MainDomain: 1 Admin Server, 2 managed Server, 1 cluster
SecondarySite
MainDomain: 1 Admin Server, 2 managed Servers, 1 cluster
Questions
1. Can I use Admin Server in Primary site to control/manage managed servers in Secondary site, and use the one in secondary site to control the managed server in primary site?
2. Will I be able to have smooth failover and session replication from cluster1 in Primary site to cluster2 in secondary site.
Tumi

1) Admin server from one domain cannot control any managed servers from any other domain.
2) You can use a load balancer to switch between sites and implement cross cluster replication as described in the link below: Failover and Replication in a Cluster

Managed server trying to start as admin server

I have one VM with SOA Suite that it is fully functional.
I made a copy of that VM and changed the hostname and IP.
Making a search under all the disk I replaced all occurences of the old hostname and IP with the new ones.
Now I can start AdminServer and soa_server, but when I try to start bam_server I'm getting the following error:
weblogic.management.ManagementException: Booting as admin server, but servername, bam_server, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
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)
The steps I'm following to start the servers it is as follows:
cd $NM
wlst.sh
startNodeManager()
nmConnect('weblogic','welcome1','localhost','5556','soa_domain','/u01/app/oracle/user_projects/domains/soa_domain')
nmStart('AdminServer')
nmStart('soa_server')
nmStart('bam_server')
This post is related to this other post, but I don't have permissions to reply on that one, so I created a new one:
starting managed server with nodemanager
Thanks in advance for any tip you can give me.

The servers starts correctly if I run the scripts, but not from the wlst.sh console:
$nohup $WL_HOME/server/bin/startNodeManager.sh > nodemanager.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/startWebLogic.sh > adminserver.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh soa_server > soa_server.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh bam_server > bam_server.out &

Simple question about WLI and admin server

Hello,
I have a domain with 3 servers in 2 machines. 2 servers forms the cluster and the other one is the admin server.
When a process finish, the WLI core execute a setStatus on JMX component of type ProcessConfiguration. This type of component is only deployed (in my installation) in the admin server. So the Integrarion cluster service depends on admin server...if I stop the admin servers all the process invocations fails...
I have tried to disable the process tracking data using wli console without results...
How I can disable this behavior?
Is there any way to deploy this type of component (ProcessConfiguration JMX) in the cluster?
Thanks
WL8.1 with SP5, WLI8.1

Hello,
You can start TOMCAT jsp engine on PC B, it will start on port 8080 on B. And now redirect the requests from Apache in PC A using the mod_rewrite. Look at the following link on how to redirect the requests, give the redirect url as PCB:8080
http://httpd.apache.org/docs/misc/howto.html#redirect
HTH
Vamsi kundeti

Error while shutting down 'Admin Server' from administration console

hi,
When I try to shutdown admin server from administration console(Weblogic server>Control>Shut Down...) I get this error:
No Machine associated with server AdminServer. Please associate a machine to this weblogic server using weblogic console first.
Not able to understand what this means....
thanks

Read up on Node Manager - a outside-of-WLS-process that can start/stop WebLogic on your OS instance. Node Manager uses the "machine" concept.
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13740/overview.htm
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html

Putting Admin Server to use

Hi all,
          We are planning to use a WL Proxy for teh cluster and I was wondering if I
          could use the Admin server for that ...
          Also how intensive in terms of memory and CPU usage is the Admin server's
          job (in a cluster of 2 managed servers).
          Also does BEA have any take on that ?
          Any help would be appreciated,
          _NR


It's not a recommended practise to use Admin server other than
          configuration & deployment purposes. Regarding the memory and cpu usage,
          it depends on the deployments and tools used to gather runtime statistics
          Otherwise the footprint should be pretty much in the range of 64mb.
          For testing purposes it's ok to use admin server as proxy server but i
          wouldn't
          recommend the same for production.
          Kumar
          [email protected] wrote:
          > Hi all,
          > We are planning to use a WL Proxy for teh cluster and I was wondering if I
          > could use the Admin server for that ...
          > Also how intensive in terms of memory and CPU usage is the Admin server's
          > job (in a cluster of 2 managed servers).
          > Also does BEA have any take on that ?
          >
          > Any help would be appreciated,
          > _NR

Weblogic admin server cluster

Hi,
I'm setting up WebLogic cluster (horizontal with 2 managed servers spanning across 2 machines).I would want to have admin server on each machine and only one admin server will be active whiel the second admin server will remain shutdown
.Can anyone please explain how I can set this up with 2 adminsitration servers and how do I make it active-passive mode for admin server and how i can bring it up in case of 1st admin server going down
Any documents would be really helpful
thanks

There can be only 1 Admin per WebLogic Domain....not more than one.
Please refer to Know more about *"What is Administration Server?"* http://weblogic-wonders.com/weblogic/2010/06/18/weblogic-initials/
If you are talking about *" Whole Server Migration "* then please refer to: http://download.oracle.com/docs/cd/E11035_01/wls100/cluster/migration.html
Note: Server migration is only supported when you use the SSH version of Node Manager. Server migration is not supported on Windows.
When a migratable server becomes unavailable for any reason, for example, if it hangs, loses network connectivity, or its host machine fails—migration is automatic. Upon failure, a migratable server is automatically restarted on the same machine if possible. If the migratable server cannot be restarted on the machine where it failed, it is migrated to another machine. In addition, an administrator can manually initiate migration of a server instance.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

Weblogic admin server in the cluster !!!!

Hi,
I am working on weblogic setup already done by my ex-colleague. I observed that, the admin server is also participating in the cluster and hence it is also one of the targets for EJB components, datasource and connection pool. Is there any performance issue in this setup ?
thanks for your time.

Thank you for your reply.
I forgot to tell you that the admin server is not an individual machine. It is setup in one of the weblogic App. servers. Therefore, I feel it is better we do not add this admin server in the cluster.
You can give me your advice. ---- topic 1
By the way, I had posted one question about targeting a datasource to the individual servers rather than to a cluster. In the existing setup, the datasource is targeted to individual servers rather
than to the cluster. The setup is running without any error.
But as per the BEA manual, we have to target the datasource to the cluster if we use cluster. So, in my current setup, is there any performance issue or may I face any problem in future by not targeting the datasource to the cluster? I appreciate if you can
try this question. ---- topic 2
Thanks in advance.

Starting weblogic cluster and admin server on Win 2000 platform

Hi! Here's my problem scenario:
I'm running my WLS 8.1 application as WLS cluster on Win 2000 platform. I have
3 replicated WLS servers in my cluster and of course one WLS server as admin server
(4 WLS servers all together). I'm starting my WLS application using Win services
which behind a scene call win 2000 comand interpreter batch-file to start the
servers. Currently I have 4 different win 2000 services each calling different
batch-files to start a WLS server (4 all together). Here's my question:
Is there any way to start my cluster (3 managed WLS servers) and WLS admin server
from single win 2000 command file (using single win 2000 service). Using win 2000
AT-command interpreter command I can start executables and command(s) and command-files
at background at specific date and time, but I want to start my WLS application
on every win 2000 platform boot, is there any way to achieve this ???
Best Regards!
Jami

hi,
Thanks for stepping up!
But I wasn't using any clustering or loadbalancing.
Just a simple Admin server, Managed server set up.
256 Meg, Pentium box running Win 2000 premium edition.
I tried tweeking around the heap size too.... coz' the operations were slogging
like anything...
Bal
"Raja Mukherjee" <[email protected]> wrote:
It seems like network issue....do you have Windows Clustering/Load Balancing
service turned on by any chance? I would also use netmon to see the traffic
between the ips....
..raja
"Bala" <[email protected]> wrote in message
news:3b3a6c00$[email protected]..
hi,
I am looking at a strange behaviour with WLS6.0SP1 installed on WINDOWS2000 Premium.
I brought up the Admin server and a Managed server. After a while theAdmin Server
is compeletely
losing the control of the managed server (for no reason).
when I tried monitoring the managed server from the console, I couldnot
access
the manager server
and the status down (red ball). I tried restarting the Admin Server
in the discover mode - NO LUCK.
But when I restart the Managed server and go to the Web Based Admin
Console and refresh, it worked. But I dont think we should be doingthat
in a
production environment.
Did anybody come across such a problem before ???
Is this a problem with Win 2000 ???
coz' it never happened with NT workstation
thanks in advance

Problem starting managed server in cluster (The name of the managed server is same as admin server)

          We have the following setup.
          CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
          administrator. We start CLUSTER3 as a self-managed server and then try and start
          CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
          1 and 2 we get the following:
          D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
          03:7001
          D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
          D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
          D:\bea\wlserver6.1>echo off
          * To start WebLogic Server, use the password *
          * assigned to the system user. The system *
          * username and password must also be used to *
          * access the WebLogic Server console from a web *
          * browser. *
          D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
          ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
          ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
          -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
          "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
          r
          <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
          Enter password to boot WebLogic server:
          Starting WebLogic Server ....
          Connecting to http://10.0.1.103:7001...
          The WebLogic Server did not start up properly.
          Exception raised: weblogic.management.configuration.ConfigurationException: The
          name of the managed server is same as admin server. The managed server will not
          be allowed to start up.
          weblogic.management.configuration.ConfigurationException: The name of the manage
          d server is same as admin server. The managed server will not be allowed to star
          t up.
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
          at weblogic.management.Admin.initialize(Admin.java:320)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          D:\bea\wlserver6.1>goto finish
          D:\bea\wlserver6.1>cd config\CLUSTER1
          D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
          D:\bea\wlserver6.1\config\CLUSTER1>
          Many thanks in advance,
          Alex Burton
          http://www.e-plus.com.au/


Don't start the admin server as managed. Removing
          -Dweblogic.management.server...
          from the command line should help.
          Alex Burton wrote:
          > We have the following setup.
          > CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
          > administrator. We start CLUSTER3 as a self-managed server and then try and start
          > CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
          > 1 and 2 we get the following:
          >
          > D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
          > 03:7001
          >
          > D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
          >
          > D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
          >
          > D:\bea\wlserver6.1>echo off
          >
          > ***************************************************
          > * To start WebLogic Server, use the password *
          > * assigned to the system user. The system *
          > * username and password must also be used to *
          > * access the WebLogic Server console from a web *
          > * browser. *
          > ***************************************************
          >
          > D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
          > ".
          > ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
          > ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
          > -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
          > "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
          > r
          > <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
          > Enter password to boot WebLogic server:
          > Starting WebLogic Server ....
          > Connecting to http://10.0.1.103:7001...
          > ***************************************************************************
          > The WebLogic Server did not start up properly.
          > Exception raised: weblogic.management.configuration.ConfigurationException: The
          > name of the managed server is same as admin server. The managed server will not
          > be allowed to start up.
          > weblogic.management.configuration.ConfigurationException: The name of the manage
          > d server is same as admin server. The managed server will not be allowed to star
          > t up.
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
          > at weblogic.management.Admin.initialize(Admin.java:320)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
          > at weblogic.Server.main(Server.java:35)
          > Reason: Fatal initialization exception
          > ***************************************************************************
          >
          > D:\bea\wlserver6.1>goto finish
          >
          > D:\bea\wlserver6.1>cd config\CLUSTER1
          >
          > D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
          >
          > D:\bea\wlserver6.1\config\CLUSTER1>
          >
          > Many thanks in advance,
          > Alex Burton
          > http://www.e-plus.com.au/

Weblogic halting while starting Admin Server

I've created a SIP cluster. My understanding is you run startWebLogic.sh to start the admin server. I'm getting the following error (no matter how I create the domain).
Can anyone help explain what I'm doing wrong?
Thanks in advance for your help
Bill Goss
<Mar 16, 2009 12:59:41 PM MDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
WebLogic SIP Server 3.1 at 668557 built on: 2007/06/30
WebLogic Diameter 3.1 at 668557 built on 2007/06/30
WebLogic SCTP 3.1 at 665356 built on 06/04/2007 03:12:47 PDT>
<Mar 16, 2009 12:59:52 PM MDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141266|http://forums.oracle.com/forums/]Parsing Failure in config.xml: WorkManagerMBean 'wlss.transport' refers to a constraint or request class 'wlss.transport.fsrc' but they are deployed on targets that have no servers in common. Please deploy the mbeans such that they share atleast one server in common.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:122)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:38)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:67)
Caused by: java.lang.IllegalArgumentException: WorkManagerMBean 'wlss.transport' refers to a constraint or request class 'wlss.transport.fsrc' but they are deployed on targets that have no servers in common. Please deploy the mbeans such that they share atleast one server in common.
at weblogic.management.configuration.WorkManagerLegalHelper.validateTargets(WorkManagerLegalHelper.java:66)
at weblogic.management.configuration.WorkManagerMBeanImpl.setFairShareRequestClass(WorkManagerMBeanImpl.java:138)
at weblogic.management.configuration.WorkManagerMBeanImpl$1.resolveReference(WorkManagerMBeanImpl.java:120)
at weblogic.descriptor.internal.ReferenceManager$UnresolvedReference.resolve(ReferenceManager.java:369)
at weblogic.descriptor.internal.ReferenceManager.resolveReferences(ReferenceManager.java:271)
at weblogic.descriptor.internal.DescriptorImpl.validate(DescriptorImpl.java:289)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:289)
at weblogic.management.provider.internal.DescriptorManagerHelper.loadDescriptor(DescriptorManagerHelper.java:52)
at weblogic.management.provider.internal.RuntimeAccessImpl$IOHelperImpl.parseXML(RuntimeAccessImpl.java:599)
at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:110)
... 7 more
config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/920/domain
[http://www.bea.com/ns/weblogic/920/domain.xsd]" xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls">
<name>sipcluster</name>
<domain-version>9.2.1.0</domain-version>
<security-configuration xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml">
<name>sipcluster</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"/>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/>
<sec:authorizer xsi:type="xacml:xacml-authorizerType"/>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"/>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"/>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{3DES}tDGHUzjR++h5UL7aQTrTUlWU9GPhPYOBWqkI4rxcfALZLiaI9f2cHBubx1NryS8quhnEs3VFHeHraeOQSdHb5ViTduPNpMYy</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{3DES}+UMAJUjFbF6d0IAm1HcG3g==</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<machine>UnixMachine</machine>
<listen-address/>
<network-access-point>
<name>sip</name>
<protocol>sip</protocol>
<listen-port>5060</listen-port>
<public-port>5060</public-port>
<http-enabled-for-this-protocol>false</http-enabled-for-this-protocol>
<tunneling-enabled>false</tunneling-enabled>
<outbound-enabled>true</outbound-enabled>
<enabled>true</enabled>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<client-certificate-enforced>false</client-certificate-enforced>
</network-access-point>
</server>
<server>
<name>ManagedServer</name>
<machine>UnixMachine</machine>
<cluster>SipCluster</cluster>
<listen-address/>
</server>
<cluster>
<name>SipCluster</name>
<multicast-address>239.192.0.0</multicast-address>
<multicast-port>17001</multicast-port>
</cluster>
<embedded-ldap>
<name>sipcluster</name>
<credential-encrypted>{3DES}H0kJUtaBQ6gon62RYVhluFVRx6+AIgqzkQ4qoTEcrp4=</credential-encrypted>
</embedded-ldap>
<configuration-version>9.2.1.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>UnixMachine</name>
<node-manager>
<name>UnixMachine</name>
<listen-address/>
</node-manager>
</machine>
<migratable-target>
<name>ManagedServer (migratable)</name>
<user-preferred-server>ManagedServer</user-preferred-server>
<cluster>SipCluster</cluster>
</migratable-target>
<self-tuning>
<fair-share-request-class>
<name>wlss.transport.fsrc</name>
<target>AdminServer</target>
<fair-share>50</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.timer.fsrc</name>
<target>AdminServer</target>
<fair-share>100</fair-share>
</fair-share-request-class>
<fair-share-request-class>
<name>wlss.tracing.fsrc</name>
<target>AdminServer</target>
<fair-share>50</fair-share>
</fair-share-request-class>
<min-threads-constraint>
<name>wlss.tracing.minthreads</name>
<target>AdminServer</target>
<count>1</count>
</min-threads-constraint>
<max-threads-constraint>
<name>wlss.timer.maxthreads</name>
<target>AdminServer</target>
<count>16</count>
<connection-pool-name/>
</max-threads-constraint>
<max-threads-constraint>
<name>wlss.tracing.maxthreads</name>
<target>AdminServer</target>
<count>1</count>
<connection-pool-name/>
</max-threads-constraint>
<capacity>
<name>wlss.transport.capacity</name>
<target>AdminServer</target>
<count>400</count>
</capacity>
<capacity>
<name>wlss.timer.capacity</name>
<target>AdminServer</target>
<count>256</count>
</capacity>
<work-manager>
<name>wlss.transport</name>
<target>SipCluster</target>
<fair-share-request-class>wlss.transport.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<capacity>wlss.transport.capacity</capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.timer</name>
<target>SipCluster</target>
<fair-share-request-class>wlss.timer.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<max-threads-constraint>wlss.timer.maxthreads</max-threads-constraint>
<capacity>wlss.timer.capacity</capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.tracing.domain</name>
<target>SipCluster</target>
<fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
<min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
<max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
<work-manager>
<name>wlss.tracing.local</name>
<target>SipCluster</target>
<fair-share-request-class>wlss.tracing.fsrc</fair-share-request-class>
<response-time-request-class xsi:nil="true"/>
<context-request-class xsi:nil="true"/>
<min-threads-constraint>wlss.tracing.minthreads</min-threads-constraint>
<max-threads-constraint>wlss.tracing.maxthreads</max-threads-constraint>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>
</self-tuning>
<custom-resource>
<name>sipserver</name>
<target>AdminServer</target>
<descriptor-file-name>custom/sipserver.xml</descriptor-file-name>
<resource-class>com.bea.wcp.sip.management.descriptor.resource.SipServerResource</resource-class>
<descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>
</custom-resource>
<admin-server-name>AdminServer</admin-server-name>
</domain>

There looks to be some problem with the Work Manager, which is causing the server to fail during the startup. Try to disable or delete the Work Manager and restart the server instance.
- - Tarun

Not able to start the weblogic admin server

Hi,
I am getting the error while starting the weblogic admin server of OAM console.
Below is the stack trace of the error
####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834234> <BEA-000000> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834387> <BEA-000000> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
####<Sep 18, 2013 4:47:14 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834847> <BEA-000000> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
####<Sep 18, 2013 4:47:15 AM IST> <Info> <Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459835526> <BEA-000000> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the username attribute value of {AES}MCSBg4hMfpsECc7LXYV6gR52kLO5DHUWyo9I1UZXMaE= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/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 weblogic.security.internal.encryption.EncryptionServiceException.>
####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the password attribute value of {AES}1hgzo9/RGaCoWQyFXIJEbYMqmz5gg9LQzjQ/J6DxbQM= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/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 weblogic.security.internal.encryption.EncryptionServiceException.>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849081> <BEA-000000> <Server state changed to STARTING>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WorkManager> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849088> <BEA-000000> <Initializing self-tuning thread pool>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849138> <BEA-000000> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849208> <BEA-170019> <The server log file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849213> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Diagnostics> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849260> <BEA-320001> <The ServerDebug service initialized successfully.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3s" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "http" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "https" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiop" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiops" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldap" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldaps" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849310> <BEA-002622> <The protocol "cluster" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849311> <BEA-002622> <The protocol "clusters" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849313> <BEA-002622> <The protocol "snmp" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002622> <The protocol "admin" is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <RJVM> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849325> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address :7003
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Sep 18, 2013 4:47:29 AM IST> <Critical> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849347> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: weblogic.security.internal.encryption.EncryptionServiceException
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:1092)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1096)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000365> <Server state changed to FAILED>
####<Sep 18, 2013 4:47:29 AM IST> <Error> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849411> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849412> <BEA-000236> <Stopping execute threads.>
Kindly help me to solve this issue.
Is anyone had faced this issue.....

Hi,
I had tried by putting the username and password in boot.properties but we are getting the same issue.
we tried by editing the config.xml file of the domain.
i.e. by
Before: <credential-encrypted>{AES}b3I7UhWtRyj4DuKMIDVtW4Ln2nzH+HiYRhhQw1H2qpU0qJMOaDlK8iFZ+LvlJu+iZs6pptFJgWz8ryyudL1Zyvf00Rg11z9Iib7hoDC8covMFuig8wx7iOGK88zeKH7U</credential-encrypted>
After: <credential-encrypted>MyCredentialInPlainText</credential-encrypted>
and restarted the admin server but shows the same error.
kindly suggest us...

Admin Server Funcationality in a WebLogic Cluster

Similar Messages

Maybe you are looking for