[Red Hat JIRA] (DROOLS-5877) Support MVEL BLiteral in the exec model
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5877?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5877:
---------------------------------
Sprint: 2020 Week 49-51 (from Nov 30)
> Support MVEL BLiteral in the exec model
> ---------------------------------------
>
> Key: DROOLS-5877
> URL: https://issues.redhat.com/browse/DROOLS-5877
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
>
> {code:java}
> @Test
> public void prova() {
> final String str =
> "global java.util.List list\n" +
> "import " + Person.class.getCanonicalName() + ";" +
> "rule R when\n" +
> "$p1 : Person(age >= 18B)" +
> "then\n" +
> " System.out.println($p1);" +
> "end\n";
> KieSession ksession = getKieSession( str );
> List<String> results = new ArrayList<>();
> ksession.setGlobal("list", results);
> ksession.insert( new Person( "Mark", 37 ) );
> ksession.insert( new Person( "Edson", 35 ) );
> ksession.insert( new Person( "Mario", 40 ) );
> ksession.fireAllRules();
> }{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (DROOLS-5882) Unreadable error message
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5882?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-5882:
---------------------------------
Component/s: Guided Decision Table Editor
> Unreadable error message
> ------------------------
>
> Key: DROOLS-5882
> URL: https://issues.redhat.com/browse/DROOLS-5882
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Reporter: Gabriele Cardosi
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: Person.java, TestDataTable.gdst
>
>
> While creating a Guided Decision Table, I should have made some mistake.
> The UI popup an error saying
> "Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://127.0.0.1:8080/business-central/verifier/dtableVerifier/0AB389FF84...)"
> I tried to lool in server log, but I found only
> "2020-12-04 13:38:03,063 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-25) Error from user: wbadmin Error ID: -614724293 Location: LibraryPerspective|$ProjectScreen,AddAssetsScreen,GuidedDecisionTableEditor?path_uri=default://master@MySpace/TestProject/src/main/resources/com/myspace/testproject/Prova2.gdst&file_name=Prova2.gdst&has_version_support=true,org.kie.workbench.common.screens.messageconsole.MessageConsole,GuidedDecisionTableEditor?path_uri=default://master@MySpace/TestProject/src/main/resources/com/myspace/testproject/TestDataTable.gdst&file_name=TestDataTable.gdst&has_version_support=true Exception: Uncaught exception: Uncaught TypeError: Cannot read property 'createElement' of undefined (http://127.0.0.1:8080/business-central/verifier/dtableVerifier/0AB389FF84...)"
> The attached file contains the created table
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14118) Distributed session manager can throw UnsupportedOperationException on concurrent calls to HttpServletRequest.getSession(...) for a given session
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14118?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-14118:
------------------------------------
Fix Version/s: 21.0.2.Final
> Distributed session manager can throw UnsupportedOperationException on concurrent calls to HttpServletRequest.getSession(...) for a given session
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-14118
> URL: https://issues.redhat.com/browse/WFLY-14118
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 21.0.1.Final, 22.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
> Fix For: 22.0.0.Beta1, 21.0.2.Final
>
>
> {noformat}
> 19:15:26,603 ERROR [io.undertow.servlet.request] (default task-3) UT015005: Error invoking method requestInitialized on listener class org.jboss.weld.module.web.servlet.WeldInitialListener: java.lang.UnsupportedOperationException
> at java.base/java.util.AbstractMap$SimpleImmutableEntry.setValue(AbstractMap.java:794)
> at org.wildfly.clustering.ee.cache@21.0.1.Final//org.wildfly.clustering.ee.cache.ConcurrentManager.apply(ConcurrentManager.java:88)
> at org.wildfly.clustering.web.cache@21.0.1.Final//org.wildfly.clustering.web.cache.session.ConcurrentSessionManager.findSession(ConcurrentSessionManager.java:70)
> at org.wildfly.clustering.web.undertow@21.0.1.Final//org.wildfly.clustering.web.undertow.session.DistributableSessionManager.getSession(DistributableSessionManager.java:227)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:858)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.spec.HttpServletRequestImpl.getSession(HttpServletRequestImpl.java:421)
> at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.module.web.servlet.SessionHolder.requestInitialized(SessionHolder.java:47)
> at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.module.web.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:247)
> at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.module.web.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:146)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.core.ApplicationListeners.requestInitialized(ApplicationListeners.java:263)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:268)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:78)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:133)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:130)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow@21.0.1.Final//org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow@21.0.1.Final//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530)
> at org.wildfly.extension.undertow@21.0.1.Final//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530)
> at org.wildfly.extension.undertow@21.0.1.Final//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530)
> at org.wildfly.extension.undertow@21.0.1.Final//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:249)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:78)
> at io.undertow.servlet@2.2.2.Final//io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:99)
> at io.undertow.core@2.2.2.Final//io.undertow.server.Connectors.executeRootHandler(Connectors.java:387)
> at io.undertow.core@2.2.2.Final//io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:841)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
> at org.jboss.xnio@3.8.2.Final//org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1280)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14094) Potential memory leak when using opentracing
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14094?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-14094:
-----------------------------------------
[~roland.spindelbalker-davila] We'll do a 21.0.2, likely the week after next, and this will be in it.
> Potential memory leak when using opentracing
> --------------------------------------------
>
> Key: WFLY-14094
> URL: https://issues.redhat.com/browse/WFLY-14094
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, MP OpenTracing
> Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final, 20.0.1.Final, 21.0.0.Final
> Reporter: Michel Erard
> Assignee: Matěj Novotný
> Priority: Major
> Labels: downstream_dependency
> Fix For: 22.0.0.Beta1, 21.0.2.Final
>
> Attachments: bad_heapdump.png, good_heapdump.png, image-2020-11-23-11-59-50-907.png
>
>
> Depending on the CDI/EJB scope the usage together with opentracing can end up in a memory leak.
> Here I did a little sample project to simulate the issue:
> [https://github.com/erard22/wildfly-memory-leak]
> Requests handeled by this class
> {code:java}
> @ApplicationScoped
> @Traced
> public class HelloWorldService {
> public String sayHello() {
> return "Hello World!";
> }
> } {code}
> leave an instance of class {{org.jboss.weld.contexts.CreationalContextImpl}} back on the heap.
> !bad_heapdump.png!
> Also when using {{@Stateless}}. It disapears when you change to {{@Dependent}}. I did some tests with different versions. It seems the issue was introduced with wildfly-19. Before it worked. I also did it with EAP. There it was fine with 7.3.0 but is now present in 7.3.3.
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[Red Hat JIRA] (WFLY-14094) Potential memory leak when using opentracing
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14094?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-14094:
------------------------------------
Fix Version/s: 21.0.2.Final
> Potential memory leak when using opentracing
> --------------------------------------------
>
> Key: WFLY-14094
> URL: https://issues.redhat.com/browse/WFLY-14094
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, MP OpenTracing
> Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final, 20.0.1.Final, 21.0.0.Final
> Reporter: Michel Erard
> Assignee: Matěj Novotný
> Priority: Major
> Labels: downstream_dependency
> Fix For: 22.0.0.Beta1, 21.0.2.Final
>
> Attachments: bad_heapdump.png, good_heapdump.png, image-2020-11-23-11-59-50-907.png
>
>
> Depending on the CDI/EJB scope the usage together with opentracing can end up in a memory leak.
> Here I did a little sample project to simulate the issue:
> [https://github.com/erard22/wildfly-memory-leak]
> Requests handeled by this class
> {code:java}
> @ApplicationScoped
> @Traced
> public class HelloWorldService {
> public String sayHello() {
> return "Hello World!";
> }
> } {code}
> leave an instance of class {{org.jboss.weld.contexts.CreationalContextImpl}} back on the heap.
> !bad_heapdump.png!
> Also when using {{@Stateless}}. It disapears when you change to {{@Dependent}}. I did some tests with different versions. It seems the issue was introduced with wildfly-19. Before it worked. I also did it with EAP. There it was fine with 7.3.0 but is now present in 7.3.3.
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months