March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12778) EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-12778?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-12778: ------------------------------------- Thanks [~spyrkob], If you don't mind can I look into this issue? > EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12778 > URL: https://issues.redhat.com/browse/WFLY-12778 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > When an EAR containing MDBS is deployed in one of the colocated master/slave servers, the application does not wait for the embedded broker to start up and generates these errors in the logs: > {code:java} > /14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => [ > "jboss.ra.activemq-ra", > "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory" > ], > {code} > When the broker is eventually started, these MDBs get deployed and start working fine without any redeployment but these errors are not desirable in the logs. > Defining the resource-ref in ejb-jar.xml or annotating with @Resource does not help either. > The application should wait for its dependencies to be available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5182) Update gwt-jsonix-schema-compiler in kie-parent

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5182?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5182: ---------------------------------------- [~jomarko] I had this [covered|https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/1229]. Admittedly I'll need to update it to a fixed version. > Update gwt-jsonix-schema-compiler in kie-parent > ----------------------------------------------- > > Key: DROOLS-5182 > URL: https://issues.redhat.com/browse/DROOLS-5182 > Project: Drools > Issue Type: Task > Affects Versions: 7.35.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools, kogito-tooling > > Once 1.2.0 verison of https://mvnrepository.com/artifact/org.kogito/gwt-jsonix-schema-compiler?... is dpeloyed, we should update it in our kie-parent pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5182) Update gwt-jsonix-schema-compiler in kie-parent

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5182: ----------------------------------- Summary: Update gwt-jsonix-schema-compiler in kie-parent Key: DROOLS-5182 URL: https://issues.redhat.com/browse/DROOLS-5182 Project: Drools Issue Type: Task Affects Versions: 7.35.0.Final Reporter: Jozef Marko Assignee: Jozef Marko Once 1.2.0 verison of https://mvnrepository.com/artifact/org.kogito/gwt-jsonix-schema-compiler?... is dpeloyed, we should update it in our kie-parent pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12829) Quickstart for MP OpenTracing 1.3

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-12829?page=com.atlassian.jira.plugi... ] Eduardo Martins updated WFLY-12829: ----------------------------------- Git Pull Request: https://github.com/wildfly/quickstart/pull/380, https://github.com/wildfly/quickstart/pull/394 > Quickstart for MP OpenTracing 1.3 > ---------------------------------- > > Key: WFLY-12829 > URL: https://issues.redhat.com/browse/WFLY-12829 > Project: WildFly > Issue Type: Task > Components: MP OpenTracing, Quickstarts > Affects Versions: 18.0.1.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 19.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5181) [Guided Rule Template] Template data tab is inconsistent if no variables defined

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5181?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5181: -------------------------------- Steps to Reproduce: # Go to http://kieci-02.lab.eng.brq.redhat.com:33940/business-central/ # Create new project and create a *Guided Rule Tumplate* in it # Go to Data tab # Press "Add row" Expected: UI reflects to the action and displays empty cells Actual !image-2020-03-19-10-15-18-705.png|thumbnail! was: # Go to http://kieci-02.lab.eng.brq.redhat.com:33940/business-central/ # Create new project and create a *Guided Rule* in it # Go to Data tab # Press "Add row" Expected: UI reflects to the action and displays empty cells Actual !image-2020-03-19-10-15-18-705.png|thumbnail! > [Guided Rule Template] Template data tab is inconsistent if no variables defined > -------------------------------------------------------------------------------- > > Key: DROOLS-5181 > URL: https://issues.redhat.com/browse/DROOLS-5181 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Affects Versions: 7.33.0.Final > Reporter: Anna Dupliak > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: TemplateData.webm, image-2020-03-19-10-15-18-705.png > > > If no template variables defined yet then, if user press *Add row* in *Data tab* of *Guided Rule Editor* the row is not appearing. At the same time the new rule appears in the Source tab. > Suggestion: to disable *Add row* button if no template var is defined > See: [^TemplateData.webm] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5181) [Guided Rule Template] Template data tab is inconsistent if no variables defined

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-5181: ------------------------------------ Summary: [Guided Rule Template] Template data tab is inconsistent if no variables defined Key: DROOLS-5181 URL: https://issues.redhat.com/browse/DROOLS-5181 Project: Drools Issue Type: Bug Components: Guided Template Editor Affects Versions: 7.33.0.Final Reporter: Anna Dupliak Assignee: Guilherme Gomes Attachments: TemplateData.webm, image-2020-03-19-10-15-18-705.png If no template variables defined yet then, if user press *Add row* in *Data tab* of *Guided Rule Editor* the row is not appearing. At the same time the new rule appears in the Source tab. Suggestion: to disable *Add row* button if no template var is defined See: [^TemplateData.webm] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5162) [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5162?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5162: ----------------------------------- Description: The DMN editor has the ability to import Java files as {{ItemDefinition}}. [~tari_manga] has requested the following enhancement: {quote} ... 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? By means of extra attribute, extensions, etc. whatever is more convenient {quote} *This JIRA is for Business Central, server-side marshalling, only. The linked JIRA is for client-side marshalling, when it becomes viable.* was: The DMN editor has the ability to import Java files as {{ItemDefinition}}. [~tari_manga] has requested the following enhancement: {quote} ... 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? By means of extra attribute, extensions, etc. whatever is more convenient {quote} This JIRA is for Business Central, server-side marshalling, only. The linked JIRA is for client-side marshalling, when it becomes viable. > [DMN Designer] Persist Java FQCN as ItemDefinition attribute for converted Java classes > --------------------------------------------------------------------------------------- > > Key: DROOLS-5162 > URL: https://issues.redhat.com/browse/DROOLS-5162 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools, kogito-tooling > > The DMN editor has the ability to import Java files as {{ItemDefinition}}. > [~tari_manga] has requested the following enhancement: > {quote} > ... > 2. ... could the DMN editor note in the ItemDefintion the FQN of the java class which was used? > By means of extra attribute, extensions, etc. whatever is more convenient > {quote} > *This JIRA is for Business Central, server-side marshalling, only. The linked JIRA is for client-side marshalling, when it becomes viable.* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2462) TransferQueueBundler: drop messages if queue is full

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2462?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2462: --------------------------- Description: When a bundler (like {{TransferQueueBundler}}) has a full queue, the senders will block. This can happen for example when the TCP {{send}} blocks due to a full send-window. Retransmission requests and responses compound the problem when the TQB's queue is full. Therefore, in addition to blocking, we should add an option to _drop_ packets when the queue is full. Investigate whether we could use some priority based scheme, which drops non-important messages first. Also investigate whether senders can selectively be unblocked when the queue is full, to either drop or add their messages. This could be done for example by removing elements from the queue, using the aformentioned filter. Look at random early detection )\[1\]) for inspiration. \[1\] https://en.wikipedia.org/wiki/Random_early_detection was: When a bundler (like {{TransferQueueBundler}}) has a full queue, the senders will block. This can happen for example when the TCP {{send}} blocks due to a full send-window. Retransmission requests and responses compound the problem when the TQB's queue is full. Therefore, in addition to blocking, we should add an option to _drop_ packets when the queue is full. Investigate whether we could use some priority based scheme, which drops non-important messages first. Also investigate whether senders can selectively be unblocked when the queue is full, to either drop or add their messages. This could be done for example by removing elements from the queue, using the aformentioned filter. > TransferQueueBundler: drop messages if queue is full > ---------------------------------------------------- > > Key: JGRP-2462 > URL: https://issues.redhat.com/browse/JGRP-2462 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.2, 5.0.0.Alpha4 > > > When a bundler (like {{TransferQueueBundler}}) has a full queue, the senders will block. > This can happen for example when the TCP {{send}} blocks due to a full send-window. > Retransmission requests and responses compound the problem when the TQB's queue is full. > Therefore, in addition to blocking, we should add an option to _drop_ packets when the queue is full. Investigate whether we could use some priority based scheme, which drops non-important messages first. > Also investigate whether senders can selectively be unblocked when the queue is full, to either drop or add their messages. This could be done for example by removing elements from the queue, using the aformentioned filter. > Look at random early detection )\[1\]) for inspiration. > \[1\] https://en.wikipedia.org/wiki/Random_early_detection -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2462) TransferQueueBundler: drop messages if queue is full

