November 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-312) Intermittent "entry point not found" issue with example Drools rules

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-312?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-312: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1028779 > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-312) Intermittent "entry point not found" issue with example Drools rules

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-312?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-312: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> made a comment on [bug 1028779|https://bugzilla.redhat.com/show_bug.cgi?id=1028779] Description of problem: Drools 6.0.0.CR5 appears to have introduced an intermittent issue where events being processed against the SLAViolation rule do not locate the 'ServiceResponseTimes' entry point. With drools debug enabled, it shows: 15:47:59,902 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (ServerService Thread Pool -- 66) KieModule was added:MemoryKieModule[ ReleaseId=org.default:artifact:1.0.0-SNAPSHOT] 15:47:59,901 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (ServerService Thread Pool -- 72) KieModule was added:MemoryKieModule[ ReleaseId=org.default:artifact:1.0.0-SNAPSHOT] 15:48:00,040 DEBUG [org.drools.core.reteoo.ReteooRuleBase] (ServerService Thread Pool -- 66) Starting Engine in PHREAK mode 15:48:00,042 DEBUG [org.drools.core.reteoo.ReteooRuleBase] (ServerService Thread Pool -- 72) Starting Engine in PHREAK mode 15:48:00,115 TRACE [org.drools.core.phreak.AddRemoveRule] (ServerService Thread Pool -- 66) Adding Rule Create situation to represent exception 15:48:00,149 TRACE [org.drools.core.phreak.AddRemoveRule] (ServerService Thread Pool -- 72) Adding Rule Create situation to represent exception 15:48:00,175 TRACE [org.drools.core.reteoo.SegmentMemory] (ServerService Thread Pool -- 72) LinkNode notify=true nmask=1 smask=1 spos=0 rules=[RuleMem Create situation to represent exception] 15:48:00,176 TRACE [org.drools.core.reteoo.SegmentMemory] (ServerService Thread Pool -- 66) LinkNode notify=true nmask=1 smask=1 spos=0 rules=[RuleMem Create situation to represent exception] 15:48:00,192 FINEST [org.overlord.rtgov.ep.drools.DroolsEventProcessor] (ServerService Thread Pool -- 72) DroolsEventProcessor init: ruleName=SLAViolation session=org.drools.core.impl.StatefulKnowledgeSessionImpl@7b1868c3 15:48:00,192 FINEST [org.overlord.rtgov.ep.drools.DroolsEventProcessor] (ServerService Thread Pool -- 66) DroolsEventProcessor init: ruleName=RaiseSituationForException session=org.drools.core.impl.StatefulKnowledgeSessionImpl@7f861957 Two different rules are being initialized in separate threads, 'SLAViolation' and 'RaiseSituationForException'. However in the TRACE lines, it shows that one rules has been initialized in both threads. Solution is to synchronize the creation of the session. > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-312) Intermittent "entry point not found" issue with example Drools rules

by Gary Brown (JIRA)

Gary Brown created RTGOV-312: -------------------------------- Summary: 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-247) Change switchyard event listener to use ExchangeInitiated/CompletedEvents

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-247?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-247: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from NEW to MODIFIED > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-311) Switchyard Exchange Validator needs to change to use ExchangeInterceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-311?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-311: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1026698 > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-311) Switchyard Exchange Validator needs to change to use ExchangeInterceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-311?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-311: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from NEW to MODIFIED > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-247) Change switchyard event listener to use ExchangeInitiated/CompletedEvents

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-247?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-247: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1026698 > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-311) Switchyard Exchange Validator needs to change to use ExchangeInterceptor

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-311?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-311. ------------------------------ Resolution: Done > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-247) Change switchyard event listener to use ExchangeInitiated/CompletedEvents

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-247?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-247. ------------------------------ Resolution: Done > 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-311) Switchyard Exchange Validator needs to change to use ExchangeInterceptor

by Gary Brown (JIRA)

Gary Brown created RTGOV-311: -------------------------------- Summary: 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues November 2013