We're updating the issue view to help you get more done. 

Last screen of setup throwing NPE in some cases?

Description

HTTP ERROR: 500INTERNAL_SERVER_ERROR

RequestURI=/setup/setup-finished.jsp

Caused by:java.lang.NullPointerException at org.jivesoftware.openfire.admin.setup.setup_002dfinished_jsp._jspService(setup_002dfinished_jsp.java:74) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:65) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:41) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:828) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)

Powered by Jetty://\

Nothing special done to trigger it, from the reporter:
LDAP server is active directory, non SSL connected. I verified all stages where given the opportunity:

DB verified - once I fixed the 'select 1' thing for proper DB2 table names,
LDAP User lookup verified, including custom decrapify filter
LDAP Group lookup verified, including custom decrapify filter
It just barfed on the last page, worked fine after a restart.

Environment

None

Acceptance Test - Entry

None

Activity

Show:
Daniel Henninger
April 10, 2008, 5:07 AM

I can not reproduce this so far.

Gaston Dombiak
April 18, 2008, 2:44 AM

This could be the case of an invalidated/expired http session.

Francisco Vives
April 24, 2008, 5:44 AM

I saw the same error and may be it is associated with the invalid session.
This is what I have done:

  1. In database setup it asked me for the DB2 driver

  2. The drivers were added and openfire restarted

  3. The page was refreshed and new information was provided

  4. Then I waited for more than 5'

  5. Then the setup was completed with mysql information.

  6. The following steps were made without errors

  7. The last step produced the NPE

Daniel Henninger
April 25, 2008, 2:04 AM

This does appear to be due to an expired session. While I don't feel we need to fix this for 3.5.1 as it should be a rare occurrence, I'd like to aim to make it at least behave in a more clean manner in the future. Rescheduling for 3.6.0.

Assignee

Daniel Henninger

Reporter

Daniel Henninger

Labels

None

Expected Effort

None

Ignite Forum URL

None

Components

Fix versions

Affects versions

Priority

Major
Configure