[Red Hat JIRA] (DROOLS-5958) Order of statements described in rule action part does not keep after model generation in executable model.
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5958?page=com.atlassian.jira.plug... ]
Luca Molteni moved RHDM-1581 to DROOLS-5958:
--------------------------------------------
Component/s: executable model
(was: BRE)
Docs QE Status: NEW
Key: DROOLS-5958 (was: RHDM-1581)
QE Status: NEW
Affects Version/s: (was: 7.5.0.GA)
(was: 7.6.0.GA)
(was: 7.5.1.GA)
(was: 7.7.0.GA)
(was: 7.8.0.GA)
(was: 7.7.1.GA)
(was: 7.9.0.GA)
(was: 7.8.1.GA)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Project: Drools (was: Red Hat Decision Manager)
> Order of statements described in rule action part does not keep after model generation in executable model.
> -----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5958
> URL: https://issues.redhat.com/browse/DROOLS-5958
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
> Attachments: reproducer_model_compiler_14a.zip
>
>
> Building a rule written in MVEL dialect like (*1) in executable rule model, the order of the statements described in action ({{then}}) part of the rule changes after model generation like (\*2). The generated code looks like that all statements outside the {{modify}} blocks come first, followed by all statements inside the {{modify}} blocks, and finally {{update}} statements for the modified properties are called together. The original order of the statements in action part should keep after model generation.
> (\*1)
> {noformat}
> package com.example.reproducer
> dialect "mvel"
> rule "rule14a"
> when
> $manufacturer : Manufacturer()
> $model : Model( manufacturer == $manufacturer )
> $car : Car( model == $model )
> then
> System.out.println("***** Action of rule14a");
> modify($model) {
> count = $model.count + 1
> }
> System.out.println("$model = " + $model + ", count = " + $model.count);
> modify($manufacturer) {
> totalCount = $manufacturer.totalCount + 1
> }
> System.out.println("$manufacturer = " + $manufacturer + ", totalCount = " + $manufacturer.totalCount);
> end
> {noformat}
> (\*2) {{LambdaConsequence<_hash_>.java}} generated from the action ({{then}}) part of the rule.
> {noformat}
> @Override()
> public void execute(org.drools.model.Drools drools, com.example.reproducer.Model $model, com.example.reproducer.Manufacturer $manufacturer) throws java.lang.Exception {
> System.out.println("***** Action of rule14a");
> System.out.println("$model = " + $model + ", count = " + $model.getCount());
> System.out.println("$manufacturer = " + $manufacturer + ", totalCount = " + $manufacturer.getTotalCount());
> $model.setCount($model.getCount() + 1);
> $manufacturer.setTotalCount($manufacturer.getTotalCount() + 1);
> drools.update($model, mask_$model);
> drools.update($manufacturer, mask_$manufacturer);
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14038) Intermittent failure MeterTest.testRates org.eclipse.microprofile.metrics.tck.metrics
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFLY-14038?page=com.atlassian.jira.plugi... ]
Jeff Mesnil reassigned WFLY-14038:
----------------------------------
Assignee: Jason Lee (was: Jeff Mesnil)
> Intermittent failure MeterTest.testRates org.eclipse.microprofile.metrics.tck.metrics
> -------------------------------------------------------------------------------------
>
> Key: WFLY-14038
> URL: https://issues.redhat.com/browse/WFLY-14038
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Cheng Fang
> Assignee: Jason Lee
> Priority: Major
>
> In WildFly CI, the test {{MeterTest.testRates org.eclipse.microprofile.metrics.tck.metrics}} failed intermittently.
> For exmaple, in [this Windows JDK 11 test run|https://ci.wildfly.org/buildConfiguration/WF_PullRequest_WindowsJdk11...].
> {code}
> java.lang.AssertionError: expected:<100.0> but was:<112.03899899654196>
> at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.junit.Assert.fail(Assert.java:89)
> at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.junit.Assert.failNotEquals(Assert.java:835)
> at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.junit.Assert.assertEquals(Assert.java:555)
> at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.junit.Assert.assertEquals(Assert.java:685)
> at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.eclipse.microprofile.metrics.tck.util.TestUtils.assertEqualsWithTolerance(TestUtils.java:41)
> at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.eclipse.microprofile.metrics.tck.metrics.MeterTest.testRates(MeterTest.java:96)
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFLY-11933?page=com.atlassian.jira.plugi... ]
Jeff Mesnil reassigned WFLY-11933:
----------------------------------
Assignee: Jason Lee (was: Jeff Mesnil)
> Error when accessing metrics with RBAC enabled
> ----------------------------------------------
>
> Key: WFLY-11933
> URL: https://issues.redhat.com/browse/WFLY-11933
> Project: WildFly
> Issue Type: Bug
> Components: Management, MP Metrics
> Affects Versions: 16.0.0.Final, 17.0.0.Final, 17.0.1.Final, 21.0.0.Final
> Reporter: Claudio Weiler
> Assignee: Jason Lee
> Priority: Major
>
> Accordingly to https://docs.wildfly.org/17/Admin_Guide.html#http-endpoint-2 and https://wildscribe.github.io/WildFly/17.0/subsystem/microprofile-metrics-..., access to metrics endpoint is controlled by the security-enabled attribute.
> When this attribute is set to false, there is an Exception when metrics are accessed. By default, this attribute is set to false on standalone.xml config.
> Please, refer to steps to reproduce. This error occurs only when RBAC are enabled.
> When RBAC is enabled for management in Wildfly, metrics throws exception:
> java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [
> ("subsystem" => "datasources"),
> ("data-source" => "ExampleDS"),
> ("statistics" => "pool")
> ]: "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\"),
> (\"statistics\" => \"pool\")
> ]' not found".
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-11731) IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFLY-11731?page=com.atlassian.jira.plugi... ]
Jeff Mesnil reassigned WFLY-11731:
----------------------------------
Assignee: Jason Lee (was: Jeff Mesnil)
> IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-11731
> URL: https://issues.redhat.com/browse/WFLY-11731
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Brian Stansberry
> Assignee: Jason Lee
> Priority: Major
>
> CI failure due to $subject -- ConstantRoleMapperTestCase in https://ci.wildfly.org/viewLog.html?buildId=139312&buildTypeId=WFPR&tab=b...
> {code}
> &#27;[0m&#27;[31m11:45:07,066 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildlfy.extension.microprofile.metrics.wildfly-registrar: org.jboss.msc.service.StartException in service org.wildlfy.extension.microprofile.metrics.wildfly-registrar: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
> at io.smallrye.metrics.MetricsRegistryImpl.register(MetricsRegistryImpl.java:113)
> at io.smallrye.metrics.setup.JmxRegistrar.register(JmxRegistrar.java:54)
> at io.smallrye.metrics.setup.JmxRegistrar.register(JmxRegistrar.java:38)
> at io.smallrye.metrics.setup.JmxRegistrar.init(JmxRegistrar.java:30)
> at org.wildfly.extension.microprofile.metrics.MetricsRegistrationService.start(MetricsRegistrationService.java:91)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> ... 6 more
> {code}
> I have a feeling this has already been reported but simple searching didn't find it.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-11638) MP Metrics - sort alphabetically /metrics output
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFLY-11638?page=com.atlassian.jira.plugi... ]
Jeff Mesnil reassigned WFLY-11638:
----------------------------------
Assignee: Jason Lee (was: Jeff Mesnil)
> MP Metrics - sort alphabetically /metrics output
> ------------------------------------------------
>
> Key: WFLY-11638
> URL: https://issues.redhat.com/browse/WFLY-11638
> Project: WildFly
> Issue Type: Enhancement
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jason Lee
> Priority: Major
>
> MP Metrics - sort alphabetically /metrics output
> When playing with https://github.com/wildfly/wildfly/pull/11949 I got upset about metrics not being sorted alphabetically or at least grouped together.
> My use case was to look at wildfly_undertow_** metrics via browser.
> base: and vendor: metrics are grouped together, WF subsystem metrics not - e.g. wildfly_undertow_** metrics were listed on 4 different places.
> If alphabetical order is not easy to be achieved, subsystem metrics should be at least grouped together.
> I know machines do not care about the order, but people have to look at /metrics too (from time to time ...).
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months