[
https://issues.apache.org/jira/browse/AMQ-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141070#comment-13141070
]
Gary Tully edited comment on AMQ-3499 at 11/1/11 10:44 AM:
-----------------------------------------------------------
sorry matt, fix already there in
http://svn.apache.org/viewvc?view=rev&rev=1170624 had not marked it as
resolved. See the subversion tab.
was (Author: gtully):
fix in http://svn.apache.org/viewvc?view=rev&rev=1170624
> 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
> 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: 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
