• 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

Communication exception when I start the admin server

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, I am not able to start the WebSphere admin server. When i checked the log files, there is a Communication Exception logged - "Check misspelled hostname or hostname case for admin server."
Please let me know which file needs to be modified.
Thanks for ur help.
 
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Did u start the server in services
 
nirupa
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am using WebSphere in AIX platform.
When I start the startupServer.sh, and then check the log file, it says
"Port XXX is already in use. Specify another port".
I changed the port in admin.config to a different one say YYY and after starting the server, I get a error message as
"Port YYY already in use"
Please let me know what is to be done
Thanks
 
Ranch Hand
Posts: 393
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
First all your name does not match with Java ranch naming policy.
secondly
2.a) issue command netstat -a and see which all ports r getting used.If u r logging as root then ports lower than 1024 is also avaiable,otherwise as non-root login these ports are not avaiable.
and look in trace file for exact error.
and If u have logged have in non-root,then make sure you have all the rights to start WAS as non-root user
and let us what trace files says ..?
[ June 19, 2002: Message edited by: james edwin ]
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic