[
https://issues.apache.org/jira/browse/TAP5-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661566#comment-14661566
]
ASF subversion and git services commented on TAP5-2486:
-------------------------------------------------------
Commit b20ed0fae7da0394caaa1609aaf3d60dda9b086a in tapestry-5's branch
refs/heads/master from [~jkemnade]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=b20ed0f ]
TAP5-2486: make sure that IOOperation descripions appear in the operations
trace if they throw an IOException #close
> 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)
