Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-851

Remoting Subsystem RemoteOutboundConnectionService is caching ConnectionURI causing issues when DNS changes

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.0.5.CR1
    • Component/s: Remoting
    • Labels:
      None

      Description

      Description of problem:
      EJB CLient was configured with DNS FQDN to configure access to a remote EJB. If run a simple test adding an entry in /etc/hosts file pointing that FQDN to localhost for tests everything works. However, after finish the tests and remove the entry, the client still connects to localhost instead of resolve the new IP address. Even adding networkaddress.cache.ttl=30 inside security settings didn't work too.

      How reproducible:
      Everytime you use DNS names to connect to a remote EJB.

      Steps to Reproduce:
      1. Configure a simple client that connects to a remote EJB using dns name
      2. add an entry in /etc/hosts mapping the dns name to localhost
      3. run the client code
      4. remove the entry in /etc/hosts
      5. run the client code again

      Actual results:
      EJB remote is still reached from localhost

      Expected results:
      After changing DNS record EJB will be reached in this new address

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  filippe.spolti Filippe Spolti
                  Reporter:
                  bmaxwell Brad Maxwell
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: