February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-415) Change JBoss schema license to ALS 2.0

by ehsavoie Hugonnet (Jira)

ehsavoie Hugonnet created JBMETA-415: ---------------------------------------- Summary: Change JBoss schema license to ALS 2.0 Key: JBMETA-415 URL: https://issues.jboss.org/browse/JBMETA-415 Project: JBoss Metadata Issue Type: Enhancement Affects Versions: 12.0.0.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet All JBoss schemas should be updated to be under ASL 2.0 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3616) [DMN Designer] Literal expression name and data type popup missing

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3616: ----------------------------------- Summary: [DMN Designer] Literal expression name and data type popup missing Key: DROOLS-3616 URL: https://issues.jboss.org/browse/DROOLS-3616 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.18.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2019-02-08 10-01-34.png If user tries to change name and data type of root Literal expression, the **Name && Data Type** popup is missing. Other expression types works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10380) ThreadPoolExecutor leak under SM due to lack of privileged block

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-10380?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet resolved WFLY-10380. -------------------------------------- Fix Version/s: 16.0.0.Beta1 Resolution: Done It seems to be corrected in Artemis 2.6.x BUT there is a bug in Artemis that fills the thread pool to the max value and keeps on replacing threads periodically. > ThreadPoolExecutor leak under SM due to lack of privileged block > ---------------------------------------------------------------- > > Key: WFLY-10380 > URL: https://issues.jboss.org/browse/WFLY-10380 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: David Lloyd > Assignee: ehsavoie Hugonnet > Priority: Critical > Labels: security-manager > Fix For: 16.0.0.Beta1 > > > Still researching the source of these leaks. > The way the leak happens is, a {{java.util.concurrent.ThreadPoolExecutor}} is constructed from an unprivileged context. The pool starts up and threads are created without a problem, however, the thread pool is never shut down. The finalizer runs but since it tries to shut down the pool with an access control context that was captured during construction, it fails because the context did not have the {{modifyThread}} {{RuntimePermission}}, and the thread pool never shuts down. > We need to identify the points where TPEs are being constructed without controlled privileges. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11639) mod cluster and HTTP2 enabled (the default) not working

by Andreas Asplund (Jira)

