Disable Jetty’s session cookies
This remediates the exception “Shared scheduler not started” and restores the functionality of enabling an app in apps.properties – see #103 (comment)
This commit is contained in:
parent
99e8b204fd
commit
2994a4becc
1 changed files with 4 additions and 4 deletions
|
@ -502,7 +502,9 @@ public class ApplicationManager implements XmlRpcHandler {
|
||||||
staticContext.start();
|
staticContext.start();
|
||||||
}
|
}
|
||||||
|
|
||||||
appContext = new ServletContextHandler(ServletContextHandler.SESSIONS);
|
// I hope I am correct assuming Helma does not need Jetty’s session management, but using
|
||||||
|
// `ServletContextHandler.SESSIONS` causes an exception: Shared scheduler not started
|
||||||
|
appContext = new ServletContextHandler(ServletContextHandler.NO_SESSIONS);
|
||||||
appContext.setContextPath(pathPattern);
|
appContext.setContextPath(pathPattern);
|
||||||
context.addHandler(appContext);
|
context.addHandler(appContext);
|
||||||
|
|
||||||
|
@ -544,9 +546,7 @@ public class ApplicationManager implements XmlRpcHandler {
|
||||||
|
|
||||||
// Remap the context paths and start
|
// Remap the context paths and start
|
||||||
ApplicationManager.this.context.mapContexts();
|
ApplicationManager.this.context.mapContexts();
|
||||||
// FIXME: Causing java.lang.IllegalStateException: Shared scheduler not started
|
this.appContext.start();
|
||||||
// Is it necessary, anway?
|
|
||||||
//this.appContext.start();
|
|
||||||
}
|
}
|
||||||
|
|
||||||
// register as XML-RPC handler
|
// register as XML-RPC handler
|
||||||
|
|
Loading…
Add table
Reference in a new issue