Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • 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
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Problem in stopping WebSphere

Ranch Hand
Posts: 116
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm facing problem while stopping WebSphere 4.0.
It displays the following error message.
"The diagnostic host name was read as "localhost"
The diagnostic port was read as "7000"
Issuing command to stop server
A connection could not be made to perform the requested operation
This ususally indicates that the target server is stopped
This may indicate that thw wrong diagnostic port was used
The stop server command failed"
Has somebody encountered this error? If so, how do we resolve this?
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have never encounter a similar problem. I feel the application server has been stopped and you are trying to stop a stopped application server. Anyway find the thread of that application server and kill -9 threadNumber will do the job.
ps -ef | grep WebSphere or /usr/ucb/ps -auxww | grep WebSphere will give you more information.
There is no "i" in denial. Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic