[
https://issues.apache.org/jira/browse/TUSCANY-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-3850.
------------------------------
Resolution: Fixed
Patch applied to 1.x and 2.x streams, thanks for the fix Sebastian.
> Tuscany 1.6 RMI bug: ConnectException after component restart
> -------------------------------------------------------------
>
> Key: TUSCANY-3850
> URL: https://issues.apache.org/jira/browse/TUSCANY-3850
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Misc Binding Extensions
> Affects Versions: Java-SCA-1.6.1
> Environment: Java 1.6.0_24, Eclipse Helios, Win XP SP3
> Reporter: Sebastian Millies
> Fix For: Java-SCA-1.x
>
> Attachments: RMIReferenceInvoker.zip, TuscanyRMI.zip
>
>
> When I have a network of components connected by RMI references,
> then restarting a component will cause a java.net.ConnectException
> in all dependent components on the next remote method call.
> I suspect some kind of connection factory caches out-of-date information.
> Example:
> ServerComponent exposes service "Server" with an RMI binding on port 8777.
> ClientComponent exposes service "Client" with an RMI binding on port 8666
> and has a reference to the service "Server".
> ClientTest is a non-SCA Java class that exercises the Client service over RMI.
> Everything works fine until the ServerComponent Java process is stopped
> and re-started. The tester will then fail, because the client cannot
> re-establish the connection to the server.
> I attach a zip-file with the example. Steps to reproduce the problem:
> Run ServerLauncher
> Run ClientLauncher
> Run ClientTest
> Stop process in which server is running
> Re-Run ServerLauncher
> Re-Run ClientTest
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
