Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

After Upgrade to 1.7.9 jetty needs several minutes to come up

Description

I did the upgrade from 1.7.7 to 1.7.9 on my SLES 10 SP2 box with the rpm packages.
The only major problem I (and some others - see mailing list) have is that jetty takes several minutes to start.

From my jetty log:
2010-03-04 13:38:18,168 INFO [Main] log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
2010-03-04 13:38:18,169 WARN [Main] JettyServer: adding context: /opennms -> /opt/opennms/jetty-webapps/opennms
2010-03-04 13:38:18,214 WARN [Main] JettyServer: adding context: /opennms-remoting -> /opt/opennms/jetty-webapps/opennms-remoting
2010-03-04 13:38:18,214 WARN [Main] JettyServer: adding context: / -> /opt/opennms/jetty-webapps/ROOT
2010-03-04 13:38:18,214 DEBUG [Main] JettyServer: OpenNMS.JettyServer initialization complete.
2010-03-04 13:38:18,214 DEBUG [Main] JettyServer: SPRING: context.classLoader= java.net.FactoryURLClassLoader@1b17a8bd
2010-03-04 13:38:19,766 DEBUG [Main] JettyServer: OpenNMS.JettyServer starting.
2010-03-04 13:38:19,766 INFO [Main] log: jetty-6.1.22

  1.  

    1. Now at least 3 minutes sitting and waiting for §"&$§"/ ##

    2. web interface is not accessible

2010-03-04 13:41:33,804 WARN [Main] log: Could not instantiate listener org.opennms.web.InitializerServletContextListener
java.lang.ClassNotFoundException: org.opennms.web.InitializerServletContextListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:579)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363)
at org.mortbay.jetty.handler.ContextHandler.loadClass(ContextHandler.java:1101)
at org.mortbay.jetty.webapp.WebXmlConfiguration.initListener(WebXmlConfiguration.java:630)
at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:368)
at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289)
at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222)
at org.mortbay.jetty.webapp.WebXmlConfiguration.configureWebApp(WebXmlConfiguration.java:180)
<snip>
2010-03-04 13:41:33,805 WARN [Main] log: Could not instantiate listener org.opennms.web.DependencyCheckingContextListener
java.lang.ClassNotFoundException: org.opennms.web.DependencyCheckingContextListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:579)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363)
at org.mortbay.jetty.handler.ContextHandler.loadClass(ContextHandler.java:1101)
at org.mortbay.jetty.webapp.WebXmlConfiguration.initListener(WebXmlConfiguration.java:630)
<snip>
2010-03-04 13:41:34,258 INFO [Main] log: Started SelectChannelConnector@0.0.0.0:8980

####################################################
After the exception the webinterface starts up with no recognizable error.

Environment

Operating System: All Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed May 18, 2010 at 9:23 AM

confirmed that everything still works without the doctype

[master 2a48ca0] fix for - slow startup of Jetty

Benjamin Reed May 18, 2010 at 7:51 AM

If you can go to http://your-host:8980/opennms-remoting/ and click on a remote monitor link and have the monitor come up, it's working.

Daniel Hammon May 18, 2010 at 6:01 AM

It´s working without the doctype.
Can I verify wether the rewrite thing still works?

Benjamin Reed May 14, 2010 at 11:43 AM

Does it work if you just take the doctype out altogether?

Daniel Hammon May 14, 2010 at 11:25 AM

Yes,

I put the dtd file in the opennms folder and changed the definition to:

<!DOCTYPE urlrewrite PUBLIC "-//tuckey.org//DTD UrlRewrite 2.6//EN"
"file://opt/opennms/urlrewrite2.5.dtd">

root@sdu10088:/opt/opennms # time /etc/init.d/opennms start
/etc/init.d/opennms start 12.94s user 1.18s system 30% cpu 46.613 total

46 aren´t that fast but after I change it back to http...:
root@sdu10088:/opt/opennms # time /etc/init.d/opennms start
Starting OpenNMS: Couldn't connect to localhost:5817 - IO::Socket::INET: connect: Connection refused
Started OpenNMS, but it has not finished starting up
failed
/etc/init.d/opennms start 15.25s user 1.16s system 26% cpu 1:02.21 total

1 Minute +x

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created March 4, 2010 at 9:34 AM
Updated January 27, 2017 at 4:26 PM
Resolved May 20, 2010 at 1:27 AM