February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9673) NullPointerException with JDK9 + wildfly-openssl + Http2 utilized

by Jan Stourac (JIRA)

[ https://issues.jboss.org/browse/WFLY-9673?page=com.atlassian.jira.plugin.... ] Jan Stourac updated WFLY-9673: ------------------------------ Affects Version/s: (was: No Release) > NullPointerException with JDK9 + wildfly-openssl + Http2 utilized > ----------------------------------------------------------------- > > Key: WFLY-9673 > URL: https://issues.jboss.org/browse/WFLY-9673 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Jan Stourac > Assignee: Stuart Douglas > > I can see bunch of NPEs and IllegalStateExceptions when I execute [http2 testsuite|https://github.com/summerwind/h2spec] against running Wildfly server (build from master/62583a78a850ba3fb182dda9b5ed35d99e016960 revision) running with JDK9 and wildfly-openssl (my openssl version is {{OpenSSL 1.1.0g-fips 2 Nov 2017}}): > {code} > 2018-01-15 13:15:04,095 ERROR [io.undertow.request.io] (default I/O-16) UT005090: Unexpected failure: java.lang.NullPointerException > at io.undertow.core//io.undertow.protocols.http2.Http2Channel.sendPing(Http2Channel.java:794) > at io.undertow.core//io.undertow.protocols.http2.Http2Channel.createChannelImpl(Http2Channel.java:489) > at io.undertow.core//io.undertow.protocols.http2.Http2Channel.createChannel(Http2Channel.java:342) > at io.undertow.core//io.undertow.protocols.http2.Http2Channel.createChannel(Http2Channel.java:68) > at io.undertow.core//io.undertow.server.protocol.framed.AbstractFramedChannel.receive(AbstractFramedChannel.java:451) > at io.undertow.core//io.undertow.server.protocol.http2.Http2ReceiveListener.handleEvent(Http2ReceiveListener.java:109) > at io.undertow.core//io.undertow.server.protocol.http2.Http2ReceiveListener.handleEvent(Http2ReceiveListener.java:60) > at org.jboss.xnio//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at io.undertow.core//io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:921) > at io.undertow.core//io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:902) > at org.jboss.xnio//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.jboss.xnio//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at io.undertow.core//io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1145) > at io.undertow.core//io.undertow.protocols.ssl.SslConduit$1.run(SslConduit.java:168) > at org.jboss.xnio.nio//org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612) > at org.jboss.xnio.nio//org.xnio.nio.WorkerThread.run(WorkerThread.java:479) > 14:32:23,593 ERROR [io.undertow.request] (default task-128) UT005071: Undertow request failed HttpServerExchange{ POST / request {Host=[127.0.0.1:8443]} response {Last-Modified=[Mon, 15 Jan 2018 07:43:34 GMT], X-Powered-By=[Undertow/1], Server=[WildFly/11], Content-Length=[2438], Content-Type=[text/html], Accept-Ranges=[bytes]}}: java.lang.IllegalStateException: UT000127: Response has already been sent > at io.undertow.core//io.undertow.io.AsyncSenderImpl.send(AsyncSenderImpl.java:122) > at io.undertow.core//io.undertow.server.handlers.resource.PathResource$1ServerTask.run(PathResource.java:184) > at io.undertow.core//io.undertow.server.handlers.resource.PathResource.serveImpl(PathResource.java:253) > at io.undertow.core//io.undertow.server.handlers.resource.PathResource.serve(PathResource.java:111) > at io.undertow.core//io.undertow.server.handlers.resource.ResourceHandler$1.handleRequest(ResourceHandler.java:337) > at io.undertow.core//io.undertow.server.Connectors.executeRootHandler(Connectors.java:332) > at io.undertow.core//io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) > at java.base/java.lang.Thread.run(Thread.java:844) > {code} > All exceptions seems to repeat. This causes 16 tests to fail. When I use JDK8 or when I switch back to JSSE ALPN instead of wildfly-openssl, no test fail at all and there are no NPEs in server.log anymore, although the IllegalStateExceptions still remains there. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3620) Upgrade log4j-jboss-logmanager from 1.1.4.Final to 1.1.5.Final

by James Perkins (JIRA)

James Perkins created WFCORE-3620: ------------------------------------- Summary: Upgrade log4j-jboss-logmanager from 1.1.4.Final to 1.1.5.Final Key: WFCORE-3620 URL: https://issues.jboss.org/browse/WFCORE-3620 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins There was a minor [bug|JBEAP-14214] found in previous versions of {{org.jboss.logmanager:log4j-jboss-logmanager}}. This is fixed in 1.1.5.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9851) Remove security dependency on clustering subsystem / infinispan

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9851?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-9851: -------------------------------------- Tangentially, spi module seems to bring in more dependencies than needed, fixing WFLY-9857. > Remove security dependency on clustering subsystem / infinispan > --------------------------------------------------------------- > > Key: WFLY-9851 > URL: https://issues.jboss.org/browse/WFLY-9851 > Project: WildFly > Issue Type: Task > Components: Clustering, Domain Management, Security > Reporter: Tomaz Cerar > Assignee: Paul Ferraro > Priority: Critical > > Currently security subsystem depends on clustering subsystem modules which bring in a big transitive dependency tree (that cannot be broken). > Dependency is there only to establish capability requirements. > Please change code to use string constants instead of enums from clustering subsystem to break down the dependency tree. Whole reason for capabilities was to not have tightly coupled subsystems. > current sip from security subsystem dependency tree > {noformat} > [INFO] +- org.wildfly:wildfly-clustering-infinispan-spi:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | +- org.wildfly:wildfly-clustering-common:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | | +- org.wildfly:wildfly-clustering-service:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | | \- org.wildfly:wildfly-naming:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | | +- org.wildfly:wildfly-naming-client:jar:1.0.7.Final:compile > [INFO] | | | +- org.wildfly.client:wildfly-client-config:jar:1.0.0.Final:compile > [INFO] | | | \- org.jboss.marshalling:jboss-marshalling-river:jar:2.0.2.Final:compile > [INFO] | | \- org.wildfly.wildfly-http-client:wildfly-http-naming-client:jar:1.0.9.Final:compile > [INFO] | | +- org.wildfly.wildfly-http-client:wildfly-http-client-common:jar:1.0.9.Final:compile > [INFO] | | +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.1.Final:compile > [INFO] | | \- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.1.1.Final:compile > [INFO] | +- org.wildfly:wildfly-clustering-marshalling-spi:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | | \- org.wildfly:wildfly-clustering-marshalling-api:jar:12.0.0.Beta2-SNAPSHOT:compile > [INFO] | +- org.infinispan:infinispan-core:jar:9.1.6.Final:compile > [INFO] | | \- org.infinispan:infinispan-commons:jar:9.1.6.Final:compile > [INFO] | \- com.github.ben-manes.caffeine:caffeine:jar:2.6.1:compile > {noformat} > we even bring in inifinspan, as otherwise it does not compile. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9857) wildfly-clustering-spi brings in unnecessary/duplicated dependencies

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9857: ------------------------------------ Summary: wildfly-clustering-spi brings in unnecessary/duplicated dependencies Key: WFLY-9857 URL: https://issues.jboss.org/browse/WFLY-9857 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9857) wildfly-clustering-spi brings in unnecessary/duplicated dependencies

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9857?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9857: --------------------------------- Affects Version/s: 12.0.0.Beta1 > wildfly-clustering-spi brings in unnecessary/duplicated dependencies > -------------------------------------------------------------------- > > Key: WFLY-9857 > URL: https://issues.jboss.org/browse/WFLY-9857 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 12.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-24) Request Access to Openshift Organization on Github

by Peter Ruan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-24?page=com.atlassian.jira.plugin.s... ] Peter Ruan resolved SWSQE-24. ----------------------------- Resolution: Done > Request Access to Openshift Organization on Github > -------------------------------------------------- > > Key: SWSQE-24 > URL: https://issues.jboss.org/browse/SWSQE-24 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Peter Ruan > > Cucushift is a "closed" repository on Openshift.org > We need access to play with it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-24) Request Access to Openshift Organization on Github

