activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-3499) Raise Logging level to warn for Transport failure exceptions
Date Wed, 14 Sep 2011 13:47:09 GMT
Raise Logging level to warn for Transport failure exceptions
------------------------------------------------------------

                 Key: AMQ-3499
                 URL: https://issues.apache.org/jira/browse/AMQ-3499
             Project: ActiveMQ
          Issue Type: Improvement
          Components: Transport
    Affects Versions: 5.5.0
            Reporter: Gary Tully
            Priority: Minor
             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: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException:
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message