Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1087205

Summary:	Infinispan issue: Inconsistent way to use the column id in the JdbcBinaryCacheStore
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Boleslaw Dawidowicz <bdawidow>
Component:	Clustering	Assignee:	Paul Ferraro <paul.ferraro>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jitka Kozana <jkudrnac>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.3.0	CC:	kkhan, lthon, mmarkus
Target Milestone:	ER4
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-28 15:37:19 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:	1087264
Bug Blocks:

Description Boleslaw Dawidowicz 2014-04-14 06:48:35 UTC

I met some issues with (at least) H2 and JdbcBinaryCacheStore that prevent to modify a value in the cache store which is quite annoying. After a deeper look, I realized that it was due to the method JdbcBinaryCacheStore.loadBucket(Integer keyHashCode) that uses setInt instead of setString like in updateBucket and insertBucket to set the id as parameter to the query. With HSQLDB and MySQL, it works normally but with H2, the result of the query is always empty so it always tries to add a new entry which of course fails because of the integrity constraint on the primary key (aka the id).

Comment 1 Boleslaw Dawidowicz 2014-04-14 06:49:39 UTC

Needed for JBoss Portal 6.2

Comment 2 Boleslaw Dawidowicz 2014-04-14 06:53:41 UTC

Needed for JBoss Portal 6.2

Comment 3 Mircea Markus 2014-04-23 15:43:10 UTC

ISPN-3680 was backported to the 5.2.x stream which has been released.

Comment 4 Kabir Khan 2014-04-23 21:23:32 UTC

Fixed by component upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1087264

Comment 5 Kabir Khan 2014-04-25 15:31:45 UTC

Moving to ER4 since ER3 is the new beta candidate, and is ER2+beta blockers only

Comment 6 Ladislav Thon 2014-05-23 10:23:42 UTC

Verified with EAP 6.3.0.ER4.

Please also note that this change (most probably) caused a regression with Sybase, see bug 1098961.