From issues at jboss.org Wed Feb 5 06:38:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 5 Feb 2014 06:38:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-347) Refactor services part of UI backend, to support multiple providers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-347: ----------------------------- Component/s: User Interface > Refactor services part of UI backend, to support multiple providers > ------------------------------------------------------------------- > > Key: RTGOV-347 > URL: https://issues.jboss.org/browse/RTGOV-347 > Project: RTGov (Run Time Governance) > Issue Type: Task > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the services information is obtained only from switchyard. Need to provide an abstraction layer that will enable other service container providers to be supported. -- 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 From issues at jboss.org Wed Feb 5 06:38:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 5 Feb 2014 06:38:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-347) Refactor services part of UI backend, to support multiple providers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-347. ------------------------------ Resolution: Done > Refactor services part of UI backend, to support multiple providers > ------------------------------------------------------------------- > > Key: RTGOV-347 > URL: https://issues.jboss.org/browse/RTGOV-347 > Project: RTGov (Run Time Governance) > Issue Type: Task > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the services information is obtained only from switchyard. Need to provide an abstraction layer that will enable other service container providers to be supported. -- 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 From issues at jboss.org Wed Feb 5 06:40:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 5 Feb 2014 06:40:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-348) Move references to service details page In-Reply-To: References: Message-ID: Gary Brown created RTGOV-348: -------------------------------- Summary: Move references to service details page Key: RTGOV-348 URL: https://issues.jboss.org/browse/RTGOV-348 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Currently reference summaries are shown at the same level as service summaries. However the references are scoped by the service in which they are used - so need to move the list onto the service details page, and ensure the list only contains the references (outbound/promoted) that are relevant to the selected service. -- 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 From issues at jboss.org Wed Feb 5 11:20:29 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Wed, 5 Feb 2014 11:20:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-331) Enable user to filter situations based on their resolution status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941595#comment-12941595 ] Michael Clay commented on RTGOV-331: ------------------------------------ hi Gary, could you pls confirm that this task is only about the UI part i.e. the changes necessary for the 'back-end' component (e.g. org.overlord.rtgov.analytics.situation.Situation et.al) will be tracked in another ticket. Regards, Michael > Enable user to filter situations based on their resolution status > ----------------------------------------------------------------- > > Key: RTGOV-331 > URL: https://issues.jboss.org/browse/RTGOV-331 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value). > Update the server side to use the filter value in its evaluation of the list of situations to be returned. -- 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 From issues at jboss.org Wed Feb 5 11:20:29 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Wed, 5 Feb 2014 11:20:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-331) Enable user to filter situations based on their resolution status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941595#comment-12941595 ] Michael Clay edited comment on RTGOV-331 at 2/5/14 11:19 AM: ------------------------------------------------------------- hi Gary, could you pls confirm that this task (and RTGOV-333) is only about the UI part i.e. the changes necessary for the 'back-end' component (e.g. org.overlord.rtgov.analytics.situation.Situation et.al) will be tracked in another ticket. Regards, Michael was (Author: michaelclay): hi Gary, could you pls confirm that this task is only about the UI part i.e. the changes necessary for the 'back-end' component (e.g. org.overlord.rtgov.analytics.situation.Situation et.al) will be tracked in another ticket. Regards, Michael > Enable user to filter situations based on their resolution status > ----------------------------------------------------------------- > > Key: RTGOV-331 > URL: https://issues.jboss.org/browse/RTGOV-331 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value). > Update the server side to use the filter value in its evaluation of the list of situations to be returned. -- 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 From issues at jboss.org Wed Feb 5 11:34:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 5 Feb 2014 11:34:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-331) Enable user to filter situations based on their resolution status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941602#comment-12941602 ] Gary Brown commented on RTGOV-331: ---------------------------------- Hi Michael No it also covers the backend part. If you would prefer, then you could create a separate linked ticket for the backend part. In terms of the changes, all the work (even for the backend) should be carried out in the rtgov-ui repo - so no changes should be made to the org.overlord.rtgov.analytics.situation.Situation class directly - any additional information (e.g. the status) should be stored as a property for now. Thanks. > Enable user to filter situations based on their resolution status > ----------------------------------------------------------------- > > Key: RTGOV-331 > URL: https://issues.jboss.org/browse/RTGOV-331 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value). > Update the server side to use the filter value in its evaluation of the list of situations to be returned. -- 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 From issues at jboss.org Wed Feb 5 11:34:29 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Wed, 5 Feb 2014 11:34:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-333) Enable user to filter situations based on allocation status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clay reassigned RTGOV-333: ---------------------------------- Assignee: Michael Clay (was: Gary Brown) > Enable user to filter situations based on allocation status > ----------------------------------------------------------- > > Key: RTGOV-333 > URL: https://issues.jboss.org/browse/RTGOV-333 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > The list of situations shown on the main page can be filtered using criteria on the left panel. > Add a new criteria to enable the list of situations to be filtered on the allocation status of: All, Assigned to me, Unassigned. > The server side should be updated to implement this new filtering criteria. -- 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 From issues at jboss.org Thu Feb 6 08:54:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 6 Feb 2014 08:54:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-348) Move references to service details page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-348. ------------------------------ Resolution: Done > Move references to service details page > --------------------------------------- > > Key: RTGOV-348 > URL: https://issues.jboss.org/browse/RTGOV-348 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently reference summaries are shown at the same level as service summaries. However the references are scoped by the service in which they are used - so need to move the list onto the service details page, and ensure the list only contains the references (outbound/promoted) that are relevant to the selected service. -- 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 From issues at jboss.org Thu Feb 6 08:54:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 6 Feb 2014 08:54:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-348) Move references to service details page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-348: ----------------------------- Component/s: User Interface > Move references to service details page > --------------------------------------- > > Key: RTGOV-348 > URL: https://issues.jboss.org/browse/RTGOV-348 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently reference summaries are shown at the same level as service summaries. However the references are scoped by the service in which they are used - so need to move the list onto the service details page, and ensure the list only contains the references (outbound/promoted) that are relevant to the selected service. -- 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 From issues at jboss.org Thu Feb 6 08:56:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 6 Feb 2014 08:56:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-349) Integration tests for situations provider and switchyard services provider In-Reply-To: References: Message-ID: Gary Brown created RTGOV-349: -------------------------------- Summary: Integration tests for situations provider and switchyard services provider Key: RTGOV-349 URL: https://issues.jboss.org/browse/RTGOV-349 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Setup an integration test structure, using arquillian, to test the rtgov situations provider and the switchyard services provider. -- 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 From issues at jboss.org Thu Feb 6 10:26:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:26:37 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-242) Change string sync objects to Object In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941918#comment-12941918 ] RH Bugzilla Integration commented on RTGOV-242: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 991388|https://bugzilla.redhat.com/show_bug.cgi?id=991388] from VERIFIED to CLOSED > Change string sync objects to Object > ------------------------------------ > > Key: RTGOV-242 > URL: https://issues.jboss.org/browse/RTGOV-242 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:26:38 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:26:38 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-282) Situation needs to support eager fetch and increased storage for description In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941923#comment-12941923 ] RH Bugzilla Integration commented on RTGOV-282: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1013559|https://bugzilla.redhat.com/show_bug.cgi?id=1013559] from VERIFIED to CLOSED > Situation needs to support eager fetch and increased storage for description > ---------------------------------------------------------------------------- > > Key: RTGOV-282 > URL: https://issues.jboss.org/browse/RTGOV-282 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:26:38 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:26:38 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-110) Derived flag incorrect for extended derived artifacts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMPUI-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941925#comment-12941925 ] RH Bugzilla Integration commented on SRAMPUI-110: ------------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1011397|https://bugzilla.redhat.com/show_bug.cgi?id=1011397] from VERIFIED to CLOSED > Derived flag incorrect for extended derived artifacts > ----------------------------------------------------- > > Key: SRAMPUI-110 > URL: https://issues.jboss.org/browse/SRAMPUI-110 > Project: S-RAMP UI > Issue Type: Bug > Components: View > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > For extended derived artifacts (e.g. SY artifacts such as SwitchYardComponentService) the derived UI flag is not being properly set. So even though these artifacts come back via a search for Derived artifacts, the data in the UI (e.g. the Derived column in the artifact list) is inaccurate. -- 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 From issues at jboss.org Thu Feb 6 10:26:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:26:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-292) Policy sync quickstart fails with clustered cache In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941947#comment-12941947 ] RH Bugzilla Integration commented on RTGOV-292: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1017304|https://bugzilla.redhat.com/show_bug.cgi?id=1017304] from VERIFIED to CLOSED > Policy sync quickstart fails with clustered cache > ------------------------------------------------- > > Key: RTGOV-292 > URL: https://issues.jboss.org/browse/RTGOV-292 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Clustered cache causes the following exception: > Caused by: java.lang.RuntimeException: [Error: cm.lock("Principals", customer): Cannot create a transactional context without a valid Transaction instance.] > [Near : {... String customer=event.properti ....}] > ^ > [Line: 1, Column: 1] > The cache container configuration is: > > > > > > > > and the overlord-rtgov.properties is updated to uncomment the infinispan.container property and point it to "java:jboss/infinispan/container/rtgov" -- 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 From issues at jboss.org Thu Feb 6 10:26:41 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:26:41 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-287) Accessor wait interval needs to be configurable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941949#comment-12941949 ] RH Bugzilla Integration commented on RTGOV-287: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1015363|https://bugzilla.redhat.com/show_bug.cgi?id=1015363] from VERIFIED to CLOSED > Accessor wait interval needs to be configurable > ----------------------------------------------- > > Key: RTGOV-287 > URL: https://issues.jboss.org/browse/RTGOV-287 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:26:42 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:26:42 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-241) Upgrade to drools version 6.0.0.CR1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941958#comment-12941958 ] RH Bugzilla Integration commented on RTGOV-241: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 991096|https://bugzilla.redhat.com/show_bug.cgi?id=991096] from VERIFIED to CLOSED > Upgrade to drools version 6.0.0.CR1 > ----------------------------------- > > Key: RTGOV-241 > URL: https://issues.jboss.org/browse/RTGOV-241 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:26:42 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:26:42 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-324) NPE occurring when rtgov enabled with switchyard cluster demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941962#comment-12941962 ] RH Bugzilla Integration commented on RTGOV-324: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1055420|https://bugzilla.redhat.com/show_bug.cgi?id=1055420] from VERIFIED to CLOSED > NPE occurring when rtgov enabled with switchyard cluster demo > ------------------------------------------------------------- > > Key: RTGOV-324 > URL: https://issues.jboss.org/browse/RTGOV-324 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > An exception is being reported when setting the properties in the CamelCompositeContext. -- 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 From issues at jboss.org Thu Feb 6 10:26:42 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:26:42 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-256) Headers not reported for switchyard events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941963#comment-12941963 ] RH Bugzilla Integration commented on RTGOV-256: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 998850|https://bugzilla.redhat.com/show_bug.cgi?id=998850] from VERIFIED to CLOSED > Headers not reported for switchyard events > ------------------------------------------ > > Key: RTGOV-256 > URL: https://issues.jboss.org/browse/RTGOV-256 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:28:32 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:32 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-223) Jboss dependency should be org.jboss.as.clustering.infinispan In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941984#comment-12941984 ] RH Bugzilla Integration commented on SRAMP-223: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 991132|https://bugzilla.redhat.com/show_bug.cgi?id=991132] from VERIFIED to CLOSED > Jboss dependency should be org.jboss.as.clustering.infinispan > ------------------------------------------------------------- > > Key: SRAMP-223 > URL: https://issues.jboss.org/browse/SRAMP-223 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > The s-ramp-server WAR has a jboss dependency on org.infinispan (which we patch because we *thought* it was missing a dependency). Instead, the dependency from s-ramp-server should be on org.jboss.as.clustering.infinispan (which has all the right dependencies). > I need to update the dependency in s-ramp-server.war *and* remove the patching from the s-ramp installer. -- 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 From issues at jboss.org Thu Feb 6 10:28:32 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:32 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-244) Activity Server allows to run any JPQL query statement over REST API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941986#comment-12941986 ] RH Bugzilla Integration commented on RTGOV-244: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 994880|https://bugzilla.redhat.com/show_bug.cgi?id=994880] from VERIFIED to CLOSED > Activity Server allows to run any JPQL query statement over REST API > -------------------------------------------------------------------- > > Key: RTGOV-244 > URL: https://issues.jboss.org/browse/RTGOV-244 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:28:32 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:32 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-248) One way interactions between services do not identify the 'interface' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941993#comment-12941993 ] RH Bugzilla Integration commented on RTGOV-248: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996010|https://bugzilla.redhat.com/show_bug.cgi?id=996010] from VERIFIED to CLOSED > One way interactions between services do not identify the 'interface' > --------------------------------------------------------------------- > > Key: RTGOV-248 > URL: https://issues.jboss.org/browse/RTGOV-248 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:28:33 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:33 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-250) Validation errors in the S-RAMP demos In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941994#comment-12941994 ] RH Bugzilla Integration commented on SRAMP-250: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1014005|https://bugzilla.redhat.com/show_bug.cgi?id=1014005] from VERIFIED to CLOSED > Validation errors in the S-RAMP demos > ------------------------------------- > > Key: SRAMP-250 > URL: https://issues.jboss.org/browse/SRAMP-250 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > -- 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 From issues at jboss.org Thu Feb 6 10:28:33 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:33 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (GADGETS-55) Using json-20070829 jar. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GADGETS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941995#comment-12941995 ] RH Bugzilla Integration commented on GADGETS-55: ------------------------------------------------ Anne-Louise Tangring changed the Status of [bug 953096|https://bugzilla.redhat.com/show_bug.cgi?id=953096] from VERIFIED to CLOSED > Using json-20070829 jar. > ------------------------ > > Key: GADGETS-55 > URL: https://issues.jboss.org/browse/GADGETS-55 > Project: Gadget Server and Gadgets > Issue Type: Bug > Affects Versions: 1.0.0.M4 > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0.0.M5 > > > Occasionally we have seen startup errors. We can more easily reproduce it if we remove the 20070829 jar. By removing the 20090211 jar we do not see the error any more. -- 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 From issues at jboss.org Thu Feb 6 10:28:33 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:33 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-310) ActivityClient sample should prompt for username and password In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941998#comment-12941998 ] RH Bugzilla Integration commented on RTGOV-310: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1021309|https://bugzilla.redhat.com/show_bug.cgi?id=1021309] from VERIFIED to CLOSED > ActivityClient sample should prompt for username and password > ------------------------------------------------------------- > > Key: RTGOV-310 > URL: https://issues.jboss.org/browse/RTGOV-310 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > To avoid recording the username and password in the pom.xml, the activity client quickstart should prompt the user to enter the details when running the app. -- 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 From issues at jboss.org Thu Feb 6 10:28:33 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:33 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-236) Missing roles for some users in overlord-idp jaas config In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941999#comment-12941999 ] RH Bugzilla Integration commented on SRAMP-236: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1001992|https://bugzilla.redhat.com/show_bug.cgi?id=1001992] from VERIFIED to CLOSED > Missing roles for some users in overlord-idp jaas config > -------------------------------------------------------- > > Key: SRAMP-236 > URL: https://issues.jboss.org/browse/SRAMP-236 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > We are missing the s-ramp role from some of the users in the overlord-idp jaas configuration. This prevents users from actually using the dtgov-ui because dtgov makes s-ramp calls at times. So anything that requires a call to s-ramp fails when that user is logged in. -- 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 From issues at jboss.org Thu Feb 6 10:28:33 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:33 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-252) BPM event process version not set In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942001#comment-12942001 ] RH Bugzilla Integration commented on RTGOV-252: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996929|https://bugzilla.redhat.com/show_bug.cgi?id=996929] from VERIFIED to CLOSED > BPM event process version not set > --------------------------------- > > Key: RTGOV-252 > URL: https://issues.jboss.org/browse/RTGOV-252 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:28:34 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:34 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-283) Fix integration bom import In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942002#comment-12942002 ] RH Bugzilla Integration commented on RTGOV-283: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1013509|https://bugzilla.redhat.com/show_bug.cgi?id=1013509] from VERIFIED to CLOSED > Fix integration bom import > -------------------------- > > Key: RTGOV-283 > URL: https://issues.jboss.org/browse/RTGOV-283 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:28:34 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:34 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-307) Derive list of service and operation names from response time collection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942006#comment-12942006 ] RH Bugzilla Integration commented on RTGOV-307: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1003928|https://bugzilla.redhat.com/show_bug.cgi?id=1003928] from VERIFIED to CLOSED > Derive list of service and operation names from response time collection > ------------------------------------------------------------------------ > > Key: RTGOV-307 > URL: https://issues.jboss.org/browse/RTGOV-307 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the list of service types, and operations for those service types, are derived from the service definition active map. However the contents of this map expires after a predefined time period, and therefore the options available in the drop down lists will not necessarily relate to the search criteria defined in the response time collection. > Therefore it would be better if the service type and operation information is derived from the complete response time collection contents instead. -- 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 From issues at jboss.org Thu Feb 6 10:28:34 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:34 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-269) Report activity logger problems via MBean In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942007#comment-12942007 ] RH Bugzilla Integration commented on RTGOV-269: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1005273|https://bugzilla.redhat.com/show_bug.cgi?id=1005273] from VERIFIED to CLOSED > Report activity logger problems via MBean > ----------------------------------------- > > Key: RTGOV-269 > URL: https://issues.jboss.org/browse/RTGOV-269 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > When the REST client fails to report a list of activity units to the server, then report issue via MBean. > To avoid reporting a notification for each failure, only report the first occurrence within a 5 min window - if the issue persists, then send a further reminder each 5 mins. > It may also be useful to provide an indication of the number of consecutive failures as a counter, so they can see when the issue is fixed. Alternatively send a notification when a failure is not reported for 1 min? -- 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 From issues at jboss.org Thu Feb 6 10:28:34 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:34 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-254) Switchyard camel-service quickstart fails due to class cast exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942010#comment-12942010 ] RH Bugzilla Integration commented on RTGOV-254: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 994413|https://bugzilla.redhat.com/show_bug.cgi?id=994413] from VERIFIED to CLOSED > Switchyard camel-service quickstart fails due to class cast exception > --------------------------------------------------------------------- > > Key: RTGOV-254 > URL: https://issues.jboss.org/browse/RTGOV-254 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Try camel-service quickstart. When executed on the server the rtgov does not record a business transaction. Moreover an exception is in the log > 10:52:39,114 DEBUG [org.switchyard.internal.EventManager] (Camel (camel-7) thread #8 - file:///home/jpechane/in) Observer threw exception on event class org.apache.camel.management.event.ExchangeCompletedEvent: java.lang.ClassCastException: org.apache.camel.component.file.GenericFileMessage cannot be cast to org.switchyard.bus.camel.CamelMessage > at org.overlord.rtgov.internal.switchyard.camel.AbstractExchangeEventProcessor.handleEvent(AbstractExchangeEventProcessor.java:77) > at org.overlord.rtgov.internal.switchyard.AbstractEventProcessor.notify(AbstractEventProcessor.java:75) > at org.switchyard.internal.EventManager.publish(EventManager.java:52) [switchyard-runtime-1.1.0.M1-redhat-1.jar:1.1.0.M1-redhat-1] > at -- 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 From issues at jboss.org Thu Feb 6 10:28:36 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:28:36 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-267) Revert to commons-codec 1.4 in gadget server and rtgov In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942015#comment-12942015 ] RH Bugzilla Integration commented on RTGOV-267: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1004864|https://bugzilla.redhat.com/show_bug.cgi?id=1004864] from VERIFIED to CLOSED > Revert to commons-codec 1.4 in gadget server and rtgov > ------------------------------------------------------ > > Key: RTGOV-267 > URL: https://issues.jboss.org/browse/RTGOV-267 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:35 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-262) ReplyTo field not set in response events when exception is thrown by swyd service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942025#comment-12942025 ] RH Bugzilla Integration commented on RTGOV-262: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1004314|https://bugzilla.redhat.com/show_bug.cgi?id=1004314] from VERIFIED to CLOSED > ReplyTo field not set in response events when exception is thrown by swyd service > --------------------------------------------------------------------------------- > > Key: RTGOV-262 > URL: https://issues.jboss.org/browse/RTGOV-262 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:36 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:36 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-314) Fix errors when importing quickstarts into JBDS-IS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942033#comment-12942033 ] RH Bugzilla Integration commented on RTGOV-314: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1029149|https://bugzilla.redhat.com/show_bug.cgi?id=1029149] from VERIFIED to CLOSED > Fix errors when importing quickstarts into JBDS-IS > -------------------------------------------------- > > Key: RTGOV-314 > URL: https://issues.jboss.org/browse/RTGOV-314 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:37 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-260) Incorrect loop counter init in JMXNotifier when removing listeners In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942037#comment-12942037 ] RH Bugzilla Integration commented on RTGOV-260: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1001594|https://bugzilla.redhat.com/show_bug.cgi?id=1001594] from VERIFIED to CLOSED > Incorrect loop counter init in JMXNotifier when removing listeners > ------------------------------------------------------------------ > > Key: RTGOV-260 > URL: https://issues.jboss.org/browse/RTGOV-260 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Loop counter incorrect initialized to list size rather than -1. -- 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 From issues at jboss.org Thu Feb 6 10:30:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:37 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-249) Use Community BOM for S-RAMP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942045#comment-12942045 ] RH Bugzilla Integration commented on SRAMP-249: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1017699|https://bugzilla.redhat.com/show_bug.cgi?id=1017699] from VERIFIED to CLOSED > Use Community BOM for S-RAMP > ---------------------------- > > Key: SRAMP-249 > URL: https://issues.jboss.org/browse/SRAMP-249 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:38 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:38 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-306) Response time gadget y-axis label incorrect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942055#comment-12942055 ] RH Bugzilla Integration commented on RTGOV-306: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1004163|https://bugzilla.redhat.com/show_bug.cgi?id=1004163] from VERIFIED to CLOSED > Response time gadget y-axis label incorrect > ------------------------------------------- > > Key: RTGOV-306 > URL: https://issues.jboss.org/browse/RTGOV-306 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Label should indicate units are milliseconds, not seconds. -- 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 From issues at jboss.org Thu Feb 6 10:30:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-249) Use Community BOM for S-RAMP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942057#comment-12942057 ] RH Bugzilla Integration commented on SRAMP-249: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1017699|https://bugzilla.redhat.com/show_bug.cgi?id=1017699] from VERIFIED to CLOSED > Use Community BOM for S-RAMP > ---------------------------- > > Key: SRAMP-249 > URL: https://issues.jboss.org/browse/SRAMP-249 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:38 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:38 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-268) Service response time aggregation not performed correctly for min/max values In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942056#comment-12942056 ] RH Bugzilla Integration commented on RTGOV-268: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1004173|https://bugzilla.redhat.com/show_bug.cgi?id=1004173] from VERIFIED to CLOSED > Service response time aggregation not performed correctly for min/max values > ---------------------------------------------------------------------------- > > Key: RTGOV-268 > URL: https://issues.jboss.org/browse/RTGOV-268 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the min/max values are based on the extreme avg values being aggregated. > However the min/max values should also be aggregated, to get a better mean value over these properties. -- 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 From issues at jboss.org Thu Feb 6 10:30:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-296) Update activityclient readme to explain how to setup username and password In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942064#comment-12942064 ] RH Bugzilla Integration commented on RTGOV-296: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1017118|https://bugzilla.redhat.com/show_bug.cgi?id=1017118] from VERIFIED to CLOSED > Update activityclient readme to explain how to setup username and password > -------------------------------------------------------------------------- > > Key: RTGOV-296 > URL: https://issues.jboss.org/browse/RTGOV-296 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-259) DroolsEventProcessor session caching not isolated or protected from redeployments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942067#comment-12942067 ] RH Bugzilla Integration commented on RTGOV-259: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1000393|https://bugzilla.redhat.com/show_bug.cgi?id=1000393] from VERIFIED to CLOSED > DroolsEventProcessor session caching not isolated or protected from redeployments > --------------------------------------------------------------------------------- > > Key: RTGOV-259 > URL: https://issues.jboss.org/browse/RTGOV-259 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Drools sessions are cached based on rule names, which are not necessarily unique across EPNs. > When the drools event processor is initialised, it is associated with an EPNContext. However if it already exists, this is not done. Therefore the issue is when a new version of an EPN is deployed, the rule will remain associated with the original EPNContext. -- 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 From issues at jboss.org Thu Feb 6 10:30:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-255) Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942074#comment-12942074 ] RH Bugzilla Integration commented on SRAMP-255: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1016591|https://bugzilla.redhat.com/show_bug.cgi?id=1016591] from VERIFIED to CLOSED > Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps > ------------------------------------------------------------------------------------------------ > > Key: SRAMP-255 > URL: https://issues.jboss.org/browse/SRAMP-255 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > This is actually an EAP bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1016591 > This JIRA issue tracks the workaround used in Overlord. The workaround is only necessary until the EAP bug is fixed. -- 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 From issues at jboss.org Thu Feb 6 10:30:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-96) Remember the selected filter criteria when navigating the UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMPUI-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942070#comment-12942070 ] RH Bugzilla Integration commented on SRAMPUI-96: ------------------------------------------------ Anne-Louise Tangring changed the Status of [bug 1018786|https://bugzilla.redhat.com/show_bug.cgi?id=1018786] from VERIFIED to CLOSED > Remember the selected filter criteria when navigating the UI > ------------------------------------------------------------ > > Key: SRAMPUI-96 > URL: https://issues.jboss.org/browse/SRAMPUI-96 > Project: S-RAMP UI > Issue Type: Enhancement > Components: View > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > The Artifacts page allows the user to select a number of filters to narrow down the list of artifacts being viewed. However, these options are lost when the user navigates to another page and then back again. We should remember the user's filter settings as long as they stay within the s-ramp application (or perhaps beyond by storing something in browser state?). -- 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 From issues at jboss.org Thu Feb 6 10:30:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-305) Missing header still results in IP attempting to evaluate expression In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942075#comment-12942075 ] RH Bugzilla Integration commented on RTGOV-305: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1011865|https://bugzilla.redhat.com/show_bug.cgi?id=1011865] from VERIFIED to CLOSED > Missing header still results in IP attempting to evaluate expression > -------------------------------------------------------------------- > > Key: RTGOV-305 > URL: https://issues.jboss.org/browse/RTGOV-305 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > If a header property does not exist, a warning is recorded by the expression evaluation is still attempted, which can lead to problems in the invoked script. -- 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 From issues at jboss.org Thu Feb 6 10:30:41 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:41 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-249) Missing values from BPM activity events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942081#comment-12942081 ] RH Bugzilla Integration commented on RTGOV-249: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996503|https://bugzilla.redhat.com/show_bug.cgi?id=996503] from VERIFIED to CLOSED > Missing values from BPM activity events > --------------------------------------- > > Key: RTGOV-249 > URL: https://issues.jboss.org/browse/RTGOV-249 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > When reporting activity events from the BPM component within SwitchYard: > ProcessCompleted event currently does not record the status of the process instance. This is available by navigating to the process instance. > The ProcessVariableSet component is missing the variable type. -- 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 From issues at jboss.org Thu Feb 6 10:30:41 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:41 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-255) Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942085#comment-12942085 ] RH Bugzilla Integration commented on SRAMP-255: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1016591|https://bugzilla.redhat.com/show_bug.cgi?id=1016591] from VERIFIED to CLOSED > Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps > ------------------------------------------------------------------------------------------------ > > Key: SRAMP-255 > URL: https://issues.jboss.org/browse/SRAMP-255 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > This is actually an EAP bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1016591 > This JIRA issue tracks the workaround used in Overlord. The workaround is only necessary until the EAP bug is fixed. -- 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 From issues at jboss.org Thu Feb 6 10:30:42 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:42 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-298) Exception from Switchyard EventProcessorManager when shutting down server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942088#comment-12942088 ] RH Bugzilla Integration commented on RTGOV-298: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1011144|https://bugzilla.redhat.com/show_bug.cgi?id=1011144] from VERIFIED to CLOSED > Exception from Switchyard EventProcessorManager when shutting down server > ------------------------------------------------------------------------- > > Key: RTGOV-298 > URL: https://issues.jboss.org/browse/RTGOV-298 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:42 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:42 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-258) DroolsEventProcessor should fail deployment if rule not found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942093#comment-12942093 ] RH Bugzilla Integration commented on RTGOV-258: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1000350|https://bugzilla.redhat.com/show_bug.cgi?id=1000350] from VERIFIED to CLOSED > DroolsEventProcessor should fail deployment if rule not found > ------------------------------------------------------------- > > Key: RTGOV-258 > URL: https://issues.jboss.org/browse/RTGOV-258 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > If the named rule does not exist, or has an error, then the EPN should fail to deploy. -- 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 From issues at jboss.org Thu Feb 6 10:30:42 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:42 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-209) Switch ModeShape to DB persisted (not file) for performance reasons In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942092#comment-12942092 ] RH Bugzilla Integration commented on SRAMP-209: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 979958|https://bugzilla.redhat.com/show_bug.cgi?id=979958] from VERIFIED to CLOSED > Switch ModeShape to DB persisted (not file) for performance reasons > ------------------------------------------------------------------- > > Key: SRAMP-209 > URL: https://issues.jboss.org/browse/SRAMP-209 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.3.0 - JBPM6 Integration > > -- 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 From issues at jboss.org Thu Feb 6 10:30:43 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:43 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-190) Create H2 db on installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942099#comment-12942099 ] RH Bugzilla Integration commented on RTGOV-190: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 947692|https://bugzilla.redhat.com/show_bug.cgi?id=947692] from VERIFIED to CLOSED > Create H2 db on installation > ---------------------------- > > Key: RTGOV-190 > URL: https://issues.jboss.org/browse/RTGOV-190 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M5 > > > Need to create an empty H2 db (with schema) on installation and then change/remove the hibernate.hbm2ddl.auto property in the persistence.xml. -- 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 From issues at jboss.org Thu Feb 6 10:30:43 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:43 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-190) Create H2 db on installation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942098#comment-12942098 ] RH Bugzilla Integration commented on RTGOV-190: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 947692|https://bugzilla.redhat.com/show_bug.cgi?id=947692] from VERIFIED to CLOSED > Create H2 db on installation > ---------------------------- > > Key: RTGOV-190 > URL: https://issues.jboss.org/browse/RTGOV-190 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M5 > > > Need to create an empty H2 db (with schema) on installation and then change/remove the hibernate.hbm2ddl.auto property in the persistence.xml. -- 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 From issues at jboss.org Thu Feb 6 10:30:43 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:43 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-253) Activity associated with a failed business txn (i.e. where exception thrown) is not recorded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942101#comment-12942101 ] RH Bugzilla Integration commented on RTGOV-253: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996136|https://bugzilla.redhat.com/show_bug.cgi?id=996136] from VERIFIED to CLOSED > Activity associated with a failed business txn (i.e. where exception thrown) is not recorded > -------------------------------------------------------------------------------------------- > > Key: RTGOV-253 > URL: https://issues.jboss.org/browse/RTGOV-253 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:44 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-278) Activty server query on context causes npe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942105#comment-12942105 ] RH Bugzilla Integration commented on RTGOV-278: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996417|https://bugzilla.redhat.com/show_bug.cgi?id=996417] from VERIFIED to CLOSED > Activty server query on context causes npe > ------------------------------------------ > > Key: RTGOV-278 > URL: https://issues.jboss.org/browse/RTGOV-278 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:30:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:44 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-279) Situation requires an explicitly defined ID In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942106#comment-12942106 ] RH Bugzilla Integration commented on RTGOV-279: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1011889|https://bugzilla.redhat.com/show_bug.cgi?id=1011889] from VERIFIED to CLOSED > Situation requires an explicitly defined ID > ------------------------------------------- > > Key: RTGOV-279 > URL: https://issues.jboss.org/browse/RTGOV-279 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Situation currently has a protected id set by Hibernate when the situation is persisted. However to enable Situations, that are created and published out as notifications, to be correlated back to the object stored in the db, we need to explicitly set the upon creation, to ensure the same ID is present when the object is published and persisted. -- 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 From issues at jboss.org Thu Feb 6 10:30:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:44 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-246) Deleted derived artifact are still available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942108#comment-12942108 ] RH Bugzilla Integration commented on SRAMP-246: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1011937|https://bugzilla.redhat.com/show_bug.cgi?id=1011937] from VERIFIED to CLOSED > Deleted derived artifact are still available > -------------------------------------------- > > Key: SRAMP-246 > URL: https://issues.jboss.org/browse/SRAMP-246 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > When a primary artifact is deleted the JCR node is moved from being rooted in '/s-ramp' to '/s-ramp-trash'. It's derived nodes are children and are moved as well. The JCR filter by '/s-ramp' still brings back the derived nodes, so they don't appear as being deleted. Opened a discussion with the ModeShape guys about this: https://community.jboss.org/message/840238#840238 -- 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 From issues at jboss.org Thu Feb 6 10:30:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:30:44 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-271) Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942110#comment-12942110 ] RH Bugzilla Integration commented on RTGOV-271: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1006709|https://bugzilla.redhat.com/show_bug.cgi?id=1006709] from VERIFIED to CLOSED > Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module > ----------------------------------------------------------------------------------------------- > > Key: RTGOV-271 > URL: https://issues.jboss.org/browse/RTGOV-271 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:32:35 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-243) Fix KieExpander In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942125#comment-12942125 ] RH Bugzilla Integration commented on SRAMP-243: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1015531|https://bugzilla.redhat.com/show_bug.cgi?id=1015531] from VERIFIED to CLOSED > Fix KieExpander > --------------- > > Key: SRAMP-243 > URL: https://issues.jboss.org/browse/SRAMP-243 > 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 > > > Should set the right model type for BPMN and DRL files. -- 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 From issues at jboss.org Thu Feb 6 10:32:36 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:36 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-312) Intermittent "entry point not found" issue with example Drools rules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942129#comment-12942129 ] RH Bugzilla Integration commented on RTGOV-312: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1028779|https://bugzilla.redhat.com/show_bug.cgi?id=1028779] from VERIFIED to CLOSED > Intermittent "entry point not found" issue with example Drools rules > -------------------------------------------------------------------- > > Key: RTGOV-312 > URL: https://issues.jboss.org/browse/RTGOV-312 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Periodically the example 'SLAViolation' rule fails to find the entry point. -- 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 From issues at jboss.org Thu Feb 6 10:32:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:37 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-245) Querying activity via REST API results in hibernate lazy instantiation exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942142#comment-12942142 ] RH Bugzilla Integration commented on RTGOV-245: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996030|https://bugzilla.redhat.com/show_bug.cgi?id=996030] from VERIFIED to CLOSED > Querying activity via REST API results in hibernate lazy instantiation exception > -------------------------------------------------------------------------------- > > Key: RTGOV-245 > URL: https://issues.jboss.org/browse/RTGOV-245 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Using a REST client to query activity events results in a hibernate lazy instantiation exception. > First solution would be to change to EAGER fetch, although this results in another hibernate exception. Possible workaround is to change ActivityType.context from being a list to a set. > Another solution would be to expand the txn boundary to encompass the REST query operation. -- 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 From issues at jboss.org Thu Feb 6 10:32:36 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:36 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-302) Call trace child node percentages are wrong In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942139#comment-12942139 ] RH Bugzilla Integration commented on RTGOV-302: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1021938|https://bugzilla.redhat.com/show_bug.cgi?id=1021938] from VERIFIED to CLOSED > Call trace child node percentages are wrong > ------------------------------------------- > > Key: RTGOV-302 > URL: https://issues.jboss.org/browse/RTGOV-302 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > The child node percentages currently add up to 100%, but their times do not add up to the total associated with the parent node. This is because time will also be spent in the parent's calling service, as well as the latency of any network communication. > So the percentages on the child nodes should reflect the percentage of time spent in the child compared to the overall time taken in the parent node. -- 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 From issues at jboss.org Thu Feb 6 10:32:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:37 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-253) Add support for Teiid artifacts in s-ramp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942143#comment-12942143 ] RH Bugzilla Integration commented on SRAMP-253: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1022586|https://bugzilla.redhat.com/show_bug.cgi?id=1022586] from VERIFIED to CLOSED > 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 From issues at jboss.org Thu Feb 6 10:32:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:37 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-249) Missing values from BPM activity events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942147#comment-12942147 ] RH Bugzilla Integration commented on RTGOV-249: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996501|https://bugzilla.redhat.com/show_bug.cgi?id=996501] from VERIFIED to CLOSED > Missing values from BPM activity events > --------------------------------------- > > Key: RTGOV-249 > URL: https://issues.jboss.org/browse/RTGOV-249 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > When reporting activity events from the BPM component within SwitchYard: > ProcessCompleted event currently does not record the status of the process instance. This is available by navigating to the process instance. > The ProcessVariableSet component is missing the variable type. -- 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 From issues at jboss.org Thu Feb 6 10:32:37 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:37 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-249) Missing values from BPM activity events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942151#comment-12942151 ] RH Bugzilla Integration commented on RTGOV-249: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996514|https://bugzilla.redhat.com/show_bug.cgi?id=996514] from VERIFIED to CLOSED > Missing values from BPM activity events > --------------------------------------- > > Key: RTGOV-249 > URL: https://issues.jboss.org/browse/RTGOV-249 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > When reporting activity events from the BPM component within SwitchYard: > ProcessCompleted event currently does not record the status of the process instance. This is available by navigating to the process instance. > The ProcessVariableSet component is missing the variable type. -- 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 From issues at jboss.org Thu Feb 6 10:32:38 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:38 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into a subdirectory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942156#comment-12942156 ] RH Bugzilla Integration commented on SRAMP-261: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1040812|https://bugzilla.redhat.com/show_bug.cgi?id=1040812] from VERIFIED to CLOSED > Move demo assembly into a subdirectory > -------------------------------------- > > Key: SRAMP-261 > URL: https://issues.jboss.org/browse/SRAMP-261 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Kevin Conner > Assignee: Kevin Conner > > The demo assembly should be in its own module and not part of the demo parent module. When built the assembly zip should exclude the assembly subdirectory and build cleanly. -- 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 From issues at jboss.org Thu Feb 6 10:32:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-267) Revert to commons-codec 1.4 in gadget server and rtgov In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942163#comment-12942163 ] RH Bugzilla Integration commented on RTGOV-267: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1004843|https://bugzilla.redhat.com/show_bug.cgi?id=1004843] from VERIFIED to CLOSED > Revert to commons-codec 1.4 in gadget server and rtgov > ------------------------------------------------------ > > Key: RTGOV-267 > URL: https://issues.jboss.org/browse/RTGOV-267 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:32:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (GADGETS-52) Duplicated guava.jar in the gadget-server.war In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GADGETS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942167#comment-12942167 ] RH Bugzilla Integration commented on GADGETS-52: ------------------------------------------------ Anne-Louise Tangring changed the Status of [bug 929172|https://bugzilla.redhat.com/show_bug.cgi?id=929172] from VERIFIED to CLOSED > Duplicated guava.jar in the gadget-server.war > --------------------------------------------- > > Key: GADGETS-52 > URL: https://issues.jboss.org/browse/GADGETS-52 > Project: Gadget Server and Gadgets > Issue Type: Bug > Affects Versions: 1.0.0.M4 > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0.0.M5 > > Attachments: GADGETS-52.patch > > > Description of problem: > There are two guava.jar causing problem of deployment of gadget-server.war. > Noticed that it is not always reproduce to every machine. > Already discussed with Jeff, it happens to some machine , well, not happens to other, which seems to me it happens randomely. > But I think the duplicate guava.jar can be fixed. I tested that guava-11.0.2.jar would cause the problem below. Hopefully we can remove it. -- 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 From issues at jboss.org Thu Feb 6 10:32:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-277) ProcessCompleted don't set default completion status, so that success reported in REST data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942166#comment-12942166 ] RH Bugzilla Integration commented on RTGOV-277: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996501|https://bugzilla.redhat.com/show_bug.cgi?id=996501] from VERIFIED to CLOSED > ProcessCompleted don't set default completion status, so that success reported in REST data > ------------------------------------------------------------------------------------------- > > Key: RTGOV-277 > URL: https://issues.jboss.org/browse/RTGOV-277 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:32:38 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:38 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-293) Deserialization issue when using clustered switchyard demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942159#comment-12942159 ] RH Bugzilla Integration commented on RTGOV-293: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1014496|https://bugzilla.redhat.com/show_bug.cgi?id=1014496] from VERIFIED to CLOSED > Deserialization issue when using clustered switchyard demo > ---------------------------------------------------------- > > Key: RTGOV-293 > URL: https://issues.jboss.org/browse/RTGOV-293 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Activity request event is stored in the switchyard exchange properties so that it can be accessed when processing the response's activity event. > When using the clustered example, the exchange is serialized to be passed between clustered nodes. The receiving node does not have access to the activity model, thus causing class not found exceptions. > Keith suggests marking the property as transient to prevent it being serialized - but this still retains the property in the requestor, which should enable the activity event processing to function correctly. -- 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 From issues at jboss.org Thu Feb 6 10:32:40 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-261) RTGov server profile cannot be installed in EAP without switchyard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942171#comment-12942171 ] RH Bugzilla Integration commented on RTGOV-261: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1003982|https://bugzilla.redhat.com/show_bug.cgi?id=1003982] from VERIFIED to CLOSED > RTGov server profile cannot be installed in EAP without switchyard > ------------------------------------------------------------------ > > Key: RTGOV-261 > URL: https://issues.jboss.org/browse/RTGOV-261 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:32:41 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:41 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-255) Remove default type from the context, so json serialized form has it listed explicitly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942178#comment-12942178 ] RH Bugzilla Integration commented on RTGOV-255: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 998829|https://bugzilla.redhat.com/show_bug.cgi?id=998829] from VERIFIED to CLOSED > Remove default type from the context, so json serialized form has it listed explicitly > -------------------------------------------------------------------------------------- > > Key: RTGOV-255 > URL: https://issues.jboss.org/browse/RTGOV-255 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:32:42 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:42 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-250) Remove java: prefix for types reported by switchyard to information procesor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942186#comment-12942186 ] RH Bugzilla Integration commented on RTGOV-250: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996523|https://bugzilla.redhat.com/show_bug.cgi?id=996523] from VERIFIED to CLOSED > Remove java: prefix for types reported by switchyard to information procesor > ---------------------------------------------------------------------------- > > Key: RTGOV-250 > URL: https://issues.jboss.org/browse/RTGOV-250 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > When switchyard Java messages are captured, the type has the 'java:' prefix. However this should be removed when logged, and used (for example) in the informatipn processor, to make the information processor etc independent of switchyard as an event source. -- 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 From issues at jboss.org Thu Feb 6 10:32:43 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:43 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-251) MVEL information transformer returns null if value is not a string In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942198#comment-12942198 ] RH Bugzilla Integration commented on RTGOV-251: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996540|https://bugzilla.redhat.com/show_bug.cgi?id=996540] from VERIFIED to CLOSED > MVEL information transformer returns null if value is not a string > ------------------------------------------------------------------ > > Key: RTGOV-251 > URL: https://issues.jboss.org/browse/RTGOV-251 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Should return the 'toString' value instead. -- 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 From issues at jboss.org Thu Feb 6 10:32:43 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:43 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-196) Create H2 db on installation for gadget server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942200#comment-12942200 ] RH Bugzilla Integration commented on RTGOV-196: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 957994|https://bugzilla.redhat.com/show_bug.cgi?id=957994] from VERIFIED to CLOSED > Create H2 db on installation for gadget server > ---------------------------------------------- > > Key: RTGOV-196 > URL: https://issues.jboss.org/browse/RTGOV-196 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > Enhance installation script to also create h2 db for gadget server. -- 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 From issues at jboss.org Thu Feb 6 10:32:44 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:44 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (GADGETS-71) Occasional ConcurrentModificationException when starting up gadget web UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GADGETS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942210#comment-12942210 ] RH Bugzilla Integration commented on GADGETS-71: ------------------------------------------------ Anne-Louise Tangring changed the Status of [bug 1018757|https://bugzilla.redhat.com/show_bug.cgi?id=1018757] from VERIFIED to CLOSED > Occasional ConcurrentModificationException when starting up gadget web UI > ------------------------------------------------------------------------- > > Key: GADGETS-71 > URL: https://issues.jboss.org/browse/GADGETS-71 > Project: Gadget Server and Gadgets > Issue Type: Bug > Reporter: Gary Brown > Assignee: Eric Wittmann > > This exception occurs periodically when starting up the gadget server and adding the gadgets to a page. It appears to be related to the service overview gadget, as that does not display any content when this exception occurs. > {noformat} > 10:23:09,459 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gadget-web].[js]] (http-/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for servlet js threw exception: java.util.ConcurrentModificationException > at java.util.TreeMap$NavigableSubMap$SubMapIterator.prevEntry(TreeMap.java:1605) [rt.jar:1.7.0_07] > at java.util.TreeMap$NavigableSubMap$DescendingSubMapKeyIterator.next(TreeMap.java:1682) [rt.jar:1.7.0_07] > at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:99) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.ComposeWarningsGuard.addGuard(ComposeWarningsGuard.java:89) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:100) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.ComposeWarningsGuard.(ComposeWarningsGuard.java:79) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.Compiler.initOptions(Compiler.java:277) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.Compiler.initModules(Compiler.java:332) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.Compiler.init(Compiler.java:312) [closure-compiler-r1741.jar:] > at com.google.javascript.jscomp.Compiler.compile(Compiler.java:511) [closure-compiler-r1741.jar:] > at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.doCompile(ClosureJsCompiler.java:205) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.compile(ClosureJsCompiler.java:172) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.js.CompilationProcessor.process(CompilationProcessor.java:48) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.js.DefaultJsProcessorRegistry.process(DefaultJsProcessorRegistry.java:53) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.js.DefaultJsServingPipeline.execute(DefaultJsServingPipeline.java:41) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.shindig.gadgets.servlet.JsServlet.doGet(JsServlet.java:93) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:55) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.shindig.common.servlet.HostFilter.doFilter(HostFilter.java:39) [shindig-common-3.0.0-beta4.jar:3.0.0-beta4] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > {noformat} -- 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 From issues at jboss.org Thu Feb 6 10:32:45 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:45 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-315) Move swyd quickstart ordermgmt app descriptor to standard location In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942212#comment-12942212 ] RH Bugzilla Integration commented on RTGOV-315: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1030020|https://bugzilla.redhat.com/show_bug.cgi?id=1030020] from VERIFIED to CLOSED > Move swyd quickstart ordermgmt app descriptor to standard location > ------------------------------------------------------------------ > > Key: RTGOV-315 > URL: https://issues.jboss.org/browse/RTGOV-315 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > The non-standard location causes problems when loading quickstart into JBDS. -- 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 From issues at jboss.org Thu Feb 6 10:32:45 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:45 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-297) Use consistent datasource naming In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942213#comment-12942213 ] RH Bugzilla Integration commented on RTGOV-297: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1017184|https://bugzilla.redhat.com/show_bug.cgi?id=1017184] from VERIFIED to CLOSED > Use consistent datasource naming > -------------------------------- > > Key: RTGOV-297 > URL: https://issues.jboss.org/browse/RTGOV-297 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:32:45 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:45 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-299) SLA reports sample deployment exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942219#comment-12942219 ] RH Bugzilla Integration commented on RTGOV-299: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1028794|https://bugzilla.redhat.com/show_bug.cgi?id=1028794] from VERIFIED to CLOSED > SLA reports sample deployment exception > --------------------------------------- > > Key: RTGOV-299 > URL: https://issues.jboss.org/browse/RTGOV-299 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > When deploying the SLA reports sample, it now throws the following exception: > {noformat} > 14:00:24,007 SEVERE [org.overlord.rtgov.internal.reports.loader.jee.JEEReportsLoader] (ServerService Thread Pool -- 89) Failed to register reports: [Error: not a statement, or badly formed structure] > [Near : {... long respTime=calcResponseTime(activity, i, ....}] > ^ > [Line: 105, Column: 19] > at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:299) [mvel2-2.1.7.Final.jar:] > at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:] > at org.mvel2.ast.TypedVarNode.(TypedVarNode.java:52) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.procTypedNode(AbstractParser.java:1412) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:794) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.nextTokenSkipSymbols(AbstractParser.java:188) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:156) [mvel2-2.1.7.Final.jar:] > at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:] > at org.mvel2.ast.IfNode.(IfNode.java:64) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.createBlockToken(AbstractParser.java:1497) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser._captureBlock(AbstractParser.java:1700) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.captureCodeBlock(AbstractParser.java:1542) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:380) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:128) [mvel2-2.1.7.Final.jar:] > at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:] > at org.mvel2.ast.IfNode.(IfNode.java:64) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.createBlockToken(AbstractParser.java:1497) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser._captureBlock(AbstractParser.java:1700) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.captureCodeBlock(AbstractParser.java:1542) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:380) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:128) [mvel2-2.1.7.Final.jar:] > at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:] > at org.mvel2.ast.IfNode.(IfNode.java:64) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.createBlockToken(AbstractParser.java:1497) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser._captureBlock(AbstractParser.java:1700) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.captureCodeBlock(AbstractParser.java:1542) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:380) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:128) [mvel2-2.1.7.Final.jar:] > at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:] > at org.mvel2.ast.ForNode.buildForEach(ForNode.java:132) [mvel2-2.1.7.Final.jar:] > at org.mvel2.ast.ForNode.(ForNode.java:49) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.createBlockToken(AbstractParser.java:1501) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser._captureBlock(AbstractParser.java:1729) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.captureCodeBlock(AbstractParser.java:1565) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:395) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:128) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:62) [mvel2-2.1.7.Final.jar:] > at org.mvel2.MVEL.compileExpression(MVEL.java:810) [mvel2-2.1.7.Final.jar:] > at org.mvel2.MVEL.compileExpression(MVEL.java:820) [mvel2-2.1.7.Final.jar:] > at org.mvel2.MVEL.compileExpression(MVEL.java:723) [mvel2-2.1.7.Final.jar:] > at org.overlord.rtgov.reports.MVELReportGenerator.init(MVELReportGenerator.java:53) [reports-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT] > at org.overlord.rtgov.reports.ReportDefinition.preInit(ReportDefinition.java:108) [reports-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT] > at org.overlord.rtgov.reports.AbstractReportsLoader.preInit(AbstractReportsLoader.java:35) [reports-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT] > at org.overlord.rtgov.internal.reports.loader.jee.JEEReportsLoader.init(JEEReportsLoader.java:96) [reports-loader-jee-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_07] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_07] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07] > at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_07] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_07] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_07] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: java.lang.NullPointerException > at org.mvel2.compiler.PropertyVerifier.getMethod(PropertyVerifier.java:576) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.PropertyVerifier.getBeanProperty(PropertyVerifier.java:300) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.PropertyVerifier.analyze(PropertyVerifier.java:117) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.ExpressionCompiler.verify(ExpressionCompiler.java:381) [mvel2-2.1.7.Final.jar:] > at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:273) [mvel2-2.1.7.Final.jar:] > ... 80 more > 14:00:24,039 INFO [org.jboss.web] (ServerService Thread Pool -- 89) JBAS018210: Register web context: /sla-report > {noformat} > This appears to be related to use of mvel 2.1.6/7. > If the defined function is not called (i.e. comment out and use default of 0), it does not cause the exception - so appears to be a problem in the compiler attempting to resolve the function. -- 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 From issues at jboss.org Thu Feb 6 10:32:46 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:46 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (GADGETS-70) Import integration bom and fix duplicate jars In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/GADGETS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942223#comment-12942223 ] RH Bugzilla Integration commented on GADGETS-70: ------------------------------------------------ Anne-Louise Tangring changed the Status of [bug 1013505|https://bugzilla.redhat.com/show_bug.cgi?id=1013505] from VERIFIED to CLOSED > Import integration bom and fix duplicate jars > --------------------------------------------- > > Key: GADGETS-70 > URL: https://issues.jboss.org/browse/GADGETS-70 > Project: Gadget Server and Gadgets > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.1.0.Final > > -- 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 From issues at jboss.org Thu Feb 6 10:32:47 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-304) Activity collector constants need to be configurable in properties file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942227#comment-12942227 ] RH Bugzilla Integration commented on RTGOV-304: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1007842|https://bugzilla.redhat.com/show_bug.cgi?id=1007842] from VERIFIED to CLOSED > Activity collector constants need to be configurable in properties file > ----------------------------------------------------------------------- > > Key: RTGOV-304 > URL: https://issues.jboss.org/browse/RTGOV-304 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:32:47 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-276) Enable activity logger defaults to be retrieved from configuration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942234#comment-12942234 ] RH Bugzilla Integration commented on RTGOV-276: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1007842|https://bugzilla.redhat.com/show_bug.cgi?id=1007842] from VERIFIED to CLOSED > Enable activity logger defaults to be retrieved from configuration > ------------------------------------------------------------------ > > Key: RTGOV-276 > URL: https://issues.jboss.org/browse/RTGOV-276 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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 From issues at jboss.org Thu Feb 6 10:32:48 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-247) Change switchyard event listener to use ExchangeInitiated/CompletedEvents In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942242#comment-12942242 ] RH Bugzilla Integration commented on RTGOV-247: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from VERIFIED to CLOSED > Change switchyard event listener to use ExchangeInitiated/CompletedEvents > ------------------------------------------------------------------------- > > Key: RTGOV-247 > URL: https://issues.jboss.org/browse/RTGOV-247 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently uses the camel initiated and completed events, so switching to use the switchyard alternatives. -- 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 From issues at jboss.org Thu Feb 6 10:32:49 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:32:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-301) Service overview mini view needs service names on the nodes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942247#comment-12942247 ] RH Bugzilla Integration commented on RTGOV-301: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1021927|https://bugzilla.redhat.com/show_bug.cgi?id=1021927] from VERIFIED to CLOSED > Service overview mini view needs service names on the nodes > ----------------------------------------------------------- > > Key: RTGOV-301 > URL: https://issues.jboss.org/browse/RTGOV-301 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the mini view of the service overview/dependency graph does not show any service names, which means a user must expand the gadget to get any useful information. -- 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 From issues at jboss.org Thu Feb 6 10:34:28 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:34:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-311) Switchyard Exchange Validator needs to change to use ExchangeInterceptor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942248#comment-12942248 ] RH Bugzilla Integration commented on RTGOV-311: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from VERIFIED to CLOSED > Switchyard Exchange Validator needs to change to use ExchangeInterceptor > ------------------------------------------------------------------------ > > Key: RTGOV-311 > URL: https://issues.jboss.org/browse/RTGOV-311 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Currently the switchyard exchange validator mechanism uses the Auditor mechanism to detect and analyse the exchanges. However this mechanism directly operates on the camel exchange, retrieving the security context as a property. > The problem with this is that the security context could be sealed, and the only way to deal with this requires the SecurityDomain, which is not accessible from the auditor. > Following discussion with Keith, it appears that the newer ExchangeInterceptors mechanism would be more appropriate - it is higher level abstraction that operates on switchyard exchanges, and therefore will be possible to use the SecurityContextManager to deal with whether or not the SecurityContext is sealed. -- 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 From issues at jboss.org Thu Feb 6 10:34:28 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:34:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-244) Kie and Teiid expanders not working from the S-RAMP-UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942249#comment-12942249 ] RH Bugzilla Integration commented on SRAMP-244: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 1015251|https://bugzilla.redhat.com/show_bug.cgi?id=1015251] from VERIFIED to CLOSED > 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 From issues at jboss.org Thu Feb 6 10:34:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 6 Feb 2014 10:34:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-231) SwitchYard XML deriver missing 'requires' attribute on component services In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12942251#comment-12942251 ] RH Bugzilla Integration commented on SRAMP-231: ----------------------------------------------- Anne-Louise Tangring changed the Status of [bug 996943|https://bugzilla.redhat.com/show_bug.cgi?id=996943] from VERIFIED to CLOSED > SwitchYard XML deriver missing 'requires' attribute on component services > ------------------------------------------------------------------------- > > Key: SRAMP-231 > URL: https://issues.jboss.org/browse/SRAMP-231 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > This SwitchYard deriver is just exploring implementation.bean tag for the 'requires' attribute but security policies are defined in service tag[0] so security/custom policies are just ignored. > [0] https://github.com/jboss-switchyard/quickstarts/blob/master/demos/policy-security-wss-username/src/main/resources/META-INF/switchyard.xml -- 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 From issues at jboss.org Sun Feb 9 10:37:29 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Sun, 9 Feb 2014 10:37:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-331) Enable user to filter situations based on their resolution status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clay resolved RTGOV-331. -------------------------------- Resolution: Done sent pull-request for RTGOV-331 > Enable user to filter situations based on their resolution status > ----------------------------------------------------------------- > > Key: RTGOV-331 > URL: https://issues.jboss.org/browse/RTGOV-331 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value). > Update the server side to use the filter value in its evaluation of the list of situations to be returned. -- 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 From issues at jboss.org Sun Feb 9 10:37:29 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Sun, 9 Feb 2014 10:37:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-331) Enable user to filter situations based on their resolution status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on RTGOV-331 started by Michael Clay. > Enable user to filter situations based on their resolution status > ----------------------------------------------------------------- > > Key: RTGOV-331 > URL: https://issues.jboss.org/browse/RTGOV-331 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value). > Update the server side to use the filter value in its evaluation of the list of situations to be returned. -- 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 From issues at jboss.org Sun Feb 9 10:41:28 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Sun, 9 Feb 2014 10:41:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-333) Enable user to filter situations based on allocation status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on RTGOV-333 started by Michael Clay. > Enable user to filter situations based on allocation status > ----------------------------------------------------------- > > Key: RTGOV-333 > URL: https://issues.jboss.org/browse/RTGOV-333 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > The list of situations shown on the main page can be filtered using criteria on the left panel. > Add a new criteria to enable the list of situations to be filtered on the allocation status of: All, Assigned to me, Unassigned. > The server side should be updated to implement this new filtering criteria. -- 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 From issues at jboss.org Mon Feb 10 14:37:28 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Mon, 10 Feb 2014 14:37:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-330) Allow situations to be allocated/assigned to individual In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clay reassigned RTGOV-330: ---------------------------------- Assignee: Michael Clay (was: Gary Brown) > 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: Michael Clay > > 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 From issues at jboss.org Tue Feb 11 10:47:28 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Tue, 11 Feb 2014 10:47:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-333) Enable user to filter situations based on allocation status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on RTGOV-333 stopped by Michael Clay. > Enable user to filter situations based on allocation status > ----------------------------------------------------------- > > Key: RTGOV-333 > URL: https://issues.jboss.org/browse/RTGOV-333 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > The list of situations shown on the main page can be filtered using criteria on the left panel. > Add a new criteria to enable the list of situations to be filtered on the allocation status of: All, Assigned to me, Unassigned. > The server side should be updated to implement this new filtering criteria. -- 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 From issues at jboss.org Tue Feb 11 12:15:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 11 Feb 2014 12:15:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-350) JMX based switchyard service provider in rtgov UI In-Reply-To: References: Message-ID: Gary Brown created RTGOV-350: -------------------------------- Summary: JMX based switchyard service provider in rtgov UI Key: RTGOV-350 URL: https://issues.jboss.org/browse/RTGOV-350 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Current DMR approach will not be portable across switchyard deployments (e.g. EAP and Fuse), so need to switch to JMX. -- 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 From issues at jboss.org Thu Feb 13 05:41:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Feb 2014 05:41:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-349) Integration tests for switchyard services provider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-349: ----------------------------- Summary: Integration tests for switchyard services provider (was: Integration tests for situations provider and switchyard services provider) > Integration tests for switchyard services provider > -------------------------------------------------- > > Key: RTGOV-349 > URL: https://issues.jboss.org/browse/RTGOV-349 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Setup an integration test structure, using arquillian, to test the rtgov situations provider and the switchyard services provider. -- 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 From issues at jboss.org Thu Feb 13 05:41:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Feb 2014 05:41:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-349) Integration tests for switchyard services provider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-349: ----------------------------- Description: Setup an integration test structure, using arquillian, to test the rtgov switchyard services provider. The situations provider can be tested outside the app server. was: Setup an integration test structure, using arquillian, to test the rtgov situations provider and the switchyard services provider. > Integration tests for switchyard services provider > -------------------------------------------------- > > Key: RTGOV-349 > URL: https://issues.jboss.org/browse/RTGOV-349 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Setup an integration test structure, using arquillian, to test the rtgov switchyard services provider. The situations provider can be tested outside the app server. -- 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 From issues at jboss.org Thu Feb 13 05:57:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Feb 2014 05:57:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-349) Integration tests for switchyard services provider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-349. ------------------------------ Resolution: Done > Integration tests for switchyard services provider > -------------------------------------------------- > > Key: RTGOV-349 > URL: https://issues.jboss.org/browse/RTGOV-349 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Setup an integration test structure, using arquillian, to test the rtgov switchyard services provider. The situations provider can be tested outside the app server. -- 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 From issues at jboss.org Thu Feb 13 05:57:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Feb 2014 05:57:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-349) Integration tests for switchyard services provider In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-349: ----------------------------- Component/s: User Interface > Integration tests for switchyard services provider > -------------------------------------------------- > > Key: RTGOV-349 > URL: https://issues.jboss.org/browse/RTGOV-349 > Project: RTGov (Run Time Governance) > Issue Type: Task > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Setup an integration test structure, using arquillian, to test the rtgov switchyard services provider. The situations provider can be tested outside the app server. -- 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 From issues at jboss.org Thu Feb 13 06:53:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Feb 2014 06:53:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-351) SwitchYard services provider should support remote JMX URL with authentication In-Reply-To: References: Message-ID: Gary Brown created RTGOV-351: -------------------------------- Summary: SwitchYard services provider should support remote JMX URL with authentication Key: RTGOV-351 URL: https://issues.jboss.org/browse/RTGOV-351 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown SwitchYard services provider supports JMX, but currently uses the local platform MBeanServer. Need to extend to use a remote JMX MBeanServer via a specified URL, that may also require configuration of a username and password. -- 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 From issues at jboss.org Thu Feb 13 06:53:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Feb 2014 06:53:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-351) SwitchYard services provider should support remote JMX URL with authentication In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-351: ----------------------------- Fix Version/s: 2.0.0.M1 > SwitchYard services provider should support remote JMX URL with authentication > ------------------------------------------------------------------------------ > > Key: RTGOV-351 > URL: https://issues.jboss.org/browse/RTGOV-351 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > SwitchYard services provider supports JMX, but currently uses the local platform MBeanServer. > Need to extend to use a remote JMX MBeanServer via a specified URL, that may also require configuration of a username and password. -- 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 From issues at jboss.org Thu Feb 13 10:49:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Feb 2014 10:49:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-350) JMX based switchyard service provider in rtgov UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-350. ------------------------------ Resolution: Done > JMX based switchyard service provider in rtgov UI > ------------------------------------------------- > > Key: RTGOV-350 > URL: https://issues.jboss.org/browse/RTGOV-350 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Current DMR approach will not be portable across switchyard deployments (e.g. EAP and Fuse), so need to switch to JMX. -- 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 From issues at jboss.org Thu Feb 13 10:49:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Feb 2014 10:49:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-350) JMX based switchyard service provider in rtgov UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-350: ----------------------------- Component/s: User Interface > JMX based switchyard service provider in rtgov UI > ------------------------------------------------- > > Key: RTGOV-350 > URL: https://issues.jboss.org/browse/RTGOV-350 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Current DMR approach will not be portable across switchyard deployments (e.g. EAP and Fuse), so need to switch to JMX. -- 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 From issues at jboss.org Fri Feb 14 12:13:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Feb 2014 12:13:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-352) Integrate Kibana into the RTGov UI In-Reply-To: References: Message-ID: Gary Brown created RTGOV-352: -------------------------------- Summary: Integrate Kibana into the RTGov UI Key: RTGOV-352 URL: https://issues.jboss.org/browse/RTGOV-352 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Integrate Kibana into the new RTGov UI, to enable user to analyse activity, situation and response time information. -- 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 From issues at jboss.org Fri Feb 14 12:19:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Feb 2014 12:19:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-353) Default kibana dashboard for RTGov UI In-Reply-To: References: Message-ID: Gary Brown created RTGOV-353: -------------------------------- Summary: Default kibana dashboard for RTGov UI Key: RTGOV-353 URL: https://issues.jboss.org/browse/RTGOV-353 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Need to define a suitable default dashboard for kibana, to provide access to services and the activity/response time information associated with them. -- 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 From issues at jboss.org Fri Feb 14 12:19:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Feb 2014 12:19:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-352) Integrate Kibana into the RTGov UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-352. ------------------------------ Resolution: Done > Integrate Kibana into the RTGov UI > ---------------------------------- > > Key: RTGOV-352 > URL: https://issues.jboss.org/browse/RTGOV-352 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Integrate Kibana into the new RTGov UI, to enable user to analyse activity, situation and response time information. -- 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 From issues at jboss.org Fri Feb 14 12:19:28 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Feb 2014 12:19:28 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-352) Integrate Kibana into the RTGov UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-352: ----------------------------- Component/s: User Interface > Integrate Kibana into the RTGov UI > ---------------------------------- > > Key: RTGOV-352 > URL: https://issues.jboss.org/browse/RTGOV-352 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Integrate Kibana into the new RTGov UI, to enable user to analyse activity, situation and response time information. -- 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 From issues at jboss.org Tue Feb 18 10:57:48 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Tue, 18 Feb 2014 10:57:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-330) Allow situations to be allocated/assigned to individual In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on RTGOV-330 started by Michael Clay. > 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: Michael Clay > > 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 From issues at jboss.org Tue Feb 18 10:57:48 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Tue, 18 Feb 2014 10:57:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-333) Enable user to filter situations based on allocation status In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clay resolved RTGOV-333. -------------------------------- Resolution: Done > Enable user to filter situations based on allocation status > ----------------------------------------------------------- > > Key: RTGOV-333 > URL: https://issues.jboss.org/browse/RTGOV-333 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > The list of situations shown on the main page can be filtered using criteria on the left panel. > Add a new criteria to enable the list of situations to be filtered on the allocation status of: All, Assigned to me, Unassigned. > The server side should be updated to implement this new filtering criteria. -- 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 From issues at jboss.org Wed Feb 19 07:41:47 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Wed, 19 Feb 2014 07:41:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-354) Situation Assignment not working in EAP environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wittmann updated RTGOV-354: -------------------------------- Description: The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it. As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered. Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService): {code} @Inject javax.enterprise.inject.Instance voidHandlerFactory; VoidHandler vh = voidHandlerFactory.get(); {code} was: The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it. As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered. Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService): @Inject javax.enterprise.inject.Instance voidHandlerFactory; VoidHandler vh = voidHandlerFactory.get(); > Situation Assignment not working in EAP environment > --------------------------------------------------- > > Key: RTGOV-354 > URL: https://issues.jboss.org/browse/RTGOV-354 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Eric Wittmann > > The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it. > As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered. > Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService): > {code} > @Inject javax.enterprise.inject.Instance voidHandlerFactory; > VoidHandler vh = voidHandlerFactory.get(); > {code} -- 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 From issues at jboss.org Wed Feb 19 07:41:47 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Wed, 19 Feb 2014 07:41:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-354) Situation Assignment not working in EAP environment In-Reply-To: References: Message-ID: Eric Wittmann created RTGOV-354: ----------------------------------- Summary: Situation Assignment not working in EAP environment Key: RTGOV-354 URL: https://issues.jboss.org/browse/RTGOV-354 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Eric Wittmann The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it. As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered. Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService): @Inject javax.enterprise.inject.Instance voidHandlerFactory; VoidHandler vh = voidHandlerFactory.get(); -- 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 From issues at jboss.org Fri Feb 21 07:39:48 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Fri, 21 Feb 2014 07:39:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-114) Apply PatternFly to s-ramp UI In-Reply-To: References: Message-ID: Eric Wittmann created SRAMPUI-114: ------------------------------------- Summary: Apply PatternFly to s-ramp UI Key: SRAMPUI-114 URL: https://issues.jboss.org/browse/SRAMPUI-114 Project: S-RAMP UI Issue Type: Task Reporter: Eric Wittmann Assignee: Eric Wittmann https://www.patternfly.org/ -- 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 From issues at jboss.org Fri Feb 21 07:39:49 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Fri, 21 Feb 2014 07:39:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-114) Apply PatternFly to s-ramp UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMPUI-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wittmann updated SRAMPUI-114: ---------------------------------- Fix Version/s: Future (Unscheduled) > Apply PatternFly to s-ramp UI > ----------------------------- > > Key: SRAMPUI-114 > URL: https://issues.jboss.org/browse/SRAMPUI-114 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Future (Unscheduled) > > > https://www.patternfly.org/ -- 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 From issues at jboss.org Fri Feb 21 09:03:48 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Fri, 21 Feb 2014 09:03:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-354) Situation Assignment not working in EAP environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wittmann reassigned RTGOV-354: ----------------------------------- Assignee: Michael Clay > Situation Assignment not working in EAP environment > --------------------------------------------------- > > Key: RTGOV-354 > URL: https://issues.jboss.org/browse/RTGOV-354 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Michael Clay > > The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it. > As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered. > Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService): > {code} > @Inject javax.enterprise.inject.Instance voidHandlerFactory; > VoidHandler vh = voidHandlerFactory.get(); > {code} -- 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 From issues at jboss.org Mon Feb 24 06:09:48 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Feb 2014 06:09:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-354) Situation Assignment not working in EAP environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-354. ------------------------------ Resolution: Done > Situation Assignment not working in EAP environment > --------------------------------------------------- > > Key: RTGOV-354 > URL: https://issues.jboss.org/browse/RTGOV-354 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Michael Clay > > The "assign" button works in the mock (dev) environment but fails in the EAP runtime environment. The Assign button appears in the UI but clicking on it has no apparent effect. Perhaps an error is being thrown by the server, but it is not logged on the EAP console and the UI does not respond to it. > As part of fixing this defect I recommend enhancing the VOID rpc handler to use the notification service to report any errors encountered. > Note: you can use the following to create managed instances of an RPC handler (into which you can inject the NotificationService): > {code} > @Inject javax.enterprise.inject.Instance voidHandlerFactory; > VoidHandler vh = voidHandlerFactory.get(); > {code} -- 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 From issues at jboss.org Mon Feb 24 06:09:49 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Feb 2014 06:09:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-330) Allow situations to be allocated/assigned to individual In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-330. ------------------------------ Resolution: Done > 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: Michael Clay > > 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 From issues at jboss.org Tue Feb 25 05:11:47 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 25 Feb 2014 05:11:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-355) UI integration tests fail when run as part of full build In-Reply-To: References: Message-ID: Gary Brown created RTGOV-355: -------------------------------- Summary: UI integration tests fail when run as part of full build Key: RTGOV-355 URL: https://issues.jboss.org/browse/RTGOV-355 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 When the switchyard integration tests are performed as part of a full build of the rtgov-ui, they fail with the following issue: {noformat} org.overlord.rtgov.ui.tests.services.switchyard.SwitchYardServicesProviderTest Time elapsed: 31011 sec <<< ERROR! java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.overlord.rtgov.ui.tests.services.switchyard.SwitchYardServicesProviderTest.createDeployment1() at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:160) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:94) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:57) at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:156) ... 56 more Caused by: java.lang.RuntimeException: Could not parse pom.xml: /home/gbrown/repositories/overlord/objectiser/rtgov-ui/rtgov-ui-core/pom.xml at org.jboss.shrinkwrap.resolver.impl.maven.aether.ClasspathWorkspaceReader.createFoundArtifact(ClasspathWorkspaceReader.java:307) at org.jboss.shrinkwrap.resolver.impl.maven.aether.ClasspathWorkspaceReader.getFoundArtifact(ClasspathWorkspaceReader.java:272) at org.jboss.shrinkwrap.resolver.impl.maven.aether.ClasspathWorkspaceReader.findArtifact(ClasspathWorkspaceReader.java:194) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:296) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:281) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186) at org.sonatype.aether.impl.internal.DefaultDependencyCollector.process(DefaultDependencyCollector.java:412) at org.sonatype.aether.impl.internal.DefaultDependencyCollector.process(DefaultDependencyCollector.java:544) at org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:240) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:333) at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenRepositorySystem.resolveDependencies(MavenRepositorySystem.java:114) at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.resolveDependencies(MavenWorkingSessionImpl.java:256) at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.using(MavenStrategyStageBaseImpl.java:67) at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.withTransitivity(MavenStrategyStageBaseImpl.java:49) at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.withTransitivity(MavenStrategyStageBaseImpl.java:38) at org.overlord.rtgov.ui.tests.services.switchyard.SwitchYardServicesProviderTest.createDeployment1(SwitchYardServicesProviderTest.java:65) ... 61 more Caused by: org.xml.sax.SAXParseException; systemId: file:/home/gbrown/repositories/overlord/objectiser/rtgov-ui/rtgov-ui-core/pom.xml; lineNumber: 56; columnNumber: 3; The markup in the document following the root element must be well-formed. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:251) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:300) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:205) at org.jboss.shrinkwrap.resolver.impl.maven.aether.ClasspathWorkspaceReader.loadPom(ClasspathWorkspaceReader.java:313) at org.jboss.shrinkwrap.resolver.impl.maven.aether.ClasspathWorkspaceReader.createFoundArtifact(ClasspathWorkspaceReader.java:286) ... 78 more {noformat} However when just the tests are performed on their own, they work. -- 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 From issues at jboss.org Tue Feb 25 05:19:47 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 25 Feb 2014 05:19:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-356) Move checkstyle config from rtgov to overlord-commons In-Reply-To: References: Message-ID: Gary Brown created RTGOV-356: -------------------------------- Summary: Move checkstyle config from rtgov to overlord-commons Key: RTGOV-356 URL: https://issues.jboss.org/browse/RTGOV-356 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Currently the checkstyle configuration is in rtgov repo. But should be moved to overlord-commons so can be shared across all overlord projects. -- 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 From issues at jboss.org Tue Feb 25 10:57:47 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 25 Feb 2014 10:57:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-357) Gadget web fails to display pages due to underlying join column name change In-Reply-To: References: Message-ID: Gary Brown created RTGOV-357: -------------------------------- Summary: Gadget web fails to display pages due to underlying join column name change Key: RTGOV-357 URL: https://issues.jboss.org/browse/RTGOV-357 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Page join column name changed to avoid conflict in ORACLE, but not updated in default schema created for h2 db. -- 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 From issues at jboss.org Tue Feb 25 12:07:48 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 25 Feb 2014 12:07:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-358) Dynamic inclusion of extensions in the Overlord UI In-Reply-To: References: Message-ID: Gary Brown created RTGOV-358: -------------------------------- Summary: Dynamic inclusion of extensions in the Overlord UI Key: RTGOV-358 URL: https://issues.jboss.org/browse/RTGOV-358 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Eric Wittmann Consider how it would be possible to have hot deployable (if possible), but atleast dynamic (without compilation) inclusion of additional screens within the Overlord UI. They should appear as top level tabs (or atleast as sub-tabs within an 'extension' area), and participate in the Overlord UI SSO session. -- 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 From issues at jboss.org Tue Feb 25 13:31:47 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Tue, 25 Feb 2014 13:31:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-332) Record message resubmission details against situation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clay reassigned RTGOV-332: ---------------------------------- Assignee: Michael Clay (was: Gary Brown) > 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: Michael Clay > > 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 From issues at jboss.org Wed Feb 26 04:59:47 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 26 Feb 2014 04:59:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-358) Dynamic inclusion of extensions in the Overlord UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown closed RTGOV-358. ---------------------------- Resolution: Done After discussion with Eric, this can already be done by include a war for the extension pages with an additional properties file in the config/overlord-apps folder. > Dynamic inclusion of extensions in the Overlord UI > -------------------------------------------------- > > Key: RTGOV-358 > URL: https://issues.jboss.org/browse/RTGOV-358 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Eric Wittmann > > Consider how it would be possible to have hot deployable (if possible), but atleast dynamic (without compilation) inclusion of additional screens within the Overlord UI. > They should appear as top level tabs (or atleast as sub-tabs within an 'extension' area), and participate in the Overlord UI SSO session. -- 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 From issues at jboss.org Thu Feb 27 05:30:47 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 27 Feb 2014 05:30:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-359) "Value too long" error when storing resubmit failure result In-Reply-To: References: Message-ID: Gary Brown created RTGOV-359: -------------------------------- Summary: "Value too long" error when storing resubmit failure result Key: RTGOV-359 URL: https://issues.jboss.org/browse/RTGOV-359 Project: RTGov (Run Time Governance) Issue Type: Bug Components: User Interface Reporter: Gary Brown Assignee: Michael Clay Related to RTGOV-332. When a failure occurs resubmitting the message, the result is stored in a property associated with the situation. However there is a length restriction of VARCHAR(255) on this field: 10:08:01,249 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-3) Value too long for column "VALUE VARCHAR(255)": "STRINGDECODE('org.overlord.rtgov.ui.client.model.UiException: org.switchyard.HandlerException: SWITCHYARD014000: Validator ''org... (12795)"; SQL statement: insert into RTGOV_SITUATION_PROPERTIES (id, name, value) values (?, ?, ?) [22001-168] The original intention of the result field was to report whether the message had been resubmitted successfully or not. Therefore we have a few options: 1) Just report 'successful' or 'failed' in this field - however this doesn't give an indication of why the resubmit failed. Although the failure is reported at the time when the resubmit is performed, so just depends whether we actually want the resubmission error to be persisted? 2) Truncate the error message - probably 250 characters would be enough anyway? However we should prefix the result with "Failed: ". Probably option 2 is best, although need to also ensure that a 'Successful' result is also recorded. -- 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 From issues at jboss.org Thu Feb 27 05:34:47 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 27 Feb 2014 05:34:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-360) Move the 'resubmit' fields closer to the resubmit button In-Reply-To: References: Message-ID: Gary Brown created RTGOV-360: -------------------------------- Summary: Move the 'resubmit' fields closer to the resubmit button Key: RTGOV-360 URL: https://issues.jboss.org/browse/RTGOV-360 Project: RTGov (Run Time Governance) Issue Type: Enhancement Components: User Interface Reporter: Gary Brown Assignee: Michael Clay Currently the resubmit by, at and result fields are displayed above the message content. I think it would be better if this information was displayed along side the 'resubmit' button, and only information once a resubmission has been performed. The text should then be of the form: Resubmitted by 'xyz' at 'date and time': 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 From issues at jboss.org Thu Feb 27 05:48:48 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Thu, 27 Feb 2014 05:48:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-359) "Value too long" error when storing resubmit failure result In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12948596#comment-12948596 ] Michael Clay commented on RTGOV-359: ------------------------------------ i think option 2 is the way to go but why not also increase the column length because 250 chars are not much for a stacktrace? pls note that there are already 2 result properties to differentiate between successful (resubmitResult = OK )and 'erroneous' resubmit (resubmitFailure = stacktrace) > "Value too long" error when storing resubmit failure result > ----------------------------------------------------------- > > Key: RTGOV-359 > URL: https://issues.jboss.org/browse/RTGOV-359 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Related to RTGOV-332. > When a failure occurs resubmitting the message, the result is stored in a property associated with the situation. However there is a length restriction of VARCHAR(255) on this field: > 10:08:01,249 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-3) Value too long for column "VALUE VARCHAR(255)": "STRINGDECODE('org.overlord.rtgov.ui.client.model.UiException: org.switchyard.HandlerException: SWITCHYARD014000: Validator ''org... (12795)"; SQL statement: > insert into RTGOV_SITUATION_PROPERTIES (id, name, value) values (?, ?, ?) [22001-168] > The original intention of the result field was to report whether the message had been resubmitted successfully or not. Therefore we have a few options: > 1) Just report 'successful' or 'failed' in this field - however this doesn't give an indication of why the resubmit failed. Although the failure is reported at the time when the resubmit is performed, so just depends whether we actually want the resubmission error to be persisted? > 2) Truncate the error message - probably 250 characters would be enough anyway? However we should prefix the result with "Failed: ". > Probably option 2 is best, although need to also ensure that a 'Successful' result is also recorded. -- 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 From issues at jboss.org Thu Feb 27 06:02:48 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 27 Feb 2014 06:02:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-359) "Value too long" error when storing resubmit failure result In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12948599#comment-12948599 ] Gary Brown commented on RTGOV-359: ---------------------------------- Aim is to currently allow the UI to be deployed on the current version of the product, which has this column length limitation. Also not sure having a complete stack trace is ideal - the field should just be providing an indication of the problem. The problem with the 'successful' status is that it is not being reported in the UI - the result field only appears to be used for reporting the failure result. It might be nice if the basic message just reports success or failure (with the by and date/time fields), but provide a hoverover/popup with the failure details when relevant? > "Value too long" error when storing resubmit failure result > ----------------------------------------------------------- > > Key: RTGOV-359 > URL: https://issues.jboss.org/browse/RTGOV-359 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Related to RTGOV-332. > When a failure occurs resubmitting the message, the result is stored in a property associated with the situation. However there is a length restriction of VARCHAR(255) on this field: > 10:08:01,249 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-3) Value too long for column "VALUE VARCHAR(255)": "STRINGDECODE('org.overlord.rtgov.ui.client.model.UiException: org.switchyard.HandlerException: SWITCHYARD014000: Validator ''org... (12795)"; SQL statement: > insert into RTGOV_SITUATION_PROPERTIES (id, name, value) values (?, ?, ?) [22001-168] > The original intention of the result field was to report whether the message had been resubmitted successfully or not. Therefore we have a few options: > 1) Just report 'successful' or 'failed' in this field - however this doesn't give an indication of why the resubmit failed. Although the failure is reported at the time when the resubmit is performed, so just depends whether we actually want the resubmission error to be persisted? > 2) Truncate the error message - probably 250 characters would be enough anyway? However we should prefix the result with "Failed: ". > Probably option 2 is best, although need to also ensure that a 'Successful' result is also recorded. -- 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 From issues at jboss.org Thu Feb 27 10:53:47 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 27 Feb 2014 10:53:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-361) Migrate from sramp UI widgets to those in overlord-commons In-Reply-To: References: Message-ID: Gary Brown created RTGOV-361: -------------------------------- Summary: Migrate from sramp UI widgets to those in overlord-commons Key: RTGOV-361 URL: https://issues.jboss.org/browse/RTGOV-361 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Some GWT based UI widgets have been moved from sramp to overlord-commons. Try migrating rtgov-ui to use the overlord-commons widgets, to remove the dependency on sramp. -- 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 From issues at jboss.org Thu Feb 27 11:17:48 2014 From: issues at jboss.org (Kurt Stam (JIRA)) Date: Thu, 27 Feb 2014 11:17:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-264) password with '!' breaks login In-Reply-To: References: Message-ID: Kurt Stam created SRAMP-264: ------------------------------- Summary: password with '!' breaks login Key: SRAMP-264 URL: https://issues.jboss.org/browse/SRAMP-264 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Shell Reporter: Kurt Stam Assignee: Kurt Stam Fix For: 0.4.0 - API Management My password contains an exclamation mark: 'admin!23'. s-ramp> s-ramp:connect http://localhost:8080/s-ramp-server S-RAMP Username: admin S-RAMP Password: ******** java.lang.IllegalArgumentException: !23: event not found -- 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 From issues at jboss.org Thu Feb 27 11:17:48 2014 From: issues at jboss.org (Kurt Stam (JIRA)) Date: Thu, 27 Feb 2014 11:17:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-264) password with '!' breaks login In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt Stam updated SRAMP-264: ---------------------------- Assignee: Eric Wittmann (was: Kurt Stam) > password with '!' breaks login > ------------------------------ > > Key: SRAMP-264 > URL: https://issues.jboss.org/browse/SRAMP-264 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.4.0 - API Management > > > My password contains an exclamation mark: 'admin!23'. > s-ramp> s-ramp:connect http://localhost:8080/s-ramp-server > S-RAMP Username: admin > S-RAMP Password: ******** > java.lang.IllegalArgumentException: !23: event not found -- 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 From issues at jboss.org Thu Feb 27 11:41:47 2014 From: issues at jboss.org (Kurt Stam (JIRA)) Date: Thu, 27 Feb 2014 11:41:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-265) persist s-ramp data on tomcat In-Reply-To: References: Message-ID: Kurt Stam created SRAMP-265: ------------------------------- Summary: persist s-ramp data on tomcat Key: SRAMP-265 URL: https://issues.jboss.org/browse/SRAMP-265 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Persistence Environment: tomcat Reporter: Kurt Stam Assignee: Eric Wittmann Fix For: 0.4.0 - API Management Need a different modeshape json config file to turn on persistence -- 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 From issues at jboss.org Thu Feb 27 11:57:48 2014 From: issues at jboss.org (Kurt Stam (JIRA)) Date: Thu, 27 Feb 2014 11:57:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-266) on tomcat password is in two places In-Reply-To: References: Message-ID: Kurt Stam created SRAMP-266: ------------------------------- Summary: on tomcat password is in two places Key: SRAMP-266 URL: https://issues.jboss.org/browse/SRAMP-266 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Governance Environment: tomcat Reporter: Kurt Stam Assignee: Eric Wittmann Fix For: 0.4.0 - API Management This maybe a commons issue, but the admin/pw is in tomcat-users.xml as well as in tomcat-users-overlord.xml. One file should be sufficient I think? -- 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 From issues at jboss.org Thu Feb 27 12:19:47 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 27 Feb 2014 12:19:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-267) Migrate gwt/bootstrap widgets to overlord-commons In-Reply-To: References: Message-ID: Gary Brown created SRAMP-267: -------------------------------- Summary: Migrate gwt/bootstrap widgets to overlord-commons Key: SRAMP-267 URL: https://issues.jboss.org/browse/SRAMP-267 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Kurt Stam Some of the common bootstrap/gwt related widgets have been moved to overlord-commons, to be shared across overlord projects. This issue is to: 1) Move any remaining widgets that are still only in sramp repo 2) Migrate sramp (and possibly dtgov) across to use the overload-commons version of the widgets, and remove the sramp copy. -- 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 From issues at jboss.org Thu Feb 27 13:29:47 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Thu, 27 Feb 2014 13:29:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-359) "Value too long" error when storing resubmit failure result In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clay resolved RTGOV-359. -------------------------------- Resolution: Done see pull request > "Value too long" error when storing resubmit failure result > ----------------------------------------------------------- > > Key: RTGOV-359 > URL: https://issues.jboss.org/browse/RTGOV-359 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Related to RTGOV-332. > When a failure occurs resubmitting the message, the result is stored in a property associated with the situation. However there is a length restriction of VARCHAR(255) on this field: > 10:08:01,249 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-3) Value too long for column "VALUE VARCHAR(255)": "STRINGDECODE('org.overlord.rtgov.ui.client.model.UiException: org.switchyard.HandlerException: SWITCHYARD014000: Validator ''org... (12795)"; SQL statement: > insert into RTGOV_SITUATION_PROPERTIES (id, name, value) values (?, ?, ?) [22001-168] > The original intention of the result field was to report whether the message had been resubmitted successfully or not. Therefore we have a few options: > 1) Just report 'successful' or 'failed' in this field - however this doesn't give an indication of why the resubmit failed. Although the failure is reported at the time when the resubmit is performed, so just depends whether we actually want the resubmission error to be persisted? > 2) Truncate the error message - probably 250 characters would be enough anyway? However we should prefix the result with "Failed: ". > Probably option 2 is best, although need to also ensure that a 'Successful' result is also recorded. -- 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 From issues at jboss.org Thu Feb 27 13:33:47 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Thu, 27 Feb 2014 13:33:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-360) Move the 'resubmit' fields closer to the resubmit button In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on RTGOV-360 started by Michael Clay. > Move the 'resubmit' fields closer to the resubmit button > -------------------------------------------------------- > > Key: RTGOV-360 > URL: https://issues.jboss.org/browse/RTGOV-360 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Currently the resubmit by, at and result fields are displayed above the message content. I think it would be better if this information was displayed along side the 'resubmit' button, and only information once a resubmission has been performed. > The text should then be of the form: > Resubmitted by 'xyz' at 'date and time': 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 From issues at jboss.org Thu Feb 27 14:29:47 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Thu, 27 Feb 2014 14:29:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-360) Move the 'resubmit' fields closer to the resubmit button In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clay resolved RTGOV-360. -------------------------------- Resolution: Done > Move the 'resubmit' fields closer to the resubmit button > -------------------------------------------------------- > > Key: RTGOV-360 > URL: https://issues.jboss.org/browse/RTGOV-360 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Currently the resubmit by, at and result fields are displayed above the message content. I think it would be better if this information was displayed along side the 'resubmit' button, and only information once a resubmission has been performed. > The text should then be of the form: > Resubmitted by 'xyz' at 'date and time': 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 From issues at jboss.org Thu Feb 27 14:33:47 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Thu, 27 Feb 2014 14:33:47 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-339) Date/time range filter does not currently allow time to be specified In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clay reassigned RTGOV-339: ---------------------------------- Assignee: Michael Clay (was: Gary Brown) > Date/time range filter does not currently allow time to be specified > -------------------------------------------------------------------- > > Key: RTGOV-339 > URL: https://issues.jboss.org/browse/RTGOV-339 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Components: User Interface > Reporter: Gary Brown > Assignee: Michael Clay > > Date/time filter only currently allows the date to be specified, which only allows the granularity to be at the level of days. > We need the user to be able to specify the filter down to the seconds level of granularity. -- 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