Uploaded image for project: 'JBoss ESB'
  1. JBoss ESB
  2. JBESB-157

Socket listeners might introduce a port conflict when reinstantiated by the controlling GpListener at parameter reload time

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 4.0 CR1
    • Fix Version/s: 4.0
    • Component/s: Rosetta
    • Labels:
      None
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      See comment.

      Show
      See comment.
    • Estimated Difficulty:
      Medium

      Description

      GpListener has at present two mechanisms to reload it's configuration parameters: a) timer driven 2) message driven.

      At parameter reload time, the controlling instance of GpListener will try to instantiate new child processes according to the new configuration values. It will allow active child threads to gracetully finish.

      New listener classes that are accepting connections on specific sockets will have a conflict when the new instance tries to listen on a port that is being used by the active instance.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  estebanschifman Esteban Schifman
                  Reporter:
                  estebanschifman Esteban Schifman
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: