Re: Stopping Timeout in Debug

From: Kieran Kelleher (kieran_list..ac.com)
Date: Mon Apr 30 2007 - 15:03:43 EDT

  • Next message: Mike Schrag: "Re: new html editor"

    Strange, it did not work :-(

    Do I need to leave JavaMonitor running permanently?

    Here is the SiteConfigf.xml after I updated the settings in
    JavaMonitor. I even rebooted completely to make sure ......

    kieranbook:/Library/WebObjects/Configuration kieran$ cat SiteConfig.xml
    <SiteConfig type="NSDictionary">
             <hostArray type="NSArray">
                     <element type="NSDictionary">
                             <type type="NSString">MACOSX</type>
                             <name type="NSString">localhost</name>
                     </element>
             </hostArray>
             <applicationArray type="NSArray">
             </applicationArray>
             <instanceArray type="NSArray">
             </instanceArray>
             <site type="NSDictionary">
                     <viewRefreshEnabled type="NSString">YES</
    viewRefreshEnabled>
                     <cnctTimeout type="NSNumber">600</cnctTimeout>
                     <viewRefreshRate type="NSNumber">60</viewRefreshRate>
                     <urlVersion type="NSNumber">4</urlVersion>
                     <recvTimeout type="NSNumber">600</recvTimeout>
                     <woAdaptor type="NSString">http://localhost/cgi-bin/
    WebObjects</woAdaptor>
             </site>
    </SiteConfig>

    On Apr 30, 2007, at 12:51 PM, Chuck Hill wrote:

    > 1. Fire up JavaMonitor and go to localhost:56789
    >
    > 2. Setup localhost as a host if this is not already done
    >
    > 3. On the Site tab, increase the Connect and Receive Timeouts (they
    > are in seconds).
    >
    > Chuck
    >
    >
    > On Apr 30, 2007, at 6:55 AM, Kieran Kelleher wrote:
    >
    >> Good morning list,
    >> I am only asking to save time experimenting with launch
    >> parameters, etc. because this is not obvious to me which setings
    >> affect this.
    >>
    >> When I want to debug in the middle of the R-R loop, my browser
    >> inevitably gets a "No instance available" message since I have the
    >> thread suspended while I examine variables. What settings can be
    >> changed to allow indefinite (or very long) waiting time for the
    >> request to finish while in debug mode.
    >>
    >> Environment
    >> FireFox 2
    >> Eclipse/very recent WOLips
    >> Direct Connect is DISABLED.
    >>
    >> I know someone probably has this already, so I would appreciate if
    >> someone could share what settings to change.
    >>
    >> Thanks, Kieran
    >>
    >
    > --
    >
    > Practical WebObjects - for developers who want to increase their
    > overall knowledge of WebObjects or who are trying to solve specific
    > problems.
    > http://www.global-village.net/products/practical_webobjects
    >
    >
    >
    >
    >



    This archive was generated by hypermail 2.0.0 : Mon Apr 30 2007 - 15:03:55 EDT