Uploaded image for project: 'JBoss Remoting'
  1. JBoss Remoting
  2. JBREM-1268

RemoteClientInvoker can change configuration map and prevent InvokerRegistry from reusing client invokers

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.5.3.SP1, 2.2.3.SP3
    • Fix Version/s: 2.5.4, 2.2.4
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ron_sigal Ron Sigal
                Reporter:
                ron_sigal Ron Sigal
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: