Servled not coming up after upgrade

I just upgraded TS 6.5 sp2 on Solaris to 6.7. All went well until trying to access through the GUI. All we can get is

"The Interwoven Web Daemon was unable to contact the Interwoven Servlet Engine. The Interwoven Servlet Engine may be down, or running on an unexpected host or port.

Please contact your system administrator. "

Has anybody seen this scenario before? At wits end here.

the following error is pointed to in servled.log - > hs_error_****.log
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xd22f7e90, pid=2861, tid=1
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_10-b03 mixed mode)
# Problematic frame:
# C [libcssdk.so+0xaf7e90] find__t8_Rb_tree5Z7TStringZt4pair2ZC7TStringZP10UserRecordZt10_Select1st1Zt4pair2ZC7TStringZP10UserRecordZ24TStringCaseAwareLessThan
Zt9allocator1ZP10UserRecordRC7TString+0x28

Which is all very good greek to me.

Find more posts tagged with

Comments

Sailesh

Have you tried restarting the servlet engine?? Also have you checked what is the port number appearing in your iw.cfg file?? Seems that your port 8080 is already used my some other application.

smwangi

There is nothing using port 8080 and yes gave tried restarting the servlet, Teamsite and the box

iw_store

if its on production don't wait here, raise case with support Smiley Wink

smwangi

All resolved now. Thanks.

THis resolved it

in
cssdk.cfg removed "allowLocalMode=true"

Beats me why it was there in the first place

Amlan

I am experiencing the same problem trying to install TS 6.7.1 on Solaris 10, but in my case the attribute "allowLocalMode=true" is commented in cssdk.cfg. Any insights

Phanie

I have no clue so asking where can I find cssdk.cfg

Thanks,
Phanie

kg_brian

I have no clue so asking where can I find cssdk.cfg

Thanks,
Phanie

iw-home/TeamSite/cssdk/cssdk.cfg I believe... you can also do a search/find command depending on your OS.

bcvbbbjnn

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=58605
This article should help but need to validate for Solaris environment as the same article speaks for Windows server.

kg_brian

Thanks for all the help guys Smiley Happy

IW support ended up helping us via our ticket and figuring out the problem, although I am not sure yet why the problem existed.

In /iwopenapi/iwopenapi the IWServiceServer.lax file had a problem.

In it, every command said RMIPORT instead of our actual port, or TARGETHOME instead of our actual home. We went through and replaced those with the actual value, and everything works great.

Adam Stoller

Making the text visible

Thanks for all the help guys

IW support ended up helping us via our ticket and figuring out the problem, although I am not sure yet why the problem existed.

In <iw-home>/iwopenapi/iwopenapi the IWServiceServer.lax file had a problem.

In it, every command said <RMIPORT> instead of our actual port, or <TARGETHOME> instead of our actual home. We went through and replaced those with the actual value, and everything works great.