February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3618) [DMN Designer] Headers don't react on Enter key

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3618: ----------------------------------- Summary: [DMN Designer] Headers don't react on Enter key Key: DROOLS-3618 URL: https://issues.jboss.org/browse/DROOLS-3618 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.18.0.Final Reporter: Jozef Marko Assignee: Jozef Marko Header cells in expression editors don't react on the enter key. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4319) Installing layers erase existing installation content

by Jean-Francois Denise (Jira)

Jean-Francois Denise created WFCORE-4319: -------------------------------------------- Summary: Installing layers erase existing installation content Key: WFCORE-4319 URL: https://issues.jboss.org/browse/WFCORE-4319 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3617) [DMN Designer] Indirect boolean and structure has a constraint

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3617: ----------------------------------- Summary: [DMN Designer] Indirect boolean and structure has a constraint Key: DROOLS-3617 URL: https://issues.jboss.org/browse/DROOLS-3617 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.18.0.Final Reporter: Jozef Marko Assignee: Guilherme Carreiro Attachments: Screenshot from 2019-02-08 08-41-18.png If user declares *boolean* or a *Structure* indirectly, he is able to set a constarint for such data type entry, however he shouldn't be able to set the constraint in such case. Please see the attached screenshot. There are 4 entries while 2 has constraints and 2 have not. Expected is no of those 4 entries has constraint. -- 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 Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3616?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3616: ----------------------------------- Story Points: 3 Sprint: 2019 Week 05-07 > [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 > Priority: Major > Labels: drools-tools > 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-11687) Upgrade JBoss EJB Client to 4.0.14.Final

by Ondra Chaloupka (Jira)

Ondra Chaloupka created WFLY-11687: -------------------------------------- Summary: Upgrade JBoss EJB Client to 4.0.14.Final Key: WFLY-11687 URL: https://issues.jboss.org/browse/WFLY-11687 Project: WildFly Issue Type: Component Upgrade Components: EJB Affects Versions: 15.0.1.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Component upgrade of jboss ejb client which brings fixes of transaction timeout remoting ejb propagation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11686) Upgrade Picketlink from 2.5.5.SP12 to 2.5.5.SP13

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-11686?page=com.atlassian.jira.plugin... ] Tomas Hofman reassigned WFLY-11686: ----------------------------------- Assignee: Kabir Khan (was: Jason Greene) > Upgrade Picketlink from 2.5.5.SP12 to 2.5.5.SP13 > ------------------------------------------------ > > Key: WFLY-11686 > URL: https://issues.jboss.org/browse/WFLY-11686 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Tomas Hofman > Assignee: Kabir Khan > Priority: Major > Labels: downstream_dependency > Fix For: 14.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11686) Upgrade Picketlink from 2.5.5.SP12 to 2.5.5.SP13

by Tomas Hofman (Jira)

Tomas Hofman created WFLY-11686: ----------------------------------- Summary: Upgrade Picketlink from 2.5.5.SP12 to 2.5.5.SP13 Key: WFLY-11686 URL: https://issues.jboss.org/browse/WFLY-11686 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Tomas Hofman Assignee: Jason Greene Fix For: 14.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11684) Upgrade WildFly Transaction Client to 1.1.3.Final

by Ondra Chaloupka (Jira)

Ondra Chaloupka created WFLY-11684: -------------------------------------- Summary: Upgrade WildFly Transaction Client to 1.1.3.Final Key: WFLY-11684 URL: https://issues.jboss.org/browse/WFLY-11684 Project: WildFly Issue Type: Component Upgrade Components: EJB, Transactions Affects Versions: 15.0.1.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka The WildFly Transaction client should be upgraded as it contains fixes for ejb transaction propagation of timeout handling. These fixes influences behaviour of the system. Those fixes are partly involved in the released EAP 7.2.0 and they are not in the WildFly upstream. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3477) MVEL: expression (1 + 2 * 3 + 4 * $v ) causes "no such method or function " for bind variable

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3477?page=com.atlassian.jira.plugi... ] Mario Fusco reopened DROOLS-3477: --------------------------------- > MVEL: expression (1 + 2 * 3 + 4 * $v ) causes "no such method or function " for bind variable > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-3477 > URL: https://issues.jboss.org/browse/DROOLS-3477 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.11.0.Final > Environment: MVEL2 2.4.2 Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Attachments: mvel2-var-test2.zip, mvel2-var-test3.zip > > > Similar issue was reported and fixed in DROOLS-2854, there is another pattern which does not work. > When MVEL evaluates > m.setStatus( 1 + 2 * 3 + 4 * m.getStatus() ); > the following exception happens. > {noformat} > Exception executing consequence for rule "Hello World" in com.sample: [Error: no such method or function: m] > [Near : {... m.setStatus( 1 + 2 * 3 + 4 * m.getStatus() ); ....}] > {noformat} -- 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: ---------------------------------------- Tracked the error down to the undertow client. Filed a bug report there [UNDERTOW-1490|https://issues.jboss.org/browse/UNDERTOW-1490] > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019