11:51 a.m.
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
11:53 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1001) MS SQL server hibernate isolation level issue
[ 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
7:58 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1001) MS SQL server hibernate isolation level issue
[ http://jira.jboss.com/jira/browse/JBPM-1001?page=comments#action_12366771 ]
Ronald van Kuijk commented on JBPM-1001:
----------------------------------------
for M$ SQL server 2005 only correct? Does this break 200x versions of the server and/or
driver?
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
4:22 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1001) MS SQL server hibernate isolation level issue
[ http://jira.jboss.com/jira/browse/JBPM-1001?page=comments#action_12366778 ]
Aleksandar Kostadinov commented on JBPM-1001:
---------------------------------------------
Version 2000 is not supported by hibernate AFAIK as it doesn't support snapshot
isolation at all. Steve Ebersole will know more about it.
We support hibernate on 2005 with the ms official jdbc driver with the option set in
hibernate properties... that's why I've filed the issue.
There is a chance you're not using a hibernate feature depending on the snapshot
isolation level.
There is a chance you need to upgrade hibernate version.
In either case Steve/hibernate dev list should know better.
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
4:37 a.m.
New subject: [JBoss JIRA] Closed: (JBPM-1001) MS SQL server hibernate isolation level issue
[ http://jira.jboss.com/jira/browse/JBPM-1001?page=all ]
Tom Baeyens closed JBPM-1001.
-----------------------------
Resolution: Deferred
we need a working test suite to start from.
somehow the configuration seems to be wrong
org.hibernate.exception.GenericJDBCException: Cannot open connection
at
org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:426)
at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:119)
at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:57)
at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1326)
at
org.jbpm.persistence.db.DbPersistenceService.beginTransaction(DbPersistenceService.java:131)
at
org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:123)
at org.jbpm.JbpmContext.getSession(JbpmContext.java:506)
at org.jbpm.db.AbstractDbTestCase.initializeMembers(AbstractDbTestCase.java:242)
at org.jbpm.db.AbstractDbTestCase.setUp(AbstractDbTestCase.java:64)
Caused by: java.sql.SQLException: This function is not supported
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.Util.<clinit>(Unknown Source)
at org.hsqldb.jdbc.jdbcConnection.setTransactionIsolation(Unknown Source)
at
org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:111)
at
org.hibernate.tool.hbm2ddl.ManagedProviderConnectionHelper.prepare(ManagedProviderConnectionHelper.java:28)
at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:180)
at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:133)
at
org.jbpm.persistence.db.DbPersistenceServiceFactory.createSchema(DbPersistenceServiceFactory.java:108)
at org.jbpm.JbpmConfiguration.createSchema(JbpmConfiguration.java:441)
at org.jbpm.JbpmConfiguration.createSchema(JbpmConfiguration.java:433)
at org.jbpm.db.AbstractDbTestCase.createSchema(AbstractDbTestCase.java:123)
at org.jbpm.db.AbstractDbTestCase.setUp(AbstractDbTestCase.java:62)
... 16 more
i didn't analyse the problems with the almost working test suite
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
6605
days inactive
6675
days old
4 comments
3 participants
participants (3)
-
Aleksandar Kostadinov (JIRA) -
Ronald van Kuijk (JIRA)
-
Tom Baeyens (JIRA)