VMware Cloud Community
agiuoco
Contributor
Contributor
Jump to solution

THROWABLE-WAS-NULL error at login after upgrade to 4.0.3

I am getting a Java exception when I log into Hyperic. This started after I upgraded my Hyperic server from version 3.2.4 to 4.0.3. Everything else seems to work after I get past the Java error, but I would like to know how to fix this because it comes up every time I log in. Full error below and here is my server information.

OS: RHEL 5, 64-bit
Hyperic Version: HQ 4.0.3, build 953


===============================
Exception:
THROWABLE-WAS-NULL (at java.lang.Exception at org.hyperic.util.StringUtil.getStackTrace(StringUtil.java:409) at org.apache.jsp.common.GenericError_jsp._jspService(Unknown Source) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:362) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:283) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Unknown Source) )
0 Kudos
1 Solution

Accepted Solutions
mcmesser
Hot Shot
Hot Shot
Jump to solution

It's not an issue with the upgrade, it's a problem with the URL you likely have in your bookmark or browser history from 3.2. See:

http://jira.hyperic.com/browse/HHQ-2858

In short, don't access http://server/Login.do since the redirect to SignIn.html causes the stacktrace. Access / or SignIn.html to avoid the error.

View solution in original post

0 Kudos
4 Replies
excowboy
Virtuoso
Virtuoso
Jump to solution

Hi,

afaik the major upgrade only is supported from 3.2.5 to 4.0.x .
Do you still have your old 3.2.4 version with the database available ? Could you try to upgrade to 3.2.5 first and then to 4.0.3 ?

Cheers,
Mirko
0 Kudos
agiuoco
Contributor
Contributor
Jump to solution

The documentation doesn't specify any supported upgrade path. It uses a 3.2.5 to 4.0 upgrade as an example, but it never says that is the only supported version to upgrade from.

http://support.hyperic.com/display/DOC/Upgrade+HQ+Components

Message was edited by: agiuoco
0 Kudos
mcmesser
Hot Shot
Hot Shot
Jump to solution

It's not an issue with the upgrade, it's a problem with the URL you likely have in your bookmark or browser history from 3.2. See:

http://jira.hyperic.com/browse/HHQ-2858

In short, don't access http://server/Login.do since the redirect to SignIn.html causes the stacktrace. Access / or SignIn.html to avoid the error.
0 Kudos
agiuoco
Contributor
Contributor
Jump to solution

Yeah, it looks like the problem was with my bookmark pointing to the Login.do page. I removed that, loaded it again, and everything is good. No error. Thanks!
0 Kudos