[overlord-issues] [JBoss JIRA] (RTGOV-663) Nested SwitchYard service calls are not logged correctly
RH Bugzilla Integration (JIRA)
issues at jboss.org
Mon Sep 14 06:06:00 EDT 2015
[ https://issues.jboss.org/browse/RTGOV-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108155#comment-13108155 ]
RH Bugzilla Integration commented on RTGOV-663:
-----------------------------------------------
Gary Brown <gbrown at redhat.com> changed the Status of [bug 1262630|https://bugzilla.redhat.com/show_bug.cgi?id=1262630] from NEW to MODIFIED
> Nested SwitchYard service calls are not logged correctly
> --------------------------------------------------------
>
> Key: RTGOV-663
> URL: https://issues.jboss.org/browse/RTGOV-663
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Components: Activity Collector
> Affects Versions: 2.1.0.Beta1
> Environment: Tested on:
> JBoss FSW 6.0.0 with RTGov UI Version 2 and
> RTGov Distribution with SwithchYard 2 & JBoss EAP 6.4
> Reporter: Sascha Dirbach
> Assignee: Gary Brown
> Attachments: sy-sca-rtgov.zip
>
>
> When I have a SwitchYard Project with a nested service call in the same Thread (e.g. same-machine SCA service) the outer invocation information is lost in the activity collector, as the ActivityUnit is kept in a ThreadLocal member variable of org.overlord.rtgov.activity.collector.AbstractActivityCollector. By calling the nested service, the previous (outer) ActivityUnit is lost.
> The source code comments & documentation state that nested calls of startScope & endScope are not supported, but I think SwitchYard services with nested service calls in the same Thread are not uncommon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the overlord-issues
mailing list