by Bela Ban (Jira)

Bela Ban created JGRP-2462: ------------------------------ Summary: TransferQueueBundler: drop messages if queue is full Key: JGRP-2462 URL: https://issues.redhat.com/browse/JGRP-2462 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.2.2, 5.0.0.Alpha4 When a bundler (like {{TransferQueueBundler}}) has a full queue, the senders will block. This can happen for example when the TCP {{send}} blocks due to a full send-window. Retransmission requests and responses compound the problem when the TQB's queue is full. Therefore, in addition to blocking, we should add an option to _drop_ packets when the queue is full. Investigate whether we could use some priority based scheme, which drops non-important messages first. Also investigate whether senders can selectively be unblocked when the queue is full, to either drop or add their messages. This could be done for example by removing elements from the queue, using the aformentioned filter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13237) Investigate mod_cluster contexts appear 'enabled' in undertow proxy even without ENABLE-APP message

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-13237?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-13237: ------------------------------------- Hi [~rhusar], Are you working on this issue? Thanks, Parul Sharma > Investigate mod_cluster contexts appear 'enabled' in undertow proxy even without ENABLE-APP message > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13237 > URL: https://issues.redhat.com/browse/WFLY-13237 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > See https://github.com/wildfly/wildfly/pull/12974#pullrequestreview-372617078 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 March 2020