June 2014 - overlord-issues - Jboss List Archives

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

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-423?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated RTGOV-423: --------------------------------------- Forum Reference: https://community.jboss.org/message/874824#874824 > 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 > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Kevin Conner > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

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

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/RTGOV-423?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato updated RTGOV-423: --------------------------------- > 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 > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Kevin Conner > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-394) Support domain mode in EAP

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/SRAMP-394?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato updated SRAMP-394: --------------------------------- > Support domain mode in EAP > -------------------------- > > Key: SRAMP-394 > URL: https://issues.jboss.org/browse/SRAMP-394 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Kevin Conner > > Support domain mode deployment of SRAMP and Overlord Commons. This will involve deploying the sramp etc wars as modules, and obtaining the properties from the domain.xml file (?). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-473) Investigate moving .cfg fuse property file info into standard rtgov properties

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-473?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-473. ------------------------------ Resolution: Done > Investigate moving .cfg fuse property file info into standard rtgov properties > ------------------------------------------------------------------------------ > > Key: RTGOV-473 > URL: https://issues.jboss.org/browse/RTGOV-473 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > To avoid additional files to configure, if no benefit, then add the info into the standard property file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-473) Investigate moving .cfg fuse property file info into standard rtgov properties

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-473?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-473: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/125 > Investigate moving .cfg fuse property file info into standard rtgov properties > ------------------------------------------------------------------------------ > > Key: RTGOV-473 > URL: https://issues.jboss.org/browse/RTGOV-473 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > To avoid additional files to configure, if no benefit, then add the info into the standard property file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-457) Situation json now includes 'properties' and 'situationProperties'

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-457?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-457: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/124 > Situation json now includes 'properties' and 'situationProperties' > ------------------------------------------------------------------ > > Key: RTGOV-457 > URL: https://issues.jboss.org/browse/RTGOV-457 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > In the recent move from JPA to Hibernate ORM it was found that queries could not work on properties, as 'properties' is a hibernate keyword - so the situationProperties property was added and the old properties getter/setter deprecated, to maintain programmatic backward compatibility. The db schema is ok as the column name is the same. > Moving forward it is probably better that the json reflects the object properties, so should use 'situationProperties' - so need to mark 'properties' as transient so not converted to json. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-457) Situation json now includes 'properties' and 'situationProperties'

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-457?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-457. ------------------------------ Resolution: Done > Situation json now includes 'properties' and 'situationProperties' > ------------------------------------------------------------------ > > Key: RTGOV-457 > URL: https://issues.jboss.org/browse/RTGOV-457 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > In the recent move from JPA to Hibernate ORM it was found that queries could not work on properties, as 'properties' is a hibernate keyword - so the situationProperties property was added and the old properties getter/setter deprecated, to maintain programmatic backward compatibility. The db schema is ok as the column name is the same. > Moving forward it is probably better that the json reflects the object properties, so should use 'situationProperties' - so need to mark 'properties' as transient so not converted to json. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

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

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-329?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-329: ---------------------------------- Can you be more specific about (3)? What problem do you see potentially occuring? > 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 > Security Level: Public(Everyone can see) > Components: Activity Collector > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > Fix For: 2.1.0.Final > > Attachments: Performance.java > > > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

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

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-329?page=com.atlassian.jira.plugin.... ] Gary Brown edited comment on RTGOV-329 at 6/19/14 4:05 AM: ----------------------------------------------------------- (2) "There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess" True, but they are no important pieces of information - so if they are slightly inaccurate because of concurrent update, it is not a significant issue - compared to the performance impact of synchronization on every failure report, on the off chance a concurrent update is happening. was (Author: objectiser): (2) "There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess" True, but they are no important pieces of information - so if they slightly inaccurate because of concurrent update, it is no a significant issue - compared to the performance impact of synchronization on every failure report, just in case. > 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 > Security Level: Public(Everyone can see) > Components: Activity Collector > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > Fix For: 2.1.0.Final > > Attachments: Performance.java > > > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

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

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-329?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-329: ---------------------------------- (2) "There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess" True, but they are no important pieces of information - so if they slightly inaccurate because of concurrent update, it is no a significant issue - compared to the performance impact of synchronization on every failure report, just in case. > 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 > Security Level: Public(Everyone can see) > Components: Activity Collector > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > Fix For: 2.1.0.Final > > Attachments: Performance.java > > > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014