Bug 1263085 - Exception "no marshalling definition available for type:oracle.sql.TIMESTAMP" when entering task list
Exception "no marshalling definition available for type:oracle.sql.TIMESTAMP"...
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: BAM (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: ER4
: 6.2.0
Assigned To: David Gutierrez
Jan Hrcek
: TestBlocker
Depends On:
  Show dependency treegraph
Reported: 2015-09-15 02:21 EDT by Jan Hrcek
Modified: 2015-10-16 03:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Server.log (search for exception from BZ title) (6.41 MB, text/plain)
2015-09-15 02:21 EDT, Jan Hrcek
no flags Details

  None (edit)
Description Jan Hrcek 2015-09-15 02:21:36 EDT
Created attachment 1073499 [details]
Server.log (search for exception from BZ title)

Description of problem:
When I enter task list perspective with business-central deployed with Oracle12c database, I get a modal with error message

"DataSet with UUID [ jbpmHumanTasks ] error: java.lang.RuntimeException: java.lang.RuntimeException: no marshalling definition avialable for type: oracle.sql.TIMESTAMP"

Checking the stacktrace in server.log reveals this exception is thrown by errai (see attachment)

Version-Release number of selected component (if applicable):
kie-wb: latest 6.3.x snapshot 

How reproducible:

Steps to Reproduce:
1. Deploy kie-wb using Oracle 12 c as underlying data source
2. Navigate to task list

Actual results:
Modal with error displayed

Expected results:
No error expected

Additional info:
Comment 1 Jan Hrcek 2015-09-15 02:27:45 EDT
Changing component & assignee, as this exception comes from dashbuilder dataset lookup.
Comment 3 Jan Hrcek 2015-10-16 03:02:59 EDT
Ok, this issue with Oracle DB is gone. Verified with BPM Suite 6.2.0 ER4

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