cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP STatus 500 in Instance Manager

Former Member
0 Kudos

Hi Guys,

we are on BOXI 3.1 and I tried to call the Instance Manager, but I got the following error:

Any help is really appreciated!

Rgds,

Christian

-


type Exception report

message 

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

exception 

org.apache.jasper.JasperException: Exception in JSP: /Kind/InstanceConsole/list.jsp:337

334: type="hidden"
335: name="appKind"
336: value="CMC" >
337: div id="<%=hostApplicationBean.getUreDivName()%>" > < ure:explorer
338: id="UniversalRepositoryExplorer"
339: communicationMode="#{instanceBean.communicationMode}"
340: enterpriseSession="#{instanceBean.enterpriseSession}"

Stacktrace:
	org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:506)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:395)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:346)
	com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:152)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:107)
	com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:137)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:214)
	com.businessobjects.webutil.boetrustguard.BOETrustedRequestCreator.doFilter(BOETrustedRequestCreator.java:96)
	com.businessobjects.webutil.boetrustguard.BOETrustFilter.doFilter(BOETrustFilter.java:83)
	com.businessobjects.webutil.TimeoutCheckerFilter.doFilter(TimeoutCheckerFilter.java:99)

-


Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I got the same issue, and I fix it by going to CMC > preference > CMC preference >

if still cannot , try login on using  "Administrator" account

Former Member
0 Kudos

Hi,

I'm having the same issue.

We installed BOXI31. SP2 and I get the same error when I click on Instance Manager link.

Were you ever able to fix this problem? and How?

Thanks.

Former Member
0 Kudos

No, still not. Maybe you got it run?

Former Member
0 Kudos

Hi Christian,

Did you log a case with the support?

I am a member of the Administrator Group. I've always been able to access Instance Manager, however suddenly I'm getting the error

"HTTP Status 500 - "

"exception - org.apache.jasper.JasperException"

"root cause - java.lang.NullPointerException".

Have tried rebooting our Tomcat servers, and restarting the SIA's.

Still same problem.

Any ideas??

Env - BOXI 3.1 (Windows, Tomcat). SP2 not yet installed.

Thanks!

Former Member
0 Kudos

Service Pack 2 for BusinessObjects Enterprise 3.x. should have fixed it..... But since "Ghassan Zghaib" is having an issue,i am confussed..

Edited by: Steny Sebastian on Jan 11, 2010 11:47 PM

Former Member
0 Kudos

Hi guys,

I was able to fix the problem by doing the following:

1. Enable tracing on the CMS.

2. restart the CMS

3. Open Instance Manager and receive the HTTP 500 error

4. Stop the CMS tracing.

5. In the resulting log file, search for SI_NEXTRUNTIME. Copy the query and run it in Query Builder.

6. Search through the Query Builder results to see whether there is a scheduled object that has a blank SI_NEXTRUNTIME

7. In the Central Management Console(CMC), delete the pending instance that is missing the SI_NEXTRUNTIME.

8. Open Instance Manager to verify the error is resolved

Former Member
0 Kudos

Thanks for your Reply, it resolved my problem...i was able to look at the instance that had the Next Run Time "BLANK" and deleted it via the History tab..

Here is What i did..

1. Enable tracing on the CMS.

2. restart the CMS

3. Open Instance Manager and receive the HTTP 500 error

4. Stop the CMS tracing.

5. In the resulting log file, search for SI_NEXTRUNTIME. Copy the query and run it in Query Builder and added a condition which says SI_NEXTRUNTIME is NULL.

6. In the Central Management Console(CMC), went to the folder that had the publication.

7. Looked at the publication history, delete the pending instance that is missing the SI_NEXTRUNTIME.

8. Open Instance Manager to verify the error is resolved

Former Member
0 Kudos

Hi,

Try redeploying the admin.war files and restart the tomcat after.

Thanks

Shiva

Former Member
0 Kudos

Steny,

I'm glad your problem is solved.

Shiva, I tried redeploying and it didn't fix my problem. The issue is with the internal query that doesn't handle the case where SI_NEXTRUNTIME is null.

Former Member
0 Kudos

Could somebody please, share the Query builder script to find the list of instances for which the SI_NEXTRUNTIME is NULL?

former_member226344
Participant
0 Kudos

Steny,

    What level of trace was run?  We are having the same issue and was unable to get any information in the log files.

Gavin