Bug 1229875

Summary: The server erroneusly prints 'Ignoring XML attribute isolation, please remove from configuration file'
Product: [JBoss] JBoss Data Grid 6 Reporter: Shay Matasaro <smatasar>
Component: ServerAssignee: Tristan Tarrant <ttarrant>
Status: CLOSED UPSTREAM QA Contact: Martin Gencur <mgencur>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.4.0CC: acai, chuffman, jdg-bugs, pzapataf, wfink
Target Milestone: ER1   
Target Release: 6.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The only isolation level supported by server configuration in the <literal>&lt;locking&gt;</literal> element of cache configuration was READ_COMMITED. Due to this, the server incorrectly printed 'Ignoring XML attribute isolation, please remove from configuration file' log message, even if isolation attribute was not present in the <literal>&lt;locking&gt;</literal> element. This issue is resolved as of Red Hat JBoss Data Grid 6.5.1 as the server currently supports specifying other isolation levels, resulting in the log message no longer being displayed.
Story Points: ---
Clone Of:
: 1246091 (view as bug list) Environment:
Last Closed: 2025-02-10 03:47:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1246091    

Description Shay Matasaro 2015-06-09 20:15:55 UTC
The server only supports READ_COMMITTED isolation and should print a warning in case someone sets a value. Unfortunately the check is wrong and the warning is always printed

Comment 6 Red Hat Bugzilla 2025-02-10 03:47:43 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.