[JBoss JIRA] (DROOLS-5073) menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)
by xiaodong zhang (Jira)
[ https://issues.redhat.com/browse/DROOLS-5073?page=com.atlassian.jira.plug... ]
xiaodong zhang updated DROOLS-5073:
-----------------------------------
Summary: menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18) (was: menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 10))
> menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5073
> URL: https://issues.redhat.com/browse/DROOLS-5073
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.19.0.Final, 7.33.0.Final
> Reporter: xiaodong zhang
> Assignee: Michael Anstis
> Priority: Major
> Attachments: maycolumns.dmn
>
>
> Menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 10).
> This happened on my macbook pro. If I use a External display. The things will be better but still hit the issue if the columns is more than 20。
> But this isn't happend on my new windows machine(i7 9th , GTX1660ti)
> So I guess this a a performance issue, when shortage of the hardware resource， the UI will refreshed when right click the cell and caused the right-click menu gone.
> Please help to check this . Thanks a lot !
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5073) menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)
by xiaodong zhang (Jira)
[ https://issues.redhat.com/browse/DROOLS-5073?page=com.atlassian.jira.plug... ]
xiaodong zhang updated DROOLS-5073:
-----------------------------------
Description:
Menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18).
This happened on my macbook pro. If I use a External display. The things will be better but still hit the issue if the columns is more than 25。
But this isn't happend on my new windows machine(i7 9th , GTX1660ti)
So I guess this a a performance issue, when shortage of the hardware resource， the UI will refreshed when right click the cell and caused the right-click menu gone.
Please help to check this . Thanks a lot !
was:
Menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 10).
This happened on my macbook pro. If I use a External display. The things will be better but still hit the issue if the columns is more than 20。
But this isn't happend on my new windows machine(i7 9th , GTX1660ti)
So I guess this a a performance issue, when shortage of the hardware resource， the UI will refreshed when right click the cell and caused the right-click menu gone.
Please help to check this . Thanks a lot !
> menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5073
> URL: https://issues.redhat.com/browse/DROOLS-5073
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.19.0.Final, 7.33.0.Final
> Reporter: xiaodong zhang
> Assignee: Michael Anstis
> Priority: Major
> Attachments: maycolumns.dmn
>
>
> Menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18).
> This happened on my macbook pro. If I use a External display. The things will be better but still hit the issue if the columns is more than 25。
> But this isn't happend on my new windows machine(i7 9th , GTX1660ti)
> So I guess this a a performance issue, when shortage of the hardware resource， the UI will refreshed when right click the cell and caused the right-click menu gone.
> Please help to check this . Thanks a lot !
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5073) menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 10)
by xiaodong zhang (Jira)
xiaodong zhang created DROOLS-5073:
--------------------------------------
Summary: menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 10)
Key: DROOLS-5073
URL: https://issues.redhat.com/browse/DROOLS-5073
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.33.0.Final, 7.19.0.Final
Reporter: xiaodong zhang
Assignee: Michael Anstis
Attachments: maycolumns.dmn
Menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 10).
This happened on my macbook pro. If I use a External display. The things will be better but still hit the issue if the columns is more than 20。
But this isn't happend on my new windows machine(i7 9th , GTX1660ti)
So I guess this a a performance issue, when shortage of the hardware resource， the UI will refreshed when right click the cell and caused the right-click menu gone.
Please help to check this . Thanks a lot !
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBEE-251) FactoryFinderCache failed to read implementation when comments present
by Scott Marlow (Jira)
[ https://issues.redhat.com/browse/JBEE-251?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on JBEE-251:
-----------------------------------
[~amarkevich]
The [github.com/eclipse-ee4j/el-ri] project might be a better place to discuss and consider changing, since that is the upstream for [https://github.com/jboss/jboss-jakarta-el-api_spec].
Another option could be for Tomcat to remove the comment.
> FactoryFinderCache failed to read implementation when comments present
> ----------------------------------------------------------------------
>
> Key: JBEE-251
> URL: https://issues.redhat.com/browse/JBEE-251
> Project: JBoss Enterprise Spec APIs
> Issue Type: Bug
> Components: jboss-el-api
> Reporter: Alexey Markevich
> Assignee: Scott Marlow
> Priority: Major
>
> Since Tomcat 9.0.31 [1] introduced ServiceLoader entry to META-INF for EL [2] following exception occurred [3].
> The same for 'jakarta.el:jakarta.el-api:3.0.3' and its FactoryFinder.
> 1. https://tomcat.apache.org/tomcat-9.0-doc/changelog.html
> 2. https://github.com/apache/tomcat/blob/9.0.31/res/META-INF/jasper-el.jar/s...
> 3.
> Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Tomcat].StandardHost[localhost].StandardContext[]]
> at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
> ... 40 more
> Caused by: javax.el.ELException: Provider # Licensed to the Apache Software Foundation (ASF) under one or more not found
> at javax.el.FactoryFinder.newInstance(FactoryFinder.java:64)
> at javax.el.FactoryFinder.find(FactoryFinder.java:103)
> at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:140)
> at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:110)
> at org.apache.jasper.runtime.JspApplicationContextImpl.<init>(JspApplicationContextImpl.java:49)
> at org.apache.jasper.runtime.JspApplicationContextImpl.getInstance(JspApplicationContextImpl.java:78)
> at org.apache.jasper.runtime.JspFactoryImpl.getJspApplicationContext(JspFactoryImpl.java:217)
> at org.jboss.weld.environment.servlet.WeldServletLifecycle.initialize(WeldServletLifecycle.java:219)
> at org.jboss.weld.environment.servlet.EnhancedListener.onStartup(EnhancedListener.java:62)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5135)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> ... 46 more
> Caused by: java.lang.ClassNotFoundException: # Licensed to the Apache Software Foundation (ASF) under one or more
> at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1365)
> at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
> at javax.el.FactoryFinder.newInstance(FactoryFinder.java:48)
> ... 56 more
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13107) Can not inject MP Config property to a HealthCheck bean
by Ingo Weiss (Jira)
Ingo Weiss created WFLY-13107:
---------------------------------
Summary: Can not inject MP Config property to a HealthCheck bean
Key: WFLY-13107
URL: https://issues.redhat.com/browse/WFLY-13107
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, MP Health
Affects Versions: 18.0.1.Final
Reporter: Ingo Weiss
Assignee: Jeff Mesnil
Fix For: 19.0.0.Beta1
Attachments: mp-1.0.war
I am playing a bit with MP specs (getting multiple specs to work together). I have been trying to return Health status based on injected config property (MP Config). However it looks like the property is not properly injected to the bean.
{code:java}
@Liveness
@ApplicationScoped
public class CDIBasedLivenessHealthCheck implements HealthCheck {
@Inject
@ConfigProperty(name = "dummy_live")
private Provider<Boolean> live;
@Override
public HealthCheckResponse call() {
return HealthCheckResponse.named("dummy")
.state(live.get())
.build();
}
}
{code}
I am get following error:
{code:java}
15:41:04,616 ERROR [org.wildfly.extension.microprofile.health.smallrye] (management I/O-2) Error processing Health Checks: java.lang.NullPointerException
at health.CDIBasedLivenessHealthCheck.call(CDIBasedLivenessHealthCheck.java:26)
at health.CDIBasedLivenessHealthCheck$Proxy$_$$_WeldClientProxy.call(Unknown Source)
at org.wildfly.extension.microprofile.health.HealthReporter.jsonObject(HealthReporter.java:120)
at org.wildfly.extension.microprofile.health.HealthReporter.fillCheck(HealthReporter.java:107)
at org.wildfly.extension.microprofile.health.HealthReporter.processChecks(HealthReporter.java:96)
at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:79)
at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:60)
at org.wildfly.extension.microprofile.health.HealthContextService$HealthCheckHandler.handleRequest(HealthContextService.java:100)
at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:672)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.nio.QueuedNioTcpServer2.acceptTask(QueuedNioTcpServer2.java:178)
at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
{code}
I believe there is a bug in MP Health integration rather than in weld. After checks are registered here in [CDIExtension|https://github.com/wildfly/wildfly/blob/master/microprofile/...] I am able to call _check.call()_ and I get _UP_ as a result. However during HTTP call here in [HealthReporter|https://github.com/wildfly/wildfly/blob/master/microprofil...] I get NPE.
I can inject a dummy bean. However if the dummy bean injects a config property, NPE is thrown.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-12811) Can not inject MP Config property to a HealthCheck bean
by Ingo Weiss (Jira)
[ https://issues.redhat.com/browse/WFLY-12811?page=com.atlassian.jira.plugi... ]
Ingo Weiss updated WFLY-12811:
------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/12824
> Can not inject MP Config property to a HealthCheck bean
> -------------------------------------------------------
>
> Key: WFLY-12811
> URL: https://issues.redhat.com/browse/WFLY-12811
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, MP Health
> Affects Versions: 18.0.1.Final
> Reporter: Ivan Straka
> Assignee: Jeff Mesnil
> Priority: Blocker
> Fix For: 19.0.0.Beta1
>
> Attachments: mp-1.0.war
>
>
> I am playing a bit with MP specs (getting multiple specs to work together). I have been trying to return Health status based on injected config property (MP Config). However it looks like the property is not properly injected to the bean.
> {code:java}
> @Liveness
> @ApplicationScoped
> public class CDIBasedLivenessHealthCheck implements HealthCheck {
> @Inject
> @ConfigProperty(name = "dummy_live")
> private Provider<Boolean> live;
> @Override
> public HealthCheckResponse call() {
> return HealthCheckResponse.named("dummy")
> .state(live.get())
> .build();
> }
> }
> {code}
> I am get following error:
> {code:java}
> 15:41:04,616 ERROR [org.wildfly.extension.microprofile.health.smallrye] (management I/O-2) Error processing Health Checks: java.lang.NullPointerException
> at health.CDIBasedLivenessHealthCheck.call(CDIBasedLivenessHealthCheck.java:26)
> at health.CDIBasedLivenessHealthCheck$Proxy$_$$_WeldClientProxy.call(Unknown Source)
> at org.wildfly.extension.microprofile.health.HealthReporter.jsonObject(HealthReporter.java:120)
> at org.wildfly.extension.microprofile.health.HealthReporter.fillCheck(HealthReporter.java:107)
> at org.wildfly.extension.microprofile.health.HealthReporter.processChecks(HealthReporter.java:96)
> at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:79)
> at org.wildfly.extension.microprofile.health.HealthReporter.getHealth(HealthReporter.java:60)
> at org.wildfly.extension.microprofile.health.HealthContextService$HealthCheckHandler.handleRequest(HealthContextService.java:100)
> at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
> at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
> at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
> at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
> at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
> at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
> at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
> at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
> at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:672)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.nio.QueuedNioTcpServer2.acceptTask(QueuedNioTcpServer2.java:178)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> {code}
> I believe there is a bug in MP Health integration rather than in weld. After checks are registered here in [CDIExtension|https://github.com/wildfly/wildfly/blob/master/microprofile/...] I am able to call _check.call()_ and I get _UP_ as a result. However during HTTP call here in [HealthReporter|https://github.com/wildfly/wildfly/blob/master/microprofil...] I get NPE.
> I can inject a dummy bean. However if the dummy bean injects a config property, NPE is thrown.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months