• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WAS 6.1 server can not be started

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

My WAS 6.1 in windows server 2003, the deployment manager and node agent are started by window services, when I try to start one of the servers using admin console, I got "server could not be started. View JVM logs for further details.", when I check log, I got nothing.
When I logged on the WAS server machine and use command line to start the WAS server, it can be started and works fine, but when I logged off from the machine, the WAS server is stopped automatically, why?

 
Marshal
Posts: 28193
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When you log off your computer, all applications which you started when you were logged on are automatically stopped. So if you want Websphere to continue running, set it up as a service (this happens automatically when you install it) and just start the service.
reply
    Bookmark Topic Watch Topic
  • New Topic