Re: Works in Debug . . .

[Scott Klement <klemscot@xxxxxxxxxxxx>]

I've found that usually when something works in debug, but doesn't work in
real life, it's a timing issue. Running in debug (even without specifying the
program name or stepping through the source) will cause the program to run a
bit more slowly.

With a sockets program, that can make a big difference because it can be
the difference between data being available and not being available.

The symptoms suggest that your client program is giving up and dropping
the connection in between reading the header and reading the body of the
data...   possibly you're "expecting" data when you shouldn't, and simply
slowing down the program causes more data to be there solving the problem.

That's purely my experience however.  The mistakes you make may be
different from the mistakes that I make :)   If you can post code
snippets, I'll see if I can tell you more...


On Mon, 17 Feb 2003, Bartell, Aaron L. (TC) wrote:

> Well, I couldn't find this in the archives after about 10 minutes of looking
> so I am going to post it.
>
> I have an RPG program that is doing a GET to an HTTP server (Tomcat) via
> sockets and receives back a response.  When I run it in debug I can see
> everything that is going on, and it works as expected.  When I run it
> outside of debug it doesn't send the same request; it just sends the header
> of the HTTP request.  I know that it is only sending the header because I
> reviewed the Tomcat logs.
>
> Here is the even weirder part (is weirder a word?). . . all I have to do is
> a STRDBG without entering a program name or nothing, and then call the
> program in question and it works!!??  Why does it work when I have the
> debugger running but it doesn't work when the debugger is not running?
>
> I have had this problem before and I don't remember how I fixed it or if we
> just took another route because we couldn't figure it out.
>
> TIA,
> Aaron Bartell