Starting WASCE 184.108.40.206 from the .bat file works correctly, attempting to start WASCE 220.127.116.11 as a Windows service returns
System Event log
The IBM WebSphere Application Server Community Edition Service - geronimosrv service terminated with service-specific error 0 (0x0).
2012-01-18 00:57:21 info Procrun (18.104.22.168) started
2012-01-18 00:57:21 info Running Service...
2012-01-18 00:57:22 info Starting service...
2012-01-18 00:57:22 http://1058 prunsrv.c error Failed executing process
2012-01-18 00:57:22 http://1271 prunsrv.c error ServiceStart returned 5
2012-01-18 00:57:22 info Run service finished.
2012-01-18 00:57:22 info Procrun finished.
Using Sun and IBM Java alternately produces the same results.
Platform details are
Windows XP SP3 version 2600.xpsp_sp3_gdr.111025-1629
WASCE version 22.214.171.124 build 201109141759
Eclipse Indigo SR 1 Build 20110916-0149
SUN Java Platform SE 6u30 version 6.0.300.12
IBM SDK Java2 Technology Edition version R2.4
This topic has been locked.
15 replies Latest Post - 2012-03-05T03:14:47Z by U4UE_xie_zhi
Pinned topic Starting WASCE 126.96.36.199 as a Windows service fails
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-03-05T03:14:47Z at 2012-03-05T03:14:47Z by U4UE_xie_zhi
SystemAdmin 110000D4XK2233 PostsACCEPTED ANSWER
Re: Starting WASCE 188.8.131.52 as a Windows service fails2012-01-21T02:52:46Z in response to U4UE_xie_zhiHi
I am having the same issue as what descirpted by "therophyte".
1.Starting WASCE 184.108.40.206 from the .bat file works correctly
2.attempting to start WASCE 220.127.116.11 as a Windows service returns
ServiceStart returned 5.
I am using Sun jdk.
I have tested in two platform:
windows xp SP3
and Window server 2003
Re: Starting WASCE 18.104.22.168 as a Windows service fails2012-02-13T02:18:08Z in response to SystemAdminHi,guys. Please replace your <WASCE_HOME>bin\service_pr.bat with which I attached before you backup it. And then try to execute the command "service_pr.bat install" again. Good luck!
Re: Starting WASCE 22.214.171.124 as a Windows service fails2012-02-13T18:43:28Z in response to U4UE_xie_zhiU4UE, the new batch file allows the service to be installed and started, but a few seconds after you start the service the CPU utilization spikes up to 100% with 99% being taken by java.exe. On windows 2003 server, the spike goes away after a few minutes, but then you can't stop the service. It fails, and you can't connect to the console either. On Windows 2008 server the CPU spike stays at 99% taken by java.exe and memory utilization swells up to about 300MB. Any assistance with this would be greatly appreciated. Thank you.
Forrest_Xia 270000P6BT82 PostsACCEPTED ANSWER
Re: Starting WASCE 126.96.36.199 as a Windows service fails2012-02-15T12:37:35Z in response to pbordinHi, pbordin, CharlieWaffles,
Thanks for trying this new service_pr.bat.
About the problem you met, Can you let us know if you could start the server normally from the command window via WASCE_HOME\bin\startup.bat? Please help post any findings here.
More information may require:
1. What's your windows version respectively?
2. What's the JDK used to start WAS CE 188.8.131.52?
3. Any error messages logged in the CE log files(var\log\server.out or/and var\log\server.log)?
Re: Starting WASCE 184.108.40.206 as a Windows service fails2012-02-15T14:02:42Z in response to Forrest_Xia> About the problem you met, Can you let us know if you could start the server normally from the command window > > via WASCE_HOME\bin\startup.bat? Please help post any findings here.
Yes, it starts correctly, no problems of cpu utilization, about 350 Mb of memory utilization reported by task manager
> More information may require:
> 1. What's your windows version respectively?
Windows 7 Professional x64
> 2. What's the JDK used to start WAS CE 220.127.116.11?
1.6.0_30 (build 1.6.0_30-b12), x64 edition
> 3. Any error messages logged in the CE log files(var\log\server.out or/and var\log\server.log)?
2012-02-15 11:55:50,546 WARN FeaturesServiceImpl Unable to add features repository at startup
java.lang.IllegalArgumentException: URI is not absolute
at java.net.URI.toURL(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Re: Starting WASCE 18.104.22.168 as a Windows service fails2012-02-15T17:57:11Z in response to Forrest_XiaThe best I can tell, the problem with with geronimo it keeps giving "java.lang.OutOfMemoryError: PermGen space" errors, and changing the -XX:MaxPermSize= to a larger value does not seem to make any difference. Hope this helps in troubleshooting.
FYI, the OS's I've tried this on are Windows 2003 32-bit and Windows 2008 64-bit, same behavior on both.
Re: Starting WASCE 22.214.171.124 as a Windows service fails2012-02-16T08:15:47Z in response to CharlieWaffleshi,CharlieWaffles. I tested WAS CE 126.96.36.199 in Windows Server 2008 Enterprise Edition R2(64bit). And the JDK I used is JRE 1.6.0 IBM J9 2.4. The CPU utilization spikes up to 100% with 99% being taken by java.exe too. But it just took one or two minutes.
1.install IBM JDK 60SR10 win.x64.
2.install IBM WAS CE188.8.131.52(201109141759)
3.remove windows service as default to install via the command "service_pr.bat remove"
4.replace service_pr.bat with which I posted in this thread.
5.install windows service via the command "service_pr.bat install".
6.start server via the command "net start geronimosrv".
a few seconds after log show service was started successfully, you can open the admin console while the CPU maybe be utilized highly. one or two minute passed, and when the memory which java.exe took reached to 500M-600M, the CPU utilization came down.
So I think WAS CE184.108.40.206 as windows service run well on the window2008 64bit. Could you provide your detail action?
By the way, could provide the memory size in your test server? And are there any other programs in use when you start WAS CE server?
Re: Starting WASCE 220.127.116.11 as a Windows service fails2012-02-16T18:40:37Z in response to U4UE_xie_zhiI will try your suggestion on the Win2008 64-bit server, but what about my Win2003 32-bit system? I am sure that the JDK will not be appropriate for it, right? And is there a problem with using the Oracle Java JDK 1.6? That is what I have on both servers right now. Should I remove that JDK prior to installing IBM's JDK? Thank you for your help.
Re: Starting WASCE 18.104.22.168 as a Windows service fails2012-02-21T16:38:41Z in response to U4UE_xie_zhiU4UE,
Could you provide a link for the IBM JDK 60SR10 win.x64 download? IBM website is not exactly user-friendly when it comes to locating downloads, and the best I could find was an SDK for 32-bit. No JDK of any kind not even for the 32-bit. Your help as always is greatly appreciated. Thank you.
Re: Starting WASCE 22.214.171.124 as a Windows service fails2012-03-05T03:14:47Z in response to CharlieWafflescould you access this link
Edited by: xiaofan_admin on Mar 4, 2012 10:14 PMUpdated on 2012-03-05T03:14:47Z at 2012-03-05T03:14:47Z by U4UE_xie_zhi