Error:
<Feb 18, 2014 9:48:51 PM SGT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Feb 18, 2014 9:48:51 PM SGT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.IllegalArgumentException: Invalid -
ve count -1
java.lang.IllegalArgumentException: Invalid -ve count -1
at weblogic.work.MinThreadsConstraint.<init>(MinThreadsConstraint.java:52)
at weblogic.work.GlobalWorkManagerComponentsFactory.create(GlobalWorkManagerComponentsFactory.java:328)
at weblogic.work.GlobalWorkManagerComponentsFactory.create(GlobalWorkManagerComponentsFactory.java:322)
at weblogic.work.GlobalWorkManagerComponentsFactory.initialize(GlobalWorkManagerComponentsFactory.java:112)
at weblogic.work.ServerWorkManagerFactory.initializeHere(ServerWorkManagerFactory.java:79)
at weblogic.work.ServerWorkManagerFactory.initialize(ServerWorkManagerFactory.java:59)
at weblogic.t3.srvr.BootService.start(BootService.java:61)
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:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
>
***************************************************************************
The WebLogic Server encountered a critical failure
Reason: Assertion violated
***************************************************************************
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class weblogic.protocol.ServerIdentityManager$Initializer
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:64)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:173)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:1078)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:429)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:415)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:206)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:482)
at weblogic.Server.main(Server.java:71)
Stopping Derby server...
Derby server stopped.
Root Cause: WorkManager is having Invalid count -1 for MinThreadsConstraint.
Resolution:
1. Go the config.xml file located at $Domain_home/config.
2. Look for the work managers having - ve( here -1) count in config.xml.
3. Modify config.xml and provide a positive number as MinThreadsConstraint. e.g. 1
4. Save config.xml
5. Restart server. It should come up without any issues.
Thank you so much! Your solution worked for me. I was facing the same problem from last one week, finally it got resolved because of your post. :)
ReplyDeleteGlad to hear that!!!
ReplyDeleteThank you so much .
DeleteThe solution was superb and really fast and accurate .
Regards
Barry
Anytime Barry!!!
DeleteRegards,
Puru
Worked For me as well. Though I dont had "-1" in config.xml, I deleted all WorkManagers and successfully started the managed servers.
ReplyDelete