April 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-437) Deprecate 'ignored subjects' support, and remove from Karaf distribution

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-437?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-437: ----------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Deprecate 'ignored subjects' support, and remove from Karaf distribution > ------------------------------------------------------------------------ > > Key: RTGOV-437 > URL: https://issues.jboss.org/browse/RTGOV-437 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Remove support for 'ignored subjects' in Karaf distribution, and deprecate in the EAP 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-380) Support RTGov UI in Karaf

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-380?focusedWorklogId=12431106&page=... ] Gary Brown logged work on RTGOV-380: ------------------------------------ Author: Gary Brown Created on: 25/Apr/14 5:17 AM Start Date: 25/Apr/14 5:17 AM Worklog Time Spent: 4 days Issue Time Tracking ------------------- Remaining Estimate: 1 week, 1 day (was: 2 weeks) Time Spent: 4 days Worklog Id: (was: 12431106) > Support RTGov UI in Karaf > ------------------------- > > Key: RTGOV-380 > URL: https://issues.jboss.org/browse/RTGOV-380 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Original Estimate: 2 weeks > Time Spent: 4 days > Remaining Estimate: 1 week, 1 day > > Enable the new RTGov UI war to be deployed in Karaf. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-380) Support RTGov UI in Karaf

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-380?page=com.atlassian.jira.plugin.... ] Work on RTGOV-380 started by Gary Brown. > Support RTGov UI in Karaf > ------------------------- > > Key: RTGOV-380 > URL: https://issues.jboss.org/browse/RTGOV-380 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Enable the new RTGov UI war to be deployed in Karaf. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-309) Use switchyard higher level security API to get principal

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-309?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-309: ----------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Use switchyard higher level security API to get principal > --------------------------------------------------------- > > Key: RTGOV-309 > URL: https://issues.jboss.org/browse/RTGOV-309 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Use the SecurityContextManager to make sure we process an un-sealed security context. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-423) Support domain mode in EAP

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-423?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-423: ----------------------------- Original Estimate: 3 days Remaining Estimate: 3 days > Support domain mode in EAP > -------------------------- > > Key: RTGOV-423 > URL: https://issues.jboss.org/browse/RTGOV-423 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Support domain mode deployment of RTGov. This will involve deploying the rtgov war as a module, and obtaining the properties the xml file (?). -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-425) Persistent retry capability

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-425?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-425: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > Persistent retry capability > --------------------------- > > Key: RTGOV-425 > URL: https://issues.jboss.org/browse/RTGOV-425 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > In various parts of the rtgov architecture, information is reported to a remote service, and if that service is not available, the information is currently discarded. > This task is to provide an infrastructure capability (as part of overlord-commons) that can store information that cannot currently be reported to the remote service, and have it replayed once the remote service becomes available. > Some of the characteristics required are: > * When the primary component (reporting the information to the remote sevice) first starts up, it should register itself with the "persistent retry" capability, providing a handler that can be used to retry sending information to the remote service. > * When a failure occurs, attempting to send information to the remote service, the primary component will invoke the "persistent retry" capability to handle the information. > * The persistent retry capability will store information in a persistent form (initially file system, but other dbs etc should be supported in the future). > * When registering with the persistent retry capability, the primary component should be able to register a retry strategy. One implementation of such a strategy could be: > ** Periodically attempt to send retry information to its remote service via the registered handler. > ** If unsuccessful, then back off and wait for the next cycle. > ** If successful, then schedule another task to send the next information for that service until either a failure occurs, in which case wait for the next retry cycle, or no further information exists. A thread pool should be used across all retry handlers. > Investigate whether there are existing open source solutions for this problem. If not, then as part of building the solution, need to ensure that it is as efficient as possible in a multi-thread situation - so (for example) when looking at a persistent file system store, need to ensure that a suitable mechanism is used that caters for the multi-threaded updates (i.e. writing new records and clearing successfully retried records). Possibly a file based db may be one option to investigate. > JUnit tests need to be written that test the solution in a multi-threaded scenario. Profiling should be performed to understand the impact of this component on normal operations, and also when retries are being performed concurrently with new information being reported. > Places where this mechanism may be used: > 1) Activity collector > 2) ElasticSearch KeyValueStore -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-295) Support deployment in EAP without switchyard

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-295?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-295: ----------------------------- Original Estimate: 1 day Remaining Estimate: 1 day Priority: Minor (was: Major) > Support deployment in EAP without switchyard > -------------------------------------------- > > Key: RTGOV-295 > URL: https://issues.jboss.org/browse/RTGOV-295 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Minor > Fix For: 2.0.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-384) Remove duplication of content EPN and ACS

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-384?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-384: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > Remove duplication of content EPN and ACS > ----------------------------------------- > > Key: RTGOV-384 > URL: https://issues.jboss.org/browse/RTGOV-384 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Currently the content/epn and acs deployments are duplicated for OSGi and JEE. Need to move the EPN and ACS resources into their own modules and just have the OSGi and JEE variations as packaging. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-336) Combine activities recorded across multiple threads

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-336?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-336: ----------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > Combine activities recorded across multiple threads > --------------------------------------------------- > > Key: RTGOV-336 > URL: https://issues.jboss.org/browse/RTGOV-336 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Minor > Fix For: 2.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > When capturing activity events via proxies in JBoss Fuse, found that when a service returned an exception, it was handled in a separate thread. > This resulted in two separate activity units, one for the activities up until the exception, and the other for the activities following the exception. > This will cause issues with correlation currently, where request/response pairs are expected to be in the same activity unit. > Two possible solutions: > (1) work on the correlation of requests/responses across activity units - which will be useful in a wider range of cases. > (2) enable activities across multiple threads to be combined - i.e. if a subsequent thread is new, allow its relationship with a previous activity event (e.g. the request) to link it to the same activity unit. Not sure of the implications on the API for this. > This work is related to RTGOV-325. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-238) Create EntityManager per request for JPAEventProcessor

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-238?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-238: ----------------------------- Priority: Minor (was: Major) > Create EntityManager per request for JPAEventProcessor > ------------------------------------------------------ > > Key: RTGOV-238 > URL: https://issues.jboss.org/browse/RTGOV-238 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Minor > Fix For: 2.0.0.Final > > > Need to profile creation of entity manager - need to create per request, although if big overhead need to find another way to ensure single entity manager used per 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

10 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 April 2014