June 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-224) Activity collector using switchyard thread to report events when max size reached

by Gary Brown (JIRA)

Gary Brown created RTGOV-224: -------------------------------- Summary: Activity collector using switchyard thread to report events when max size reached Key: RTGOV-224 URL: https://issues.jboss.org/browse/RTGOV-224 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.Final Although activity units are reported in a separate thread, based on a periodic timer, if the max number of activity units is reached before the timer is triggered, then they are reported in the same thread as the caller (i.e. switchyard app). So need to ensure these are also handled in a separate thread. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-223) H2 exception when concurrent access

by Gary Brown (JIRA)

Gary Brown created RTGOV-223: -------------------------------- Summary: H2 exception when concurrent access Key: RTGOV-223 URL: https://issues.jboss.org/browse/RTGOV-223 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.Final Need to add ';MVCC=true' to URL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-222) Change license to Apache

by Gary Brown (JIRA)

Gary Brown created RTGOV-222: -------------------------------- Summary: Change license to Apache Key: RTGOV-222 URL: https://issues.jboss.org/browse/RTGOV-222 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.Final Update headers and include the Apache license in each repo and distribution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-162) Reporting capability against historic activity information with SLA report as example

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-162?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-162: ---------------------------------- Changed approach to use activity information directly, instead of situations, as situations represent an alert at a particular time, rather than over a time period. Also built a deployable report capability, to enable reports to be easily added and accessible via a REST service. > Reporting capability against historic activity information with SLA report as example > ------------------------------------------------------------------------------------- > > Key: RTGOV-162 > URL: https://issues.jboss.org/browse/RTGOV-162 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.Final > > > Need to determine what information should be stored in the Situation to enable a report to be compiled based on service performance and availability. > The criteria for what constitutes a violation of a particular customer's SLA needs to be defined. For example, the SLAs may only apply within particular day/time periods - which will also need to take into account timezones. > Need to see whether this per customer information can be stored in SRAMP repo, and also reported via Polymita, as requires further analysis of the underlying information - and possibly needs to be presented in a tabular form. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-162) SLA report based on historic analysis of Situations

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-162?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-162. ------------------------------ Resolution: Done > SLA report based on historic analysis of Situations > --------------------------------------------------- > > Key: RTGOV-162 > URL: https://issues.jboss.org/browse/RTGOV-162 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.Final > > > Need to determine what information should be stored in the Situation to enable a report to be compiled based on service performance and availability. > The criteria for what constitutes a violation of a particular customer's SLA needs to be defined. For example, the SLAs may only apply within particular day/time periods - which will also need to take into account timezones. > Need to see whether this per customer information can be stored in SRAMP repo, and also reported via Polymita, as requires further analysis of the underlying information - and possibly needs to be presented in a tabular form. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-162) Reporting capability against historic activity information with SLA report as example

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-162?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-162: ----------------------------- Summary: Reporting capability against historic activity information with SLA report as example (was: SLA report based on historic analysis of Situations) > Reporting capability against historic activity information with SLA report as example > ------------------------------------------------------------------------------------- > > Key: RTGOV-162 > URL: https://issues.jboss.org/browse/RTGOV-162 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.Final > > > Need to determine what information should be stored in the Situation to enable a report to be compiled based on service performance and availability. > The criteria for what constitutes a violation of a particular customer's SLA needs to be defined. For example, the SLAs may only apply within particular day/time periods - which will also need to take into account timezones. > Need to see whether this per customer information can be stored in SRAMP repo, and also reported via Polymita, as requires further analysis of the underlying information - and possibly needs to be presented in a tabular form. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-206) POMs should use ModeShape's BOM to correctly bring in all of its dependencies

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-206?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-206: ----------------------------------- Assignee: Eric Wittmann > POMs should use ModeShape's BOM to correctly bring in all of its dependencies > ----------------------------------------------------------------------------- > > Key: SRAMP-206 > URL: https://issues.jboss.org/browse/SRAMP-206 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Randall Hauch > Assignee: Eric Wittmann > > S-RAMP should use ModeShape's BOM (see [here|https://docs.jboss.org/author/display/MODE/Getting+Started#GettingSt...]) to pull in whatever ModeShape dependencies are needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-206) POMs should use ModeShape's BOM to correctly bring in all of its dependencies

by Randall Hauch (JIRA)

[ https://issues.jboss.org/browse/SRAMP-206?page=com.atlassian.jira.plugin.... ] Randall Hauch updated SRAMP-206: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/274 This change slightly simplifies the dependencies but more importantly ensures a consistent set of versions as used by ModeShape. The BOM also excludes whatever transitive dependencies are not needed. > POMs should use ModeShape's BOM to correctly bring in all of its dependencies > ----------------------------------------------------------------------------- > > Key: SRAMP-206 > URL: https://issues.jboss.org/browse/SRAMP-206 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Randall Hauch > > S-RAMP should use ModeShape's BOM (see [here|https://docs.jboss.org/author/display/MODE/Getting+Started#GettingSt...]) to pull in whatever ModeShape dependencies are needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-206) POMs should use ModeShape's BOM to correctly bring in all of its dependencies

by Randall Hauch (JIRA)

[ https://issues.jboss.org/browse/SRAMP-206?page=com.atlassian.jira.plugin.... ] Randall Hauch updated SRAMP-206: -------------------------------- Component/s: Persistence > POMs should use ModeShape's BOM to correctly bring in all of its dependencies > ----------------------------------------------------------------------------- > > Key: SRAMP-206 > URL: https://issues.jboss.org/browse/SRAMP-206 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Randall Hauch > > S-RAMP should use ModeShape's BOM (see [here|https://docs.jboss.org/author/display/MODE/Getting+Started#GettingSt...]) to pull in whatever ModeShape dependencies are needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-206) POMs should use ModeShape's BOM to correctly bring in all of its dependencies

by Randall Hauch (JIRA)

Randall Hauch created SRAMP-206: ----------------------------------- Summary: POMs should use ModeShape's BOM to correctly bring in all of its dependencies Key: SRAMP-206 URL: https://issues.jboss.org/browse/SRAMP-206 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Randall Hauch S-RAMP should use ModeShape's BOM (see [here|https://docs.jboss.org/author/display/MODE/Getting+Started#GettingSt...]) to pull in whatever ModeShape dependencies are needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2013