Bug 1281864
| Summary: | Marshalling error accessing remote EJB services app with Sybase DB | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||
| Component: | jBPM Core | Assignee: | Alessandro Lazarotti <alazarot> | ||||
| Status: | CLOSED EOL | QA Contact: | Radovan Synek <rsynek> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 6.2.0 | CC: | alazarot, kverlaen, lpetrovi, mczernek, rrajasek, tradej | ||||
| Target Milestone: | DR1 | Keywords: | TestBlocker | ||||
| Target Release: | 6.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
When you use Sybase Database Management System with application using EJB services, a marshalling error ("java.lang.ClassNotFoundException: com.sybase.jdbc4.tds.SybTimestamp") may occur with some calls on client side. To fix the issue, add a Sybase JDBC driver on the client class path.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1295535 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-03-27 20:00:15 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1213755, 1295535 | ||||||
| Attachments: |
|
||||||
|
Description
Radovan Synek
2015-11-13 16:08:27 UTC
fixed on master jbpm master: https://github.com/droolsjbpm/jbpm/commit/78a35ca456c5b6c4afcd6eb1551023147f1cd9da in case it needs to be back ported please assign back to me Requesting backport to 6.3.x back ported to 6.3.x jbpm 6.3.x: https://github.com/droolsjbpm/jbpm/commit/394a79af8d4d0b3cc2303129d56d9ca720665963 Have to reassign the issue, as it has been fixed only partially - there are additional classes which cannot be serialized during communication via EJB remoting. Basically, every class containing java.util.Date attribute that could be sent via EJB API is hit by this issue. Based on failing tests, here is a list of these classes, but there could be more, please double check it: org.jbpm.kie.services.impl.model.NodeInstanceDesc org.jbpm.kie.services.impl.model.VariableStateDesc org.jbpm.kie.services.impl.model.UserTaskInstanceDesc I am starting to think that we should stop fixing (or sort of going around and impacting other parts of code) because of badly written 3rd party code. In this case our solution should be to recommend end users to add sybase driver on client class path and problem will be solved. Trying to spot all possible cases where sybase impl can get in the way might become a never ending story. Thoughts? The proposed solution fixes the problem - I suggest rolling back the previously implemented fix and to update a documentation. changes reverted on master jbpm master: https://github.com/droolsjbpm/jbpm/commit/f4cffb54b49168cea78cd58234853a89a9d19986 moving to modified, in case it shall be back ported to 6.3.x branch please put back on me Verified with BPMS-6.3.0.DR2 |