tapestry-dev 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-2486) OperationTracker does not work across threads
Date Fri, 07 Aug 2015 08:58:45 GMT

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

Jochen Kemnade commented on TAP5-2486:
--------------------------------------

No, the problem is a completely different one. Apparently, the description is not reported
for IOOperations:
{code}
 @SetupRender
  void testOperationTracker() throws IOException {
    operationTracker.perform("Inner operation", () -> {
      throw new IOException(Thread.currentThread().getName());
    });
  }
{code}
The trace does not contain "Inner operation". Is that intended? I think it's confusing.

> OperationTracker does not work across threads
> ---------------------------------------------
>
>                 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)

Mime
View raw message