 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
GEORGE Guest
|
Posted: Sun Apr 17, 2005 12:51 am Post subject: unable to debug |
|
|
I just downloaded JBuilder 2005 Foundation; When I do SHIFT-F9 to debug a
project I get the following message:
-- Cannot configure Java debug process arguments --
com.sun.jdi.connect.IllegalConnectorArgumentsException: Not listening
Any help will be appreciated.
TIA
George
|
|
| Back to top |
|
 |
GEORGE Guest
|
Posted: Mon Apr 18, 2005 11:55 pm Post subject: Re: unable to debug |
|
|
Ok Never mind. It's a firewall issue: JBuilder requires outbound internet
access.
"GEORGE" <geo (AT) nowhere (DOT) net> wrote
| Quote: | I just downloaded JBuilder 2005 Foundation; When I do SHIFT-F9 to debug a
project I get the following message:
-- Cannot configure Java debug process arguments --
com.sun.jdi.connect.IllegalConnectorArgumentsException: Not listening
Any help will be appreciated.
TIA
George
|
|
|
| Back to top |
|
 |
Ken Warner Guest
|
Posted: Tue Apr 19, 2005 12:07 am Post subject: Re: unable to debug |
|
|
In other words, JBuilder has a Spyware function so that
every time you debug, Borland is notified that you are
debugging. Is this to track use pasterns and isn't it
time that companies stop "observing" us???
GEORGE wrote:
| Quote: | Ok Never mind. It's a firewall issue: JBuilder requires outbound internet
access.
"GEORGE" <geo (AT) nowhere (DOT) net> wrote in message
news:4261b322 (AT) newsgroups (DOT) borland.com...
I just downloaded JBuilder 2005 Foundation; When I do SHIFT-F9 to debug a
project I get the following message:
-- Cannot configure Java debug process arguments --
com.sun.jdi.connect.IllegalConnectorArgumentsException: Not listening
Any help will be appreciated.
TIA
George
|
|
|
| Back to top |
|
 |
Lori M Olson [TeamB] Guest
|
Posted: Tue Apr 19, 2005 12:10 am Post subject: Re: unable to debug |
|
|
Ken Warner wrote:
| Quote: | In other words, JBuilder has a Spyware function so that
every time you debug, Borland is notified that you are
debugging. Is this to track use pasterns and isn't it
time that companies stop "observing" us???
|
Relax. The debugger is making an outbound connection TO LOCALHOST. No
spyware involved.
--
Regards,
Lori Olson [TeamB]
------------
Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.
Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html
|
|
| Back to top |
|
 |
George Guest
|
Posted: Tue Apr 19, 2005 1:34 pm Post subject: Re: unable to debug |
|
|
Yes, that's what I observed so I had no problems granting the access.
But incidentally, java.exe and javaw.exe also request internet
access....why?
"Lori M Olson [TeamB]" <javadragon (AT) techie (DOT) com> wrote
| Quote: | Ken Warner wrote:
In other words, JBuilder has a Spyware function so that
every time you debug, Borland is notified that you are
debugging. Is this to track use pasterns and isn't it
time that companies stop "observing" us???
Relax. The debugger is making an outbound connection TO LOCALHOST. No
spyware involved.
--
Regards,
Lori Olson [TeamB]
------------
Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.
Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html
|
|
|
| Back to top |
|
 |
Lori M Olson [TeamB] Guest
|
Posted: Tue Apr 19, 2005 2:37 pm Post subject: Re: unable to debug |
|
|
George wrote:
| Quote: | Yes, that's what I observed so I had no problems granting the access.
But incidentally, java.exe and javaw.exe also request internet
access....why?
|
Which version of java.exe and javaw.exe are we talking about? I know
that there are the beginnings of some JVM/classloader sharing starting
to appear in JDK 5, so it's probably using the port check to see if
another instance of java is running already.
--
Regards,
Lori Olson [TeamB]
------------
Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.
Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html
|
|
| Back to top |
|
 |
George Guest
|
Posted: Tue Apr 19, 2005 2:46 pm Post subject: Re: unable to debug |
|
|
I'm talking about JDK 5. Sun AppServer 8.1 requests access too.
"Lori M Olson [TeamB]" <javadragon (AT) techie (DOT) com> wrote
| Quote: | George wrote:
Yes, that's what I observed so I had no problems granting the access.
But incidentally, java.exe and javaw.exe also request internet
access....why?
Which version of java.exe and javaw.exe are we talking about? I know
that there are the beginnings of some JVM/classloader sharing starting
to appear in JDK 5, so it's probably using the port check to see if
another instance of java is running already.
--
Regards,
Lori Olson [TeamB]
------------
Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.
Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html
|
|
|
| Back to top |
|
 |
Ken Warner Guest
|
Posted: Tue Apr 19, 2005 4:25 pm Post subject: Re: unable to debug |
|
|
I get it, the debugger uses sockets to connect to the running
program. I should have figured this out. It's the way
debuggers usually work.
My bad...
Lori M Olson [TeamB] wrote:
| Quote: | Ken Warner wrote:
In other words, JBuilder has a Spyware function so that
every time you debug, Borland is notified that you are
debugging. Is this to track use pasterns and isn't it
time that companies stop "observing" us???
Relax. The debugger is making an outbound connection TO LOCALHOST. No
spyware involved.
|
|
|
| Back to top |
|
 |
Shankar Unni Guest
|
Posted: Wed Apr 20, 2005 8:49 pm Post subject: Re: unable to debug |
|
|
Ken Warner wrote:
| Quote: | In other words, JBuilder has a Spyware function so that
every time you debug, Borland is notified that you are
debugging.
|
Wow, for a moment there, I thought I was in a time warp and that time
had jumped back 19 days..
|
|
| Back to top |
|
 |
Shawn Castrianni Guest
|
Posted: Sun Jun 19, 2005 8:36 pm Post subject: Re: unable to debug |
|
|
Is there a way to customize what IP address Borland specifies on the command
line when debugging? By default, it looks like it uses this:
-Xrunjdwp:transport=dt_socket,address=<hostname>:1490
where hostname is the hostname of the computer running JBuilder. I would
like to specify 127.0.0.1 instead. Yes, I know they mean the same thing,
but actually some VPN software is set to encrypt traffic to certain IP
addresse. Therefore, it is resolving <hostname> to its IP address and
encrypting it. If I could specify 127.0.0.1 instead, the VPN software would
know to NOT encrypt it since it skips the loopback address.
"GEORGE" <geo (AT) nowhere (DOT) net> wrote
| Quote: | I just downloaded JBuilder 2005 Foundation; When I do SHIFT-F9 to debug a
project I get the following message:
-- Cannot configure Java debug process arguments --
com.sun.jdi.connect.IllegalConnectorArgumentsException: Not listening
Any help will be appreciated.
TIA
George
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|