WAS launched but failed initialization
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Search for "enabled" within security.xml. It was the first occurrence of "enabled" in the Windows security.xml file; I can not guarantee that this will be the case for AIX, so check that the line looks something like what I described.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 108
- Joined: Sat Feb 05, 2005 6:52 pm
- Location: US
Followed your instructions, Worked great.
xmlns:security="http://www.ibm.com/websphere/appserver/ ... curity.xmi" xmi:id="Security_1" useLocalSecurityServer="true" useDomainQualifiedUserNames="false" enabled="false" cacheTimeout="600"
xmlns:security="http://www.ibm.com/websphere/appserver/ ... curity.xmi" xmi:id="Security_1" useLocalSecurityServer="true" useDomainQualifiedUserNames="false" enabled="false" cacheTimeout="600"
Every great mistake has a halfway moment, a split second when it can be recalled and perhaps remedied.
Server launched. Waiting for initialization status.
Ray/Abhi,
I have a similar situation , during installation it hangs at 35% "Starting Websphere Application Server" . I installing on a 2003 windows server. Here is the log from StartServer.log .
************ Start Display Current Environment ************
Host Operating System is Windows 2003, version 5.2
Java version = J2RE 1.4.2 IBM Windows 32 build cn142-20060421 (SR5) (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\IBM\WebSphere\AppServer
user.install.root = C:\IBM\WebSphere\AppServer/profiles/default
Java Home = C:\IBM\WebSphere\AppServer\java\jre
ws.ext.dirs = C:\IBM\WebSphere\AppServer\java\lib;C:\IBM\WebSphere\AppServer\classes;C:\IBM\WebSphere\AppServer\lib;C:\IBM\WebSphere\AppServer\installedChannels;C:\IBM\WebSphere\AppServer\lib\ext;C:\IBM\WebSphere\AppServer\web\help;C:\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime
Classpath = C:\IBM\WebSphere\AppServer/profiles/default\properties;C:\IBM\WebSphere\AppServer\properties;C:\IBM\WebSphere\AppServer\lib\bootstrap.jar;C:\IBM\WebSphere\AppServer\lib\j2ee.jar;C:\IBM\WebSphere\AppServer\lib\lmproxy.jar;C:\IBM\WebSphere\AppServer\lib\urlprotocols.jar
Java Library path = C:\IBM\WebSphere\AppServer\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\IBM\WebSphere\AppServer\bin;C:\IBM\WebSphere\AppServer\java\bin;C:\IBM\WebSphere\AppServer\java\jre\bin;C:\Program Files\Legato\nsr\bin;C:\Program Files\Support Tools\;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\IBM\SQLLIB\BIN;C:\IBM\SQLLIB\FUNCTION;C:\IBM\SQLLIB\SAMPLES\REPL;C:\IBM\SQLLIB\BIN
Current trace specification = *=info
************* End Display Current Environment *************
[4/28/10 10:13:19:729 EDT] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[4/28/10 10:13:19:932 EDT] 0000000a AdminTool A ADMU0128I: Starting tool with the default profile
[4/28/10 10:13:19:932 EDT] 0000000a AdminTool A ADMU3100I: Reading configuration for server: server1
[4/28/10 10:13:23:198 EDT] 0000000a AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
It just hangs at this point. Any advise ?
Thanks!
I have a similar situation , during installation it hangs at 35% "Starting Websphere Application Server" . I installing on a 2003 windows server. Here is the log from StartServer.log .
************ Start Display Current Environment ************
Host Operating System is Windows 2003, version 5.2
Java version = J2RE 1.4.2 IBM Windows 32 build cn142-20060421 (SR5) (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\IBM\WebSphere\AppServer
user.install.root = C:\IBM\WebSphere\AppServer/profiles/default
Java Home = C:\IBM\WebSphere\AppServer\java\jre
ws.ext.dirs = C:\IBM\WebSphere\AppServer\java\lib;C:\IBM\WebSphere\AppServer\classes;C:\IBM\WebSphere\AppServer\lib;C:\IBM\WebSphere\AppServer\installedChannels;C:\IBM\WebSphere\AppServer\lib\ext;C:\IBM\WebSphere\AppServer\web\help;C:\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime
Classpath = C:\IBM\WebSphere\AppServer/profiles/default\properties;C:\IBM\WebSphere\AppServer\properties;C:\IBM\WebSphere\AppServer\lib\bootstrap.jar;C:\IBM\WebSphere\AppServer\lib\j2ee.jar;C:\IBM\WebSphere\AppServer\lib\lmproxy.jar;C:\IBM\WebSphere\AppServer\lib\urlprotocols.jar
Java Library path = C:\IBM\WebSphere\AppServer\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\IBM\WebSphere\AppServer\bin;C:\IBM\WebSphere\AppServer\java\bin;C:\IBM\WebSphere\AppServer\java\jre\bin;C:\Program Files\Legato\nsr\bin;C:\Program Files\Support Tools\;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\IBM\SQLLIB\BIN;C:\IBM\SQLLIB\FUNCTION;C:\IBM\SQLLIB\SAMPLES\REPL;C:\IBM\SQLLIB\BIN
Current trace specification = *=info
************* End Display Current Environment *************
[4/28/10 10:13:19:729 EDT] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[4/28/10 10:13:19:932 EDT] 0000000a AdminTool A ADMU0128I: Starting tool with the default profile
[4/28/10 10:13:19:932 EDT] 0000000a AdminTool A ADMU3100I: Reading configuration for server: server1
[4/28/10 10:13:23:198 EDT] 0000000a AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
It just hangs at this point. Any advise ?
Thanks!
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
One of the rules here is: different question ==> start new thread
Your problem is not "WAS launched but failed initialization". That's why a new thread is needed, so as to aid future searchers.
Your problem is not "WAS launched but failed initialization". That's why a new thread is needed, so as to aid future searchers.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.