[jira] Commented: (JCR-781) RMI: Allow custom socket factories

["Ate Douma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489217 ] 

Ate Douma commented on JCR-781:
-------------------------------

Jukka,

As result of this change the JCR-RMI server is no longer working for us.

We now get the following exception when trying to retrieve the repository from a client:

java.rmi.UnmarshalException: error unmarshalling return; nested exception is: 
	java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: sun.rmi.transport.proxy.RMIMasterSocketFactory
	at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
	at java.rmi.Naming.lookup(Naming.java:84)
	at org.apache.jackrabbit.rmi.client.ClientRepositoryFactory.getRepository(ClientRepositoryFactory.java:86)

The UnicastRemoteObject (parent class of ServerObject) uses the UnicastServerRef2 when initialized with a RMIClientSocketFactory  and RMIServerSocketFactory, instead of using the UnicastServerRef as before your change.
Somehow, this now results in breaking down the RMI transport when using the RMISocketFactory.getDefaultSocketFactory() for the RMIClientSocketFactory  and RMIServerSocketFactory.

How did you test this new configuration, e.g. which SocketFactories did you use?
We've tested this out with both Java 1.4.2 and Java 1.5 on both Windows and Linux, using the default RMI socket factories, all with the same result :(
Right now, we are forced to fall back to the "old" solution from before your changes to get things running again.

Could you please provide some guidance how we might solve this so we can again move forward to the latest version?

Regards,

Ate

> RMI: Allow custom socket factories
> ----------------------------------
>
>                 Key: JCR-781
>                 URL: https://issues.apache.org/jira/browse/JCR-781
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: rmi
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.3
>
>
> The current JCR-RMI server classes always use the default RMI socket factory. Provide a mechanism for specifying a custom socket factory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.