February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-6041) "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-6041?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-6041: -------------------------------------- Description: With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line) {noformat} rule R dialect "mvel" when Person(name == "Mario") then Person p2 = new Person("John"); p2.age = 30 insert(p2); end {noformat} exec-model fails with {noformat} CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type {noformat} while standard-drl runs successfully. I'm not sure if exec-model should work the same as standard-drl (treat a new line as a delimiter?), or give a better error message. This looks to be a rare issue but when using spreadsheet, it's possible to forget to add a semicolon. (Then users don't notice the mistake because standard-drl executes it succesfully) was: With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line) {noformat} rule R dialect "mvel" when Person(name == "Mario") then Person p2 = new Person("John"); p2.age = 30 insert(p2); end {noformat} exec-model fails with {noformat} CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type {noformat} while standard-drl runs successfully. I'm not sure if exec-model should work the same as standard-drl (treat a new line as a delimiter?), or give a better error message. > "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect > -------------------------------------------------------------------------------------------- > > Key: DROOLS-6041 > URL: https://issues.redhat.com/browse/DROOLS-6041 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.50.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line) > {noformat} > rule R > dialect "mvel" > when > Person(name == "Mario") > then > Person p2 = new Person("John"); > p2.age = 30 > insert(p2); > end > {noformat} > exec-model fails with > {noformat} > CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type > {noformat} > while standard-drl runs successfully. > I'm not sure if exec-model should work the same as standard-drl (treat a new line as a delimiter?), or give a better error message. > This looks to be a rare issue but when using spreadsheet, it's possible to forget to add a semicolon. (Then users don't notice the mistake because standard-drl executes it succesfully) -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5292) Remove Java EE References from the i18n strings

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFCORE-5292: -------------------------------------------- Summary: Remove Java EE References from the i18n strings Key: WFCORE-5292 URL: https://issues.redhat.com/browse/WFCORE-5292 Project: WildFly Core Issue Type: Task Components: Server Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana Replace Java EE References from the i18n strings. Those strings are in the various XXXLogger.java files and the LocalDescriptions.properties files. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5969) Rule relationship analysis graph : handling special syntax or usage rules

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5969?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5969: -------------------------------------- Sprint: 2021 Week 07-09 (from Feb 15) > Rule relationship analysis graph : handling special syntax or usage rules > ------------------------------------------------------------------------- > > Key: DROOLS-5969 > URL: https://issues.redhat.com/browse/DROOLS-5969 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.49.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Basic parsing and generating graph is done. > Now using real rules, find issues caused by special syntax or usage and fix. Add tests to drools-impact-analysis-itests. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6041) "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-6041?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-6041: -------------------------------------- Description: With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line) {noformat} rule R dialect "mvel" when Person(name == "Mario") then Person p2 = new Person("John"); p2.age = 30 insert(p2); end {noformat} exec-model fails with {noformat} CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type {noformat} while standard-drl runs successfully. I'm not sure if exec-model should work the same as standard-drl (treat a new line as a delimiter?), or give a better error message. was: With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line) {noformat} rule R dialect "mvel" when Person(name == "Mario") then Person p2 = new Person("John"); p2.age = 30 insert(p2); end {noformat} exec-model fails with {noformat} CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type {noformat} while standard-drl runs successfully. I'm not sure if exec-model should work the same as standard-drl, or give a better error message. > "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect > -------------------------------------------------------------------------------------------- > > Key: DROOLS-6041 > URL: https://issues.redhat.com/browse/DROOLS-6041 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.50.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line) > {noformat} > rule R > dialect "mvel" > when > Person(name == "Mario") > then > Person p2 = new Person("John"); > p2.age = 30 > insert(p2); > end > {noformat} > exec-model fails with > {noformat} > CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type > {noformat} > while standard-drl runs successfully. > I'm not sure if exec-model should work the same as standard-drl (treat a new line as a delimiter?), or give a better error message. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6041) "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-6041?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-6041: -------------------------------------- Description: With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line) {noformat} rule R dialect "mvel" when Person(name == "Mario") then Person p2 = new Person("John"); p2.age = 30 insert(p2); end {noformat} exec-model fails with {noformat} CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type {noformat} while standard-drl runs successfully. I'm not sure if exec-model should work the same as standard-drl, or give a better error message. was: With a rule like this: (See, semicolon is missing in the "p2.age = 30" line) {noformat} rule R dialect "mvel" when Person(name == "Mario") then Person p2 = new Person("John"); p2.age = 30 insert(p2); end {noformat} exec-model fails with {noformat} CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type {noformat} while standard-drl runs successfully. I'm not sure if exec-model should work the same as standard-drl, or give a better error message. > "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect > -------------------------------------------------------------------------------------------- > > Key: DROOLS-6041 > URL: https://issues.redhat.com/browse/DROOLS-6041 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.50.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line) > {noformat} > rule R > dialect "mvel" > when > Person(name == "Mario") > then > Person p2 = new Person("John"); > p2.age = 30 > insert(p2); > end > {noformat} > exec-model fails with > {noformat} > CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type > {noformat} > while standard-drl runs successfully. > I'm not sure if exec-model should work the same as standard-drl, or give a better error message. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6041) "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-6041: ----------------------------------------- Summary: "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect Key: DROOLS-6041 URL: https://issues.redhat.com/browse/DROOLS-6041 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.50.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi With a rule like this: (See, semicolon is missing in the "p2.age = 30" line) {noformat} rule R dialect "mvel" when Person(name == "Mario") then Person p2 = new Person("John"); p2.age = 30 insert(p2); end {noformat} exec-model fails with {noformat} CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type {noformat} while standard-drl runs successfully. I'm not sure if exec-model should work the same as standard-drl, or give a better error message. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14434) Heap usage continuously growing and exhausting available heap memory in production

