January 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2599) Update activemq-artimes to 1.1.0.wildfly-010

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Luis Barreiro created pull request #966 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Update activemq-artimes to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2599) Update activemq-artimes to 1.1.0.wildfly-010

by Luis Barreiro (JIRA)

Luis Barreiro created JBTM-2599: ----------------------------------- Summary: Update activemq-artimes to 1.1.0.wildfly-010 Key: JBTM-2599 URL: https://issues.jboss.org/browse/JBTM-2599 Project: JBoss Transaction Manager Issue Type: Bug Components: Application Server Integration Reporter: Luis Barreiro Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2595: ------------------------------------- This would be better discussed over in the forum: https://developer.jboss.org/en/jbosstm/content?filterID=contentstatus%5bp... When discussing, please provide the configuration you are using (including datasource configuration as pooling is implemented already in PostGres driver - org.postgresql.ds.PGPoolingDataSource). TransactionalDriver will reuse connections for the same transaction if configured to do so: https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jdbc/classes/co... I will close this for now, we can reopen depending upon how the discussion goes. Thanks for your interest, Tom > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2595. ------------------------------- Resolution: Incomplete Description > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2595: -------------------------------- Component/s: (was: JTA) > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2595: -------------------------------- Issue Type: Feature Request (was: Bug) > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when pull request #957 was created in GitHub --------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.later > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > There are a couple of advantages to this: > 1. In the common case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > 2. In the case where the recovery manager and transaction manager are distributed, the current behaviour of orphan detection can be employed (or the timeout interval extended) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2583: ------------------------------------- Prototype: https://github.com/jbosstm/narayana/pull/957 > Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.later > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > There are a couple of advantages to this: > 1. In the common case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > 2. In the case where the recovery manager and transaction manager are distributed, the current behaviour of orphan detection can be employed (or the timeout interval extended) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2593. ------------------------------- Resolution: Done > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.next > > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2593: --------------------------------- > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2016