server 3.7 to 5.6 upgrade failing to start

[topkatz]

I'm trying to upgrade a working jasperserver 3.7 ce install on CentOS 7 up to 5.6.1

My 3.7 is using packaged tomcat 5.5 and installed mysql.  I downloaded the jasperreports-server-cp-5.6.1.bin.zip and folowed the upgrade directions.  I exported my 3.7 data.  I then copied and edited the buildomatic config.  I then ran js-upgrade-newdb-ce.sh with my exported file.  I did recive a "WARNING: JAVA_HOME enviorment not found"  It rant eh script and said it succeded.  After I started back up jasperserver usign the jasperctl script.  Trying to log in I get 404.  Here is the catalina.out:

Dec 11, 2014 11:53:30 AM org.apache.coyote.http11.Http11BaseProtocol destroyINFO: Stopping Coyote HTTP/1.1 on http-8080Dec 11, 2014 11:53:36 AM org.apache.coyote.http11.Http11BaseProtocol initINFO: Initializing Coyote HTTP/1.1 on http-8080Dec 11, 2014 11:53:36 AM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 338 msDec 11, 2014 11:53:36 AM org.apache.catalina.core.StandardService startINFO: Starting service CatalinaDec 11, 2014 11:53:36 AM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/5.5.20Dec 11, 2014 11:53:36 AM org.apache.catalina.core.StandardHost startINFO: XML validation disabledDec 11, 2014 11:53:37 AM org.apache.catalina.startup.HostConfig deployDirectorySEVERE: Error deploying web application directory jasperserverorg.apache.commons.logging.LogConfigurationException: java.lang.UnsupportedClassVersionError: Bad version number in .class file (Caused by java.lang.UnsupportedClassVersionError: Bad version number in .class file)    at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:538)    at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)    at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)    at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:380)    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4114)    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)    at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)    at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)    at org.apache.catalina.core.StandardService.start(StandardService.java:450)    at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)    at org.apache.catalina.startup.Catalina.start(Catalina.java:551)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)    at java.lang.reflect.Method.invoke(Method.java:585)    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file    at java.lang.ClassLoader.defineClass1(Native Method)    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)    at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1815)    at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:869)    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1322)    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1201)    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)    at java.lang.Class.forName0(Native Method)    at java.lang.Class.forName(Class.java:164)    at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)    at org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:317)    at org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:120)    at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:629)    at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)    at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)    at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)    at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)    at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)    at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)    at org.apache.log4j.Logger.getLogger(Logger.java:104)    at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:229)    at org.apache.commons.logging.impl.Log4JLogger.<init>(Log4JLogger.java:65)    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)    at java.lang.reflect.Constructor.newInstance(Constructor.java:494)    at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)    ... 26 more[/code]

Not sure what went wrong.  I can see that the jasperctl script is useing the JRE_HOME in the jasperserver-3.7 dir.  Any ideas what happend or what to look at?