SP6 upgrade issue

[former_member719672]

Hi All,

We upgraded our BOXI 3.1 SP3 to SP5 and finally to SP6. We are facing issue with the tomcat homepage opening.

http://localhost:8080/

Due to this reason we are neither able to logon to InfoView nor on Cmc.

Please help me with this issue.

Regards,

Deepak

[DayaJha]

Hi Deepak,

Please share the error details when you try to login in CMC or Infoview.

Thanks,

Daya

[former_member719672]

Hi Daya,
When try to open the CMC page its showing website found but not able to load the page. Even the tomcat homepage is not getting displayed http://localhost:8080/

Also we are seeing a that while stopping the tomcat its not at all getting stopped automatically. we meed to manually stop the tomcat.

Thanks

Deepak

[DayaJha]

Hi Deepak,

Please share the logs of Tomcat and BOBJ Application.

Tomcat Logs: Check in tomcat directory

BOBJ Application Logs: Check in Business Objects\logging directory in that SIA File.

Or Please Share the screen shots of CMC or Infoview

Thanks,

Daya

[former_member719672]

Hi Daya,

I got the issue resolved by rebotting the server but CMC seems to be very slow.

Regards,

Deepak

[Former Member]

Hi Deepak,

For your first issue, loading up http://localhost:8080/ is a Tomcat related issue. As soon as you install Tomcat, without deploying any kind of web applcations to it, you should see that page. If you don't, then you know something is wrong with the way Tomcat installed.

As far as your second issue, trying stopping Tomcat, clearing out the cache files ($CATALINA_HOME\work\Catalina\localhost), starting Tomcat back up. Something may just have gone wrong with the way Tomcat created the cache file. By deleting the old one and allowing Tomcat to create a new one, it should speed things up a bit.

If you're still noticing this slowish, redeploy the CMC application, after stopping the Tomcat service, to Tomcat using the following command in the command prompt:

wdeploy tomcat55 -DAPP=CMC deploy

I'd further suggest clearing out cache files, before starting Tomcat back up after a deployment, to ensure that no old files are left lingering around. This way, you know you have a clean deployment of CMC and it isn't that.

Hopefully the above resolves your issue.

-Victor