Didn't the Java EE server pool the actual JCR sessions in earlier versions?
Such that, when a logout on a JCA handle had been called, the actual JCR
session was not logged out but returned to a connection pool. Furthermore
the size of this connection pool could be configured via min- and
max-pool-size entries in the jcr-ds.xml. Has this behaviour been removed?
-- 
View this message in context: http://jackrabbit.510166.n4.nabble.com/jackrabbit-jca-2-2-repository-shutdows-after-every-logout-tp3088765p3206525.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.