Bug 1175386
| Summary: | Dashboard builder SecurityLogging workspace problem with some DBs used for logging | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Jan Stastny <jstastny> | ||||
| Component: | Dashboard Builder | Assignee: | David Le Sage <dlesage> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.0 | CC: | atangrin, jstastny, nshendye, vhalbert | ||||
| Target Milestone: | --- | Keywords: | Documentation | ||||
| Target Release: | 6.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
When using either a PostgreSQL or MySQL database for command logging, the JBoss Data Virtualization dashboard fails due to its inability to find the AuditLog or CommandLog tables. This is due to the case sensitive names that these database use and the table names exist in lower case. The dashboard fails with an exception indicating it cannot find the table. The workaround is to edit the data source query in the dashboard. The JBoss Data Virtualization Dashboard should be able to present data from these tables.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-03-22 23:29:33 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: |
|
||||||
MySql 5.1 isn't a supported database (don't look at supported datasources for this) - see supported databases on the supported configuration page, but 5.5 is. Can you confirm this fails the same way on Postgres 9.2? Which is what we're indicating that's supposed as a database. Hi Van, I have just tried with PostgreSQL 9.2 and I can confirm, that this fails too. It seems that you have to use a db which is clean to run into the issue. A db which wasn't used as logging database before and thus doesn't have the auditlog table created yet. You are right about the case sensitive issue. The fix would be to edit the data source query in the dashboard, to make it lower case. As for the first start versus subsequent start issues, that appears to be a hibernate issue on what's its choosing to do. I would say, just make this a KI for postgres and mysql. And I'll make the change to the dashboard for future releases. Is this ok? Yes Van, I think it is sufficient measure for the issue. Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-11 to Coding In Progress Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-11 to Open Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-11 to Resolved I've got the fix in. Would it be possible for you to try the attached war which contains the changes? I've got posgres 9.3.5 installed and I don't have the case sensitive issue. Back ported fixes to the 2.0.x branch. Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-11 to Closed |
Created attachment 970176 [details] postgresLog Description of problem: When using database logging problems with deploying dashboard builder occur. It depends on the type of used database for logging. With Oracle and SQLServer the dashboard builder deploys fine. But with MySQL, PostgreSQL not. For MySQL 5.1 db: 14:33:27,638 ERROR [org.jboss.dashboard.dataset.sql.SQLDataSet] (ServerService Thread Pool -- 54) Error in load() SQLDataset. SQL = Select * from AuditLog: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'dballo02.AuditLog' doesn't exist When examined the db directly, there is a table called 'auditlog' within schema 'dballo02'. I tried running the query from error message and got the same error, but with 'dballo02.auditlog' the query works just fine. Looks like case-sensitivity issue. MySQL 5.5 worked fine. For PostgreSQL 9.1 db: During the first starting of server and deploying of dashboard builder an error is thrown about non-existing auditlog table. Consecutive starts/deployments run fine. See the attached postgresLog.