[infinispan-issues] [JBoss JIRA] (ISPN-2040) Workaround for transactional misbehaviour of JDBC store with ManagedConnectionPool

[ https://issues.jboss.org/browse/ISPN-2040?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2040: ----------------------------------------------- Misha H. Ali <mhusnain(a)redhat.com&gt; made a comment on [bug 758178|https://bugzilla.redhat.com/show_bug.cgi?id=758178] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Previously, when the JDBC Cache Store was configured without specifying connnectionFactoryClass, the ManagedConnectionFactory was selected by default. As a result, ManagedConnectionFactory could not connect to the database. This behavior is now fixed and a connection to the database is established as expected when no connectionFactoryClass is specified for the JDBC Cache Store.+Previously, when the JDBC Cache Store was configured without specifying <classname>connnectionFactoryClass</classname>, the <classname>ManagedConnectionFactory</classname> was selected by default. As a result, <classname>ManagedConnectionFactory</classname> could not connect to the database. This behavior is now fixed and a connection to the database is established as expected when no <classname>connectionFactoryClass</classname> is specified for the JDBC Cache Store. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira