This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 235186 - remote debug attach fails to attempt to make a connection
Summary: remote debug attach fails to attempt to make a connection
Status: RESOLVED DUPLICATE of bug 237184
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.3.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-28 16:05 UTC by wallymarvin
Modified: 2015-09-04 14:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
what I observed (432 bytes, text/plain)
2013-08-28 16:06 UTC, wallymarvin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description wallymarvin 2013-08-28 16:05:55 UTC

    
Comment 1 wallymarvin 2013-08-28 16:06:59 UTC
Created attachment 139381 [details]
what I observed
Comment 2 Martin Entlicher 2013-08-28 16:57:52 UTC
You do not need to attach text comments, you can write directly into the comments area.

Actually, I do not understand much what did you do and what do you expect.
Did you use the Attach Debugger dialog? If yes, what options did you select?
Comment 3 wallymarvin 2013-09-04 15:47:42 UTC
You didn't look at the comments, and just closed it without doing any work. Your system seems to have messed up the description, but the comments are complete.
Comment 4 wallymarvin 2013-09-04 15:48:54 UTC
Comment on attachment 139381 [details]
what I observed

>I did a wirefish dump of a remote debug attach during an attach attempt, at the IP interface of the machine containing the Ide. I got no packets originating to the server port (remote jvm) requested, actually no activity whatsoever on the IDE side. A telnet to that port worked well enough to show an error on the server side. Why dosen't the IDE attempt a connection?
>
>jdb seems to be able to connect
>
>Version is 7.3.1 Confused
Comment 5 wallymarvin 2013-09-04 15:50:11 UTC
Comment on attachment 139381 [details]
what I observed

I did a wirefish dump of a remote debug attach during an attach attempt, at the IP interface of the machine containing the Ide. I got no packets originating to the server port (remote jvm) requested, actually no activity whatsoever on the IDE side. A telnet to that port worked well enough to show an error on the server side. Why dosen't the IDE attempt a connection?
>
>jdb seems to be able to connect
>
>Version is 7.3.1 Confused
Comment 6 wallymarvin 2013-09-04 15:50:59 UTC
I did a wirefish dump of a remote debug attach during an attach attempt, at the IP interface of the machine containing the Ide. I got no packets originating to the server port (remote jvm) requested, actually no activity whatsoever on the IDE side. A telnet to that port worked well enough to show an error on the server side. Why dosen't the IDE attempt a connection?
>
>jdb seems to be able to connect
>
>Version is 7.3.1 Confused
Comment 7 Martin Entlicher 2013-09-04 16:21:25 UTC
I've read what you wrote, but I did not understand much what was the problem.
Since I was busy with other issues, I forgot to reply to your direct e-mail, I'm sorry.

You wrote:
I chose socket connection to the correct host. What the bug is about is choosing that dialog with a socket connection should have initiated a packet out the Ethernet interface connecting to the net that connects to the host running the remote JVM in socket server mode. I saw none. With both telnet and JDB, I saw packet activity on the interface. With JDB is was able to connect to the remote JVM. I assume there is some configuration needed to get Netbeans to do the connect, but the examples on the net I could find say it should work.

Do have direct connection between the two hosts, or is one behind a firewall? If you're behind a firewall, do you have proxy settings set correctly in NetBeans IDE?
Can you please look into Output -> Debugger Console?
It should contain something like "Attaching to <host name>:<port>" followed by some error message.
Comment 8 Martin Entlicher 2015-09-04 14:10:55 UTC
This looks as a similar problem to issue #237184.
When the connection fails, a debug message is printed into messages.log file. That may help to identify the issue.

*** This bug has been marked as a duplicate of bug 237184 ***