[ https://issues.jboss.org/browse/WFLY-11639?page=com.atlassian.jira.plugin... ] Andreas Asplund commented on WFLY-11639: ---------------------------------------- HTTP2-Settings=[AAEAABAAAAIAAAABAAQAAP//AAUAAEAA] is incorrectly encoded. It is currently encoded with the standard Base64 encoding table but according to the HTTP2 spec it should be encoded with the Base64url table. See [https://http2.github.io/http2-spec/#discover-http|https://http2.github.io...]. > mod cluster and HTTP2 enabled (the default) not working > ------------------------------------------------------- > > Key: WFLY-11639 > URL: https://issues.jboss.org/browse/WFLY-11639 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 15.0.1.Final > Environment: Mac OS X 10.14.3 > Tested on both > AdoptOpenJDK 1.8.0_202-b08 > AdoptOpenJDK 11.0.1+13 > Reporter: Andreas Asplund > Assignee: Radoslav Husar > Priority: Major > > mod cluster and HTTP2 enabled (the default) when using listener default in the modcluster subsystem. When turning off HTTP2 the clustering starts working again. Nothing is printed in the logs by default so DEBUG logging has to be turned on for undertow. > Steps to reproduce: > {code} > unzip wildfly-dist-15.0.1.Final.zip > # Terminal 1 > cd wildfly-15.0.1.Final/bin/ > ./standalone.sh -c standalone-load-balancer.xml -Djava.net.preferIPv4Stack=true -b 127.0.0.1 -Djboss.modcluster.multicast.address=230.0.0.4 > # Terminal 2 > cd wildfly-15.0.1.Final/bin/ > ./standalone.sh -c standalone-ha.xml -Djboss.node.name=node1 -Djboss.socket.binding.port-offset=100 -Djboss.modcluster.multicast.address=230.0.0.4 > # Terminal 3 > cd wildfly-15.0.1.Final/bin/ > ./standalone.sh -c standalone-ha.xml -Djboss.node.name=node2 -Djboss.socket.binding.port-offset=200 -Djboss.modcluster.multicast.address=230.0.0.4 > # Terminal 4 > cd wildfly-15.0.1.Final/bin/ > ./jboss-cli.sh -c > /subsystem=logging/logger=io.undertow:add(level=ALL) > /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL) > connect localhost:10090 > /subsystem=logging/logger=io.undertow:add(level=ALL) > /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL) > /subsystem=modcluster/proxy=default:write-attribute(name=listener,value=default) > reload > connect localhost:10190 > /subsystem=logging/logger=io.undertow:add(level=ALL) > /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL) > /subsystem=modcluster/proxy=default:write-attribute(name=listener,value=default) > reload > {code} > The following can be seen in the logs on the proxied servers: > {code} > 16:30:23,409 TRACE [io.undertow.request] (default I/O-7) Opened connection with /127.0.0.1:50002 > 16:30:23,410 DEBUG [io.undertow.request.error-response] (default I/O-7) Setting error code 500 for exchange HttpServerExchange{ OPTIONS * request {HTTP2-Settings=[AAEAABAAAAIAAAABAAQAAP//AAUAAEAA], Connection=[Upgrade, HTTP2-Settings], Upgrade=[h2c], User-Agent=[mod_cluster ping], Host=[127.0.0.1]} response {}}: java.lang.RuntimeException > at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1410) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:393) > 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.HttpReadListener.handleEvent(HttpReadListener.java:59) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > 16:30:23,410 DEBUG [io.undertow.request.io] (default I/O-7) UT005013: An IOException occurred: java.io.IOException: Invalid base64 character encountered: 47 > at io.undertow.util.FlexBase64$Decoder.nextByte(FlexBase64.java:1048) > at io.undertow.util.FlexBase64$Decoder.nextByte(FlexBase64.java:1015) > at io.undertow.util.FlexBase64$Decoder.decode(FlexBase64.java:1277) > at io.undertow.util.FlexBase64$Decoder.decode(FlexBase64.java:1347) > at io.undertow.util.FlexBase64$Decoder.decode(FlexBase64.java:1413) > at io.undertow.util.FlexBase64$Decoder.access$500(FlexBase64.java:983) > at io.undertow.util.FlexBase64.decodeURL(FlexBase64.java:320) > at io.undertow.server.protocol.http2.Http2UpgradeHandler.handleHttp2Upgrade(Http2UpgradeHandler.java:158) > at io.undertow.server.protocol.http2.Http2UpgradeHandler.handleUpgradeBody(Http2UpgradeHandler.java:107) > at io.undertow.server.protocol.http2.Http2UpgradeHandler.handleRequest(Http2UpgradeHandler.java:97) > at io.undertow.server.handlers.DisallowedMethodsHandler.handleRequest(DisallowedMethodsHandler.java:61) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > 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.HttpReadListener.handleEvent(HttpReadListener.java:59) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > 16:30:23,411 TRACE [io.undertow.server.HttpServerExchange] (default I/O-7) Starting to write response for HttpServerExchange{ OPTIONS * request {HTTP2-Settings=[AAEAABAAAAIAAAABAAQAAP//AAUAAEAA], Connection=[Upgrade, HTTP2-Settings], Upgrade=[h2c], User-Agent=[mod_cluster ping], Host=[127.0.0.1]} response {Connection=[keep-alive], Content-Length=[0], Date=[Wed, 23 Jan 2019 15:30:23 GMT]}} > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4318) Upgrade jboss-classfilewriter from 1.2.2.Final to 1.2.3.Final

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4318: -------------------------------------- Summary: Upgrade jboss-classfilewriter from 1.2.2.Final to 1.2.3.Final Key: WFCORE-4318 URL: https://issues.jboss.org/browse/WFCORE-4318 Project: WildFly Core Issue Type: Component Upgrade Components: Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 8.0.0.Beta5 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4314) Enchance keystore CLI commands

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFCORE-4314?page=com.atlassian.jira.plugi... ] Bartosz Baranowski edited comment on WFCORE-4314 at 2/8/19 2:28 AM: -------------------------------------------------------------------- * read-alias ** dumps HEXed key, signature etc. Usually its not required? Add 'verbose' parameter ** requires 'alias' parameter, maybe should be 'name' to align with other server resources? * read-aliases - add 'recursive' and 'verbose'(check above) to allow read of more than names? * add default 'relative-to' to avoid punching "jboss.server.config.dir" * auto complete does not work from subsystem=elytron level. ie /subsystem=elytron/key-store=X:add - this will autocomplete, however cd /subsystem=elytron; key-store=X:add - this wont ( even 'key'+TAB wont) was (Author: baranowb): * read-alias ** dumps HEXed key, signature etc. Usually its not required? Add 'verbose' parameter ** requires 'alias' parameter, maybe should be 'name' to align with other server resources? * read-aliases - add 'recursive' and 'verbose'(check above) to allow read of more than names? * add default 'relative-to' to avoid punching "jboss.server.config.dir" * auto complete does not work from subsystem=elytron level. ie /subsystem=elytron/key-store=X:add - this will autocomplete, however cd /subsystem=elytron; key-store=X:add - this wont ( even 'key'+TAB wont) Improve output of read alias CLI command. Right now, by default read OP dumps every piece of information, like public-key, signature etc etc. Those are in HEX form, which are useful, but clutter output since they are really long. In case of one entry it is fine, but if there are more, it might be really hard to follow. verbos=true - full info, default, verbose==false ? > Enchance keystore CLI commands > ------------------------------ > > Key: WFCORE-4314 > URL: https://issues.jboss.org/browse/WFCORE-4314 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2330) Replace StringBuilder with simple string concatenation

