tapestry-commits mailing list archives

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

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

Jochen Kemnade commented on TAP5-2531:
--------------------------------------

Can you provide a stacktrace along with the error message, Bob?

> 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
>
> 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