Jetty session clustering using jetty-maven-plugin

Question

I'm trying to set up session clustering using this

My jetty.xml:

....
<Set name="sessionIdManager">
    <New id="jdbcIdMgr" class="org.eclipse.jetty.server.session.JDBCSessionIdManager">
        <Arg>
            <Ref id="Server"/>
        </Arg>
        <Set name="workerName"><Property name="jetty.jdbcSession.workerName" default="node1"/></Set>
        <Set name="scavengeInterval"><Property name="jetty.jdbcSession.scavenge" default="1800"/></Set>

        <Call name="setDriverInfo">
            <Arg><Property name="jetty.jdbcSession.driverClass"
                           default="com.mysql.jdbc.jdbc2.optional.MysqlDataSource"/></Arg>
            <Arg><Property name="jetty.jdbcSession.connectionURL"
                           default="jdbc:mysql://${datasource.dbServerName}:${datasource.dbServerPort}/${datasource.dbName}"/></Arg>
        </Call>
    </New>
</Set>
.....

My jetty-web.xml :

<Get name="Server">
        <Get id="jdbcIdMgr" name="sessionIdManager"/>
    </Get>

    <Set name="sessionHandler">
        <New class="org.eclipse.jetty.server.session.SessionHandler">
            <Arg>
                <New id="jdbcmgr" class="org.eclipse.jetty.server.session.JDBCSessionManager">
                    <Set name="idManager">
                        <Ref id="jdbcIdMgr"/>
                    </Set>
                </New>
            </Arg>
        </New>
    </Set>

The problem is that I'm getting NPE during server startup, because Server instance is not set to my WebAppContext instance so I can't get my sessionIdManager using :

<Get name="Server">
    <Get id="jdbcIdMgr" name="sessionIdManager"/>
</Get>

I looked at jetty-maven plugin sources and found that at first it configures my WebAppContext instance and then in calls setServer:

    //set up the webapp and any context provided
    this.server.configureHandlers();
    configureWebApplication();
    this.server.addWebApplication(webApp);

How can I properly set up my session clustering stuff?

Answer 1

After digging in the sources I extended JDBCSessionManager class, where I set _sessionIdManager property:

import org.eclipse.jetty.server.Server;
import org.eclipse.jetty.server.session.HashSessionIdManager;
import org.eclipse.jetty.server.session.JDBCSessionManager;

public class ScoopSessionManager extends JDBCSessionManager {

    @Override
    public void doStart() throws Exception {
        final Server server = getSessionHandler().getServer();
        _sessionIdManager = server.getSessionIdManager();
        if (_sessionIdManager == null) {
            _sessionIdManager = new HashSessionIdManager();
            server.setSessionIdManager(_sessionIdManager);
        }
        super.doStart();
    }
}

Seems to be working now.