tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2531) OperationTracker doesn't report path when failing to create exception report files
Date Tue, 23 Feb 2016 03:02:18 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158199#comment-15158199
] 

Hudson commented on TAP5-2531:
------------------------------

FAILURE: Integrated in tapestry-trunk-freestyle #1557 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1557/])
Fixed TAP5-2531 (OperationTracker doesn't report path when failing to (bobharner: rev 1c2a1ed1438ac1c8f565c49ca1999ad23e6593d1)
* tapestry-core/src/main/java/org/apache/tapestry5/internal/services/exceptions/ExceptionReporterImpl.java


> OperationTracker doesn't report path when failing to create exception report files
> ----------------------------------------------------------------------------------
>
>                 Key: TAP5-2531
>                 URL: https://issues.apache.org/jira/browse/TAP5-2531
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Bob Harner
>            Assignee: Bob Harner
>             Fix For: 5.4.1
>
>
> Currently, if OperationTracker is blocked from creating its exception report file due
to file permissions, the error message in the console doesn't give the path where it is trying
to create the file:
> [ERROR] TapestryModule.ExceptionReporter Unable to write exception report exception-20160215-151536-801.0.txt:
No such file or directory



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message