Uploaded image for project: 'JS - JobScheduler'
  1. JS - JobScheduler
  2. JS-729

SCHEDULER-289 TCP-port should be available immediately for JobScheduler restart

    XMLWordPrintable

Details

    Description

      Current Situation
      After stopping the JobScheduler with JOC or with the start script (both will use the command <modify_spooler cmd='terminate'/>):

      ./bin/jobscheduler.sh stop
      

      then the TCP port is not immediately available for re-use by JobScheduler.

      netstat -na | grep 4444
      tcp        0      0 127.0.0.1:44824         127.0.0.1:4444          TIME_WAIT   
      tcp        0      0 127.0.0.1:44825         127.0.0.1:4444          TIME_WAIT
      

      The ports are closed after the net.ipv4.tcp_fin_timeout settings in /etc/sysctl.conf

      Desired Behavior
      After termination of JobScheduler the ports are immediately available for a JobScheduler restart.
      A JobScheduler restart shows no message "TCP-port ... blocked" in the JobScheduler log file.
      The JobScheduler will re-use the port immediately after a restart.

      Attachments

        Issue Links

          Activity

            People

              jz Joacim Zschimmer
              jz Joacim Zschimmer
              Florian Schreiber Florian Schreiber (Inactive)
              Oliver Haufe Oliver Haufe
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified