RemotingClientInvoker can change configuration map and prevent InvokerRegistry from reusing client invokers ----------------------------------------------------------------------------------------------------------- Key: JBREM-1268 URL: https://issues.jboss.org/browse/JBREM-1268 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3.SP3, 2.5.3.SP1 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.3.SP2, 2.2.3.SP4 When org.jboss.remoting.InvokerRegistry.createClientInvoker() looks to reuse an existing client invoker, it compares the InvokerLocator and the configuration map. However, if org.jboss.remoting.RemoteClientInvoker() finds "socketFactoryClassName" in the InvokerLocator, it adds it to the configuration map, so the new client invoker gets stored with an updated configuration map. When InvokerRegistry.createClientInvoker() is called again with identical parameters, it can't match the incoming configuration map with the one associated with the previously created client invoker, and it creates a new client invoker. Reported by Patrick Speer. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira