Bug 1188420
Summary: | [GSS](6.4.z) EJB Asynchronous pass POJO by reference leading to ClassCastException errors in remote invocations | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | William Antônio <wsiqueir> | |
Component: | EJB | Assignee: | Brad Maxwell <bmaxwell> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | hsvabek | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.2.0 | CC: | bbaranow, bmaxwell, cdewolf, cdollar, jawilson, rsvoboda, smumford | |
Target Milestone: | CR2 | |||
Target Release: | EAP 6.4.1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Known Issue | ||
Doc Text: |
In this release of JBoss EAP 6, an Asynchronous EJB call via the EJB's Remote Interface from a client to an EJB running in the same JVM fails with a ClassCastException.
This is because the request/response are not being marshalled as they should and the client and EJB are not using the same classloader.
This is expected to be resolved in a future release and the request/response will be marshalled as it should since it is a Remote interface call, allowing the client and EJB to use different classloaders and not fail with a ClassCastException.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1191758 (view as bug list) | Environment: | ||
Last Closed: | 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: | 1191758, 1207953 |
Description
William Antônio
2015-02-02 20:29:48 UTC
Brad Maxwell <bmaxwell> updated the status of jira WFLY-4331 to Reopened Brad Maxwell <bmaxwell> updated the status of jira WFLY-4331 to Resolved Re-acking after "qa_ack flag reset for and jboss-eap-6.4.0 and jboss-eap-6.4.z items" cleanup. verified Retroactively bulk-closing issues from released EAP 6.4 cummulative patches. Retroactively bulk-closing issues from released EAP 6.4 cummulative patches. |