Foxhound 4 - Patch 5 

2017 09 15  -  $readme-for-patch-Foxhound4-4729-005-monitor-unresponsive.txt

If you experience any problems or challenges with this patch, or 
with your copy of Foxhound 4 in general, please contact breck.carter@gmail.com.

...many issues can be resolved quickly!

    ************************************************
    *****     SCROLL DOWN FOR INSTRUCTIONS     *****
    ************************************************

-----------------------------------------------------------------------

    ********************************************
    *****     DESCRIPTION OF THE FIXES     *****
    ********************************************

This patch is for installed copies of Foxhound 4 build 4729. 

This patch changes the Monitor Database part of Foxhound 4 to work 
around changes in SQL Anywhere 16 and 17 that result in the Foxhound 
Monitor becoming unresponsive.

Foxhound may become unresponsive when the monitor is unable to make 
a network connection to a target database, and it may be accompanied 
by an endless loop of bogus error messages in the Foxhound file 
C:\ProgramData\RisingRoad\Foxhound4\foxhound4_debug.txt:

   Attempt to reload definition for event "rroad_monitor_sample_loop" 
   failed due to concurrent event execution.

This patch removes connection timeout and timeout retry processes from
the Foxhound Database Monitor, as well as eliminating explicit CHECKPOINT 
statements from the Foxhound Purge process.

There are also manual alternatives to this patch:

   Check "never timeout" on the section 4. Connection Timeout of the 
   Foxhound Options page.

   Run Foxhound on builds 2127 to 2193 of SQL Anywhere 16.

   Run Foxhound on build 1359 of SQL Anywhere 17 or earlier.

   Click the Stop All Sampling button on the Monitor tab of the
   Foxhound Menu page (although the symptom may reappear later).

This patch can be applied independently from other patches.

-----------------------------------------------------------------------

   ******************************* 
   *****     INSTRUCTIONS    *****
   ******************************* 

1. Shut down Foxhound 4, if it's running. 

2. If desired, make a backup copy the Foxhound 4 folder:
      C:\ProgramData\RisingRoad\Foxhound4

3. Unzip this file:   zipped-patch-Foxhound4-4729-005-monitor-unresponsive.zip
   into this folder:  C:\ProgramData\RisingRoad\Foxhound4

   It will create this file: patch-Foxhound4-4729-005-monitor-unresponsive.patch

4. Start Foxhound 4; it will automatically apply the patch.

5. Wait a few seconds for Foxhound 4 to shut down automatically;
   you won't see it happen in the browser, but you will see the Windows 
   process disappear.

6. Start Foxhound 4 again, to continue work.

-----------------------------------------------------------------------

   ******************************** 
   *****     OPTIONAL STEPS   *****
   ******************************** 

7. Optional: Verify the patch was applied OK.

   Scroll to the bottom of this text file:

      C:\ProgramData\RisingRoad\Foxhound4\foxhound4_debug.txt 

=====
I. 09/15 09:58:55. ---------------------------------------
I. 09/15 09:58:55. Foxhound Version 4.0 by RisingRoad - Extended Edition 4.0.4729a built at  
                      2016 10 04 07:08 in a SQL Anywhere 16.0.0.2127 database created at 2016 10 04 07:07
I. 09/15 09:58:55. ---------------------------------------
I. 09/15 09:58:55. The patch file is being applied to the Foxhound database: "patch-Foxhound4-4729-005-monitor-unresponsive.patch"
I. 09/15 09:58:55. DIAG 2017-09-15 09:58:55.728 Starting patch-Foxhound4-4729-005-monitor-unresponsives.txt
I. 09/15 09:58:55. DIAG 2017-09-15 09:58:55.729    DROP EVENT fire_once
I. 09/15 09:58:55. DIAG 2017-09-15 09:58:55.737    CREATE EVENT fire_once
I. 09/15 09:58:55. DIAG 2017-09-15 09:58:55.752    @sql = ALTER EVENT fire_once ADD SCHEDULE START TIME '2017-09-15 09:59:05.752'
I. 09/15 09:58:55. DIAG 2017-09-15 09:58:55.754    ALTER EVENT fire_once ENABLE
I. 09/15 09:58:55. The patch file was executed: "patch-Foxhound4-4729-005-monitor-unresponsive.patch"
I. 09/15 09:59:05. DIAG 2017-09-15 09:59:05.086    STOP ENGINE UNCONDITIONALLY
I. 09/15 09:59:06. Database server shutdown requested by STOP ENGINE statement
W. 09/15 09:59:08. TCPIP listener on IP address (::):49156 is exiting
W. 09/15 09:59:08. TCPIP listener on IP address 0.0.0.0:49156 is exiting
W. 09/15 09:59:08. HTTP listener on IP address (::):80 is exiting
W. 09/15 09:59:08. HTTP listener on IP address 0.0.0.0:80 is exiting
I. 09/15 09:59:08. Starting checkpoint of "f" (foxhound4.db) at Fri Sep 15 2017 09:59
I. 09/15 09:59:08. Finished checkpoint of "f" (foxhound4.db) at Fri Sep 15 2017 09:59
I. 09/15 09:59:08. Database server stopped at Fri Sep 15 2017 09:59
=====

8. Optional: Check patch history.

   Use All Programs - Foxhound4 - Tools - Adhoc Query Foxhound Database via ISQL

   SELECT * FROM applied_patch ORDER BY file_name;

   file_name,applied_to_build_number,inserted_at,updated_at,status
   'patch-Foxhound4-4729-005-monitor-unresponsive.patch',4729,'2017-09-15 09:58:55.691','2017-09-15 09:58:55.757',
      The patch file was executed: "patch-Foxhound4-4729-005-monitor-unresponsive.patch"

-- end --