[
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)