[
http://jira.jboss.com/jira/browse/JBCACHE-802?page=all ]
Manik Surtani reopened JBCACHE-802:
-----------------------------------
The problem here though is that when using transactions that span multiple calls, this
breaks things.
A proper solution would be to use a rudimentary internal pool (HashMap of open conns) for
the non-managed factory.
NonManagedConnectionFactory does not place new connections in
ThreadLocal (JDBCCacheLoader)
-------------------------------------------------------------------------------------------
Key: JBCACHE-802
URL:
http://jira.jboss.com/jira/browse/JBCACHE-802
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Cache loaders
Affects Versions: 1.4.0.SP1
Reporter: Manik Surtani
Assigned To: Manik Surtani
Fix For: 2.0.0, 1.4.0.SP2
In NonManagedConnectionFactory.getConnection():
public Connection getConnection()
{
Connection con = (Connection) connection.get();
if(con == null)
{
try
{
con = DriverManager.getConnection(url, usr, pwd);
// CODE ADDED HERE
connection.set(con);
// END CODE MODIFICATION
}
catch(SQLException e)
...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira