April 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Werner Müller edited comment on RTGOV-650 at 4/16/15 7:56 AM: -------------------------------------------------------------- Original comment deleted. This was a relict from an incorrect setup. Sorry for that. was (Author: woern): Trying to resubmit a situation. In the URL list is an URL that points to a running SY app. This app however is not an intended resubmit target. It has an SCA Binding, but not for the resubmit target service. (In fact, it has a service with the same local name but in a different namespace.) When HttpInvoker#invoke(...) tries that URL from the list, it gets a response code 404, not an IOException. There is no logic that handles code 404, so the variable 'reply' is returned as null. In SwitchYardResubmitActionProvider#resubmit(...), the first statement after invoker.invoke(rm) is reply.isFault(). This now throws a NPE which is not handled as an invocation error, continuing to work on the list of URLs. Instead, the NPE is wrongly treated as an Exception response. > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-649) Status handling for Situations

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ] Werner Müller commented on RTGOV-649: ------------------------------------- I'm using the JPA store with h2. > Status handling for Situations > ------------------------------ > > Key: RTGOV-649 > URL: https://issues.jboss.org/browse/RTGOV-649 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed: > - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED: > Either remove other values, or provide means to configure the values. > - The default entry for the Status filter on the Situations page shall be (the new value) OPEN: > This includes all Status values other than RESOLVED. > > - A Situation's Status should be changed only programmatically (see below): > Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration. > > - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'. > (This is to be consistent with the resubmit behaviour as defined below.) > - The initial state of a (root) Situation is UNRESOLVED. > When a Situation is resubmitted: > (1) 'assignedTo' is set to the current user (overriding the current value) > (2a) If no failure is encountered (no child situation is created), > the Status is changed to RESOLVED. > (2b) If a failure is encountered (and a child situation is created), > the Status is changed to IN_PROGRESS. > - A Situation in Status RESOLVED must not be resubmitted anymore: > (1) The Resubmit button on the "Message" tab is disabled. > (2) The Situation is excluded from a bulk resubmit. > > As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-649) Status handling for Situations

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-649: ---------------------------------- Sorry that you've experienced problems - I had not seen this behaviour during my testing - but will see if I can reproduce. Were you using the JPA or Elasticsearch Activity/Situation stores? > Status handling for Situations > ------------------------------ > > Key: RTGOV-649 > URL: https://issues.jboss.org/browse/RTGOV-649 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed: > - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED: > Either remove other values, or provide means to configure the values. > - The default entry for the Status filter on the Situations page shall be (the new value) OPEN: > This includes all Status values other than RESOLVED. > > - A Situation's Status should be changed only programmatically (see below): > Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration. > > - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'. > (This is to be consistent with the resubmit behaviour as defined below.) > - The initial state of a (root) Situation is UNRESOLVED. > When a Situation is resubmitted: > (1) 'assignedTo' is set to the current user (overriding the current value) > (2a) If no failure is encountered (no child situation is created), > the Status is changed to RESOLVED. > (2b) If a failure is encountered (and a child situation is created), > the Status is changed to IN_PROGRESS. > - A Situation in Status RESOLVED must not be resubmitted anymore: > (1) The Resubmit button on the "Message" tab is disabled. > (2) The Situation is excluded from a bulk resubmit. > > As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-655) Situations page only partially refreshed

by Werner Müller (JIRA)

