Post install grief with JTS/CLM 4.0.4 and WAS 8.5.0.0
I was able to install both WAS 8.5 and JTS/CLM 4.0.4 with success. I cannot get the WAS server to restart however after modifications to WAS (configure for SQL server and install .war files) per the interactive guide and what I found @ https://jazz.net/wiki/bin/view/Deployment/ConfigureCLMOnWASWithLDAP.
Everything seemed to be going great until restart of server: F:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>stopServer.bat server1 ADMU0116I: Tool information is being logged in file F:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\stopServer.log ADMU7702I: Because server1 is registered to run as a Windows Service, the request to stop this server will be completed by stopping the associated Windows Service. ADMU0116I: Tool information is being logged in file F:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\stopServer.log ADMU0128I: Starting tool with the AppSrv01 profile ADMU3100I: Reading configuration for server: server1 ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server server1 stop completed.
F:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>startServer.bat server1 ADMU0116I: Tool information is being logged in file F:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\startServer.log ADMU7701I: Because server1 is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service. ADMU0116I: Tool information is being logged in file F:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\startServer.log ADMU0128I: Starting tool with the AppSrv01 profile ADMU3100I: Reading configuration for server: server1 ADMU3200I: Server launched. Waiting for initialization status. ADMU3011E: Server launched but failed initialization. Server logs, startServer.log, and other log files under F:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1 should contain failure information. ADMU7704E: Failed while trying to start the Windows Service associated with server: server1; probable error executing WASService.exe: Starting Service: jmini-alm1Node01Service failed to start. startServer return code = -1 Looking at start log: Host Operating System is Windows Server 2008 R2, version 6.1 Java version = 1.6.0, Java Compiler = j9jit26, Java VM name = IBM J9 VM was.install.root = F:\IBM\WebSphere\AppServer user.install.root = F:\IBM\WebSphere\AppServer\profiles\AppSrv01 Java Home = F:\IBM\WebSphere\AppServer\java\jre ws.ext.dirs = F:\\IBM\\WebSphere\\AppServer\\java\\lib;F:\\IBM\\WebSphere\\AppServer\\classes;F:\\IBM\\WebSphere\\AppServer\\lib;F:\\IBM\\WebSphere\\AppServer\\installedChannels;F:\\IBM\\WebSphere\\AppServer\\lib\\ext;F:\\IBM\\WebSphere\\AppServer\\web\\help;F:\\IBM\\WebSphere\\AppServer\\deploytool\\itp\\plugins\\com.ibm.etools.ejbdeploy\\runtime Classpath = F:\IBM\WebSphere\AppServer\profiles\AppSrv01\properties;F:\IBM\WebSphere\AppServer\properties;F:\IBM\WebSphere\AppServer\lib\startup.jar;F:\IBM\WebSphere\AppServer\lib\bootstrap.jar;F:\IBM\WebSphere\AppServer\java\lib\tools.jar;F:\IBM\WebSphere\AppServer/lib/lmproxy.jar;F:\IBM\WebSphere\AppServer/lib/urlprotocols.jar Java Library path = F:\IBM\WebSphere\AppServer\java\jre\bin\default;F:\IBM\WebSphere\AppServer\java\jre\bin;C:\Windows\system32;C:\Windows;F:\IBM\WebSphere\AppServer\lib\native\win\x86_64;F:\IBM\WebSphere\AppServer\bin;F:\IBM\WebSphere\AppServer\java\bin;F:\IBM\WebSphere\AppServer\java\jre\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\ActivIdentity\ActivClient\;C:\Program Files (x86)\ActivIdentity\ActivClient\;c:\Program Files (x86)\java\jre7\bin\;;. Orb Version = IBM Java ORB build orb626-20120304.00 Current trace specification = *=info:com.ibm.*=all ************* End Display Current Environment ************* [12/5/13 15:13:43:086 PST] 00000001 ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all. [12/5/13 15:13:43:117 PST] 00000001 WsServerContr 1 Executing executeUtilityOnWindows with args: F:\IBM\WebSphere\AppServer\profiles\AppSrv01\config jmini-alm1Node01Cell jmini-alm1Node01 server1 -fromWinService \\.\pipe\w6SvcPipe_1FBDE_1557C [12/5/13 15:13:43:117 PST] 00000001 WsServerContr 1 invokedByWindowsService has been set to true earlier [12/5/13 15:13:43:117 PST] 00000001 ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info. [12/5/13 15:13:43:242 PST] 00000001 AdminTool A ADMU0128I: Starting tool with the AppSrv01 profile [12/5/13 15:13:43:257 PST] 00000001 AdminTool A ADMU3100I: Reading configuration for server: server1 [12/5/13 15:13:43:273 PST] 00000001 ImplFactory W WSVR0072W: Ignoring undeclared override of interface, com.ibm.websphere.cluster.topography.DescriptionManager, with implementation, com.ibm.ws.cluster.propagation.bulletinboard.BBDescriptionManager [12/5/13 15:13:43:663 PST] 00000001 ModelMgr I WSVR0801I: Initializing all server configuration models [12/5/13 15:13:49:170 PST] 00000001 WorkSpaceMana A WKSP0500I: Workspace configuration consistency check is disabled. [12/5/13 15:13:52:633 PST] 00000001 AdminTool A ADMU3200I: Server launched. Waiting for initialization status. [12/5/13 15:13:54:910 PST] 00000001 AdminTool A ADMU3011E: Server launched but failed initialization. Server logs, startServer.log, and other log files under F:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1 should contain failure information. ideas? Thanks, Paul |
Accepted answer
|
I ended up rebooting server and was able to login to WAS and JTS consoles.
I will give this a look if I run into same issue. Thanks! -Paul Ralph Schoon selected this answer as the correct answer
|
One other answer
Ralph Schoon (63.1k●3●36●46)
| answered Dec 06 '13, 8:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Paul, I have seen WAS not shutting down and if it does not shut down, it won't restart.
Please have a look at this old workshop: https://jazz.net/library/article/662 there is an appendix, if I recall correctly, that explains how to kill the Java VM's of WAS still running to terminate WAS. Using the service stop and restart won't help either. Short of killing processes that don't terminate or a reboot, nothing will, I guess. I am not sure what the root cause could be, but I would try killing the Java VM's to be able to try to find out. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.