Dear QPID users,

I am using the QPID JMS client API (version 0.3.0). (I don't have
information about the broker.) I don't have much experience in using the
Qpid Messaging API.

Last week I detected an unexpected disconnection. These are the last qpid
API log entries.

main.log
2015-06-25 10:40:53.506 - INFO - System.out: nioEventLoopGroup-2-1, WRITE:
TLSv1.2 Application Data, length = 517
2015-06-25 10:41:14.811 - INFO - System.out: nioEventLoopGroup-2-1, called
closeOutbound()
2015-06-25 10:41:14.811 - INFO - System.out: nioEventLoopGroup-2-1,
closeOutboundInternal()
2015-06-25 10:41:14.811 - INFO - System.out: nioEventLoopGroup-2-1
2015-06-25 10:41:14.811 - INFO - System.out: , SEND TLSv1.2 ALERT:  
2015-06-25 10:41:14.811 - INFO - System.out: warning, 
2015-06-25 10:41:14.811 - INFO - System.out: description = close_notify
2015-06-25 10:41:14.811 - INFO - System.out: nioEventLoopGroup-2-1, WRITE:
TLSv1.2 Alert, length = 64
2015-06-25 10:41:14.811 - INFO - System.out: nioEventLoopGroup-2-1, called
closeInbound()
2015-06-25 10:41:14.811 - INFO - System.out: nioEventLoopGroup-2-1, fatal
error: 80: Inbound closed before receiving peer's close_notify: possible
truncation attack?
javax.net.ssl.SSLException: Inbound closed before receiving peer's
close_notify: possible truncation attack?
2015-06-25 10:41:14.812 - INFO - System.out: %% Invalidated:  [Session-1,
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256]
2015-06-25 10:41:14.812 - INFO - System.out: nioEventLoopGroup-2-1
2015-06-25 10:41:14.812 - INFO - System.out: , SEND TLSv1.2 ALERT:  
2015-06-25 10:41:14.812 - INFO - System.out: fatal, 
2015-06-25 10:41:14.812 - INFO - System.out: description = internal_error
2015-06-25 10:41:14.812 - INFO - System.out: nioEventLoopGroup-2-1,
Exception sending alert: java.io.IOException: writer side was already
closed.

2015-06-25 10:41:14.816 - WARN - Error caught while closing Provider: 
(strange ... log entry without exception)

frame.log
2015-06-25 10:40:27.076 - INFO - SENT: Disposition{role=RECEIVER,
first=1094, last=1094, settled=true, state=Accepted{}, batchable=false}
2015-06-25 10:40:53.505 - INFO - SENT: Transfer{handle=0, deliveryId=1095,
deliveryTag=0, messageFormat=0, settled=null, more=false,
rcvSettleMode=null, state=null, resume=false, aborted=false,
batchable=false}
2015-06-25 10:41:14.815 - INFO - SENT: Close{error=null}

However my application ran on.

I thought that I will get an exception, if I trying to send a messages after
the connection was closed. But I could send further requests without any
exception.
Is the connection still open or closed?

I have read that the API tries to establish the connection again. But I
couldn't find any hint in the log files. (Maybe I ignored the logger.)

How can I handle these disconnections? Do I need an ExceptionHandler? How
can I distinguish between recoverable and these fatal errors?

Thank your for your help.

Regards
Henry



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/How-to-detect-handle-these-connection-lost-tp7627365.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to