• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

Websphere Stopping Issue

Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everyone,

I am not yet through with the issue that I had posted last time.Let me repeat the same with more detailed manner in this topic.
I am working on a web application which uses Websphere 4.0 as a web server.
I do development and testing on Test Server which has no issue what so ever.
But Live server shuts down unexpectedly once or twice in a month which is obviously not desirable.
After going through the logs, one thing I realized is that the Websphere tries to restart for some reason automatically and while restarting, it fails and stops suddenly.

The logs for the same are give at the bottom.
Can anyone please give their thoughts on this?
What makes the Websphere to restart automatically?

Thanks & Regards,

************ Start Display Current Environment ************
WebSphere AE 4.0.1 a0131.07 running with process name in1inetapps1/Default Server and process id 6112
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.3.0 IBM build cn130-20010609 (JIT enabled: jitc), Java Compiler = jitc
server.root = D:\WebSphere\AppServer
Java Home = D:\WebSphere\AppServer\java\jre
ws.ext.dirs = D:/WebSphere/AppServer/java/lib;D:/WebSphere/AppServer/classes;D:/WebSphere/AppServer/lib;D:/WebSphere/AppServer/lib/ext;D:/SQLLIB/java/db2java.zip
Classpath = D:/WebSphere/AppServer/properties;D:/WebSphere/AppServer/lib/bootstrap.jar
Java Library path = D:\WebSphere\AppServer\java\jre\bin;.;C:\WINNT\system32;C:\WINNT;D:\\WebSphere\\AppServer\\bin;D:\\SQLLIB\\bin;D:\\SQLLIB\\function;D:\\WebSphere\\AppServer\\java\\bin;D:\Program Files\ibm\gsk5\lib;d:\IBMDebug\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;D:\Program Files\SQLLIB\BIN;D:\Program Files\SQLLIB\SAMPLES\REPL;d:\bin;C:\jdk1.3.0_02\bin;D:\IBM\IMNNQ;D:\SQLLIB\BIN;D:\SQLLIB\FUNCTION;D:\SQLLIB\SAMPLES\REPL;D:\SQLLIB\HELP;D:\WebSphere\AppServer\bin
Current trace specification =
************* End Display Current Environment *************
[06.02.14 08:32:51:714 GMT+05:30] 725ce35a Server U Version : 4.0.1
[06.02.14 08:32:51:824 GMT+05:30] 725ce35a Server U Edition: Advanced Edition for Multiplatforms
[06.02.14 08:32:51:870 GMT+05:30] 725ce35a Server U Build date: Thu Aug 09 00:00:00 GMT+05:30 2001
[06.02.14 08:32:51:917 GMT+05:30] 725ce35a Server U Build number: a0131.07
[06.02.14 08:32:54:402 GMT+05:30] 725ce35a DrAdminServer I WSVR0053I: DrAdmin available on port 2727
[06.02.14 08:32:55:620 GMT+05:30] 138c235d Server A WSVR0023I: Server Default Server open for e-business
[06.02.14 08:58:59:080 GMT+05:30] 138c235d Server I WSVR0024I: Server Default Server stopped
Ketan Mohite
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey Friends,

I tried to find out reason for my problem on other sites through google and came to know about these Websphere Timeout parameters.
1.ping interval,
2.ping timeout,and
3.ping initial timeout

Most of the places it was mentioned that increasing these parameters avoids the ping errors.These ping errors makes Websphere to stop and start again(which is happening in my issue).

But I am not getting through the definitions of these parameters.
Can anyone please suggest which parameter should I increase in order to overcome my problem and upto what extent?

My default parameters for Websphers are
60 seconds for ping interval, 200 for ping timeout, and 300 for ping initial timeout.

Thanks & regards,
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!