[
http://jira.jboss.com/jira/browse/JBPM-1001?page=comments#action_12366690 ]
Aleksandar Kostadinov commented on JBPM-1001:
---------------------------------------------
To be clear you have to use the MS JDBC driver to reproduce the problem.
MS SQL server hibernate isolation level issue
---------------------------------------------
Key: JBPM-1001
URL:
http://jira.jboss.com/jira/browse/JBPM-1001
Project: JBoss jBPM
Issue Type: Bug
Reporter: Aleksandar Kostadinov
Assigned To: Tom Baeyens
When MS SQL server is used hibernate *requires* "hibernate.connection.isolation
4096" in hibernate.properties.
Though when this option is set over 200 tests fail. See
http://dev45.qa.atl.jboss.com:8585/hudson/job/JBPM.3_mssql2005-msjdbc/2/ and
http://dev45.qa.atl.jboss.com:8585/hudson/job/JBPM.3_mssql2005-msjdbc/3/
The first one is with the option and the second one without. You can see the difference.
I've marked these builds so hudson will not delete them. If you need this option so
you are able to test your changes I'll do. As well you could request an MS SQL server
user account for manual testing.
FYI I've set some database options so this isolation level is used by default
(required for jtds as well as it doesn't support 4096 isolation value). But having the
option should not break things as it is not breaking them for hibernate automated builds.
--
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