HP BladeSystem

Asi_2 — Wed, 24 Aug 2005 10:09:08 GMT

hi All

i upgrade from version 4.2 to version 5

but when i try to connect to the HP BladeSystem,
i get an error that say HTTP Status 500 the exception "org.apache.jasper.JasperException: Unable to compile class for JSP"

in the old version everything work great and in the new version only the HP BladeSystem not working

can anyone know what the meaning of this error

thanks

Re: HP BladeSystem

MASCIO — Thu, 25 Aug 2005 04:51:40 GMT

Hi,
I have the same problem.

I upgraded my HP SIM 4.2 SP2 running on W2k3 with the SIM 5.0.
The upgrade worked fine :

Custom install, not installed the following 3 options.

- ProLiant Essentials Performance Management Pack v1.11
- ProLiant Essentials Virtual Machine Management Pack v1.11
- ProLiant Essentials Server Migration Pack v1.11

The SIM seem working fine except for one thing,

the HP BladeSystem, when I select it, the following message appear :

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: 9 in the jsp file: /mxportal/bladeime/Montero.jsp
Generated servlet error:
C:\Program Files\HP\Systems Insight

Manager\jboss\server\hpsim\work\jboss.web\localhost\_\org\apache\jsp\mxportal\bladeime\Montero_jsp.java:84: cannot find

symbol
symbol : method getCollectionClient()
location: class com.hp.mx.portal.ui.MxLoginBean
MxCollectionClient collectionClient = loginBean.getCollectionClient();
^

An error occurred at line: 9 in the jsp file: /mxportal/bladeime/Montero.jsp
Generated servlet error:
C:\Program Files\HP\Systems Insight

Manager\jboss\server\hpsim\work\jboss.web\localhost\_\org\apache\jsp\mxportal\bladeime\Montero_jsp.java:85:

getCollection(com.hp.mx.core.objectmodel.MxObjectID) in com.hp.mx.core.client.MxCollectionClient cannot be applied to

(java.lang.String)
collection = collectionClient.getCollection(MxCollectionConstants_t.HP_BLADESYSTEM);
^
2 errors

org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332)
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:412)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:472)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
sun.reflect.GeneratedMethodAccessor241.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAsPrivileged(Unknown Source)
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:272)
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)
java.security.AccessController.doPrivileged(Native Method)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
sun.reflect.GeneratedMethodAccessor242.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAsPrivileged(Unknown Source)
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:272)
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:217)

note The full stack trace of the root cause is available in the Apache Tomcat/5.0.30 logs.

Michele

Re: HP BladeSystem

Darrin Rawls — Mon, 29 Aug 2005 11:00:42 GMT

Can you let us know the upgrade 'path' you took - we can't duplicate this anywhere. Like SIM 4.1, up to 4.2 SP1, SIM5.

Anything else you can think of that would be different than the norm?

Also, be sure and log a support case so we can get the support folks tied in!

Re: HP BladeSystem

MASCIO — Tue, 30 Aug 2005 08:16:57 GMT

Hi,

This was the history : 4.1 / 4.2 / 4.2SP1 /
Hotfix for mx authentication (Administrator was renamed on the Server) / BladeSystem 1.1
4.2 SP2 / 5.0

Trendmicro TMCM is also running on the Server.

Michele

Re: HP BladeSystem

Crystal Diaz — Tue, 20 Dec 2005 15:44:04 GMT

Was this ever resolved? I an having the same problem.

Re: HP BladeSystem

MASCIO — Wed, 21 Dec 2005 02:19:29 GMT

Hi,

Yes for me, but I had to uninstall SIM AND
delete the old's SIM Database whitin
SQL Server. After the new install,
everything seem to work.

Michele

topic Re: HP BladeSystem in Server Management - Systems Insight Manager

HP BladeSystem

Re: HP BladeSystem

Re: HP BladeSystem

Re: HP BladeSystem

Re: HP BladeSystem

Re: HP BladeSystem