by Bela Ban (Jira)

Bela Ban created JGRP-2330: ------------------------------ Summary: Replace StringBuilder with simple string concatenation Key: JGRP-2330 URL: https://issues.jboss.org/browse/JGRP-2330 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.0.17 Apparently simple string concatenation is faster than StringBuilder.append(). Also, we have occurrences of StringBuilder.append() that's not guarded by a {{log.isTraceEnabled()}} (e.g. in {{NAKACK2.overwriteDigest()}}): remove that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3062) [DMN Designer] [UX] Automatic layout feature prompt

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3062?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3062: ------------------------------------- I vote for second one, if I can :) > [DMN Designer] [UX] Automatic layout feature prompt > --------------------------------------------------- > > Key: DROOLS-3062 > URL: https://issues.jboss.org/browse/DROOLS-3062 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Liz Clayton > Priority: Major > Labels: UX, drools-tools > > User should be able to invoke automatic layout feature anytime during diagram design phase. There should appear prompt that would explain the autolayout feature. > Please propose the the prompt. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3613) Error testing a rule scenario with a Map

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3613?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3613: ---------------------------------- Story Points: 3 > Error testing a rule scenario with a Map > ---------------------------------------- > > Key: DROOLS-3613 > URL: https://issues.jboss.org/browse/DROOLS-3613 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Fix serialization format from Map to string -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4317) Upgrade jboss-logmanager from 2.1.5.Final to 2.1.7.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4317?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4317: --------------------------------------- Please note I've left LOGMGR-218 open as I need to get a fix into master. However the 2.1 branch (2.1.7.Final tag) includes the fix so it can be considered resolved for this JIRA. > Upgrade jboss-logmanager from 2.1.5.Final to 2.1.7.Final > -------------------------------------------------------- > > Key: WFCORE-4317 > URL: https://issues.jboss.org/browse/WFCORE-4317 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Upgrade jboss-logmanager from 2.1.5.Final to 2.1.7.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019