Christoph, You should have:
1 SessionIdManager per Server 1 SessionManager per Context, sharing the same SessionIdManager If you have this setup, and can reproduce a problem on a recent jetty-9 version, then please post a bug, including details of your os, java version, jetty version, and configuration of your JDBCSessionIdManager and JDBCSessionManager set up (a repro test project would be most welcome): https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jetty Jan On 6 November 2014 20:21, Christoph Läubrich <[email protected]> wrote: > I have an embedded Jetty with JDBC Sessions. From time to time I see wired > exceptions about "ForeignKeyContraintViolation". > I now noticed, that my application contains two JDBCSessionManager that both > use the same JDBCSessionIDManager. > > I wondering if this might be problematic or if it is okay to reuse the ID > Manager or if it might be even problematic to have more than one > JDBCSessionManager at all... > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users -- Jan Bartel <[email protected]> www.webtide.com 'Expert Jetty/CometD developer,production,operations advice' _______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
