On Mon, May 3, 2010 at 2:33 PM, Paul Menzel pm.deb...@googlemail.com wrote:
Am Montag, den 03.05.2010, 14:21 +0200 schrieb Torsten Werner:
Open Eclipse. Open a Java project and instead of just Run → Run (Ctrl +
F11) do Run → Debug (F11). It will complain with the above error
message.
That
Am Dienstag, den 04.05.2010, 21:10 +0200 schrieb Torsten Werner:
On Mon, May 3, 2010 at 2:33 PM, Paul Menzel pm.deb...@googlemail.com wrote:
Am Montag, den 03.05.2010, 14:21 +0200 schrieb Torsten Werner:
Open Eclipse. Open a Java project and instead of just Run → Run (Ctrl +
F11) do Run →
Dear Debian folks,
Am Mittwoch, den 03.03.2010, 06:57 + schrieb Debian Bug Tracking System:
[…]
#560056: net.ipv6.bindv6only=1 breaks java networking
It has been closed by Torsten Werner twer...@debian.org.
Unfortunately I just hit this bug using Eclipse yesterday.
Trying to do a
Hi,
Paul Menzel schrieb:
Unfortunately I just hit this bug using Eclipse yesterday.
Trying to do a debug run I got
ERROR: transport error 202: connect failed: Connection refused
ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510)
JDWP exit
Am Montag, den 03.05.2010, 14:21 +0200 schrieb Torsten Werner:
Paul Menzel schrieb:
Unfortunately I just hit this bug using Eclipse yesterday.
Trying to do a debug run I got
ERROR: transport error 202: connect failed: Connection refused
ERROR: JDWP Transport
On Thu, 04 Mar 2010 20:57:04 +0100
Torsten Werner mail.twer...@googlemail.com wrote:
Hi Patrice,
Patrice DUROUX schrieb:
I still have some problem using Tomcat server since the last update
(6b18~pre1-3) on AMD64 architecture with the standard setting
net.ipv6.bindv6only=1 in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrice DUROUX schrieb:
tcp6 0 0 :::8080 :::*LISTEN
19152/java
I think that is the correct behaviour. The server listens on :::8080 and
net.ipv6.bindv6only=1 is set. That means it won't accept
Hy,
I still have some problem using Tomcat server since the last update
(6b18~pre1-3) on AMD64 architecture with the standard setting
net.ipv6.bindv6only=1 in /etc/sysctl.d/bindv6only.conf
The server starts without complaining (no more Socket exception) but
then they are not reachable.
May
Hi Patrice,
Patrice DUROUX schrieb:
I still have some problem using Tomcat server since the last update
(6b18~pre1-3) on AMD64 architecture with the standard setting
net.ipv6.bindv6only=1 in /etc/sysctl.d/bindv6only.conf
may you send the output of
$ sudo netstat -tlpn | grep java
after
Eclipse (upstream Eclipse Classic) still fails to update or install
additional sw:
$ strace -f -econnect /opt/eclipse/eclipse
[pid 12075] connect(118, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr(127.0.0.1)}, 16) = 0
[pid 12075] connect(118, {sa_family=AF_INET6,
Jindřich Makovička schrieb:
$ strace -f -econnect /opt/eclipse/eclipse
Which package version, which architecture are you using?
Torsten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This bug also breaks my personal java installation I keep in
/opt/java/ (not even package managed).
I'm trying to connect to LOCALHOST from Java! Brutal bug to
track down. Try googling for java localhost network is unreachable!
Ha!
Personally, I consider this a Debian bug, not a Java
Package: openjdk-6-jdk
Version: 6b16-1.6.1-2
Severity: important
Netbase has recently introduced the sysctl-setting
net.ipv6.bindv6only=1 in /etc/sysctl.d/bindv6only.conf and this setting
will probably be the default in squeeze.
This setting breaks networking in java, and any traffic will for
13 matches
Mail list logo