Werner Müller created RTGOV-655: ----------------------------------- Summary: Situations page only partially refreshed Key: RTGOV-655 URL: https://issues.jboss.org/browse/RTGOV-655 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Werner Müller Assignee: Gary Brown Priority: Minor After a bulk delete, the UI is not fully refreshed: The "Displaying" on the top right as well as the paging buttons stay as they are. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-649) Status handling for Situations

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ] Werner Müller reopened RTGOV-649: --------------------------------- A request is sent in that triggers a SchemaValidationException. A Situation is properly crated for that. Without changing the message, it is is resubmitted 3 times, creating the same Exception again and again. With the 3rd resubmit, the original 'root' situation and the 1st resubmit go to RESOLVED. The 2nd and 3rd resubmit stay IN_PROGRESS. This continues with each resubmit, so that only the last resubmit and the one before are IN_PROGRESS. > Status handling for Situations > ------------------------------ > > Key: RTGOV-649 > URL: https://issues.jboss.org/browse/RTGOV-649 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed: > - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED: > Either remove other values, or provide means to configure the values. > - The default entry for the Status filter on the Situations page shall be (the new value) OPEN: > This includes all Status values other than RESOLVED. > > - A Situation's Status should be changed only programmatically (see below): > Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration. > > - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'. > (This is to be consistent with the resubmit behaviour as defined below.) > - The initial state of a (root) Situation is UNRESOLVED. > When a Situation is resubmitted: > (1) 'assignedTo' is set to the current user (overriding the current value) > (2a) If no failure is encountered (no child situation is created), > the Status is changed to RESOLVED. > (2b) If a failure is encountered (and a child situation is created), > the Status is changed to IN_PROGRESS. > - A Situation in Status RESOLVED must not be resubmitted anymore: > (1) The Resubmit button on the "Message" tab is disabled. > (2) The Situation is excluded from a bulk resubmit. > > As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Werner Müller reopened RTGOV-650: --------------------------------- Trying to resubmit a situation. In the URL list is an URL that points to a running SY app. This app however is not an intended resubmit target. It has an SCA Binding, but not for the resubmit target service. (In fact, it has a service with the same local name but in a different namespace.) When HttpInvoker#invoke(...) tries that URL from the list, it gets a response code 404, not an IOException. There is no logic that handles code 404, so the variable 'reply' is returned as null. In SwitchYardResubmitActionProvider#resubmit(...), the first statement after invoker.invoke(rm) is reply.isFault(). This now throws a NPE which is not handled as an invocation error, continuing to work on the list of URLs. Instead, the NPE is wrongly treated as an Exception response. > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-653) Persistent filter criteria on Situations page

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-653?page=com.atlassian.jira.plugin.... ] Werner Müller reopened RTGOV-653: --------------------------------- The filter criteria are reset with a browser refresh (on the Situations page as well as on any other page). > Persistent filter criteria on Situations page > --------------------------------------------- > > Key: RTGOV-653 > URL: https://issues.jboss.org/browse/RTGOV-653 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The filter criteria on the "Situations" page should be preserved during the session. > Currently they are cleared when you navigate away from that page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-652) Sortable columns on Resubmit Failures tab

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-652?page=com.atlassian.jira.plugin.... ] Werner Müller closed RTGOV-652. ------------------------------- > Sortable columns on Resubmit Failures tab > ----------------------------------------- > > Key: RTGOV-652 > URL: https://issues.jboss.org/browse/RTGOV-652 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The columns on the "Resubmit Failures" tab should be sortable, as they are on the "Situations" page. > The default sort order should be the same as the default sort order on the "Situations" page (currently descending by Timestamp). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-651) Add a Refresh button to Resubmit Failures tab

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-651?page=com.atlassian.jira.plugin.... ] Werner Müller closed RTGOV-651. ------------------------------- > Add a Refresh button to Resubmit Failures tab > --------------------------------------------- > > Key: RTGOV-651 > URL: https://issues.jboss.org/browse/RTGOV-651 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Beta2 > > > A Refresh button is missing on the "Resubmit Failures" tab, as it is available on the "Situations" page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-654) RT-Gov Analytics not accessible on https due to hardcoded protocol for ElasticSearch URL

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-654?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-654. ------------------------------ Fix Version/s: 2.1.0.Beta2 Resolution: Done Thanks for identifying the solution Martin. > RT-Gov Analytics not accessible on https due to hardcoded protocol for ElasticSearch URL > ---------------------------------------------------------------------------------------- > > Key: RTGOV-654 > URL: https://issues.jboss.org/browse/RTGOV-654 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Affects Versions: 2.0.0.Final > Environment: RT-Gov 2.0.0 on FSW 6.0.0 > Reporter: Martin Weiler > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Access via http is working fine (http://<host>:<port>/rtgov-ui/analytics.html#/dashboard) but with https (https://<host>:<port>/rtgov-ui/analytics.html#/dashboard) we run into the following error: > {noformat} > Error Could not reach http://<host>:<port>/rtgov-ui/elasticsearch/_nodes. If you are using a proxy, ensure it is configured correctly > {noformat} > It seems that it is internally redirecting https request to http protocol with https port. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2015