[JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Tom Jenkinson created pull request #1007 in GitHub
--------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> JDBC Connection leak with Postgres
> ----------------------------------
>
> Key: JBTM-2667
> URL: https://issues.jboss.org/browse/JBTM-2667
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA
> Affects Versions: 5.3.2.Final
> Reporter: Alexis Hassler
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed.
> The problem can be workarounded by adding a modifier :
> {code:java}
> ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName());
> {code}
> With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2667:
--------------------------------
Issue Type: Bug (was: Feature Request)
> JDBC Connection leak with Postgres
> ----------------------------------
>
> Key: JBTM-2667
> URL: https://issues.jboss.org/browse/JBTM-2667
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA
> Affects Versions: 5.3.2.Final
> Reporter: Alexis Hassler
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed.
> The problem can be workarounded by adding a modifier :
> {code:java}
> ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName());
> {code}
> With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2667:
--------------------------------
Fix Version/s: 5.next
> JDBC Connection leak with Postgres
> ----------------------------------
>
> Key: JBTM-2667
> URL: https://issues.jboss.org/browse/JBTM-2667
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: JTA
> Affects Versions: 5.3.2.Final
> Reporter: Alexis Hassler
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed.
> The problem can be workarounded by adding a modifier :
> {code:java}
> ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName());
> {code}
> With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-2667:
-----------------------------------
Assignee: Tom Jenkinson
> JDBC Connection leak with Postgres
> ----------------------------------
>
> Key: JBTM-2667
> URL: https://issues.jboss.org/browse/JBTM-2667
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: JTA
> Affects Versions: 5.3.2.Final
> Reporter: Alexis Hassler
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed.
> The problem can be workarounded by adding a modifier :
> {code:java}
> ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName());
> {code}
> With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres
by Alexis Hassler (JIRA)
Alexis Hassler created JBTM-2667:
------------------------------------
Summary: JDBC Connection leak with Postgres
Key: JBTM-2667
URL: https://issues.jboss.org/browse/JBTM-2667
Project: JBoss Transaction Manager
Issue Type: Feature Request
Components: JTA
Affects Versions: 5.3.2.Final
Reporter: Alexis Hassler
When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed.
The problem can be workarounded by adding a modifier :
{code:java}
ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName());
{code}
With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2666:
--------------------------------
Release Notes Text: (was: Resolved in jenkins config)
> karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart
> --------------------------------------------------------------------------------
>
> Key: JBTM-2666
> URL: https://issues.jboss.org/browse/JBTM-2666
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Demonstrator
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Blocker
>
> {code}
> [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2666:
-------------------------------------
Resolved in jenkins config
> karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart
> --------------------------------------------------------------------------------
>
> Key: JBTM-2666
> URL: https://issues.jboss.org/browse/JBTM-2666
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Demonstrator
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Blocker
>
> {code}
> [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-2666.
---------------------------------
Release Notes Text: Resolved in jenkins config
Resolution: Migrated to another ITS
> karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart
> --------------------------------------------------------------------------------
>
> Key: JBTM-2666
> URL: https://issues.jboss.org/browse/JBTM-2666
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Demonstrator
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Blocker
>
> {code}
> [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (JBTM-2666) karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2666?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2666:
--------------------------------
Fix Version/s: (was: 5.next)
> karaf-services-maven-plugin 4.1.0-SNAPSHOT not found in JBTM and OSGI quickstart
> --------------------------------------------------------------------------------
>
> Key: JBTM-2666
> URL: https://issues.jboss.org/browse/JBTM-2666
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Demonstrator
> Reporter: Gytis Trikleris
> Assignee: Amos Feng
> Priority: Blocker
>
> {code}
> [ERROR] Plugin org.apache.karaf.tooling:karaf-services-maven-plugin:4.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.karaf.tooling:karaf-services-maven-plugin:jar:4.1.0-SNAPSHOT: Could not find artifact org.apache.karaf.tooling:karaf-services-maven-plugin:pom:4.1.0-SNAPSHOT -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months