[jetty-users] Is it problematic to use one JDBCSessionIDManager for mult

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jetty-users] Is it problematic to use one JDBCSessionIDManager for multiple JDBCSessionManager

From: Christoph Läubrich <laeubi@xxxxxxxxxxxxxx>
Date: Thu, 06 Nov 2014 10:21:21 +0100
Delivered-to: jetty-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jetty-users>
List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11

I have an embedded Jetty with JDBC Sessions. From time to time I seewired exceptions about "ForeignKeyContraintViolation".I now noticed, that my application contains two JDBCSessionManager thatboth use the same JDBCSessionIDManager.

I wondering if this might be problematic or if it is okay to reuse theID Manager or if it might be even problematic to have more than oneJDBCSessionManager at all...

Follow-Ups:
- Re: [jetty-users] Is it problematic to use one JDBCSessionIDManager for multiple JDBCSessionManager
  - From: Jan Bartel

Prev by Date: Re: [jetty-users] Where does Jetty dispatch to worker thread happens.
Next by Date: Re: [jetty-users] Is it problematic to use one JDBCSessionIDManager for multiple JDBCSessionManager
Previous by thread: [jetty-users] badMessage: 400 No URI for HttpChannelOverHttp@61addd0d{r=1, c=false, a=IDLE, uri=-}
Next by thread: Re: [jetty-users] Is it problematic to use one JDBCSessionIDManager for multiple JDBCSessionManager
Index(es):
- Date
- Thread

Breadcrumbs