July 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-524) Drools processor : Steam mode does handle results of async rule activation

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-524?page=com.atlassian.jira.plugin.... ] ivan mckinley updated RTGOV-524: -------------------------------- Attachment: ordermgmt-demo.zip simple quick start > Drools processor : Steam mode does handle results of async rule activation > --------------------------------------------------------------------------- > > Key: RTGOV-524 > URL: https://issues.jboss.org/browse/RTGOV-524 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Event Processor > Affects Versions: 2.0.0.Final > Reporter: ivan mckinley > Assignee: Gary Brown > Attachments: ordermgmt-demo.zip > > > When a sliding rule is defined of Steam mode and Async Mode of the droolsEventprocessor. Rule is activated but the handling of the results fails with a NPE. > NPE traced back to the Node object responsible for handling the forward of the serialized object as the passed in _container object is null; > See, > https://issues.jboss.org/browse/RTGOV-393 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-524) Drools processor : Steam mode does handle results of async rule activation

by ivan mckinley (JIRA)

ivan mckinley created RTGOV-524: ----------------------------------- Summary: Drools processor : Steam mode does handle results of async rule activation Key: RTGOV-524 URL: https://issues.jboss.org/browse/RTGOV-524 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Components: Event Processor Affects Versions: 2.0.0.Final Reporter: ivan mckinley Assignee: Gary Brown When a sliding rule is defined of Steam mode and Async Mode of the droolsEventprocessor. Rule is activated but the handling of the results fails with a NPE. NPE traced back to the Node object responsible for handling the forward of the serialized object as the passed in _container object is null; See, https://issues.jboss.org/browse/RTGOV-393 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-520) Set "not_analyzed" as the default setting for fields added to rtgov.

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-520?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-520: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > Set "not_analyzed" as the default setting for fields added to rtgov. > --------------------------------------------------------------------- > > Key: RTGOV-520 > URL: https://issues.jboss.org/browse/RTGOV-520 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: ivan mckinley > Assignee: ivan mckinley > Priority: Minor > Fix For: 2.1.0.Final > > > In rtgov-mapping.json. have the mapping set all fields to Not_analyzed. this avoids the issue outlined in https://issues.jboss.org/browse/RTGOV-461 > in there are mappings that required the field to be analyzed then they should be explicitly configured. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-520) Set "not_analyzed" as the default setting for fields added to rtgov.

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-520?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-520: ----------------------------- Parent: (was: RTGOV-419) Issue Type: Enhancement (was: Sub-task) > Set "not_analyzed" as the default setting for fields added to rtgov. > --------------------------------------------------------------------- > > Key: RTGOV-520 > URL: https://issues.jboss.org/browse/RTGOV-520 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: ivan mckinley > Assignee: ivan mckinley > Priority: Minor > Fix For: 2.0.0.Final > > > In rtgov-mapping.json. have the mapping set all fields to Not_analyzed. this avoids the issue outlined in https://issues.jboss.org/browse/RTGOV-461 > in there are mappings that required the field to be analyzed then they should be explicitly configured. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-336) Combine activities recorded across multiple threads

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-336?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-336: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > Combine activities recorded across multiple threads > --------------------------------------------------- > > Key: RTGOV-336 > URL: https://issues.jboss.org/browse/RTGOV-336 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > When capturing activity events via proxies in JBoss Fuse, found that when a service returned an exception, it was handled in a separate thread. > This resulted in two separate activity units, one for the activities up until the exception, and the other for the activities following the exception. > This will cause issues with correlation currently, where request/response pairs are expected to be in the same activity unit. > Two possible solutions: > (1) work on the correlation of requests/responses across activity units - which will be useful in a wider range of cases. > (2) enable activities across multiple threads to be combined - i.e. if a subsequent thread is new, allow its relationship with a previous activity event (e.g. the request) to link it to the same activity unit. Not sure of the implications on the API for this. > This work is related to RTGOV-325. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-453) Create JPA EPN integration test

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-453?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-453: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > Create JPA EPN integration test > ------------------------------- > > Key: RTGOV-453 > URL: https://issues.jboss.org/browse/RTGOV-453 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > RTGOV-374 improved JPA/ORM support, including the ability for an EPN to pass either a JPA persistence.xml or a native Hibernate hibernate.cfg.xml. This is unit tested, but needs incorporated into the integration tests. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-451) Support deployment on Karaf3

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-451?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-451: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > Support deployment on Karaf3 > ---------------------------- > > Key: RTGOV-451 > URL: https://issues.jboss.org/browse/RTGOV-451 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-505) maven:deploy CLI command missing maven.type property sometimes

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-505: ----------------------------------- Summary: maven:deploy CLI command missing maven.type property sometimes Key: SRAMP-505 URL: https://issues.jboss.org/browse/SRAMP-505 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Shell Reporter: Eric Wittmann Assignee: David virgil naranjo Fix For: 0.5.0 The maven:deploy s-ramp cli command does not currently set the maven.type property under all circumstances. A requirement is that maven.type always be set. Currently the CLI command gets this information from the arguments to the command. In some cases the user will not include the "type" information on the command line. In this case the type should be pulled from the file extension of the file being uploaded. If the file being uploaded does *not* have an extension and the maven.type is not provided as part of the GAV argument, then the command should fail. Note: the name of the artifact should also include the file's extension - this is currently being left off. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-523) Situation Call trace UI shows traces for all situations in system

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-523?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-523: ------------------------------------- gotcha, .. Guess I should be generating random data :) > Situation Call trace UI shows traces for all situations in system > ------------------------------------------------------------------ > > Key: RTGOV-523 > URL: https://issues.jboss.org/browse/RTGOV-523 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Interface > Affects Versions: 2.0.0.Final > Reporter: ivan mckinley > Assignee: Gary Brown > Attachments: calltrace.png > > > See screenshot. > Reproduce > - build and deploy ordermanagement example > - build and deploy SLA example > -in the order managemen app/ folder run the order3 which generates SLA situations > mvn exec:java -Dreq=order3 -Dcount=10 > Naviate to the situation UI and select any of the 10 SLAs show. the call trace of the selected situation shows call traces of other situations > see screen shot -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-523) Situation Call trace UI shows traces for all situations in system

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-523?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-523. ------------------------------ Resolution: Rejected Sorry Ivan, I should have checked more details before asking you to raise an issue. The call trace is built up based on correlation between activities. In this case, you have generated 10 business transactions with the same 'conversation' id (i.e. orderId = 3), and therefore from the call trace perspective, they are all part of the same business transaction. > Situation Call trace UI shows traces for all situations in system > ------------------------------------------------------------------ > > Key: RTGOV-523 > URL: https://issues.jboss.org/browse/RTGOV-523 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Interface > Affects Versions: 2.0.0.Final > Reporter: ivan mckinley > Assignee: Gary Brown > Attachments: calltrace.png > > > See screenshot. > Reproduce > - build and deploy ordermanagement example > - build and deploy SLA example > -in the order managemen app/ folder run the order3 which generates SLA situations > mvn exec:java -Dreq=order3 -Dcount=10 > Naviate to the situation UI and select any of the 10 SLAs show. the call trace of the selected situation shows call traces of other situations > see screen shot -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2014