On Mon, Sep 29, 2008 at 11:45 AM, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> Hi,
>
> "Out of the blue", I am suddenly getting strange exceptions (see
> below), but more importantly, it happens when it communicates with all
> kinds of hosts. Why is Jini doing that? (I have no Unicast discovery
> in my code)

Ok, the many different hosts is all the ones that is reported by the
system (got various VPN's and crap installed nowadays).

I added configuration

import java.net.InetAddress;
import java.net.NetworkInterface;

net.jini.discovery.LookupDiscovery
{
    multicastInterfaces = new NetworkInterface[] {
NetworkInterface.getByInetAddress( InetAddress.getByName( "127.0.0.1"
) ) };

}

to get rid of those, but the main problem with Exception remains.

I turned on some logging output... The first exception that occurs.


HANDLED: exception decoding multicast announcement
com.sun.jini.discovery.DiscoveryProtocolException
        at 
com.sun.jini.discovery.DiscoveryV1.decodeMulticastAnnouncement(DiscoveryV1.java:366)
        at 
com.sun.jini.discovery.Discovery.decodeMulticastAnnouncement(Discovery.java:352)
        at net.jini.discovery.LookupDiscovery$11.run(LookupDiscovery.java:3259)
        at java.security.AccessController.doPrivileged(Native Method)
        at 
net.jini.discovery.LookupDiscovery.decodeMulticastAnnouncement(LookupDiscovery.java:3256)
        at 
net.jini.discovery.LookupDiscovery.access$2700(LookupDiscovery.java:696)
        at 
net.jini.discovery.LookupDiscovery$DecodeAnnouncementTask.run(LookupDiscovery.java:1523)
        at com.sun.jini.thread.TaskManager$TaskThread.run(TaskManager.java:331)
Caused by: java.nio.BufferUnderflowException
        at java.nio.Buffer.nextGetIndex(Buffer.java:404)
        at java.nio.HeapByteBuffer.getLong(HeapByteBuffer.java:387)
        at 
com.sun.jini.discovery.DiscoveryV1.decodeMulticastAnnouncement(DiscoveryV1.java:343)
        ... 7 more
Sep 29, 2008 1:48:03 PM net.jini.config.AbstractConfiguration getEntryInternal
FAILED: [EMAIL PROTECTED], component
net.jini.lookup.ServiceDiscoveryManager, name leaseManager: entry not
found

looks pretty serious to me.

What I think has happened is that a Mac OSX update has occur between
now and yesterday when it worked.

"ifconfig" reports;

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::21f:f3ff:fed7:4fd6%en0 prefixlen 64 scopeid 0x4
        inet 192.168.100.41 netmask 0xffffff00 broadcast 192.168.100.255
        ether 00:1f:f3:d7:4f:d6
        media: autoselect (100baseTX <full-duplex,flow-control>) status: active
        supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP
<full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP
<full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX
<full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX
<full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT
<full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none

which I interpret as that Multicast is enabled.

Anything else I could look for?


Cheers
niclas

Reply via email to