Bug 1075719 - JDBC store properties are ignore or cause an exception
Summary: JDBC store properties are ignore or cause an exception
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server
Version: 6.1.0,6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR3
: 6.2.1
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-12 16:34 UTC by Tristan Tarrant
Modified: 2025-02-10 03:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:35:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Patch for JDG 6.1.x (4.27 KB, patch)
2014-03-12 17:09 UTC, Tristan Tarrant 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-4100 0 Major Resolved Could not set the store properties for a *-keyed-jdbc-store 2018-09-03 03:40:27 UTC

Description Tristan Tarrant 2014-03-12 16:34:04 UTC 
Setting JDBC store properties (databaseType, dropTableOnExit, etc) either is ignored or causes an exception depending on the version (6.1 or 6.2).
Comment 2 Tristan Tarrant 2014-03-12 17:09:45 UTC 
Created attachment 873671 [details]
Patch for JDG 6.1.x
Comment 3 Jakub Markos 2014-03-27 11:26:58 UTC 
When running our tests with <property name="databaseType">${database.type}</property> on 6.2.1.CR2 I see this on server startup:

12:17:07,675 WARN  [org.infinispan.configuration.parsing.XmlConfigHelper] (ServerService Thread Pool -- 17) ISPN000282: Unrecognized attribute databaseType.  Please check your configuration.  Ignoring!!
Comment 4 Martin Gencur 2014-03-27 11:42:35 UTC 
We used to have databaseType configuration property in our tests. Why did we remove it? jmarkos?
Comment 5 Vitalii Chepeliuk 2014-03-28 10:01:33 UTC 
Because it caused exception when we were using it when jmarkos made migration from 6.1.0 to 6.2.0. And this property is not needed anymore because infinispan automatically recognize DB type.
Comment 6 Martin Gencur 2014-03-28 10:11:16 UTC 
This is exactly the case when have to file a bug instead of just removing configuration property that stopped working! We cannot configure the databaseType currently in the server in any way. The fact that the current set of databases we have is automatically recognized by JDG does not mean that it will be able to recognize them forever. This configuration property has a reason to be there. We need to add it back to our tests once this issue is fixed.
Comment 7 Jakub Markos 2014-03-28 13:58:46 UTC 
Tested the databaseType property with mysql55 - all OK. Also tried setting ORACLE but actually using mysql, and the server failed, so I assume the property is correctly picked up.
Verified.
Comment 8 wfink 2014-03-28 18:18:53 UTC 
(In reply to Vitalii Chepeliuk from comment #5)
> Because it caused exception when we were using it when jmarkos made
> migration from 6.1.0 to 6.2.0. And this property is not needed anymore
> because infinispan automatically recognize DB type.

There is a case for IBM DB2 where you must set DB2_390 for a special dialect/driver manual. So there is still a need!
Comment 9 Vitalii Chepeliuk 2014-03-29 17:00:59 UTC 
(In reply to wfink from comment #8)
> (In reply to Vitalii Chepeliuk from comment #5)
> > Because it caused exception when we were using it when jmarkos made
> > migration from 6.1.0 to 6.2.0. And this property is not needed anymore
> > because infinispan automatically recognize DB type.
> 
> There is a case for IBM DB2 where you must set DB2_390 for a special
> dialect/driver manual. So there is still a need!

Agree with you. But we had no issues with testing DB2
Comment 10 Red Hat Bugzilla 2025-02-10 03:35:20 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.