river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregg Wonderly (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-13) net.jini.discovery.LookupDiscovery logging is verbose and distracting to debugging
Date Fri, 02 Mar 2007 21:18:50 GMT
net.jini.discovery.LookupDiscovery logging is verbose and distracting to debugging
----------------------------------------------------------------------------------

                 Key: RIVER-13
                 URL: https://issues.apache.org/jira/browse/RIVER-13
             Project: River
          Issue Type: Improvement
         Environment: Any Machine with multiple network interfaces, some of which are not
active.
            Reporter: Gregg Wonderly


On my laptop computer, I have 3 different network interfaces available.  Wireless, wired and
bluetooth.  When trying to debug certain LookupDiscovery issues, I wanted to turn logging
up to the FINE level.  Apon doing this, I was suddenly greeted with huge amounts of logging
related to the inactive interfaces not being able to use multicast.  On top of that, the logger
used seems to not be setup correctly.

Below is an extraction of the log file showing the two, recurring log entries.  The HANDLED
entry has a "null" logger name, which makes it difficult to know how to turn that entry on/off.

03/02/2007 15:05:39 [net.jini.discovery.LookupDiscovery#29] CONFIG # LookupDiscovery - multicast
network interface(s): [name:lo (MS TCP Loopback interface) index: 1 addresses:
/127.0.0.1;
, name:eth0 (Realtek RTL8139/810x Family Fast Ethernet NIC - Packet Scheduler Miniport) index:
2 addresses:
, name:eth1 (Bluetooth Device (Personal Area Network) #3) index: 65541 addresses:
, name:eth2 (Broadcom 802.11b/g WLAN - Packet Scheduler Miniport) index: 1507331 addresses:
/192.168.5.104;
]
03/02/2007 15:05:39 [null#30] HANDLED # network interface is bad or not configured for multicast:
name:eth0 (Realtek RTL8139/810x Family Fast Ethernet NIC - Packet Scheduler Miniport) index:
2 addresses:

java.net.SocketException: bad argument for IP_MULTICAST_IF2: No IP addresses bound to interface
        at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method)
        at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:299)
        at java.net.MulticastSocket.setNetworkInterface(MulticastSocket.java:502)
        at net.jini.discovery.LookupDiscovery$AnnouncementListener.<init>(LookupDiscovery.java:1033)
        at net.jini.discovery.LookupDiscovery$7.run(LookupDiscovery.java:3102)
        at java.security.AccessController.doPrivileged(Native Method)
        at net.jini.security.Security$5.run(Security.java:543)
        at java.security.AccessController.doPrivileged(Native Method)
        at net.jini.security.Security.doPrivileged(Security.java:540)
        at net.jini.discovery.LookupDiscovery.beginDiscovery(LookupDiscovery.java:3100)
        at net.jini.discovery.LookupDiscovery.<init>(LookupDiscovery.java:1957)
        at net.jini.discovery.LookupDiscoveryManager.beginDiscovery(LookupDiscoveryManager.java:1493)
        at net.jini.discovery.LookupDiscoveryManager.<init>(LookupDiscoveryManager.java:936)

I'd like to recommend a hierarchy of loggers be used in this code.  I think that there would
be some value in having the discovery logging support loggers with suffixes such as

...unicast.eth0
...multicast.eth0

or

...eth0.multicast
...eth0.unicast

to help the user be able to turn off unneed logging information.  I'm not sure exactly what
logger names make the most sense, but I think something with more information in the logger
name would be helpful in managing the logging output more effectively.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message