Handling ConnectionDroppedExeption and java.net.ConnectException after IPL

Hi,

I hava a Java program running in WebSphere that reads and writes
continuously to a iSeries DataQueue through the jt400 classes.
When the iSeries is IPL'd, i want the Java program to stay alive and
continue when the iSeries is up and running. To achieve this, 
I handled the ConnectionDroppedException. However, sometimes
java.netConnectException is fired instead of the ConnectionDropped
Exception. So I handle them both and perfom a retry in either case. In case
of the connectException, this works, but whenever the
ConnectionDroppedException is thrown, the program stops reading and writing,
without terminating the Java process. to start reading
and writing again I have to restart the Java app.
So my problem is that the behaviour is not entirely predictable concerning
the Exception that is thrown after an IPL.

Does anybody have a robust way to handle this?

Jeroen de Wolf

W2K
WSDC5.0
iSeries 4.5