I've applied this fix to the 1.x and 2.x trunks now. ...ant
On Wed, Dec 14, 2011 at 10:49 AM, ant elder <[email protected]> wrote: > Sorry, i'll go apply that now. > > ...ant > > On Wed, Dec 14, 2011 at 9:52 AM, Millies, Sebastian > <[email protected]> wrote: >> Hello there, >> >> when looking at the 1.x trunk recently for another reason, I noticed that >> my patch for TUSCANY-3850 has never been applied. If there is a problem >> with that patch, is there a way I could improve it? >> >> -- Sebastian >> >> -----Original Message----- >> From: ant elder (JIRA) [mailto:[email protected]] >> Sent: Wednesday, March 23, 2011 9:22 AM >> To: Millies, Sebastian >> Subject: [jira] [Commented] (TUSCANY-3850) Tuscany 1.6 RMI bug: >> ConnectException after component restart >> >> >> [ >> https://issues.apache.org/jira/browse/TUSCANY-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010025#comment-13010025 >> ] >> >> ant elder commented on TUSCANY-3850: >> ------------------------------------ >> >> Thanks for the patch Sebastian, i'll go look at getting it applied. >> >>> 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 >>> 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. >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> IDS Scheer Consulting GmbH >> Geschäftsführer/Managing Directors: Kamyar Niroumand, Ivo Totev >> Sitz/Registered office: Altenkesseler Straße 17, 66115 Saarbrücken, Germany >> - Registergericht/Commercial register: Saarbrücken HRB 19681 >> http://www.softwareag.com >>
