Return-Path: 
 <users-return-19690-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org>
X-Original-To: apmail-jackrabbit-users-archive@minotaur.apache.org
Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1B64ED10E
	for <apmail-jackrabbit-users-archive@minotaur.apache.org>;
 Mon, 20 May 2013 09:02:33 +0000 (UTC)
Received: (qmail 91243 invoked by uid 500); 20 May 2013 09:02:33 -0000
Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org
Received: (qmail 90641 invoked by uid 500); 20 May 2013 09:02:31 -0000
Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:users@jackrabbit.apache.org>
List-Id: <users.jackrabbit.apache.org>
Reply-To: users@jackrabbit.apache.org
Delivered-To: mailing list users@jackrabbit.apache.org
Delivered-To: moderator for users@jackrabbit.apache.org
Received: (qmail 14148 invoked by uid 99); 20 May 2013 08:25:09 -0000
X-ASF-Spam-Status: No, hits=2.0 required=5.0
	tests=SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: error (nike.apache.org: encountered temporary error during SPF
 processing of domain of psrutka@centrum.cz)
Date: Mon, 20 May 2013 01:24:07 -0700 (PDT)
From: Menzi <psrutka@centrum.cz>
To: users@jackrabbit.apache.org
Message-ID: <1369038247317-4658726.post@n4.nabble.com>
Subject: Problem with jboss 5 configuration.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

I've encountered a problem with jackrabbit pool in jboss 5 and jackrabbit
2.0. 

I've a jcr datasource configured like this 

 <tx-connection-factory>
    <jndi-name>jcr/local</jndi-name>
    <xa-transaction />
    <track-connection-by-tx>true</track-connection-by-tx>
    <rar-name>jackrabbit-jca.rar</rar-name>
    <connection-definition>javax.jcr.Repository</connection-definition>
    <config-property name="homeDir"
type="java.lang.String">${jackrabbit.homedir}</config-property>
    <config-property name="configFile"
type="java.lang.String">classpath:repository.xml</config-property>
    <config-property name="bindSessionToTransaction"
type="java.lang.Boolean">true</config-property>
    <no-tx-separate-pools />
    <max-pool-size>30</max-pool-size>
</tx-connection-factory>

like this, application works fine, but i'm getting this error really often
(it's thrown every time i'm logging into dms session with this code) 

         Repository repo = (Repository)
ctx.lookup(repository.getJndiName()); 
        Credentials cred = new SimpleCredentials(userId, new char[] { 'p',
'w', 'd' }); 
        Session s = repo.login(cred); 

Destroying connection that could not be successfully matched:
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@8cd0558[state=NORMAL
mc=org.apache.jackrabbit.jca.JCAManagedConnection@6eec369a handles=0
lastUse=1366642930773 permit=false trackByTx=false
mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@8a800c9
context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@6f7fc42f
xaResource=org.apache.jackrabbit.jca.TransactionBoundXAResource@4c19d8eb
txSync=null] 


when i add to datasource configuration, error mentioned earlier dissapears,
but each connection to jcr creates it's own subpool (which is kinda crazy,
becouse after few hours of application running it creates like 700
subpools). I Tryed searching for possible problems with tag and found out
that it uses ConnectionRequestInfo to authenticate connections but so far
had no success with configuring that. 

Any idea what could i try next to get rid of both problems at once?



--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Problem-with-jboss-5-configuration-tp4658726.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.