jQuery in Action, 2nd edition*
The moose likes Websphere and the fly likes WAS 6.1 server1 as windows service is not working Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS 6.1 server1 as windows service is not working " Watch "WAS 6.1 server1 as windows service is not working " New topic
Author

WAS 6.1 server1 as windows service is not working

krish kaman
Greenhorn

Joined: Dec 29, 2010
Posts: 2
Dear friends , I have an issue and I hope you will be able to help me to solve the problem .

I have WAS 5.1 installed and 6.1 installed on the Windows 2003 Server . We have 5.1 server1 registred with windows services , So that every time the mechine starts the admin console can be accessable . Similarly I wanted to resister WAS 6.1.0.33 (base installation) server1 from one of the profile , but it is not starting up and giving the following error .

When I made the windows service startup Type as Disabled and start from command proppt "startServer server1" its coming up fine .

On other windows box I have just WAS 6.1 and I am able to register server1 as windows service and able to start w/ no issue .


Logs start ->>>>

************ Start Display Current Environment ************
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 2
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20100808 (JIT enabled)
J9VM - 20100629_60535_lHdSMr
JIT - 20100623_16197_r8
GC - 20100211_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = F:\Apps\WAS6.1
user.install.root = F:\Apps\WAS6.1\profiles\WSFPAppSrv03
Java Home = F:\Apps\WAS6.1\java\jre
ws.ext.dirs = F:\\Apps\\WAS6.1\\java\\lib;F:\\Apps\\WAS6.1\\classes;F:\\Apps\\WAS6.1\\lib;F:\\Apps\\WAS6.1\\installedChannels;F:\\Apps\\WAS6.1\\lib\\ext;F:\\Apps\\WAS6.1\\web\\help;F:\\Apps\\WAS6.1\\deploytool\\itp\\plugins\\com.ibm.etools.ejbdeploy\\runtime
Classpath = F:\Apps\WAS6.1\profiles\WSFPAppSrv03\properties;F:\Apps\WAS6.1\properties;F:\Apps\WAS6.1\lib\startup.jar;F:\Apps\WAS6.1\lib\bootstrap.jar;F:\Apps\WAS6.1/lib/j2ee.jar;F:\Apps\WAS6.1/lib/lmproxy.jar;F:\Apps\WAS6.1/lib/urlprotocols.jar;F:\Apps\WAS6.1\java\lib\tools.jar
Java Library path = F:\Apps\WAS6.1\java\jre\bin;.;F:\Apps\WAS6.1\bin;F:\Apps\WAS6.1\java\bin;F:\Apps\WAS6.1\java\jre\bin;C:\WINDOWS\system32;C:\WINDOWS\system32;F:\Apps\IBM\WebSphere MQ\Java\lib;C:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\Apps\IBM\WebSphere MQ\bin;F:\Apps\IBM\WebSphere MQ\WEMPS\bin;C:\WINDOWS\system32\WindowsPowerShell\v1.0;F:\PROGRA~2\IBM\SQLLIB\BIN;F:\PROGRA~2\IBM\SQLLIB\FUNCTION
Current trace specification = *=info:com.ibm.*=all
************* End Display Current Environment *************
[12/29/10 11:40:05:156 EST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
[12/29/10 11:40:05:156 EST] 0000000a WsServerContr 1 Executing executeUtilityOnWindows with args: F:\Apps\WAS6.1\profiles\WSFPAppSrv03\config WWSTDTESTWS01Node03Cell WWSTDTESTWS01Node03 server1 -fromWinService \\.\pipe\w6SvcPipe_18079_FDD0
[12/29/10 11:40:05:156 EST] 0000000a WsServerContr 1 invokedByWindowsService has been set to true earlier
[12/29/10 11:40:05:156 EST] 0000000a ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info.
[12/29/10 11:40:05:218 EST] 0000000a AdminTool A ADMU0128I: Starting tool with the WSFPAppSrv03 profile
[12/29/10 11:40:05:218 EST] 0000000a AdminTool A ADMU3100I: Reading configuration for server: server1
[12/29/10 11:40:07:921 EST] 0000000a AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
[12/29/10 11:40:17:984 EST] 0000000a AdminTool A ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in zOS) and other log files under F:\Apps\WAS6.1\profiles\WSFPAppSrv03\logs\server1 should contain failure information.

Logs end ->>>>

I did not find sysout.log at all created and I did not find much info in StartServer.log . I have Empty native_syserr and native_sysout .
Could you please help .

Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

This "F" drive which the config file refers to... is it a fixed hard drive on that server? Or is it a mapped drive which you map when you signed on to the machine?

I'm guessing you map it when you sign on, as most servers don't have F drives. Windows services don't have access to mapped drives so that's probably why Websphere won't run as a service with that configuration. Probably just as well, running Websphere from a remote system isn't really a good idea anyway.
krish kaman
Greenhorn

Joined: Dec 29, 2010
Posts: 2
Thanks for quick reply

F:\ is not a mapped drive . Its one of the partition . We have WAS 5.1 also in the same drive and able to add as service and running .
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WAS 6.1 server1 as windows service is not working