Bug 1075719
| Summary: | JDBC store properties are ignore or cause an exception | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Tristan Tarrant <ttarrant> | ||||
| Component: | Server | Assignee: | Tristan Tarrant <ttarrant> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Martin Gencur <mgencur> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.0, 6.2.0 | CC: | jdg-bugs, pruivo, wfink | ||||
| Target Milestone: | CR3 | ||||||
| Target Release: | 6.2.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Setting custom JDBC store properties causes an exception to be thrown. This has been fixed and it is now possible to configure JDBC cache store with custom properties such as databaseType.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2025-02-10 03:35:20 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: | |||||||
| Attachments: |
|
||||||
|
Description
Tristan Tarrant
2014-03-12 16:34:04 UTC
Created attachment 873671 [details]
Patch for JDG 6.1.x
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!!
We used to have databaseType configuration property in our tests. Why did we remove it? jmarkos? 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. 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. 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. (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! (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 This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |