Re: Service Manager 9.33 Mobility upgrade issue. (195 Views)
Occasional Contributor
Posts: 5
Registered: ‎05-03-2014
Message 1 of 3 (242 Views)

Service Manager 9.33 Mobility upgrade issue.

Hi, all,


Today I try to upgrade service manager mobility from 9.30 to 9.33, but failed. I've upgraded my server and client successfully. My upgrade steps: go to \\HP\Service Manager 9.30\SM_Mobility\Tomcat\webapps, delete the mobileItsmWebApp folder, delete cache, temp and log files, then copy and replace the mobileItsmWebApp.war from the But when I restart the tomcat, I get below error message:


Error deploying web application archive mobileItsmWebApp.war
java.lang.UnsupportedClassVersionError: org/apache/compressfilter/CompressionFilter : Unsupported major.minor version 51.0 (unable to load class org.apache.compressfilter.CompressionFilter)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(
at org.apache.catalina.loader.WebappClassLoader.findClass(
at org.apache.catalina.loader.WebappClassLoader.loadClass(
at org.apache.catalina.loader.WebappClassLoader.loadClass(
at org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(
at org.apache.catalina.startup.WebAnnotationSet.loadApplicationFilterAnnotations(
at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(
at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(
at org.apache.catalina.startup.ContextConfig.start(
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
at org.apache.catalina.core.StandardContext.start(
at org.apache.catalina.core.ContainerBase.addChildInternal(
at org.apache.catalina.core.ContainerBase.addChild(
at org.apache.catalina.core.StandardHost.addChild(
at org.apache.catalina.startup.HostConfig.deployWAR(
at org.apache.catalina.startup.HostConfig.deployWARs(
at org.apache.catalina.startup.HostConfig.deployApps(
at org.apache.catalina.startup.HostConfig.start(
at org.apache.catalina.startup.HostConfig.lifecycleEvent(
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
at org.apache.catalina.core.ContainerBase.start(
at org.apache.catalina.core.StandardHost.start(
at org.apache.catalina.core.ContainerBase.start(
at org.apache.catalina.core.StandardEngine.start(
at org.apache.catalina.core.StandardService.start(
at org.apache.catalina.core.StandardServer.start(
at org.apache.catalina.startup.Catalina.start(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.apache.catalina.startup.Bootstrap.start(
at org.apache.catalina.startup.Bootstrap.main(


I search the error on google, it says that this exception can occur when the source is built targeting a JDK that is not supported by the JDK attempting to run it. And I also search the JDK information, the class file version for Java SE 7 is 51. Does it means I need unistall my JDK6 and reinstall the JDK7?

Posts: 26
Registered: ‎09-17-2012
Message 2 of 3 (212 Views)

Re: Service Manager 9.33 Mobility upgrade issue.

Yes Kimi..
For SM Mobility 9.33 please find the compatibility s/w
Apache Tomcat 7.0.32 or a later version
Note: The application server should run on Oracle JRE 1.7
(update 45 or a later version).
Occasional Contributor
Posts: 5
Registered: ‎05-03-2014
Message 3 of 3 (195 Views)

Re: Service Manager 9.33 Mobility upgrade issue.

Thanks for your reply. Tomcat works well now after reinsatll JDK 7u55. But when I visit the URL in the chrome broswer, something will display but I don't know what is it.




Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /WEB-INF/jsp/login_std_mobile.jsp(18,33) The function getMessage must be used with a prefix when a default namespace is not specified
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(


Now I doubt the sm9.33.2001_Mobility zip file, waiting for SM expert explaination.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.