June 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-496) Fabric profile has hardcoded features.xml version

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-496?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-496. ------------------------------ Resolution: Done > Fabric profile has hardcoded features.xml version > ------------------------------------------------- > > Key: RTGOV-496 > URL: https://issues.jboss.org/browse/RTGOV-496 > 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 > > > Need to use filtered resources to configure appropriate version. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-496) Fabric profile has hardcoded features.xml version

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-496?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-496: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/117 > Fabric profile has hardcoded features.xml version > ------------------------------------------------- > > Key: RTGOV-496 > URL: https://issues.jboss.org/browse/RTGOV-496 > 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 > > > Need to use filtered resources to configure appropriate version. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-494) Fix 404 when first visiting rtgov ui in fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-494?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-494: ----------------------------- Fix Version/s: (was: 2.0.0.Final) > Fix 404 when first visiting rtgov ui in fuse > -------------------------------------------- > > Key: RTGOV-494 > URL: https://issues.jboss.org/browse/RTGOV-494 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-494) Fix 404 when first visiting rtgov ui in fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-494?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-494. ------------------------------ Resolution: Rejected Fix is in overlord-commons. > Fix 404 when first visiting rtgov ui in fuse > -------------------------------------------- > > Key: RTGOV-494 > URL: https://issues.jboss.org/browse/RTGOV-494 > 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 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-496) Fabric profile has hardcoded features.xml version

by Gary Brown (JIRA)

Gary Brown created RTGOV-496: -------------------------------- Summary: Fabric profile has hardcoded features.xml version Key: RTGOV-496 URL: https://issues.jboss.org/browse/RTGOV-496 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 Need to use filtered resources to configure appropriate version. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-495) Enable Elasticsearch response size to be configured

by Gary Brown (JIRA)

Gary Brown created RTGOV-495: -------------------------------- Summary: Enable Elasticsearch response size to be configured Key: RTGOV-495 URL: https://issues.jboss.org/browse/RTGOV-495 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 The response size currently defaults to 10, which is not high enough for many queries (especially for activity types). We need to set a reasonable maximum, so will default to a higher value and enable it to be overridden by properties when necessary. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-494) Fix 404 when first visiting rtgov ui in fuse

by Gary Brown (JIRA)

Gary Brown created RTGOV-494: -------------------------------- Summary: Fix 404 when first visiting rtgov ui in fuse Key: RTGOV-494 URL: https://issues.jboss.org/browse/RTGOV-494 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 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-389) Performance issue in s-ramp client when using custom properties in query results

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-389?page=com.atlassian.jira.plugin.... ] Work on SRAMP-389 started by Eric Wittmann. > Performance issue in s-ramp client when using custom properties in query results > -------------------------------------------------------------------------------- > > Key: SRAMP-389 > URL: https://issues.jboss.org/browse/SRAMP-389 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > There is a feature in s-ramp queries where the client can request that each artifact returned by a query also include a specific subset of the artifact's custom properties. This is in addition to the standard set of meta-data that is always returned when a query is performed. > We currently use this feature in the dtgov WorkflowQueryService class to return the 'query' and 'workflow' custom properties (so they can be displayed in the UI list). > Getting these custom properties while processing the result set is very slow (see ArtifactSummary::getCustomPropertyValue). > I haven't actually verified this, but I *believe* the reason this is slow is because a new JAXB context is created for each ArtifactSummary in the query result list. Creating a JAXB context is a heavy weight operation. > If this is truly the cause, we should try to share the JAXB context in some way. We need to determine whether it is thread-safe, in which case we should have a single JAXB context (singleton). If not, we should create it on a ThreadLocal. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-389) Performance issue in s-ramp client when using custom properties in query results

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-389?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-389: ----------------------------------- Assignee: Eric Wittmann (was: David virgil naranjo) > Performance issue in s-ramp client when using custom properties in query results > -------------------------------------------------------------------------------- > > Key: SRAMP-389 > URL: https://issues.jboss.org/browse/SRAMP-389 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > There is a feature in s-ramp queries where the client can request that each artifact returned by a query also include a specific subset of the artifact's custom properties. This is in addition to the standard set of meta-data that is always returned when a query is performed. > We currently use this feature in the dtgov WorkflowQueryService class to return the 'query' and 'workflow' custom properties (so they can be displayed in the UI list). > Getting these custom properties while processing the result set is very slow (see ArtifactSummary::getCustomPropertyValue). > I haven't actually verified this, but I *believe* the reason this is slow is because a new JAXB context is created for each ArtifactSummary in the query result list. Creating a JAXB context is a heavy weight operation. > If this is truly the cause, we should try to share the JAXB context in some way. We need to determine whether it is thread-safe, in which case we should have a single JAXB context (singleton). If not, we should create it on a ThreadLocal. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-437) Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-437?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-437. ------------------------------- > Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1 > ----------------------------------------------------------------------- > > Key: SRAMP-437 > URL: https://issues.jboss.org/browse/SRAMP-437 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > After the first time it works ok. Probably has something to do with the ;jessionid= that is getting dumped onto the end of the URL. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014