January 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-332) Record message resubmission details against situation

by Gary Brown (JIRA)

Gary Brown created RTGOV-332: -------------------------------- Summary: Record message resubmission details against situation Key: RTGOV-332 URL: https://issues.jboss.org/browse/RTGOV-332 Project: RTGov (Run Time Governance) Issue Type: Feature Request Components: User Interface Reporter: Gary Brown Assignee: Gary Brown When message is resubmitted, record the date/time, who resubmitted it, and the status of the resubmission (success/fail) in the properties of the situation, and saved back to the db. If these properties exist on a situation - when the situation details are displayed, they should be displayed on the Message tab, so that user avoids resubmitting again if previously successful. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-330) Allow situations to be allocated/assigned to individual

by Gary Brown (JIRA)

Gary Brown created RTGOV-330: -------------------------------- Summary: Allow situations to be allocated/assigned to individual Key: RTGOV-330 URL: https://issues.jboss.org/browse/RTGOV-330 Project: RTGov (Run Time Governance) Issue Type: Feature Request Components: User Interface Reporter: Gary Brown Assignee: Gary Brown Allow a situation to be assigned to a user. To avoid maintaining list of users (for now), we will use a ‘take’ approach, so the currently logged in user can ‘take’ responsibility for a situation (if not already associated with another user). This will result in their username being associated with a property on the situation, and the situation being recorded back to the db. Once the user is responsible for the situation, they should have the ability to set its status. Current status values will be Unresolved (default value upon a situation being assigned) and Resolved. To avoid the scenario where a situation remains associated with a user while no action is being taken, it should be possible for a more privileged user to be able to 'take' it from another assigned user. This may only happen if this user has a 'management' role - to be discussed further. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-244) Kie and Teiid expanders not working from the S-RAMP-UI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-244?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-244: ----------------------------------------------- kconner(a)redhat.com changed the Status of [bug 1015251|https://bugzilla.redhat.com/show_bug.cgi?id=1015251] from MODIFIED to ON_QA > Kie and Teiid expanders not working from the S-RAMP-UI > ------------------------------------------------------ > > Key: SRAMP-244 > URL: https://issues.jboss.org/browse/SRAMP-244 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > These integrations are missing dependencies that need to be added so they can discovered by the servicelocator. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-253) Add support for Teiid artifacts in s-ramp

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-253?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-253: ----------------------------------------------- kconner(a)redhat.com changed the Status of [bug 1022586|https://bugzilla.redhat.com/show_bug.cgi?id=1022586] from MODIFIED to ON_QA > Add support for Teiid artifacts in s-ramp > ----------------------------------------- > > Key: SRAMP-253 > URL: https://issues.jboss.org/browse/SRAMP-253 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > Add support for Teiid artifacts as first-class supported artifacts in s-ramp. This should be done by implementing a deriver for the teiid XML file as well as an expander for Teiid archives (VDB). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-329) Consider refactoring/cleanup of ActivtyServerLogger

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-329?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-329: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1056449 > Consider refactoring/cleanup of ActivtyServerLogger > --------------------------------------------------- > > Key: RTGOV-329 > URL: https://issues.jboss.org/browse/RTGOV-329 > Project: RTGov (Run Time Governance) > Issue Type: Quality Risk > Components: Activity Collector > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > > 1) I consider the code to be overcomplicated - are we really getting any performance boost with reusing the ArrayList of events? I found on the web that clear() might be even slower than new allocation > 2) There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess > 3) I am not sure if it is wise to mix synchronization on Java level - _timer in BatchedActivityUnitLogger - and Java EE level - method synchornization on @Singleton -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-328) Activity Server should support async processing of submitted events

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-328?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-328: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1056447 > Activity Server should support async processing of submitted events > ------------------------------------------------------------------- > > Key: RTGOV-328 > URL: https://issues.jboss.org/browse/RTGOV-328 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: Activity Server > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > > Activity Collector does not care about return value from activity server invocation. Thus the api should provide a method that will allow submit activities in one-way fashion. The REST invocation will return immediately and the activities will be stored in storage asynchronously in another 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-326) Provide more options for handling events when RTGov server is unavailable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-326?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-326: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1056444 > Provide more options for handling events when RTGov server is unavailable > ------------------------------------------------------------------------- > > Key: RTGOV-326 > URL: https://issues.jboss.org/browse/RTGOV-326 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: Activity Collector > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > > Provider a configurable functionality that will allow to handle situations when RTGov server is not available. There should be at least three different options how to handle such situation > 1) drop - as is now > 2) temporary storage - in local file or memory > 3) block receiving further activities -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-327) ActivityServerLogger should support retry when submits to activity server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-327?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-327: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1056446 > ActivityServerLogger should support retry when submits to activity server > ------------------------------------------------------------------------- > > Key: RTGOV-327 > URL: https://issues.jboss.org/browse/RTGOV-327 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Activity Collector > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > > Whenever there is a temporary network issue the activity batch is dropped. There should be a retry mechanism implemented to overcome minor infrastructure issues. > In this case the activity server needs to be guarded against double submit. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-329) Consider refactoring/cleanup of ActivtyServerLogger

by Jiri Pechanec (JIRA)

Jiri Pechanec created RTGOV-329: ----------------------------------- Summary: Consider refactoring/cleanup of ActivtyServerLogger Key: RTGOV-329 URL: https://issues.jboss.org/browse/RTGOV-329 Project: RTGov (Run Time Governance) Issue Type: Quality Risk Components: Activity Collector Affects Versions: 1.0.0.Final Reporter: Jiri Pechanec Assignee: Gary Brown 1) I consider the code to be overcomplicated - are we really getting any performance boost with reusing the ArrayList of events? I found on the web that clear() might be even slower than new allocation 2) There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess 3) I am not sure if it is wise to mix synchronization on Java level - _timer in BatchedActivityUnitLogger - and Java EE level - method synchornization on @Singleton -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-328) Activity Server should support async processing of submitted events

by Jiri Pechanec (JIRA)

Jiri Pechanec created RTGOV-328: ----------------------------------- Summary: Activity Server should support async processing of submitted events Key: RTGOV-328 URL: https://issues.jboss.org/browse/RTGOV-328 Project: RTGov (Run Time Governance) Issue Type: Feature Request Components: Activity Server Affects Versions: 1.0.0.Final Reporter: Jiri Pechanec Assignee: Gary Brown Activity Collector does not care about return value from activity server invocation. Thus the api should provide a method that will allow submit activities in one-way fashion. The REST invocation will return immediately and the activities will be stored in storage asynchronously in another 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, 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 January 2014