activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (AMQ-3499) Raise Logging level to warn for Transport failure exceptions
Date Tue, 01 Nov 2011 10:44:32 GMT


Gary Tully resolved AMQ-3499.

       Resolution: Fixed
    Fix Version/s:     (was: 5.x)
         Assignee: Gary Tully

fix in
> Raise Logging level to warn for Transport failure exceptions
> ------------------------------------------------------------
>                 Key: AMQ-3499
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Minor
>              Labels: acrivemq, failure, log, stomp, transport
>             Fix For: 5.6.0
> Transport failure is usually an indication that there is a problem in the jms connection
oriented sphere, less so in stomp.
> Stuff like
> {code}2011-07-13 11:46:00,340 [2.179.220:52512] INFO Transport - Transport failed: PKIX path validation failed:
timestamp check failed{code} should be a warn.
> For stomp, connection reset and EOf exceptions should be suppressed as they are normal
in the absence of DISCONNECT frame.
> With debug level logging, all failures and stack traces are visible.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message