You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Rick McGuire (JIRA)" <ji...@apache.org> on 2007/01/31 16:01:28 UTC
[jira] Created: (OPENEJB-462) Openejb RMI stub serialization
causing some RMI failures.
Openejb RMI stub serialization causing some RMI failures.
---------------------------------------------------------
Key: OPENEJB-462
URL: https://issues.apache.org/jira/browse/OPENEJB-462
Project: OpenEJB
Issue Type: Bug
Components: corba
Affects Versions: 2.3
Reporter: Rick McGuire
Assigned To: Rick McGuire
Fix For: 2.3
openejb is using a special Yoko hook for managing RMI Stub interactions. Part of the openejb implementation of that hook overrides the stub serialization and instead replaces this with an instance of CORBAEJBMemento. As a general solution, this doesn't work, as the correct contexts are not set up to deserialize the method argument until after the request has been deserialized. This is a chicken-and-egg problem. It turns out, the Yoko RMI support is handling everything just fine, and the specialized replacement object is not required, so this method can just be deleted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OPENEJB-462) Openejb RMI stub serialization causing
some RMI failures.
Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick McGuire closed OPENEJB-462.
--------------------------------
Resolution: Fixed
Committed revision 501870.
> Openejb RMI stub serialization causing some RMI failures.
> ---------------------------------------------------------
>
> Key: OPENEJB-462
> URL: https://issues.apache.org/jira/browse/OPENEJB-462
> Project: OpenEJB
> Issue Type: Bug
> Components: corba
> Affects Versions: 2.3
> Reporter: Rick McGuire
> Assigned To: Rick McGuire
> Fix For: 2.3
>
>
> openejb is using a special Yoko hook for managing RMI Stub interactions. Part of the openejb implementation of that hook overrides the stub serialization and instead replaces this with an instance of CORBAEJBMemento. As a general solution, this doesn't work, as the correct contexts are not set up to deserialize the method argument until after the request has been deserialized. This is a chicken-and-egg problem. It turns out, the Yoko RMI support is handling everything just fine, and the specialized replacement object is not required, so this method can just be deleted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.