• 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
  • Paul Clapham
  • Tim Cooke
  • Jeanne Boyarsky
  • Liutauras Vilda
Sheriffs:
  • Frank Carver
  • Henry Wong
  • Ron McLeod
Saloon Keepers:
  • Tim Moores
  • Frits Walraven
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Himai Minh

starting the server

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i got the IBM websphere server and i have installed it
and while i am trying to start server it is showing error message like this

"C:\Program Files\IBM\WebSphere\AppServer\bin>startserver server1
ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\startServer.log
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.
ADMU7704E: Failed while trying to start the Windows Service associated with
server: server1;
probable error executing WASService.exe: Starting
Service: mildh0413Node01
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.



and another dought is do i need set any classpath. If so please tell me to which jar file it should point
how to deploy the project
 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Windows service? Windows service? I spit on the windows service.

The windows service just kicks off the startup batch file. The windows service is good for starting off tiny, insignificant applications like Norton Anti-Virus, or Windows Messaging. But for real applications built by IBM, the windows service is a waste.

The windows service expects everythnig to start up in 10 seconds or something. If your app server has a 500 meg footprint, which is the minimum practially with WebSphere, then just filling that memeory will take longer than the service is willing to wait. As a result, you get a timeout error from the service, despite the fact that WebSphere is starting normally and properly.

Plus, the service only starts server1, which is useless when you go to a federated domain.

Do the startserver server1 thing from the DOS propmt, aka command prompt, and look for errors there.

From that point, if there are problems, look in the log files.

Here's a great link about troubleshooting WebSphere Application Server problems, including info on trace logs, system logs, error logs, activity logs, the service log, and the IBM Log Analyzer tool:

How to TroubleShoot WebSphere Application Server Errors and Problems

Good luck!

-Cameron McKenzie
 
We begin by testing your absorbancy by exposing you to this tiny ad:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic