When w3Monitor detects a FlashConnect port in either the system or Pick BASIC debugger, it removes the connection automatically unless this feature is overridden by enabling debugging.
|
Port x in debugger, connection removed |
For more information, refer to the options listed in the topic w3Apps in the FlashConnect Programmer’s Guide; or in w3DebugOK API found in the FlashConnect Programmer’s Online Reference to modify this feature.
|
CAUTION |
If you are debugging a program in FlashConnect and heartbeats are being used, the heartbeat may not be processed. If w3Monitor is running and the heartbeat is not processed, the w3Monitor may log off the program being debugged. To avoid this, turn on FlashConnect debugging as described in Using the FlashConnect Server Debug Program. |
|
NOTE |
If D3 performance slows while w3Monitor is checking server pool connections, verify that the dm,jobs, and run-time errors files are properly sized. If it is not properly sized, correct the size or delete the completed jobs (use the clear-jobs command). |
See Also
Debugging and Diagnosing FlashConnect Configuration
Diagnosing FlashConnect Configuration Problems (D3 Only)
Running the Loop-Back Test (D3 Only)
Static Application Debug Strategy
Dynamic Application Debug Strategy
Determining if the Application is in the Debugger
Using the FlashConnect Server Debug Program
Recording Outgoing HTML Code and Incoming Variables
Testing FCService on a Specified Machine and Port
Logging Diagnostic Messages for FCService and FCSocketServer
Examining CGI and Form Variables