Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Teamsite Installation in Solaris
mmadhu
Hi,
I have installed teamsite on Solaris. The problem that we are facing is the servlet keeps going down and we have to execute iwreset to start it again. I am not able to figure out the reason for this....can help on this will be appreciated.
Thanks,
Madhu
Find more posts tagged with
Comments
tvaughan
Hi Madhu,
What servlet? Have you tried tailing your iwserver.log?
mmadhu
I see this when i access the following URL:
http://10.225.22.11:81/iw/webdesk/teamsite/launch.jsp
I get the following message:
The TeamSite Web Daemon was unable to contact the TeamSite Servlet Engine. The TeamSite Servlet Engine may be down, or running on an unexpected host or port.
Please contact your system administrator.
i haven't check the logs.................
bscott1
Per the article attached below from the main IW site you should execute your iwreset command using the nohup command first. See below:
Article: 45678
Servlet engine dying on Solaris
Synopsis
If the Tomcat server, aka the servlet engine, keeps dying, this article may be of help.
Details
If you start TeamSite or run iwreset in a telnet session, the processes are tied to the telnet process. When the session is closed, the problem manifests itself by stating to the user that TeamSite is:
1 - Unable to contact the server (if the java process is still running)
2 - The TeamSite Web Daemon was unable to contact the TeamSite Servlet Engine.
3 - The TeamSite Servlet Engine may be down, or running on an unexpected host or
port. Please contact your system administrator (if the related java process
died along with iwopenapi)
Recommended practice is to log into the machine as a normal user, then su to root for TeamSite administration. If you do need to use telnet, the workaround is to run:
nohup iwreset -a
Or start TeamSite with nohup:
nohup /etc/init.d/iw.server start
Migrateduser
You may also want to take a look at /var/adm/iwui/servled.log Sometimes when servletd dies it will leave an exception that will give some clue as to what may have gone wrong.