[jira] [Commented] (JCR-5062) Attempt to return connection twice
[ https://issues.apache.org/jira/browse/JCR-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849201#comment-17849201 ] Julian Reschke commented on JCR-5062: - We could add debug information to find out why the connection is closed twice. But it's a bit of work. (We have similar code in Oak's RDB code). > Attempt to return connection twice > -- > > Key: JCR-5062 > URL: https://issues.apache.org/jira/browse/JCR-5062 > Project: Jackrabbit Content Repository > Issue Type: Bug >Affects Versions: 2.20.16 >Reporter: Henrik Hald Nørgaard >Priority: Minor > Attachments: stacktrace.txt > > > We are using a JackRabbit content repository and are going to update some > nodes with a new mixin. While iterating through the nodes that should be > updated, the following warning sometimes appears in the log: > {{WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] > (ServerService Thread Pool -- 88) IJ000609: Attempt to return connection > twice: > org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@f6ff104[state=NORMAL > managed > connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7f3ceaf7 > connection handles=0 lastReturned=1715156332529 lastValidated=1715156332529 > lastCheckedOut=1715156332528 trackByTx=false > pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@16cc91e8 > mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@53f6d09[pool=DezideAuthorJackrabbit]]: > java.lang.Throwable: STACKTRACE}} > I have attached a stacktrace. > It seems that the database connection handled by the > BundleDbPersistenceManager can in some situations be closed twice? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5062) Attempt to return connection twice
[ https://issues.apache.org/jira/browse/JCR-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849200#comment-17849200 ] Henrik Hald Nørgaard commented on JCR-5062: --- Thank you for your reply. It will be difficult to write a test case that consistently reproduces this warning. It seems to appear when we are doing "a lot" of work in the repository and it does not appear consistently. I think that we will close our eyes and ignore this warning for now. > Attempt to return connection twice > -- > > Key: JCR-5062 > URL: https://issues.apache.org/jira/browse/JCR-5062 > Project: Jackrabbit Content Repository > Issue Type: Bug >Affects Versions: 2.20.16 >Reporter: Henrik Hald Nørgaard >Priority: Minor > Attachments: stacktrace.txt > > > We are using a JackRabbit content repository and are going to update some > nodes with a new mixin. While iterating through the nodes that should be > updated, the following warning sometimes appears in the log: > {{WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] > (ServerService Thread Pool -- 88) IJ000609: Attempt to return connection > twice: > org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@f6ff104[state=NORMAL > managed > connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7f3ceaf7 > connection handles=0 lastReturned=1715156332529 lastValidated=1715156332529 > lastCheckedOut=1715156332528 trackByTx=false > pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@16cc91e8 > mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@53f6d09[pool=DezideAuthorJackrabbit]]: > java.lang.Throwable: STACKTRACE}} > I have attached a stacktrace. > It seems that the database connection handled by the > BundleDbPersistenceManager can in some situations be closed twice? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5062) Attempt to return connection twice
[ https://issues.apache.org/jira/browse/JCR-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847254#comment-17847254 ] Julian Reschke commented on JCR-5062: - Potentially. Jackrabbit Classic is more on less on life support, with a few components still in use outside (such as utils, spi, webdav). That is, almost no work is happening on core components anymore. Is there any chance to write a test case that reproduces this? Alternatively, it might be helpful to add better diagnostics to the DB handling code. PRs welcome :-) > Attempt to return connection twice > -- > > Key: JCR-5062 > URL: https://issues.apache.org/jira/browse/JCR-5062 > Project: Jackrabbit Content Repository > Issue Type: Bug >Affects Versions: 2.20.16 >Reporter: Henrik Hald Nørgaard >Priority: Minor > Attachments: stacktrace.txt > > > We are using a JackRabbit content repository and are going to update some > nodes with a new mixin. While iterating through the nodes that should be > updated, the following warning sometimes appears in the log: > {{WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] > (ServerService Thread Pool -- 88) IJ000609: Attempt to return connection > twice: > org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@f6ff104[state=NORMAL > managed > connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7f3ceaf7 > connection handles=0 lastReturned=1715156332529 lastValidated=1715156332529 > lastCheckedOut=1715156332528 trackByTx=false > pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@16cc91e8 > mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@53f6d09[pool=DezideAuthorJackrabbit]]: > java.lang.Throwable: STACKTRACE}} > I have attached a stacktrace. > It seems that the database connection handled by the > BundleDbPersistenceManager can in some situations be closed twice? -- This message was sent by Atlassian Jira (v8.20.10#820010)