You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/08/07 11:12:46 UTC
[jira] [Commented] (TAP5-2486) IOOperation descriptions do not show
up in the operation trace
[ https://issues.apache.org/jira/browse/TAP5-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661536#comment-14661536 ]
Jochen Kemnade commented on TAP5-2486:
--------------------------------------
If I throw a RuntimeException, the description is shown in the trace. I guess we should not call {{handleFinally()}} in {{org.apache.tapestry5.ioc.internal.OperationTrackerImpl.perform(String, IOOperation<T>)}} if the IOOperation actually throws an IOException.
> IOOperation descriptions do not show up in the operation trace
> --------------------------------------------------------------
>
> Key: TAP5-2486
> URL: https://issues.apache.org/jira/browse/TAP5-2486
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
>
> If OperationTracker is used to track operations in forked threads (which for instance happens if you use Java 8 parallel streams), the exception report will not contain those operations. This might even be a gerenal problem with per-thread services. I don't see a solution yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)