December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14243) New JAXB tests in WFLY-13968 fails on ee9 profile

by Ricardo Martin Camarero (Jira)

Ricardo Martin Camarero created WFLY-14243: ---------------------------------------------- Summary: New JAXB tests in WFLY-13968 fails on ee9 profile Key: WFLY-14243 URL: https://issues.redhat.com/browse/WFLY-14243 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Ricardo Martin Camarero Assignee: Ricardo Martin Camarero The new JAXB tests introduced in WFLY-13968 fails when using the ee9 profile: * org.jboss.as.test.integration.jaxb.unit.JAXBContextSystemPropCustomTestCase * org.jboss.as.test.integration.jaxb.unit.JAXBContextUsingPropertiesTestCase The reason is that in ee9 the system property and the keys inside the {{jaxb.properties}} file needs to be prefixed by {{jakarta}} instead of {{javax}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14234) EJB bean method direct memory buffer leaking

by Mike Zhary (Jira)

[ https://issues.redhat.com/browse/WFLY-14234?page=com.atlassian.jira.plugi... ] Mike Zhary commented on WFLY-14234: ----------------------------------- I hope it'll help with investigations from your side. > EJB bean method direct memory buffer leaking > -------------------------------------------- > > Key: WFLY-14234 > URL: https://issues.redhat.com/browse/WFLY-14234 > Project: WildFly > Issue Type: Bug > Components: EJB, IO > Affects Versions: 19.0.0.Final > Reporter: Mike Zhary > Assignee: Flavia Rainone > Priority: Major > Attachments: 2020-11-10-112753_563x276_scrot.png, src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java > > > Wildfly.19.0.1.Final standalone > We're using haproxy to balance ejb calls between wildfly servers. > That's very useful model, but there are problems with it. > All connections are declared as remote-outbound-connection and it works. > {code} > <remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}"> > <properties> > <property name="SASL_POLICY_NOANONYMOUS" value="false"/> > <property name="SSL_ENABLED" value="false"/> > </properties> > </remote-outbound-connection> > {code} > But there is the problem when some from servers is offline. haproxy send response by http and sends RST by tcp, but WF can't make sense of this response. > Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online) > But everything is clear, when port closed or server don't response for a calls. > Haproxy doesn't have feature to don't listen port if backed is offline. > At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case) > At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each. > Take a look: > !2020-11-10-112753_563x276_scrot.png|thumbnail! > Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254 > The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there. > We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design. > As per investigations DMB used for an SSL connection, but we don't it. > So we were to patch jboss-remoting class RemoteConnectionProvider. > after that we'd solved issue with leaking of DMB. > Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java] > Please take look how this bug can be fixed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14234) EJB bean method direct memory buffer leaking

by Mike Zhary (Jira)

[ https://issues.redhat.com/browse/WFLY-14234?page=com.atlassian.jira.plugi... ] Mike Zhary commented on WFLY-14234: ----------------------------------- Hi. there are to be 2 servers and haproxy between them. [wildfly-server1] <-> [haproxy] <-> [wildfly-server2] there are to be defined remote connections to haproxy server like this: {code} <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/> <outbound-connections> <remote-outbound-connection name="remote-ejb-connection" outbound-socket-binding-ref="remote-ejb" protocol="http-remoting" security-realm="ejb-security-realm" username="ejb"> <properties> <property name="SASL_POLICY_NOANONYMOUS" value="false"/> <property name="SSL_ENABLED" value="false"/> </properties> </remote-outbound-connection> </outbound-connections> {code} {code} <outbound-socket-binding name="remote-ejb"> <remote-destination host="test-ejb-balance01" port="30001"/> </outbound-socket-binding> {code} haproxy.cfg {code} ### start config for haproxy_host.name balance frontend balance_test-wf01 bind 192.168.230.13:30000 mode tcp default_backend test-wf01_servers option tcplog log global capture request header X-Forwarded-For len 15 backend test-wf01_servers balance roundrobin server server-test-wf01 test-wf01:8080 check ### stop config for haproxy_host.name balance ### start config for haproxy_host.name balance frontend balance_test-wf02 bind 192.168.230.13:30001 mode tcp default_backend test-wf02_servers option tcplog log global capture request header X-Forwarded-For len 15 backend test-wf02_servers balance roundrobin server server-test-wf02 test-wf02:8080 check ### stop config for haproxy_host.name balance {code} You can see tcp mode in *haproxy.cfg*, but I'd tried even http mode. In order to reproduce this scheme I deployed application which calls remote-ejb on wildfly-server2. When wildfly-server2 is online there are no problems. But if I'll shutdown wildfly there I'll have situation I described before. > EJB bean method direct memory buffer leaking > -------------------------------------------- > > Key: WFLY-14234 > URL: https://issues.redhat.com/browse/WFLY-14234 > Project: WildFly > Issue Type: Bug > Components: EJB, IO > Affects Versions: 19.0.0.Final > Reporter: Mike Zhary > Assignee: Flavia Rainone > Priority: Major > Attachments: 2020-11-10-112753_563x276_scrot.png, src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java > > > Wildfly.19.0.1.Final standalone > We're using haproxy to balance ejb calls between wildfly servers. > That's very useful model, but there are problems with it. > All connections are declared as remote-outbound-connection and it works. > {code} > <remote-outbound-connection name="{{ c.name }}" outbound-socket-binding-ref="{{ c.socket_binding }}" protocol="http-remoting" security-realm="{{ c.security_realm }}" username="{{ c.user }}"> > <properties> > <property name="SASL_POLICY_NOANONYMOUS" value="false"/> > <property name="SSL_ENABLED" value="false"/> > </properties> > </remote-outbound-connection> > {code} > But there is the problem when some from servers is offline. haproxy send response by http and sends RST by tcp, but WF can't make sense of this response. > Problem can be reprouced when servers listening port, but there is no repsonse for ejb call(in our case it means haproxy doesn't have suitable backend online) > But everything is clear, when port closed or server don't response for a calls. > Haproxy doesn't have feature to don't listen port if backed is offline. > At OS problems shows as huge count(equal to thread count) of connections in state CLOSE_WAIT. That means server had send packet TCP_FIN and client accepted it, but there were no respond on it. In other words WF and it's subsystems didn't agree with closing connection and it becomes to CLOSE_WAIT. At OS side closing connection in sometime and took it as dead(it's normal case) > At WF memory it appears as growing count of objects org.xnio.ByteBufferSlicePool$PooledByteBuffer, that have attribute buffer that holds about 2mb each. > Take a look: > !2020-11-10-112753_563x276_scrot.png|thumbnail! > Problem allocated in XNIO library. There were found a mistake and looks very similar to our problem. XNIO-254 > The same time we'd found XNIO-380 and we tried it with last version of this library(snapshot 3.9), no results were there. > We tried get undrestanding ow DMB clean, but did nothing due to too complicated code design. > As per investigations DMB used for an SSL connection, but we don't it. > So we were to patch jboss-remoting class RemoteConnectionProvider. > after that we'd solved issue with leaking of DMB. > Our patched library: [^src_main_java_org_jboss_remoting3_remote_RemoteConnectionProvider.java] > Please take look how this bug can be fixed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ELYWEB-119) Create GitHub CI Workflow

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-119: --------------------------------------- Summary: Create GitHub CI Workflow Key: ELYWEB-119 URL: https://issues.redhat.com/browse/ELYWEB-119 Project: Elytron Web Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.8.1.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5903) [DMN Designer] - possibility to sort enumerations list alphabetically

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5903?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5903: ---------------------------------------- [~uxdlc] I reassigned to [~karreiro] but it may well require UX involvement to consider how/where the User can invoke preset sorting. > [DMN Designer] - possibility to sort enumerations list alphabetically > --------------------------------------------------------------------- > > Key: DROOLS-5903 > URL: https://issues.redhat.com/browse/DROOLS-5903 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Lubomír Terifaj > Assignee: Guilherme Gomes > Priority: Minor > Labels: UXTeam, drools-tools > Attachments: sort-enumerations.png > > > See attached screenshot > The issue has been reported by [~msnoussi1]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5903) [DMN Designer] - possibility to sort enumerations list alphabetically

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5903?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-5903: -------------------------------------- Assignee: Guilherme Gomes (was: Elizabeth Clayton) > [DMN Designer] - possibility to sort enumerations list alphabetically > --------------------------------------------------------------------- > > Key: DROOLS-5903 > URL: https://issues.redhat.com/browse/DROOLS-5903 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Lubomír Terifaj > Assignee: Guilherme Gomes > Priority: Minor > Labels: UXTeam, drools-tools > Attachments: sort-enumerations.png > > > See attached screenshot > The issue has been reported by [~msnoussi1]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5912) Rule relationship analysis graph : fine grained nodes

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5912?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5912: ------------------------------------------- We may revisit this JIRA after releasing the first version and getting feedback. Experiment code: https://github.com/tkobayas/drools/tree/BAPL-1788-graph-dev-fine-grained > Rule relationship analysis graph : fine grained nodes > ----------------------------------------------------- > > Key: DROOLS-5912 > URL: https://issues.redhat.com/browse/DROOLS-5912 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.47.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Consider fine grained nodes where Node = Constraints/Actions as an advanced feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5912) Rule relationship analysis graph : fine grained nodes

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5912: ----------------------------------------- Summary: Rule relationship analysis graph : fine grained nodes Key: DROOLS-5912 URL: https://issues.redhat.com/browse/DROOLS-5912 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 7.47.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi Consider fine grained nodes where Node = Constraints/Actions as an advanced feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5911) It's not possible to save arrow edits on DMN Editor

by Lubomír Terifaj (Jira)

[ https://issues.redhat.com/browse/DROOLS-5911?page=com.atlassian.jira.plug... ] Lubomír Terifaj commented on DROOLS-5911: ----------------------------------------- The issue has been found during KOGITO-3998 review. I am adding steps to reproduce. > It's not possible to save arrow edits on DMN Editor > --------------------------------------------------- > > Key: DROOLS-5911 > URL: https://issues.redhat.com/browse/DROOLS-5911 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.48.0.Final > Reporter: Wagner Lemos > Assignee: Roger Martinez > Priority: Major > Labels: Stunner, kogito, kogito-tooling > > On the DMN Editor, making a change on the arrow that connects two nodes isn't being saved. An example of change is moving the rear or tip of the arrow to another side of the node -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5853) Rule relationship analysis graph : convert model into graph

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5853?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5853: -------------------------------------- Summary: Rule relationship analysis graph : convert model into graph (was: Rule relationship analysis core : convert model into graph) > Rule relationship analysis graph : convert model into graph > ----------------------------------------------------------- > > Key: DROOLS-5853 > URL: https://issues.redhat.com/browse/DROOLS-5853 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.46.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Convert model into navigable graph which is the basis of visualization (regardless of visualization methods). > See https://github.com/mariofusco/drools-impact-analysis -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 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 December 2020