by Peter Ruan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-24?page=com.atlassian.jira.plugin.s... ] Peter Ruan commented on SWSQE-24: --------------------------------- https://mojo.redhat.com/docs/DOC-28694 if you don't have access to that document, below is what you need Github private repo Access 1. Create an account with your Red Hat email in GitHub · Build software better, together. , and update your company as "Red Hat" and your real name from ldap to your GitHub profile . 2. Send email to aos-qe(a)redhat.com to request access private OpenShift github repo with your github id specified in email. Subject: Request to access OpenShift private github repos Body: I'm a new member/intern from OpenShift QE, my github id is <replace it with your github id>, my github name is <replace it with your github name>, Could you please help add me to OpenShift group in github so that I could have view access to some private repos. > Request Access to Openshift Organization on Github > -------------------------------------------------- > > Key: SWSQE-24 > URL: https://issues.jboss.org/browse/SWSQE-24 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Peter Ruan > > Cucushift is a "closed" repository on Openshift.org > We need access to play with it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7185) JSON-B 1.0 Support

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-7185?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-7185: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10872, https://github.com/wildfly/wildfly/pull/10900 (was: https://github.com/wildfly/wildfly/pull/10872) > JSON-B 1.0 Support > ------------------ > > Key: WFLY-7185 > URL: https://issues.jboss.org/browse/WFLY-7185 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 12.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9853) NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-9853?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-9853: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1510010 Bugzilla Update: Perform > NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-9853 > URL: https://issues.jboss.org/browse/WFLY-9853 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Chao Wang > Assignee: Stefan Guilhen > > "NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration" is recorded in server.log during quickstart example run by changing log level: > {noformat} > <logger category="org.jboss.as.security"> > <level name="TRACE"/> > </logger> > <logger category="org.jboss.security"> > <level name="TRACE"/> > </logger> > {noformat} > See detailed description in community discussion [#907134|https://developer.jboss.org/message/907134] > I choose Jira component picketbox since the exception is titled as "PBOX000293: Exception caught: javax.naming.NameNotFoundException" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-131) Logger.getEffectiveLevel() not working correctly

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-131?page=com.atlassian.jira.plu... ] Ingo Weiss moved JBEAP-14258 to JBLOGGING-131: ---------------------------------------------- Project: JBoss Logging (was: JBoss Enterprise Application Platform) Key: JBLOGGING-131 (was: JBEAP-14258) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: jboss-logging-log4j (was: Logging) Affects Version/s: (was: 7.1.0.GA) > Logger.getEffectiveLevel() not working correctly > ------------------------------------------------ > > Key: JBLOGGING-131 > URL: https://issues.jboss.org/browse/JBLOGGING-131 > Project: JBoss Logging > Issue Type: Bug > Components: jboss-logging-log4j > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Minor > > The Logger.getEffectiveLevel() method doesn't seem to return correct values. > In a test, we set the log level for a category to TRACE and the method sometimes returns TRACE and sometimes returns DEBUG. Whichever value is returns stays the same until the next time the application is deployed at which point it may change. > The same behavior seems to exist as well on EAP 7.0 and EAP 6.4. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

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 2018