April 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-657) NPE in Situations page when filtering by Severity

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-657?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-657: ---------------------------------- Thanks for the additional info - I'll let you know. > NPE in Situations page when filtering by Severity > ------------------------------------------------- > > Key: RTGOV-657 > URL: https://issues.jboss.org/browse/RTGOV-657 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Werner Müller > Assignee: Gary Brown > > When selecting any value but 'Any' in the Severity filter DD list, a NPE is thrown. No situations are displayed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-657) NPE in Situations page when filtering by Severity

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-657?page=com.atlassian.jira.plugin.... ] Werner Müller commented on RTGOV-657: ------------------------------------- Hi Gary, I'm quite busy today - so just a short info: It is related to the JPA store (tested with H2 and DB2). The cause for the issue is that the host variable for the severity value is not set in the query. Please let me know if you still need a stack trace. If so, I can provide it tomorrow. > NPE in Situations page when filtering by Severity > ------------------------------------------------- > > Key: RTGOV-657 > URL: https://issues.jboss.org/browse/RTGOV-657 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Werner Müller > Assignee: Gary Brown > > When selecting any value but 'Any' in the Severity filter DD list, a NPE is thrown. No situations are displayed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-657) NPE in Situations page when filtering by Severity

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-657?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-657: ---------------------------------- Hi Werner - Have tried to reproduce this without success - do you have any additional diagnostics, stack trace, etc that may help to narrow down the issue. > NPE in Situations page when filtering by Severity > ------------------------------------------------- > > Key: RTGOV-657 > URL: https://issues.jboss.org/browse/RTGOV-657 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Werner Müller > Assignee: Gary Brown > > When selecting any value but 'Any' in the Severity filter DD list, a NPE is thrown. No situations are displayed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-660) Elasticsearch cluster support

by Viliam Repan (JIRA)

Viliam Repan created RTGOV-660: ---------------------------------- Summary: Elasticsearch cluster support Key: RTGOV-660 URL: https://issues.jboss.org/browse/RTGOV-660 Project: RTGov (Run Time Governance) Issue Type: Bug Components: Activity Server Affects Versions: 2.0.0.Final Reporter: Viliam Repan Assignee: Gary Brown It's not possible to configure rtgov server to create elasticsearch node which should joing existing cluster. * it's not possible to configure node through xml (in standalone-full.xml) - properties are ignored or something as well as through {{-Delasticsearch.config}} property file - can't configure more hosts for unicast {{discovery.zen.ping.unicast.hosts}} with comma separated hosts doesn't work * http servlet for kibana doesn't take multiple nodes into account - you can just set one value to {{Elasticsearch.server}} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-659) Property cluster.name doesn't work

by Viliam Repan (JIRA)

[ https://issues.jboss.org/browse/RTGOV-659?page=com.atlassian.jira.plugin.... ] Viliam Repan updated RTGOV-659: ------------------------------- Issue Type: Bug (was: Feature Request) > Property cluster.name doesn't work > ---------------------------------- > > Key: RTGOV-659 > URL: https://issues.jboss.org/browse/RTGOV-659 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Activity Server > Affects Versions: 2.0.0.Final > Environment: jboss eap 6.3, elasticsearch 1.3.9 > Reporter: Viliam Repan > Assignee: Gary Brown > > When I put: > {code:xml} > <oc:property name="cluster.name" value="whatever"/> > {code} > to jboss standalone-full.xml it's not taken into account, elasticsearch node is still searching for cluster "elasticsearch". It can be changed only through {{-Delasticsearch.config}} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-659) Property cluster.name doesn't work

by Viliam Repan (JIRA)

Viliam Repan created RTGOV-659: ---------------------------------- Summary: Property cluster.name doesn't work Key: RTGOV-659 URL: https://issues.jboss.org/browse/RTGOV-659 Project: RTGov (Run Time Governance) Issue Type: Feature Request Components: Activity Server Affects Versions: 2.0.0.Final Environment: jboss eap 6.3, elasticsearch 1.3.9 Reporter: Viliam Repan Assignee: Gary Brown When I put: {code:xml} <oc:property name="cluster.name" value="whatever"/> {code} to jboss standalone-full.xml it's not taken into account, elasticsearch node is still searching for cluster "elasticsearch". It can be changed only through {{-Delasticsearch.config}} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-658) Columns too short in RTGov DB

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-658?page=com.atlassian.jira.plugin.... ] Werner Müller closed RTGOV-658. ------------------------------- Ok, I created https://access.redhat.com/support/cases/#/case/01436183 for that. > Columns too short in RTGov DB > ----------------------------- > > Key: RTGOV-658 > URL: https://issues.jboss.org/browse/RTGOV-658 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Werner Müller > Assignee: Gary Brown > > Last autumn, we reported two columns being too short in the RTGov DB: > - RTGOV_ACTIVITITY_PROPERTIES.VALUE, and > - RTGOV_SITUATION_PROPERTIES.VALUE. > Now I discovered two other columns that are too short in the DB2 variant only: > - RTGOV_ACTIVITIES.CONTENT, and > - RTGOV_SITUATIONS.DESCRIPTION. > For DB2, they are defined as CLOB(10240), which is far too short for some message's content. In all other DB variants, they are defined with the maximum value for a CLOB. Please change them accordingly in the DB2 variant. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-658) Columns too short in RTGov DB

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-658?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-658. ------------------------------ Resolution: Rejected Hi Werner, This will need to be reported as a support case on the product, as that is where the db schemas are managed for the supported dbs. > Columns too short in RTGov DB > ----------------------------- > > Key: RTGOV-658 > URL: https://issues.jboss.org/browse/RTGOV-658 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Werner Müller > Assignee: Gary Brown > > Last autumn, we reported two columns being too short in the RTGov DB: > - RTGOV_ACTIVITITY_PROPERTIES.VALUE, and > - RTGOV_SITUATION_PROPERTIES.VALUE. > Now I discovered two other columns that are too short in the DB2 variant only: > - RTGOV_ACTIVITIES.CONTENT, and > - RTGOV_SITUATIONS.DESCRIPTION. > For DB2, they are defined as CLOB(10240), which is far too short for some message's content. In all other DB variants, they are defined with the maximum value for a CLOB. Please change them accordingly in the DB2 variant. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-658) Columns too short in RTGov DB

by Werner Müller (JIRA)

Werner Müller created RTGOV-658: ----------------------------------- Summary: Columns too short in RTGov DB Key: RTGOV-658 URL: https://issues.jboss.org/browse/RTGOV-658 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Werner Müller Assignee: Gary Brown Last autumn, we reported two columns being too short in the RTGov DB: - RTGOV_ACTIVITITY_PROPERTIES.VALUE, and - RTGOV_SITUATION_PROPERTIES.VALUE. Now I discovered two other columns that are too short in the DB2 variant only: - RTGOV_ACTIVITIES.CONTENT, and - RTGOV_SITUATIONS.DESCRIPTION. For DB2, they are defined as CLOB(10240), which is far too short for some message's content. In all other DB variants, they are defined with the maximum value for a CLOB. Please change them accordingly in the DB2 variant. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-657) NPE in Situations page when filtering by Severity

by Werner Müller (JIRA)

Werner Müller created RTGOV-657: ----------------------------------- Summary: NPE in Situations page when filtering by Severity Key: RTGOV-657 URL: https://issues.jboss.org/browse/RTGOV-657 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Werner Müller Assignee: Gary Brown When selecting any value but 'Any' in the Severity filter DD list, a NPE is thrown. No situations are displayed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 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 2015