[Hibernate-JIRA] Created: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
4:52 p.m.
DefaultMergeEventListener changes CheckNullability flag - not thread save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to TRUE
and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
John SMith commented on HHH-6689:
---------------------------------
Have not managed to create a simple test case where this bug can be replicated, but with
ongoing load testing, it is happening frequently. We have managed to remove all of the
scenarios from our application code where null checking causes us a problem - except for
one exception which occurs at approx line 104 in DefaultMergeEventListener.java
if ( isNullabilityCheckedGlobal( event.getSession() ) ) {
throw new TransientObjectException(
"one or more objects is an unsaved transient instance - save transient instance(s)
before merging: " +
transientEntityNames );
}
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Labels: hibernate
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:58 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Piotr Findeisen commented on HHH-6689:
--------------------------------------
Steps to reproduce should be as follow:
# take an entity class {{E}} with non-null field
# set {{checkNullability}} to false
# If you now execute {{merge}} on new instance of {{E}}, you shall not receive
{{PropertyValueException}}. If you have additional validation defined for entity {{E}},
you could receive {{javax.validation.ConstraintViolationException}} instead
# Repeat step no. 3 in two threads several times. In
{{DefaultMergeEventListener.mergeTransientEntity}} {{PropertyValueException}} is caught
and handled this way: {code}if ( isNullabilityCheckedGlobal( source ) ) {
throw ex;
}
else {
// retry save w/o checking for non-nullable properties
// (the failure will be detected later)
saveTransientEntity( copy, entityName, requestedId, source, copyCache, false );
}{code} Because {{isNullabilityCheckedGlobal}} is affected by by the other thread, it can,
incorrectly return {{true}}.
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Labels: hibernate
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:03 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Piotr Findeisen commented on HHH-6689:
--------------------------------------
Btw. it seems very probable that the sequence the following operations done in
{{saveTransientEntity}}
* read global checkNullability flag
* change global checkNullability flag to true
* restore global checkNullability flag to read value
when executed by 2 threads at the same time can *change checkNullability flag to {{true}}
for ever*. For this to happen it's enough that
* first thread reads the flag and sets it temporarily to {{true}}
* second thread reads {{true}} (the temporary value)
* first thread completes {{merge}} and restores flag to the original value
* second threads completes {{merge}} and restores flag to the temporary value of
{{true}}
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Labels: hibernate
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:07 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Piotr Findeisen edited comment on HHH-6689 at 10/28/11 4:06 AM:
----------------------------------------------------------------
Btw. it seems very probable that the sequence the following operations done in
{{saveTransientEntity}} ([see source on
github|https://github.com/hibernate/hibernate-core/blob/3.6/hibernate-cor...])
* read global checkNullability flag
* change global checkNullability flag to true
* restore global checkNullability flag to read value
when executed by 2 threads at the same time can *change checkNullability flag to {{true}}
for ever*. For this to happen it's enough that
* first thread reads the flag and sets it temporarily to {{true}}
* second thread reads {{true}} (the temporary value)
* first thread completes {{merge}} and restores flag to the original value
* second threads completes {{merge}} and restores flag to the temporary value of
{{true}}
was (Author: piofinsy):
Btw. it seems very probable that the sequence the following operations done in
{{saveTransientEntity}}
* read global checkNullability flag
* change global checkNullability flag to true
* restore global checkNullability flag to read value
when executed by 2 threads at the same time can *change checkNullability flag to {{true}}
for ever*. For this to happen it's enough that
* first thread reads the flag and sets it temporarily to {{true}}
* second thread reads {{true}} (the temporary value)
* first thread completes {{merge}} and restores flag to the original value
* second threads completes {{merge}} and restores flag to the temporary value of
{{true}}
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Labels: hibernate
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:07 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Piotr Findeisen edited comment on HHH-6689 at 10/28/11 4:07 AM:
----------------------------------------------------------------
Btw. it seems very probable that the sequence the following operations done in
{{saveTransientEntity}} ([see source on
github|https://github.com/hibernate/hibernate-core/blob/3.6/hibernate-cor...])
* read global checkNullability flag
* change global checkNullability flag to true
* restore global checkNullability flag to read value
when executed by 2 threads at the same time can *change checkNullability flag to {{true}}
for ever*. For this to happen it's enough that
* first thread reads the flag and sets it temporarily to {{true}}
* second thread reads {{true}} (the temporary value)
* first thread completes {{merge}} and restores flag to the original value
* second threads completes {{merge}} and restores flag to the temporary value of
{{true}}
was (Author: piofinsy):
Btw. it seems very probable that the sequence the following operations done in
{{saveTransientEntity}} ([see source on
github|https://github.com/hibernate/hibernate-core/blob/3.6/hibernate-cor...])
* read global checkNullability flag
* change global checkNullability flag to true
* restore global checkNullability flag to read value
when executed by 2 threads at the same time can *change checkNullability flag to {{true}}
for ever*. For this to happen it's enough that
* first thread reads the flag and sets it temporarily to {{true}}
* second thread reads {{true}} (the temporary value)
* first thread completes {{merge}} and restores flag to the original value
* second threads completes {{merge}} and restores flag to the temporary value of
{{true}}
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Labels: hibernate
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:18 p.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Gail Badner reassigned HHH-6689:
--------------------------------
Assignee: Gail Badner
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:46 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Gail Badner updated HHH-6689:
-----------------------------
Fix Version/s: 4.0.0.next
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.0.0.next
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:47 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Steve Ebersole updated HHH-6689:
--------------------------------
Fix Version/s: (was: 4.0.0.CR6)
4.0.0.next
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.0.0.next
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Strong Liu updated HHH-6689:
----------------------------
Fix Version/s: (was: 4.0.0.CR7)
4.0.0.next
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.0.0.next
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:24 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Steve Ebersole updated HHH-6689:
--------------------------------
Fix Version/s: (was: 4.0.0.Final)
4.0.1
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.0.1
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:10 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Gail Badner updated HHH-6689:
-----------------------------
Fix Version/s: (was: 4.0.1)
4.1.0
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.1.0
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Gail Badner updated HHH-6689:
-----------------------------
Fix Version/s: (was: 4.1.0)
4.0.1
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.0.1
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:09 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Steve Ebersole updated HHH-6689:
--------------------------------
Fix Version/s: (was: 4.0.1)
4.1.0
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.1.0
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6 p.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689?page=c...
]
Gail Badner resolved HHH-6689.
------------------------------
Resolution: Fixed
Fixed by HHH-5472.
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6689
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.1.0
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 p.m.
New subject: [Hibernate-JIRA] Closed: (HHH-6689) DefaultMergeEventListener changes CheckNullability flag - not thread save
[
https://hibernate.onjira.com/browse/HHH-6689?page=com.atlassian.jira.plug...
]
Steve Ebersole closed HHH-6689.
-------------------------------
Closing for 4.1 release
DefaultMergeEventListener changes CheckNullability flag - not thread
save
-------------------------------------------------------------------------
Key: HHH-6689
URL: https://hibernate.onjira.com/browse/HHH-6689
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 3.6.5
Environment: Websphere Application Server 7.0, DB2, Windows Server, Hibernate
3.6.5
Reporter: John SMith
Assignee: Gail Badner
Labels: hibernate
Fix For: 4.1.0
saveTransientEntity() method saves the CheckNullability setting, changes it using the
getFactory().getSettings().setCheckNullability method, and does save processing. After
save processing, the saved value is restored.
During load testing, we have had situations where the CheckNullability becomes set to
TRUE and causes failures because of null checks.
It has been difficult to debug, but it appears that this is not thread safe - multiple
threads accessing this method can change the value of this setting.
It can also be that a database error can cause an exception that will cause the
checkNullability flan not to be reset.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4701
days inactive
4835
days old
hibernate-issues@lists.jboss.org
15 comments
5 participants
participants (5)
-
Gail Badner (JIRA) -
John SMith (JIRA)
-
Piotr Findeisen (JIRA)
-
Steve Ebersole (JIRA)
-
Strong Liu (JIRA)