Re: Connection Refused Exceptions

I am still intermittently getting the ConnectException: connection
refused after I restart my services.  However I have recently switched
Jini logging on and have discovered this hidden exception:

FINE: RMI TCP Connection(1)-192.168.0.205: [192.168.0.205] exception:
java.lang.NullPointerException
at
net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl.updateSeqNumber(ServiceDiscoveryManager.java:920)
at
net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl.notifyServiceMap(ServiceDiscoveryManager.java:902)
at
net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl.access$0(ServiceDiscoveryManager.java:890)
at
net.jini.lookup.ServiceDiscoveryManager$LookupCacheImpl$LookupListener.notify(ServiceDiscoveryManager.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

The only reference to this error I can find is this thread here:

http://archives.java.sun.com/cgi-bin/wa?A2=ind0204&L=jini-users&P=41182

Given that the person who posted this bug, also appeared to be having
ConnectExceptions, could this be the root of my issues??  In the thread
Bob mentions that the only thing that should cause this bug is a
concurrent discard of the lookup service, yet I see nothing to show that
this (in my case) is the case.  As I have a DiscoveryListener registered
with the LDM and it's discarded method never seems to fire.

Bob Scheifler wrote:
>> I've recently been trying to fix a problem with some Jini (v1.2.1_001)
>
> I don't suppose there's any chance you could try this with 2.1?
> A number of SDM bugs were fixed after 1.2.1.

Do we know if this bug has been fixed in Jini 2.1?  How much work is
typically involved in an upgrade of Jini 1.2.1 to Jini 2.1?  The API's
seem to be backwardly compatible.  We have what I'd imagine to be a
fairly typical RMI based Jini system.  I'm guessing it's not quite so
straightforward as just changing the classes on the classpath?


--
Rick Moynihan
Software Engineer
Calico Jack LTD
http://www.calicojack.co.uk/

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]