- Original Message -
From: "Javier Lopez" <[EMAIL PROTECTED]>
To: "John L. Utz III" <[EMAIL PROTECTED]>; "Paul Kinnucan"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 08, 2001 2:33 PM
Subject: RE: JDEBug vs Win2K and/
ng to the process.
Javier
-Original Message-
From: John L. Utz III [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 08, 2001 1:01 PM
To: Paul Kinnucan
Cc: [EMAIL PROTECTED]
Subject: RE: JDEBug vs Win2K and/or NT4: Status?
hi paul;
i have time to work on this again over the next few
to pursue it, here is some background. One of the
> >> steps performed by JDEbug when launching an application is to create a
> server
> >> socket. JDEbug allows Java to choose the port number of the server socket
> >> (e.g., 1900). JDEbug then sends this port number back to
gt;then
>> triees to connect to the socket on the specified port. What appears is that
>> somehow, on some systems, the port number gets bumped by 1 so that
JDEbug is
>> waiting on port 1901 while the JDE is trying to connect to port 1900.
>>
>> Any thoughts as to why this mig
s
> waiting on port 1901 while the JDE is trying to connect to port 1900.
>
> Any thoughts as to why this might be happening?
>
> - Paul
>
> >
> > Javier
> >
> >
> > -Original Message-
> > From: Jim Goodwin [mailto:[EMAIL PROTE
r file, I'll give
>it a spin and see what happens.
>
>- Original Message -
>From: "Paul Kinnucan" <[EMAIL PROTECTED]>
>To: "Javier Lopez" <[EMAIL PROTECTED]>; "Jim Goodwin"
><[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
he port number gets bumped by 1 so that JDEbug is
waiting on port 1901 while the JDE is trying to connect to port 1900.
Any thoughts as to why this might be happening?
- Paul
>
> Javier
>
>
> -Original Message-
> From: Jim Goodwin [mailto:[EMAIL PROTECTED]]
> Sent
Title: JDEBug vs Win2K and/or NT4: Status?
The timeout problem still happens to me on
Windows 2000 SP1. It does not happen on Windows 2000 without
SP1.
In the Messages buffer: No response to command 1.
(process = 1; timeout = 30 sec.)
At this point,
it's pretty much dead. There
Title: JDEBug vs Win2K and/or NT4: Status?
I tried it on simple
class, (JDE->Debug App)
and I get something
like
Error: debugger
didn't respond to command:-1 2607 launch 12 -vmexec javaw
-classic
or something like
No response to
command 2612. (process = 13; timeout = 30 sec
Title: JDEBug vs Win2K and/or NT4: Status?
Hi all,
I see in the mail-traffic that Paul K has changed the JDEBug code to avoid
setting priority on the thread when launching the debuggee process, in an
effort to cure the problems with deadlocking at launch.
What has not appeared is any user
10 matches
Mail list logo
