SocketException on client callback

[jamoore]

2009-11-16 08:02:58,669 ERROR [ ome.services.blitz.impl.ServiceFactoryI] (l.Server-7) Unknown error on oneway ClientCallback.sessionClosed to ClientCallback/c834d3ae-6
104-449c-8a1d-ed0678f0e3d6
Ice.SocketException
    error = 0
        at IceInternal.Network.doFinishConnect(Network.java:428)
        at IceInternal.TcpTransceiver.initialize(TcpTransceiver.java:33)
        at Ice.ConnectionI.initialize(ConnectionI.java:1536)
        at Ice.ConnectionI.socketReady(ConnectionI.java:1116)
        at Ice.ConnectionI$SocketReadyCallback.socketReady(ConnectionI.java:2299)
        at IceInternal.SelectorThread.run(SelectorThread.java:203)
        at IceInternal.SelectorThread$HelperThread.run(SelectorThread.java:273)
Caused by: java.net.NoRouteToHostException: No route to host
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:574)
        at IceInternal.Network.doFinishConnect(Network.java:393)
        ... 6 more
2009-11-16 08:02:58,669 INFO  [ ome.services.blitz.impl.ServiceFactoryI] (l.Server-7) Closing ome.services.blitz.impl.ServiceFactoryI@6ef6363 session
2009-11-16 08:02:58,670 INFO  [ ome.services.blitz.impl.ServiceFactoryI] (l.Server-7) Unregistered servant:1df2c33d-7c7c-46f2-a05a-8d8b1028a4aa/omero.api.IQuery(omero.
api._IQueryTie@e8c680b)
2009-11-16 08:02:58,670 INFO  [ ome.services.blitz.impl.ServiceFactoryI] (l.Server-7) Removed servant from adapter: omero.api.IQuery
2009-11-16 08:02:58,670 INFO  [ome.services.sessions.state.SessionCache] (l.Server-7) Destroying session 1df2c33d-7c7c-46f2-a05a-8d8b1028a4aa due to : Remove session c
alled
2009-11-16 08:02:58,670 INFO  [                 org.perf4j.TimingLogger] (l.Server-7) start[1258358574765] time[3905] tag[omero.session]

[jmoore]

(In [7622]) Adding catch clause for SocketException (See #1667)

[jmoore]

(In [7630]) Adding catch clause for SocketException (See #1667)

original-svn-id: ​file:///home/svn/omero/branches/Beta4.2@7622 05709c45-44f0-0310-885b-81a1db45b4a6

[jmoore]

This catches another particular case which we can do nothing about and logs it at WARN, which is good, and other specific exceptions will be continue to be logged at ERROR so we can add them, but in general a broader strategy would be useful. Adding this ticket to the "See alsos" for the exception review (#799)