My problem was user error, I am embarrased to admit. The default
.profile on the target machine was pointing to jdk1.1. Sorry for the
wasted bandwidth.
Chuck
-----Original Message-----
From: paulk [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 27, 2000 9:15 PM
To: jde
Cc: paulk
Subject: Re: JDEbug error: No response to command 1. (process = 1;
timeout = 10 sec.)
At 07:48 AM 7/28/00 +0200, Ulrich Kriegel wrote:
>Chuck Irvine wrote:
>>
>> I've just installed jde/jpda/JDEbug on a Solaris box. When I invoke
>> "JDE->Debug App", I get:
>> No response to command 1. (process = 1; timeout = 10 sec.)
>> This seems a little fishy because the error comes up more or less
>> immediately, while the error message mentions "10 sec.". One
possibility
>> that comes to mind is that JDE or one of its dependent packages
doesn't
>> like the version of emacs that I am running, 20.3.1. I know its a
little
>> old. Any help is much appreciated. Thanks!
>>
>The same happens at our site
Please don't jump to conclusions. There are any number of reasons why
the
debugger might not respond to a command from the JDE. In Chuck's case,
the
reason is that a class not found exception occurs in the JDEbug code
before
it gets a chance to respond to the command. The missing class happens to
be
java.util.HashMap, one of the core JDK classes. Is this the problem you
are
experiencing? I find the error Chuck is experiencing very weird since
this
class is part of the JDK 1.2.2 rt.jar file and the rt.jar file is on the
default classpath for the JDK 1.2.2 vm. I would suspect that the rt.jar
file is missing or that some other version of the JDK is being used.
Note also that Chuck has not properly configured his LD_LIBRARY_PATH to
run
JDEbug, though I do not think this is the root of this particular
problem.
> - with NT there are no problems but using Solaris 2.7 and JDK 1.1.2,
1.1.2_05a
>whe above described error occur.
>Since this is not the first description of that problem with Solaris
the
>question arises: "Did somebody succedd using Jdebug on Solaris?"
>--
I have been using JDEbug on Solaris for the last nine months without any
problem, most recently on Solaris 2.6. I sincerely doubt there is
anything
peculiar to Solaris 2.7 that would cause this error.
- Paul
