Bug 1320021 - Old dashbuilder does not work with MariaDB10
Summary: Old dashbuilder does not work with MariaDB10
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BAM
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ER2
: ---
Assignee: David Gutierrez
QA Contact: Gui Jospin
URL:
Whiteboard:
Depends On: 1309714
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 07:01 UTC by Jan Hrcek
Modified: 2020-03-27 20:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:07:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server.log with exceptions (289.93 KB, text/plain)
2016-03-22 07:01 UTC, Jan Hrcek
no flags Details
server.log from local test (less cluttered with irrelevant stuff) (168.39 KB, text/plain)
2016-03-22 07:22 UTC, Jan Hrcek
no flags Details

Description Jan Hrcek 2016-03-22 07:01:17 UTC
Created attachment 1138898 [details]
server.log with exceptions

Description of problem:
The old Dashbuilder does not work with MariaDB 10.
I believe there was a misunderstanding when this was reported in previous bug #1309714 some time ago. That bug was intended to report error with the "old" dashbuilder, but the fix seems to have been done in the new, UF-based dashbuilder.

Checking 6.3.0 ER1 There are some errors during deployment (see below + full server.log in attachment)
07:43:49,232 ERROR [org.jboss.dashboard.error.ErrorManager] (ServerService Thread Pool -- 78) UNEXPECTED ERROR.
org.mariadb.jdbc.internal.util.dao.QueryException: Incorrect string value: '\xE3\x83\xA6\xE3\x83\xBC...' for column 'value' at row 1

I tried to reproduce this issue locally (with a mariadb10 instance from DB allocator) and got the same errors.


------------
Trying to use dashbuilder in the browser I can see login screen, but after logging in I always get:

JBWEB000065: HTTP Status 404 - /dashbuilder/j_security_check
JBWEB000309: type JBWEB000067: Status report
JBWEB000068: message /dashbuilder/j_security_check
JBWEB000069: description JBWEB000124: The requested resource is not available.



Version-Release number of selected component (if applicable):
BPM Suite 6.3.0 ER1

How reproducible:
Always

Steps to Reproduce:
1. Configure Maria DB datasource (allocate maria db in db allocator)

  1.a download mariadb jdbc driver:
http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.0.0/mariadb10/jdbc4/mariadb-java-client-1.3.4.jar

  1.b. Configure jdbc driver as module in EAP
> cat modules/com/mariadb/main/module.xml
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.mariadb">
  <resources>
    <resource-root path="mariadb-java-client-1.3.4.jar"/>
  </resources>
  <dependencies>
    <module name="javax.api"/>
    <module name="javax.transaction.api"/>
  </dependencies>
</module>

  1.c Configure connection parameters & jdbc driver in standalone/configuration/standalone.xml

2. Login to dashbuilder

Actual results:
The above mentioned error after logging in

Expected results:
No errors

Additional info:
BPM Suite 6.3.0 ER1 can be downloaded here:
http://download.eng.brq.redhat.com/devel/candidates/BPMS/BPMS-6.3.0.ER1/

Comment 1 Jan Hrcek 2016-03-22 07:21:10 UTC
Adding one more server.log
(less cluttered from starting and trying to login to dashbuilder locally. Also removed kie-server.war which is irrelevant for this use case)

Comment 2 Jan Hrcek 2016-03-22 07:22:02 UTC
Created attachment 1138902 [details]
server.log from local test (less cluttered with irrelevant stuff)

Comment 3 David Gutierrez 2016-03-31 07:25:58 UTC
I tested both old & UF dashbuilder as part of the fix for:

https://bugzilla.redhat.com/show_bug.cgi?id=1309714


Old dashbuilder works fine. I can't reproduce the issue mentioned above.

I used a MariaDB 10 instance from dballocator and configured the DB connection as described here:

https://github.com/droolsjbpm/jbpm-dashboard/blob/master/jbpm-dashboard-distributions/src/main/wildfly8/README.md#jbpm-dashboard-deployment

Comment 4 Jan Hrcek 2016-04-04 05:17:57 UTC
David, you're right. It turns out that one of our MariaDB instances (the one connected to middleware jenkins) is somehow corrupted. I executed the tests on Central CI jenkins with another MariaDB instance and the tests have passed. Verified with BPM Suite 6.2.0 ER2


Note You need to log in before you can comment on or make changes to this bug.