Jump to content
We've recently updated our Privacy Statement, available here ×

Upgrade from 3.0.1 to 3.1 failed: SEVERE: Error


leeyuiwah

Recommended Posts

Hi,

Season's greetings everyone!

I just upgraded my JasperServer Pro from 3.0.1 to 3.1, but then it refused to start.

I was already following the procedures outlined in the installation guide (Chapter 9: Upgrading from JasperServer 3.0 to JasperServer 3.1)

The error messages of apache-tomcat/logs/catalina.*.log is listed below -- but the most important lines are

Dec 24, 2008 6:42:06 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Dec 24, 2008 6:42:06 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/jasperserver-pro] startup failed due to previous errors

Apparently there were no error messages shown in localhost.*.log, but I am listing it anyway.

From my browser pointing to the server, I got this message: 404: The requested resource (/jasperserver-pro/) is not available.

Any help is appreciated.

 

Clement

Code:
catalina.*.logDec 24, 2008 6:42:01 PM org.apache.coyote.http11.Http11BaseProtocol initINFO: Initializing Coyote HTTP/1.1 on http-8080Dec 24, 2008 6:42:01 PM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 392 msDec 24, 2008 6:42:01 PM org.apache.catalina.core.StandardService startINFO: Starting service CatalinaDec 24, 2008 6:42:01 PM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/5.5.20Dec 24, 2008 6:42:01 PM org.apache.catalina.core.StandardHost startINFO: XML validation disabledDec 24, 2008 6:42:06 PM org.apache.catalina.core.StandardContext startSEVERE: Error listenerStartDec 24, 2008 6:42:06 PM org.apache.catalina.core.StandardContext startSEVERE: Context [/jasperserver-pro] startup failed due to previous errorsDec 24, 2008 6:42:06 PM org.apache.coyote.http11.Http11BaseProtocol startINFO: Starting Coyote HTTP/1.1 on http-8080Dec 24, 2008 6:42:06 PM org.apache.jk.common.ChannelSocket initINFO: JK: ajp13 listening on /0.0.0.0:8009Dec 24, 2008 6:42:06 PM org.apache.jk.server.JkMain startINFO: Jk running ID=0 time=0/14  config=nullDec 24, 2008 6:42:06 PM org.apache.catalina.storeconfig.StoreLoader loadINFO: Find registry server-registry.xml at classpath resourceDec 24, 2008 6:42:06 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 5298 ms---------------------------------------------------------------------localhost.*.logDec 24, 2008 6:42:06 PM org.apache.catalina.core.ApplicationContext logINFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain: [org.apache.webapp.balancer.RuleChain: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News / Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.rules.RequestParameterRule: Target param name: paramName / Target param value: paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL: http://jakarta.apache.org]]
Link to comment
Share on other sites

  • Replies 1
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Okay, I found the problem was related to two things

1. config parameters in WEB-INF/js.{mail,scheduler}.properties must be merged (manually) into the file WEB-INF/js.quartz.properties (see Section 9.3 of the Installation Guide)

2. there must not any one of the two stray files in the file system (see Appendix B.2.3 of the Installation Guide):

apache-tomcat/webapps/jasperserver-pro.war

apache-tomcat/conf/Catalina/localhost/jasperserver-pro.xml

For more info, see this thread

http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=48943&res=41

or equivalently,

http://tinyurl.com/6vc4wb

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...