jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From deba <debasan...@gmail.com>
Subject Connections remain open even after calling session.logout()
Date Thu, 19 May 2011 15:22:06 GMT
Hi All,
I am using  jboss-5.1.0.GA , MSSQL 2005. and Jackrabbit 2.1.0

 " <FileSystem class="org.apache.jackrabbit.core.fs.db.MSSqlFileSystem">
       
	             
       
       	   
     </FileSystem> "

Each time  MSSQL datasource re-accessed , in Jboss  
the following STACKTRACE  is printed in the console and the execution stops
for 4-5 seconds:

I  found no connection left open in my code . I an using session.logout() to
close the session.

Please suggest a solution .

Attaching the STACKTRACE for reference  :--

18:15:46,302 INFO  [CachedConnectionManager] Closing a connection for you. 
Please close them yourself:
org.jboss.resource.adapter.jdbc.jdk5.WrappedConnectionJDK5@1072512

java.lang.Throwable: STACKTRACE  at
org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:
278) at
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:52
4) at
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseCon
nectionManager2.java:941)
        at
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
        at
org.apache.jackrabbit.core.persistence.bundle.ConnectionFactory.getConnection(ConnectionFactory.java:67)
        at
org.apache.jackrabbit.core.persistence.bundle.ConnectionRecoveryManager.setupConnection(ConnectionRecoveryMan
ager.java:334)
        at
org.apache.jackrabbit.core.persistence.bundle.ConnectionRecoveryManager.<init>(ConnectionRecoveryManager.java
:139)
        at
org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager.init(BundleDbPersistenceManager.java
:595)
        at
org.apache.jackrabbit.core.RepositoryImpl.createPersistenceManager(RepositoryImpl.java:1429)
        at
org.apache.jackrabbit.core.RepositoryImpl.access$800(RepositoryImpl.java:125)
        at
org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.doInitialize(RepositoryImpl.java:2014)
        at
org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.initialize(RepositoryImpl.java:1997)
        at
org.apache.jackrabbit.core.RepositoryImpl.initStartupWorkspaces(RepositoryImpl.java:535)
        at
org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:366)
        at
org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:673)
        at
org.apache.jackrabbit.core.TransientRepository$3.getRepository(TransientRepository.java:249)
        at
org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:279)
        at
org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:375)
        at
org.apache.jackrabbit.jca.JCAManagedConnectionFactory.openSession(JCAManagedConnectionFactory.java:153)
        at
org.apache.jackrabbit.jca.JCAManagedConnectionFactory.createManagedConnection(JCAManagedConnectionFactory.jav
a:189)
        at
org.apache.jackrabbit.jca.JCAManagedConnectionFactory.createManagedConnection(JCAManagedConnectionFactory.jav
a:181)
        at
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalMana
gedConnectionPool.java:633)
        at
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPoo
l.java:267)
        at
org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnection
Pool.java:622)
        at
org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:
404)
        at
org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)
        at
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:49
6)
        at
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseCon
nectionManager2.java:941)
        at
org.apache.jackrabbit.jca.JCARepositoryHandle.login(JCARepositoryHandle.java:72)
        at
org.apache.jackrabbit.commons.AbstractRepository.login(AbstractRepository.java:123)
        at
com.jcr.service.impl.JCRJackRabbitImpl.login(JCRJackRabbitImpl.java:114)

Thanks
-Deba

--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Connections-remain-open-even-after-calling-session-logout-tp3536065p3536065.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Mime
View raw message