July 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-664) Provide a gateway to translate hawkular BTM fragments into RTGov activity events

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-664?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-664: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/311 > Provide a gateway to translate hawkular BTM fragments into RTGov activity events > -------------------------------------------------------------------------------- > > Key: RTGOV-664 > URL: https://issues.jboss.org/browse/RTGOV-664 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > Translate any Service nodes, from BTM business transaction fragments, into Activity Events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-664) Provide a gateway to translate hawkular BTM fragments into RTGov activity events

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-664?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-664. ------------------------------ Resolution: Done > Provide a gateway to translate hawkular BTM fragments into RTGov activity events > -------------------------------------------------------------------------------- > > Key: RTGOV-664 > URL: https://issues.jboss.org/browse/RTGOV-664 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > Translate any Service nodes, from BTM business transaction fragments, into Activity Events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-664) Provide a gateway to translate hawkular BTM fragments into RTGov activity events

by Gary Brown (JIRA)

Gary Brown created RTGOV-664: -------------------------------- Summary: Provide a gateway to translate hawkular BTM fragments into RTGov activity events Key: RTGOV-664 URL: https://issues.jboss.org/browse/RTGOV-664 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.2.0 Translate any Service nodes, from BTM business transaction fragments, into Activity Events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on ARTIF-752: ------------------------------------- If you want to change the database being used, you will need to swap out the datasource file that is installed by default with one that is configured for the database you wish to test. The default datasource file is configured for H2. If you want to test using mysql, for example, you will need to remove the `artificer-h2-ds.xml` file and replace it with something like artificer-mysql-ds.xml. Additionally, you will need to manually change some properties in the `artificer.properties` file. Specifically you will need to change these values: https://github.com/ArtificerRepo/artificer/blob/master/installer/src/main... The installer likely will never support anything but the default H2 configuration. So alternative DBs will always need to be configured manually. > Change of the artificer datasource configuration does not change datasource name > -------------------------------------------------------------------------------- > > Key: ARTIF-752 > URL: https://issues.jboss.org/browse/ARTIF-752 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Final > Reporter: Viliam Kasala > Assignee: Brett Meyer > > Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name

by Viliam Kasala (JIRA)

[ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.... ] Viliam Kasala commented on ARTIF-752: ------------------------------------- How would be possible to change database, when new installer (overlay) of S-RAMP will ready? There is a requirement to test all the possible supported database instances. > Change of the artificer datasource configuration does not change datasource name > -------------------------------------------------------------------------------- > > Key: ARTIF-752 > URL: https://issues.jboss.org/browse/ARTIF-752 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Final > Reporter: Viliam Kasala > Assignee: Brett Meyer > > Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name

by Viliam Kasala (JIRA)

Viliam Kasala created ARTIF-752: ----------------------------------- Summary: Change of the artificer datasource configuration does not change datasource name Key: ARTIF-752 URL: https://issues.jboss.org/browse/ARTIF-752 Project: Artificer Issue Type: Bug Affects Versions: 1.0.0.Final Reporter: Viliam Kasala Assignee: Brett Meyer Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-645: ----------------------------- Fix Version/s: 2.2.0 (was: 2.1.0.Final) > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-636) Enable integration tests to run on EAP and/or Wildfly

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-636?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-636: ----------------------------- Fix Version/s: 2.2.0 (was: 2.1.0.Final) > Enable integration tests to run on EAP and/or Wildfly > ----------------------------------------------------- > > Key: RTGOV-636 > URL: https://issues.jboss.org/browse/RTGOV-636 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > Currently integration tests only run against a pre-downloaded EAP. Now that Wildfly is supported, enable integration tests to be run against it, and download Wildfly if not available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-663) Nested SwitchYard service calls are not logged correctly

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-663?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-663. ------------------------------ Resolution: Done Thanks for the contribution. > 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.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-663) Nested SwitchYard service calls are not logged correctly

by Sascha Dirbach (JIRA)

[ https://issues.jboss.org/browse/RTGOV-663?page=com.atlassian.jira.plugin.... ] Sascha Dirbach updated RTGOV-663: --------------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/309 > 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.3.15#6346)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2015