by Manas Panda (Jira)

[ https://issues.redhat.com/browse/WFLY-14434?page=com.atlassian.jira.plugi... ] Manas Panda commented on WFLY-14434: ------------------------------------ Thank you so much Paul. > Heap usage continuously growing and exhausting available heap memory in production > ---------------------------------------------------------------------------------- > > Key: WFLY-14434 > URL: https://issues.redhat.com/browse/WFLY-14434 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Manas Panda > Assignee: Paul Ferraro > Priority: Major > Attachments: Heap_Size_keeps_increasing.jpg, Heap_dump_analysis_1.jpg > > > # Problem description: > Critical issue of heap usage continuously growing and exhausting available heap memory in production. As you can see in below heap dump org.infinispan.container.impl.DefaultDataContainer is growing as the time passes and not garbage collected by GC. This increase in heap happening after upgrading from Wildfly 10.1 to Wildfly 18.0.1. There is no change in JDK in both cases ( Wildfly 10.1 and Wildfly 18.0.1). > 2. Web application environment > * OS: RHEL 7.5 > * Wildfly 18.0.1 > * JDK 1.8 > * Wildfly is being run in cluster mode > * Integrated with Keycloak 3.4.3 for SSO ( SAML) > * Enabled Wildfly clustering mode > * G1GC garbage collector used. And 20gigs of heap allocated ( -Xmx) > * Environment of Web App on Wildfly 10.1 is same ( except Wildfly 18) with same hardware > * Web application uses Spring web framework and security > 3. Heap dump analysis > * We have few web users logging in and every second and external application consuming few API’s exposed by same application. > * As you can see infinispan.container.impl.DefaultDataContainer Has already grown 14gigs. > * Please note that web application does not use infinispan directly. > * The heap does not grow in wildfly 10.1 and its normal ( garbage gets collected and size gets reduced after GC) > Please find the snapshot as attached. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14277) Update our MicroProfile JWT support to 1.2 as required by MicroProfile 4

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-14277?page=com.atlassian.jira.plugi... ] James Perkins commented on WFLY-14277: -------------------------------------- Sorry for the noise. I resolved the wrong issue :) > Update our MicroProfile JWT support to 1.2 as required by MicroProfile 4 > ------------------------------------------------------------------------ > > Key: WFLY-14277 > URL: https://issues.redhat.com/browse/WFLY-14277 > Project: WildFly > Issue Type: Feature Request > Components: MP JWT, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Labels: merged-to-feature-branch > Fix For: 23.0.0.Beta1 > > > For spec changes see: > [https://github.com/eclipse/microprofile-jwt-auth/releases/tag/1.2] > and: > https://github.com/eclipse/microprofile-jwt-auth/compare/1.1...1.2 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14277) Update our MicroProfile JWT support to 1.2 as required by MicroProfile 4

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-14277?page=com.atlassian.jira.plugi... ] James Perkins reopened WFLY-14277: ---------------------------------- > Update our MicroProfile JWT support to 1.2 as required by MicroProfile 4 > ------------------------------------------------------------------------ > > Key: WFLY-14277 > URL: https://issues.redhat.com/browse/WFLY-14277 > Project: WildFly > Issue Type: Feature Request > Components: MP JWT, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Labels: merged-to-feature-branch > Fix For: 23.0.0.Beta1 > > > For spec changes see: > [https://github.com/eclipse/microprofile-jwt-auth/releases/tag/1.2] > and: > https://github.com/eclipse/microprofile-jwt-auth/compare/1.1...1.2 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14052) EE 9 jms/core20/jmscontexttopictests#getMetaDataTest tests expects JMS version 3.0 but is seeing 2.0

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14052?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-14052. ------------------------------------- Fix Version/s: 23.0.0.Beta1 Resolution: Done > EE 9 jms/core20/jmscontexttopictests#getMetaDataTest tests expects JMS version 3.0 but is seeing 2.0 > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-14052 > URL: https://issues.redhat.com/browse/WFLY-14052 > Project: WildFly > Issue Type: Sub-task > Components: JMS > Reporter: Scott Marlow > Assignee: Emmanuel Hugonnet > Priority: Major > Labels: EE9 > Fix For: 23.0.0.Beta1 > > > {quote} > \u001b[0m\u001b[0m13:52:58,657 INFO [stdout] (Thread-161) 11-06-2020 13:52:58: ERROR: Error: incorrect JMSVersion=2.0 > \u001b[0m\u001b[0m13:52:58,657 INFO [stdout] (Thread-161) 11-06-2020 13:52:58: ERROR: Error: incorrect JMSMajorVersion=2 > \u001b[0m\u001b[0m13:52:58,657 INFO [stdout] (Thread-161) 11-06-2020 13:52:58: ERROR: getMetaDataTest failed > \u001b[0m\u001b[0m13:52:58,658 INFO [stdout] (Thread-161) 11-06-2020 13:52:58: ERROR: Test case throws exception: getMetaDataTest failed > \u001b[0m\u001b[0m13:52:58,658 INFO [stdout] (Thread-161) 11-06-2020 13:52:58: ERROR: Exception at: > \u001b[0m\u001b[0m13:52:58,658 INFO [stdout] (Thread-161) 11-06-2020 13:52:58: ERROR: com.sun.ts.lib.harness.EETest$Fault: getMetaDataTest failed > \u001b[0m\u001b[0m13:52:58,658 INFO [stdout] (Thread-161) at com.sun.ts.tests.jms.core20.jmscontexttopictests.Client.getMetaDataTest(Client.java:475) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at java.lang.reflect.Method.invoke(Method.java:498) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at com.sun.ts.lib.harness.EETest.run(EETest.java:596) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:115) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at com.sun.ts.tests.common.vehicle.EmptyVehicleRunner.run(EmptyVehicleRunner.java:40) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:105) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:486) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at com.sun.ts.lib.harness.EETest.run(EETest.java:285) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at com.sun.ts.tests.common.vehicle.VehicleClient.main(VehicleClient.java:38) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > \u001b[0m\u001b[0m13:52:58,659 INFO [stdout] (Thread-161) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > \u001b[0m\u001b[0m13:52:58,660 INFO [stdout] (Thread-161) at java.lang.reflect.Method.invoke(Method.java:498) > \u001b[0m\u001b[0m13:52:58,660 INFO [stdout] (Thread-161) at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:99) > \u001b[0m\u001b[0m13:52:58,660 INFO [stdout] (Thread-161) at java.lang.Thread.run(Thread.java:748) > {quote} > [jakarta.jms.ConnectionMetaData.classConnectionMetaData|https://jakarta.ee/specifications/messaging/3.0/apidocs/] is returning Jakarta EE 8 versions instead of Jakarta EE 9.0 versions -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2021