[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5327:
--------------------------------
Attachment: (was: TestSpace_TestProject.zip)
> Multiselect dropdown for enumerated values - numbers
> ----------------------------------------------------
>
> Key: DROOLS-5327
> URL: https://issues.redhat.com/browse/DROOLS-5327
> Project: Drools
> Issue Type: Bug
> Components: Guided Template Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Attachments: MySpace_project.zip
>
>
> During verification of DROOLS-5011 was spotted corner case that was not fixed.
> In the original issue customer user attached project with enumeration for *String* field and used that field in guided rule template.
> The issue is if user follow the same scenario but instead of *String* field, some number type is used, for example *Integer*. In such case, when user added data to rule template, multiselect dropdown was shown correctly, however in the grid was always shown 0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5327:
--------------------------------
Description:
During verification of DROOLS-5011 was spotted corner case that was not fixed.
In the original issue customer user attached project with enumeration for *String* field and used that field in guided rule template.
The issue is if user follow the same scenario but instead of *String* field, some number type is used, for example *Integer*. In such case, when user added data to rule template, multiselect dropdown was shown correctly, however in the grid was always shown 0.
was:In earlier versions business central editor for a Guided Rule Template would display list (multiselect drop down )of enumerated values in Data tab if the user added a Template Key of type Enumerations, but in latest version it's shown as a normal text field not displaying enum values drop down .
> Multiselect dropdown for enumerated values - numbers
> ----------------------------------------------------
>
> Key: DROOLS-5327
> URL: https://issues.redhat.com/browse/DROOLS-5327
> Project: Drools
> Issue Type: Bug
> Components: Guided Template Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Attachments: TestSpace_TestProject.zip
>
>
> During verification of DROOLS-5011 was spotted corner case that was not fixed.
> In the original issue customer user attached project with enumeration for *String* field and used that field in guided rule template.
> The issue is if user follow the same scenario but instead of *String* field, some number type is used, for example *Integer*. In such case, when user added data to rule template, multiselect dropdown was shown correctly, however in the grid was always shown 0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5327:
--------------------------------
Attachment: (was: add-row.webm)
> Multiselect dropdown for enumerated values - numbers
> ----------------------------------------------------
>
> Key: DROOLS-5327
> URL: https://issues.redhat.com/browse/DROOLS-5327
> Project: Drools
> Issue Type: Bug
> Components: Guided Template Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Attachments: TestSpace_TestProject.zip
>
>
> In earlier versions business central editor for a Guided Rule Template would display list (multiselect drop down )of enumerated values in Data tab if the user added a Template Key of type Enumerations, but in latest version it's shown as a normal text field not displaying enum values drop down .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5327:
--------------------------------
Attachment: TestSpace_TestProject.zip
> Multiselect dropdown for enumerated values - numbers
> ----------------------------------------------------
>
> Key: DROOLS-5327
> URL: https://issues.redhat.com/browse/DROOLS-5327
> Project: Drools
> Issue Type: Bug
> Components: Guided Template Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Attachments: TestSpace_TestProject.zip, add-row.webm
>
>
> In earlier versions business central editor for a Guided Rule Template would display list (multiselect drop down )of enumerated values in Data tab if the user added a Template Key of type Enumerations, but in latest version it's shown as a normal text field not displaying enum values drop down .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5327:
--------------------------------
Tester: Anna Dupliak (was: Jozef Marko)
> Multiselect dropdown for enumerated values - numbers
> ----------------------------------------------------
>
> Key: DROOLS-5327
> URL: https://issues.redhat.com/browse/DROOLS-5327
> Project: Drools
> Issue Type: Bug
> Components: Guided Template Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Attachments: TestSpace_TestProject.zip, add-row.webm
>
>
> In earlier versions business central editor for a Guided Rule Template would display list (multiselect drop down )of enumerated values in Data tab if the user added a Template Key of type Enumerations, but in latest version it's shown as a normal text field not displaying enum values drop down .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5327?page=com.atlassian.jira.plug... ]
Jozef Marko reassigned DROOLS-5327:
-----------------------------------
Assignee: Jozef Marko (was: Toni Rikkola)
> Multiselect dropdown for enumerated values - numbers
> ----------------------------------------------------
>
> Key: DROOLS-5327
> URL: https://issues.redhat.com/browse/DROOLS-5327
> Project: Drools
> Issue Type: Bug
> Components: Guided Template Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Attachments: TestSpace_TestProject.zip, add-row.webm
>
>
> In earlier versions business central editor for a Guided Rule Template would display list (multiselect drop down )of enumerated values in Data tab if the user added a Template Key of type Enumerations, but in latest version it's shown as a normal text field not displaying enum values drop down .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5327) Multiselect dropdown for enumerated values - numbers
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5327:
-----------------------------------
Summary: Multiselect dropdown for enumerated values - numbers
Key: DROOLS-5327
URL: https://issues.redhat.com/browse/DROOLS-5327
Project: Drools
Issue Type: Bug
Components: Guided Template Editor
Affects Versions: 7.33.0.Final
Reporter: Jozef Marko
Assignee: Toni Rikkola
Attachments: add-row.webm
In earlier versions business central editor for a Guided Rule Template would display list (multiselect drop down )of enumerated values in Data tab if the user added a Template Key of type Enumerations, but in latest version it's shown as a normal text field not displaying enum values drop down .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13461) Jaxrs requires bean-validation when cdi is present
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13461?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13461:
---------------------------------------------
[~brian.stansberry], or perhaps make bean-validation layer an optional dependency of cdi? cloud-profile and jaxrs-server have optional explicit dependencies on bean-validation that could be removed.
> Jaxrs requires bean-validation when cdi is present
> --------------------------------------------------
>
> Key: WFLY-13461
> URL: https://issues.redhat.com/browse/WFLY-13461
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 20.0.0.Beta1
> Reporter: Jean Francois Denise
> Assignee: Alessio Soldano
> Priority: Major
>
> We are provisioning a server containing jaxrs and cdi. The deployment fails with the pasted exception.
> This has been caused by fix for WFLY-13189. bean-validation subsystem used to be provisioned with cdi.
> {quote}
> 12:57:20,521 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 16) RESTEASY002225: Deploying javax.ws.rs.core.Application: class com.example.demo.rest.RestApplication
> 12:57:20,562 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 16) MSC000001: Failed to start service jboss.deployment.unit."ROOT.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."ROOT.war".undertow-deployment: javax.validation.ValidationException: RESTEASY008520: Unable to load Validation support
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: javax.validation.ValidationException: RESTEASY008520: Unable to load Validation support
> at org.jboss.resteasy.plugins.validation.AbstractValidatorContextResolver.getContext(AbstractValidatorContextResolver.java:97)
> at org.jboss.resteasy.plugins.validation.ValidatorContextResolver.getContext(ValidatorContextResolver.java:16)
> at org.jboss.resteasy.core.ResourceMethodInvoker.<init>(ResourceMethodInvoker.java:131)
> at org.jboss.resteasy.core.ResourceMethodRegistry.processMethod(ResourceMethodRegistry.java:351)
> at org.jboss.resteasy.core.ResourceMethodRegistry.register(ResourceMethodRegistry.java:278)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:229)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:201)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:187)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:164)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:81)
> at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:485)
> at org.jboss.resteasy.spi.ResteasyDeployment.startInternal(ResteasyDeployment.java:286)
> at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:92)
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:119)
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
> at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)
> at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:305)
> at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:145)
> at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:585)
> at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:556)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530)
> at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:598)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:97)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
> ... 8 more
> Caused by: javax.validation.NoProviderFoundException: Unable to create a Configuration, because no Jakarta Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath.
> at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:291)
> at org.jboss.resteasy.plugins.validation.AbstractValidatorContextResolver.getConfig(AbstractValidatorContextResolver.java:78)
> at org.jboss.resteasy.plugins.validation.AbstractValidatorContextResolver.getContext(AbstractValidatorContextResolver.java:90)
> ... 34 more
> 12:57:20,567 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "jaxrs.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ROOT.war\".undertow-deployment" => "javax.validation.ValidationException: RESTEASY008520: Unable to load Validation support
> Caused by: javax.validation.ValidationException: RESTEASY008520: Unable to load Validation support
> Caused by: javax.validation.NoProviderFoundException: Unable to create a Configuration, because no Jakarta Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath."}}
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13444) Observing High CPU in EPollArrayWrapper.epollCtl default I/O thread
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13444?page=com.atlassian.jira.plugi... ]
Radoslav Husar edited comment on WFLY-13444 at 5/13/20 9:22 AM:
----------------------------------------------------------------
[~ev.srinivas] WildFly 10.1 is an old release, please reproduce with the latest (e.g. 19.1) release.
was (Author: rhusar):
[~ev.srinivas] WildFly 10.1 is an old releas, please reproduce with the latest (e.g. 19.1) release.
> Observing High CPU in EPollArrayWrapper.epollCtl default I/O thread
> -------------------------------------------------------------------
>
> Key: WFLY-13444
> URL: https://issues.redhat.com/browse/WFLY-13444
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Srinivas ev
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: IO thread memory.PNG, IO thread.PNG, Thread consuming high CPU.PNG, ThreadDump1set.zip, ThreadDump2set.zip, default IO thread 73.PNG, stack trace from snapshot.PNG, stack trace in thread dump.PNG, top command output.PNG
>
>
> Facing high CPU by one of the default I/O thread In Wildfly 10.1.0 Final. Looks none of our application component thread is consuming.
> Can somebody check what is triggering this issue? I attached the thread stack to this Jira. This is blocking our releases. When the CPU cores are high in number, multiple default I/O threads will kick in consuming the CPU in 90~100% range continuously.
> Wildfly 10.1.0 Final
> Java -
> openjdk version "1.8.0_232"
> OpenJDK Runtime Environment (build 1.8.0_232-b09)
> OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode
> ---------------------------------------------------------------------------------------------------
> at java.lang.Throwable.fillInStackTrace(Native Method)
> at java.lang.Throwable.fillInStackTrace(Throwable.java:784)
> at java.lang.Throwable.<init>(Throwable.java:251)
> at java.lang.Exception.<init>(Exception.java:54)
> at java.io.IOException.<init>(IOException.java:47)
> at java.nio.channels.ClosedChannelException.<init>(ClosedChannelException.java:52)
> at org.xnio.ssl.JsseStreamConduit.write(JsseStreamConduit.java:1022)
> at org.xnio.conduits.ConduitStreamSinkChannel.write(ConduitStreamSinkChannel.java:150)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:385)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:372)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.WriteReadyHandler$ChannelListenerHandler.writeReady(WriteReadyHandler.java:65)
> at org.xnio.ssl.JsseStreamConduit.run(JsseStreamConduit.java:393)
> at org.xnio.ssl.JsseStreamConduit.readReady(JsseStreamConduit.java:547)
> at org.xnio.ssl.JsseStreamConduit$2.readReady(JsseStreamConduit.java:319)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
> -------------------------------------------------------------------------------------------
> at sun.nio.ch.EPollArrayWrapper.epollCtl(Native Method)
> at sun.nio.ch.EPollArrayWrapper.updateRegistrations(EPollArrayWrapper.java:299)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:268)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:515)
> -----------------------------------------------------------------------------------
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13444) Observing High CPU in EPollArrayWrapper.epollCtl default I/O thread
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13444?page=com.atlassian.jira.plugi... ]
Radoslav Husar commented on WFLY-13444:
---------------------------------------
[~ev.srinivas] WildFly 10.1 is an old releas, please reproduce with the latest (e.g. 19.1) release.
> Observing High CPU in EPollArrayWrapper.epollCtl default I/O thread
> -------------------------------------------------------------------
>
> Key: WFLY-13444
> URL: https://issues.redhat.com/browse/WFLY-13444
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Srinivas ev
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: IO thread memory.PNG, IO thread.PNG, Thread consuming high CPU.PNG, ThreadDump1set.zip, ThreadDump2set.zip, default IO thread 73.PNG, stack trace from snapshot.PNG, stack trace in thread dump.PNG, top command output.PNG
>
>
> Facing high CPU by one of the default I/O thread In Wildfly 10.1.0 Final. Looks none of our application component thread is consuming.
> Can somebody check what is triggering this issue? I attached the thread stack to this Jira. This is blocking our releases. When the CPU cores are high in number, multiple default I/O threads will kick in consuming the CPU in 90~100% range continuously.
> Wildfly 10.1.0 Final
> Java -
> openjdk version "1.8.0_232"
> OpenJDK Runtime Environment (build 1.8.0_232-b09)
> OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode
> ---------------------------------------------------------------------------------------------------
> at java.lang.Throwable.fillInStackTrace(Native Method)
> at java.lang.Throwable.fillInStackTrace(Throwable.java:784)
> at java.lang.Throwable.<init>(Throwable.java:251)
> at java.lang.Exception.<init>(Exception.java:54)
> at java.io.IOException.<init>(IOException.java:47)
> at java.nio.channels.ClosedChannelException.<init>(ClosedChannelException.java:52)
> at org.xnio.ssl.JsseStreamConduit.write(JsseStreamConduit.java:1022)
> at org.xnio.conduits.ConduitStreamSinkChannel.write(ConduitStreamSinkChannel.java:150)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:385)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:372)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.WriteReadyHandler$ChannelListenerHandler.writeReady(WriteReadyHandler.java:65)
> at org.xnio.ssl.JsseStreamConduit.run(JsseStreamConduit.java:393)
> at org.xnio.ssl.JsseStreamConduit.readReady(JsseStreamConduit.java:547)
> at org.xnio.ssl.JsseStreamConduit$2.readReady(JsseStreamConduit.java:319)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
> -------------------------------------------------------------------------------------------
> at sun.nio.ch.EPollArrayWrapper.epollCtl(Native Method)
> at sun.nio.ch.EPollArrayWrapper.updateRegistrations(EPollArrayWrapper.java:299)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:268)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:515)
> -----------------------------------------------------------------------------------
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months