Why the Webservice For Demantra Fails To Start? (Doc ID 1552804.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Demantra Demand Management - Version 7.3.1 and later
Information in this document applies to any platform.

Goal

Webservice for Demantra fails to start.

From the startserver.log file:

 ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
 WsServerContr 1 Executing executeUtilityOnWindows with args: C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config Node01Cell Node01 server1
 WsServerContr 1 Getting WindowsService obj with: server1 and C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config Node01Cell Node01 server1
 WindowsServic > getWindowsServiceNameForServer() Entry
 WindowsServic 1 In executeCommand, args arC: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -getServiceName server1 -profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01
 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@667c667c
 WindowsServic 3 inputRec == IBMWAS61Service - Node01
 WindowsServic 1 retCode from childProcess.waitFor() is 0
 WindowsServic 3 exitCode = 0
 WindowsServic 1 Trying to new up WindowsService using serverName=server1, winServiceName=Node01
 WindowsServic > getServiceLogName() Entry
 WindowsServic 1 In executeCommand, args arC: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -getServiceLogName server1 -profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01
 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@57165716
[13/05/13 05:53:33:763 CAT] 0000000e WindowsServic 3 inputRec == C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\Node01 Service.log
 WindowsServic 1 retCode from childProcess.waitFor() is 0
 WindowsServic 3 exitCode = 0
 WindowsServic 1 In executeCommand, args arC: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -status Node01
 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@72147214
[13/05/13 05:53:34:778 CAT] 00000010 WindowsServic 3 inputRec == The service is stopped.
 WindowsServic 1 retCode from childProcess.waitFor() is 1
 WindowsServic 3 exitCode = 1
 WindowsServic 1 In executeCommand, args arC: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -status Node01
 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@d360d36
 WindowsServic 3 inputRec == The service is stopped.
 WindowsServic 1 retCode from childProcess.waitFor() is 1
 WindowsServic 3 exitCode = 1
 WsServerContr 1 Window service status (1=stopped, 2=started, 3=not-registred) is 1
 AdminTool A 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.
 WindowsServic 3 arrayList = [C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe, -start, Node01]
 WindowsServic 1 In executeCommand, args arC: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -start Node01
 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@3a2c3a2c
 WindowsServic 3 waitForFileExist(C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\Node01 Service.log)
 EncodingUtils > getProperEncoding Entry
 EncodingUtils 3 System.getProperty("file.encoding") is: Cp1252
 EncodingUtils > isPlatformWindows() Entry
 WindowsServic 3 *** returned readerencoding = Cp850
 WindowsServic 3 inputRec == Starting ServicC: Node01
 WindowsServic 3 inputRec == Timed out waiting for service to respond to command, after 60 seconds.
 WindowsServic 3 inputRec == Failed to start service, or timed out while waiting for start to complete. Check the logs for details.
 WindowsServic 3 inputRec ==
 WindowsServic 1 retCode from childProcess.waitFor() is -1
 WindowsServic 3 -- interrupt the thread that is collecting stdout
 WindowsServic 3 exitCode = -1
 WindowsServic 3 readAndDisplayServiceLogFile(), caught InterruptedException
 WindowsServic 3 Timed out waiting for service to respond to command, after 60 seconds.Failed to start service, or timed out while waiting for start to complete. Check the logs for details.
 AdminTool A ADMU7704C: Failed while trying to start the Windows Service associated with server: server1;
probable error executing WASService.exC: Starting ServicC: Node01
Timed out waiting for service to respond to command, after 60 seconds.Failed to start service, or timed out while waiting for start to complete. Check the logs for details.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms