[JBoss JIRA] (WFLY-11814) PrometheusCollector is not thread-safe causing NPEs during deployment
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-11814:
-----------------------------------
Summary: PrometheusCollector is not thread-safe causing NPEs during deployment
Key: WFLY-11814
URL: https://issues.jboss.org/browse/WFLY-11814
Project: WildFly
Issue Type: Bug
Components: MP Metrics
Affects Versions: 16.0.0.Final
Reporter: Paul Ferraro
Assignee: Jeff Mesnil
The logic within PrometheusCollector.addMetricFamilySampleSupplier(...) is not thread safe and can easily trigger an NPE during deployment.
e.g.
{noformat}
10:33:32,706 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."web-sso.ear"."sso-with-no-auth.war".metrics: org.jboss.msc.service.StartException in service jboss.deployment.subunit."web-sso.ear"."sso-with-no-auth.war".metrics: 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.NullPointerException
at org.wildfly.extension.microprofile.metrics.PrometheusCollector.addMetricFamilySampleSupplier(PrometheusCollector.java:32)
at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics0(MetricCollector.java:157)
at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics0(MetricCollector.java:166)
at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics(MetricCollector.java:92)
at org.wildfly.extension.microprofile.metrics.deployment.DeploymentMetricService.start(DeploymentMetricService.java:54)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
... 6 more
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFCORE-4303) NullPointerException - with SNI configured on IBM JDK 1.8
by Diana Vilkolakova (Jira)
[ https://issues.jboss.org/browse/WFCORE-4303?page=com.atlassian.jira.plugi... ]
Diana Vilkolakova reassigned WFCORE-4303:
-----------------------------------------
Assignee: Diana Vilkolakova
> NullPointerException - with SNI configured on IBM JDK 1.8
> ---------------------------------------------------------
>
> Key: WFCORE-4303
> URL: https://issues.jboss.org/browse/WFCORE-4303
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Environment: IBM JDK 1.8:
> {code}
> java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 8.0.5.20 - pxa6480sr5fp20-20180802_01(SR5 FP20))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180731_393394 (JIT enabled, AOT enabled)
> OpenJ9 - bd23af8
> OMR - ca1411c
> IBM - 98805ca)
> JCL - 20180719_01 based on Oracle jdk8u181-b12
> {code}
> Reporter: Jan Stourac
> Assignee: Diana Vilkolakova
> Priority: Major
>
> When running with IBM JDK 1.8, there is an NPE during the request performed against https-listener which has configured 'server-ssl-sni-context' instance (when using standard 'server-ssl-context' no exception is present):
> {code}
> $ curl https://localhost:8443 -k
> curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8443
> {code}
> related exception in server.log:
> {code}
> 18:23:01,227 ERROR [io.undertow.request.io] (default I/O-6) UT005090: Unexpected failure: java.lang.NullPointerException
> at io.undertow.protocols.ssl.SslConduit.doUnwrap(SslConduit.java:772)
> at io.undertow.protocols.ssl.SslConduit.read(SslConduit.java:567)
> at org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127)
> at io.undertow.server.protocol.http.AlpnOpenListener$AlpnConnectionListener.handleEvent(AlpnOpenListener.java:348)
> at io.undertow.server.protocol.http.AlpnOpenListener.handleEvent(AlpnOpenListener.java:305)
> at io.undertow.server.protocol.http.AlpnOpenListener.handleEvent(AlpnOpenListener.java:64)
> 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.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:131)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> {code}
> When I switch to OpenSSL provider using
> {code}
> /subsystem=elytron/server-ssl-context=defaultSSC:write-attribute(name=providers,value=openssl)
> {code}
> then the exception disappears.
> ----
> Note: sometimes I can also see shorter exception stacktrace:
> {code}
> 18:17:15,711 ERROR [io.undertow.request.io] (default I/O-2) UT005090: Unexpected failure: java.lang.NullPointerException
> at io.undertow.protocols.ssl.SslConduit.doUnwrap(SslConduit.java:772)
> at io.undertow.protocols.ssl.SslConduit.doHandshake(SslConduit.java:648)
> at io.undertow.protocols.ssl.SslConduit.access$900(SslConduit.java:63)
> at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1136)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3734) Executable model: Imports not evaluated correctly for fact declarations
by Olli Johnson (Jira)
Olli Johnson created DROOLS-3734:
------------------------------------
Summary: Executable model: Imports not evaluated correctly for fact declarations
Key: DROOLS-3734
URL: https://issues.jboss.org/browse/DROOLS-3734
Project: Drools
Issue Type: Bug
Affects Versions: 7.17.0.Final, 7.12.0.Final
Reporter: Olli Johnson
Assignee: Mario Fusco
If using the executable model (building with -DgenerateModel=YES) compilation errors occur for types defined in Java being used in DRL of the same maven model.
When attempting to import a Java class defined under the same pom.xml module as the current rules file 'CompilationProblemErrorResult: cannot find symbol' errors are observed. Even when the import is not needed (Java type defined in same package as DRL rules), if the type is used in a type declaration the 'cannot find symbol' error is still observed.
Errors are of the form:
{code}
[ERROR] Unable to build KieBaseModel:all
CompilationProblemErrorResult: cannot find symbol
symbol: class MyFact
location: package olijohns
CompilationProblemErrorResult: cannot find symbol
symbol: class MyFact
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months