Re: Any solutions for the "Gave up waiting for Emacs to connect to SIO port: " Win2K woes
- Original Message - From: "Mandler, George" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Mandler, George" <[EMAIL PROTECTED]>; "'Paul Kinnucan'" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, May 30, 2001 3:59 PM Subject: RE: Any solutions for the "Gave up waiting for Emacs to connect to SIO port: " Win2K woes > Thanks Javier. > OK I totally went into brain-fry mode and blew it. For the record I am now > working under SP2. > My mistake was that I was doing a JDEbug->LaunchApp , but not doing a > JDE->DebugApp. Re-reading > the JDEbugUG for the nth time I see the sentence "At this point, you should > set one or more breakpoints in the application and select the Run command > from the JDEbug menu". > > However I'm still convinced I wouldn't have worked under SP1, because I > never got to the connection even with a jde-bug-sio-connect-delay equal to > 1. So for whatever reason installing SP2 either fixed or hid the real > problem. > So Paul when you get your dandy Windoze2K machine try it out with SP1 in > your copious spare time and see what happens. > Hi George, Thanks for persisting. For what it's worth, JDE 2.2.7.1 incorporates a change contributed by Eugene Gavrilov that may have helped to solve the problem. The way JDEbug works is that it creates a socket, passes the port number of the socket back to Emacs, and then waits for Emacs to connect to the socket at the specified port. Previously, JDEbug created the socket and started waiting on one thread while another thread passed the socket port back to Emacs. In the latest version, the same thread that creates the port passes the port number back to Emacs BEFORE it starts waiting for a connect (i.e., before it executes socket.accept(). This cleared the hangup on the HP system that Eugene uses. I'm hoping that it may solve the problem for others. - Paul
RE: Any solutions for the "Gave up waiting for Emacs to connect to SIO port: " Win2K woes
Thanks Javier. OK I totally went into brain-fry mode and blew it. For the record I am now working under SP2. My mistake was that I was doing a JDEbug->LaunchApp , but not doing a JDE->DebugApp. Re-reading the JDEbugUG for the nth time I see the sentence "At this point, you should set one or more breakpoints in the application and select the Run command from the JDEbug menu". However I'm still convinced I wouldn't have worked under SP1, because I never got to the connection even with a jde-bug-sio-connect-delay equal to 1. So for whatever reason installing SP2 either fixed or hid the real problem. So Paul when you get your dandy Windoze2K machine try it out with SP1 in your copious spare time and see what happens. humbly, george > -Original Message- > From: Javier Lopez [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 30, 2001 2:05 PM > To: Mandler, George; 'Paul Kinnucan' > Cc: [EMAIL PROTECTED] > Subject: RE: Any solutions for the "Gave up waiting for Emacs > to connect > to SIO port: " Win2K woes > > > For whatever is worth, the *JDEbug* output of the > jde-bug-sio-connect-delay > with less than 14 looks good, normal behavior. You just need > to set up > some breakpoints and you are good to go. > > I have that variable jde-big-sio-connect-delay set up to 1. > FYI, it is the amount of time emacs wait for a response for > the debugger. > > It breaks after 15s, because that's the timeout in the > DebuggeeSIO.java. > I am guessing that emacs waits for whatever the > jde-bug-sio-connect-delay > is before doing anything, less than 14 it connects before the debugger > stop waiting. > > my 2 cents, > > Javier >
RE: Any solutions for the "Gave up waiting for Emacs to connect to SIO port: " Win2K woes
For whatever is worth, the *JDEbug* output of the jde-bug-sio-connect-delay with less than 14 looks good, normal behavior. You just need to set up some breakpoints and you are good to go. I have that variable jde-big-sio-connect-delay set up to 1. FYI, it is the amount of time emacs wait for a response for the debugger. It breaks after 15s, because that's the timeout in the DebuggeeSIO.java. I am guessing that emacs waits for whatever the jde-bug-sio-connect-delay is before doing anything, less than 14 it connects before the debugger stop waiting. my 2 cents, Javier
RE: Any solutions for the "Gave up waiting for Emacs to connect to SIO port: " Win2K woes
g standard I/O handshake.") (jde-dbo-event-set 1 "all" (list "Thread" 1 "main" "runnable" "suspended by debugger" (list) (list) nil) (list 'jde-dbo-vm-start-event)) (jde-dbo-message 1 "initSIOConnect: starting SIO connect thread.") (jde-dbo-command-result 1 1705) (jde-dbo-message 1 "Debugger waiting for Emacs to connect to app SIO port 1705.") (jde-dbo-error 1 "Gave up waiting for Emacs to connect to SIO port: 1705") == END jde-bug-sio-connect-delay >14 > -Original Message- > From: Paul Kinnucan [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 29, 2001 9:48 PM > To: Mandler, George > Cc: [EMAIL PROTECTED] > Subject: Re: Any solutions for the "Gave up waiting for Emacs > to connect > to SIO port: " Win2K woes > > > At 07:19 PM 5/29/2001 -0400, you wrote: > >Hi, > >I've spent way too many hours attempting to get JDEbug working under > >Windoze2K. I've searched the archives and found some emails > from the fall > >suggesting changing jde-bug-sio-connect-delay and > >jde-bug-debugger-host-address , but that didn't seem to make > a difference. > >Hitting return in the *JDEbug* buffer didn't make a > difference either. > >Recently there were postings on Apr 27th about this bug and > someone said it > >doesn't happen with straight Win2K, but did happen with SP1, > I can't revert > >back to the original Win2K, so I installed SP2, but > unfortunately it still > >occurs. Running it from the command line also gives me the > port connection > >failure. > > > >The symptoms are similar to what other unfortunate souls > developing under > >Win2K have experienced. It doesn't connect to the port and > the minibuffer > >will display the "No response to command 1. (process = 1; > timeout = 30 > >sec.)" in the minibuffer if I don't hit those carriage returns in the > >*JDEbug* buffer. > > What happens if you hit the carriage returns in the *JDEbug* buffer? > > What version of the JDK are you using? > > This bug is very frustrating for me because I have NEVER > experienced it in > two years of using JDEbug on Solaris and Windows 95, > Millenium, and NT. But > there is hope. My office machine is scheduled to be upgrade > to Win2k within > the next two weeks. > > - Paul >
