Re: RDP V8.0 Debug loses connection intermittently

Will do. Should be easy to find since I generally am the one starting up the debug server under my profile. I will stop then restart it, then we have some testing to do this afternoon which will hopefully recreate the issue so I can send a smaller job log your way. If not, I'll send the bigger one I anticipate with the current run.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Xuan Chen
Sent: Tuesday, April 26, 2011 2:29 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDP V8.0 Debug loses connection intermittently

It sounds there was some problem with debug server in the system.

Could you please collect the following information once you encounter the
problems again:

Try to find if there is any job name QB5SERVER running under your user
profile. If yes, collect the job log.
If no, try to see if any spool file with the same name, and collect the
contents of that spool file.

Thanks,

Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx





"Tarr, Kenneth" <Kenneth.Tarr@xxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
26/04/2011 10:10 AM
Please respond to
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>


To
"'Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] RDP V8.0 Debug loses connection intermittently






I've had this situation happen on rare occasion in the past, but now that
I am on RDP V8.0 (8.0.0.2) and was using it extensively yesterday to debug
an application and experienced this issue several times, I wanted to post
this to the group. It will hopefully shed some light on either a problem
known to others in the community, or isolate it as a local issue on our
end. Or the likely issue I am doing something wrong.

Here are the scenarios.

1) When you attempt to connect to a job that is running, most of the time
it successfully connects and stops the program on the line it is
executing. There are other times however the debugger returns a message
something similar to "connection with the debug server was lost". (My
theory is that, if the actual program being debugged is running it will
connect, but if another program in the stack is running that was called by
the program being debugged, it can't connect. I theorize this because
whenever I have the job on hold and try to connect with debug, it can't on
the same premise that the program isn't moving forward -- see #3 below.)

2) When in debug, if I veer away from the debug application to another
Windows application (like a Client Access session), on occasion it comes
back with a "continue waiting for debug server to respond" message. At
that point I click OK, but never can resume my debugging. After awhile,
RDP just gets hung up, so my only recourse is to abruptly end the
application, which releases the debugged job and allows it to continue
running (it is no longer at an EVTW state). This happens about 10% or
less of the time, but yesterday it was happening a lot more.

3) When you attempt to connect to a job that was placed on hold, in the
past the predecessor WDSC was able to release that job and in turn stop it
at the next debuggable line. Now when I try doing this in RDP, I get a
message (something like "error trying to connect" message). The job
remains on hold fortunately, but the only way to get the debugger to
connect is to release the job.

Any ideas? Thanks in advance for your input.
This e-mail and attachment(s) may contain information that is privileged,
confidential, and/or exempt from disclosure under applicable law. If the
reader of this message is not the intended recipient, you are hereby
notified that any dissemination, distribution, or copy of this message is
strictly prohibited. If received in error, please notify the sender
immediately and delete/destroy the message and any copies thereof.
Although Associated Banc-Corp and/or its affiliates (collectively
"Associated") attempt to prevent the passage of viruses via e-mail and
attachments thereto, Associated does not guarantee that either are
virus-free, and accepts no liability for any damage sustained as a result
of any such viruses. Any federal tax advice contained in this
communication (including any attachments) is not intended or written to be
used or referred to in the promoting, marketing, or recommending of any
entity, investment plan or agreement, nor is such advice intended or
written !
to be used, and cannot be used, by a taxpayer for the purpose of avoiding
penalties under the Internal Revenue Tax Code