[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#562954: marked as done (java-common: All java networking ignores ipv4 interfaces)

Your message dated Sun, 11 Apr 2010 13:40:44 +0200
with message-id <4BC1B53C.3040005@thykier.net>
and subject line Re: Bug#562954: java-common: All java networking ignores ipv4 interfaces
has caused the Debian Bug report #562954,
regarding java-common: All java networking ignores ipv4 interfaces
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
562954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562954
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: java-common
Version: 0.34
Severity: grave
Justification: renders package unusable


Since my last upgrade of java, all java applications that use networking
stopped working. After some research I found that this is because of
a change that makes java start to use ipv6 instead of ipv4.

I have to following interfaces (ifconfig):

br0       Link encap:Ethernet  HWaddr 00:1a:92:3a:4a:c1  
          inet addr:192.168.2.4  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::21a:92ff:fe3a:4ac1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2656682 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1257786 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1473927102 (1.3 GiB)  TX bytes:406009708 (387.2 MiB)

eth1      Link encap:Ethernet  HWaddr 00:1a:92:3a:4a:c1  
          inet6 addr: fe80::21a:92ff:fe3a:4ac1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2656682 errors:0 dropped:1798 overruns:0 frame:0
          TX packets:1257827 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1474631718 (1.3 GiB)  TX bytes:406015654 (387.2 MiB)
          Interrupt:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:350463 errors:0 dropped:0 overruns:0 frame:0
          TX packets:350463 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:42943362 (40.9 MiB)  TX bytes:42943362 (40.9 MiB)

And the following routing info (route):

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
localnet        *               255.255.255.0   U     0      0        0 br0
default         ansset.localdom 0.0.0.0         UG    0      0        0 br0


Starting 'java' with -Djava.net.preferIPv4Stack=true solves the problem
for that particular application, but not entirely because some
applications invoke java again themselves, ie a restart or subprocess.
It's not nice to have to edit scripts of packages to get them to
work again (scripts are not configuration files).

Basically, all java networking got broken by this change (unless you
have and use ipv6 interfaces).

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

java-common depends on no packages.

java-common recommends no packages.

Versions of packages java-common suggests:
pn  default-jre                   <none>     (no description available)
ii  equivs                        2.0.7-0.1  Circumvent Debian package dependen

-- no debconf information

--- End Message ---
--- Begin Message --- 
I am closing this as "not a bug" (in java-common at least).

As pointed out, this is a bug in either netbase or individual JVMs. To
the best of my knowledge openjdk-6 is now unaffected by it and sun-java6
is still affected. I do not know how gcj is doing in this regard.

~Niels

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: