ccpro jsp 500 error on upgrading to 7.4.1 TS

Just upgraded from 7.3.1 to 7.4.1 . Upgrade went smoothly. TeamSite seems to have installed properly as admin ui & "TeamSite UI" seems to be working.

But "Content Center Professional" is our main UI which seems to be broken with following error shown on the jsp page.

Seems this has something to do with the reporting module.

iwjboss log & ccpro jsp screenshots are attached .

Any pointers on debugging?

TS 7.4.1

RHEL 5.3

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

org.apache.jasper.JasperException: Unable to compile class for JSP: 

An error occurred at line: 30 in the generated java file
Only a type can be imported. com.interwoven.ui.teamsite.util.ReportsUtil resolves to a package

An error occurred at line: 42 in the jsp file: /ccpro/common/navbar.inl
ReportsUtil cannot be resolved
39:     boolean hasDomain = domainIndex >= 0;
40:     visibleName = hasDomain ? displayName.substring(domainIndex+1) : displayName;
41: }
42:  boolean isAdvancedReportInstalled = ReportsUtil.isAdvancedReportInstalled(client);
43: %>
44: 
45: <script type="text/javascript">

Find more posts tagged with

Comments

MikeMiracle

from this stackoverflow post. http://stackoverflow.com/questions/1858463/java-error-only-a-type-can-be-imported-xyz-resolves-to-a-package

It seems com.interwoven.ui.teamsite.util.ReportsUtil is not in the classpath for ccpro webapp.

Copying a jar which has the said class may solve the problem , But I am not sure which jar has the class.

Rick Poulin

Did you have TeamSite JARs in your UITK build? Meaning in folders TeamSite/local/config/lib/content_center/customer_src and livesite_customer_src. If so, those would have to be updated with the latest copies. Otherwise, you can try rebuilding the iw-cc app from source using

# sudo TeamSite/install/install_webapps.ipl -i -f content_center

MikeMiracle

Had to take help from HP support. teamsite.jar was still old after the inplace upgrade . copying the latest jar from one of the webapps and making the toolkit fixed the issue.