May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFBUILD-39) Wildfly-build-tools ignores dependency management

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFBUILD-39?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil updated WFBUILD-39: ------------------------------------ Affects Version/s: 1.2.11.Final > Wildfly-build-tools ignores dependency management > ------------------------------------------------- > > Key: WFBUILD-39 > URL: https://issues.jboss.org/browse/WFBUILD-39 > Project: WildFly Build Tools > Issue Type: Bug > Affects Versions: 1.2.11.Final > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Critical > Fix For: 1.2.12.Final > > > After processing https://github.com/jbossas/jboss-eap7/pull/2594 the distribution still contains {{slf4j-api-1.7.22.redhat-1.jar}} artifact. > {noformat} > 44 ./jboss-eap-7.1/modules/system/layers/base/org/slf4j/main/slf4j-api-1.7.22.redhat-1.jar > 44 ./jboss-eap-7.1/modules/system/layers/base/org/slf4j/ext/main/slf4j-ext-1.7.22.redhat-2.jar > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-39) Wildfly-build-tools ignores dependency management

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFBUILD-39?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil updated WFBUILD-39: ------------------------------------ Fix Version/s: 1.2.12.Final > Wildfly-build-tools ignores dependency management > ------------------------------------------------- > > Key: WFBUILD-39 > URL: https://issues.jboss.org/browse/WFBUILD-39 > Project: WildFly Build Tools > Issue Type: Bug > Affects Versions: 1.2.11.Final > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Critical > Fix For: 1.2.12.Final > > > After processing https://github.com/jbossas/jboss-eap7/pull/2594 the distribution still contains {{slf4j-api-1.7.22.redhat-1.jar}} artifact. > {noformat} > 44 ./jboss-eap-7.1/modules/system/layers/base/org/slf4j/main/slf4j-api-1.7.22.redhat-1.jar > 44 ./jboss-eap-7.1/modules/system/layers/base/org/slf4j/ext/main/slf4j-ext-1.7.22.redhat-2.jar > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3992) Improving error messages from backend to cell popover

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3992?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3992: -------------------------------- Labels: ScenarioSimulation (was: ) > Improving error messages from backend to cell popover > ------------------------------------------------------ > > Key: DROOLS-3992 > URL: https://issues.jboss.org/browse/DROOLS-3992 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.22.0.Final > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > Labels: ScenarioSimulation > > Aim of this ticket: > - Improve error messages sent by server to the cell popover in case of specific errors: eg. > [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. > - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. > Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3992) Improving error messages from backend to cell popover

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3992?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3992: -------------------------------- Affects Version/s: 7.22.0.Final > Improving error messages from backend to cell popover > ------------------------------------------------------ > > Key: DROOLS-3992 > URL: https://issues.jboss.org/browse/DROOLS-3992 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.22.0.Final > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > Labels: ScenarioSimulation > > Aim of this ticket: > - Improve error messages sent by server to the cell popover in case of specific errors: eg. > [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. > - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. > Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3992) Improving error messages from backend to cell popover

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3992?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3992: -------------------------------- Tester: Jozef Marko > Improving error messages from backend to cell popover > ------------------------------------------------------ > > Key: DROOLS-3992 > URL: https://issues.jboss.org/browse/DROOLS-3992 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > > Aim of this ticket: > - Improve error messages sent by server to the cell popover in case of specific errors: eg. > [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. > - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. > Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3992) Improving error messages from backend to cell popover

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3992?page=com.atlassian.jira.plugi... ] Yeser Amer reassigned DROOLS-3992: ---------------------------------- Assignee: Yeser Amer (was: Daniele Zonca) > Improving error messages from backend to cell popover > ------------------------------------------------------ > > Key: DROOLS-3992 > URL: https://issues.jboss.org/browse/DROOLS-3992 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > > Aim of this ticket: > - Improve error messages sent by server to the cell popover in case of specific errors: eg. > [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. > - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. > Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2345) NPE in ASYM_ENCRYPT

by Bela Ban (Jira)

Bela Ban created JGRP-2345: ------------------------------ Summary: NPE in ASYM_ENCRYPT Key: JGRP-2345 URL: https://issues.jboss.org/browse/JGRP-2345 Project: JGroups Issue Type: Bug Affects Versions: 4.0.19 Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.1.0 Stack trace: {noformat} 2019-05-09 08:38:39,518 ERROR [org.jgroups.protocols.UDP] (jgroups-10,Clusterd6c8baf6-b087-4deb-a0b2-dbab8302a80atrunk-83693,umstest-win10-3-24714) failed processing batch: java.lang.NullPointerException at org.jgroups.protocols.Encrypt.up(Encrypt.java:192) at org.jgroups.protocols.ASYM_ENCRYPT.up(ASYM_ENCRYPT.java:176) at org.jgroups.protocols.BARRIER.up(BARRIER.java:196) at org.groups.stack.Protocol.up(Protocol.java:371) at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:216) at org.jgroups.stack.Protocol.up(Protocol.java:371) at org.jgroups.stack.Protocol.up(Protocol.java:371) at org.jgroups.stack.Protocol.up(Protocol.java:371) at org.jgroups.protocols.TP.passBatchUp(TP.java:1276) at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.passBatchUp(MaxOneThreadPerSender.java:284) at org.jgroups.util.SubmitToThreadPool$BatchHandler.run(SubmitToThreadPool.java:136) at org.jgroups.util.MaxOneThreadPerSender$BatchHandlerLoop.run(MaxOneThreadPerSender.java:273) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3992) Improving error messages from backend to cell popover

by Yeser Amer (Jira)

Yeser Amer created DROOLS-3992: ---------------------------------- Summary: Improving error messages from backend to cell popover Key: DROOLS-3992 URL: https://issues.jboss.org/browse/DROOLS-3992 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Yeser Amer Assignee: Daniele Zonca Aim of this ticket: - Improve error messages sent by server to the cell popover in case of specific errors: eg. [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12019) Cannot remove a undertow server resource at one time

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-12019?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-12019: ----------------------------------- {quote} Kabir Khan Does the management API diff thing compare operation definitions, or does it just do resources/attributes? {quote} [~brian.stansberry] - it only compares resources/attributes. > Cannot remove a undertow server resource at one time > ---------------------------------------------------- > > Key: WFLY-12019 > URL: https://issues.jboss.org/browse/WFLY-12019 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 16.0.0.Final > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > Cannot remove a server attribute. > {noformat} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server:remove() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.undertow.server.default-server.default-host was depended upon by service jboss.undertow.server.default-server.default-host.filter-ref.x-powered-by-header, service jboss.undertow.server.default-server.default-host.location. > /, service jboss.undertow.server.default-server.default-host.filter-ref.server-header", > "rolled-back" => true, > "response-headers" => undefined > } > {noformat} > However, it can be removed executing same command again. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12057) Upgrade WildFly Core 9.0.0.Beta5

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-12057: ---------------------------------- Summary: Upgrade WildFly Core 9.0.0.Beta5 Key: WFLY-12057 URL: https://issues.jboss.org/browse/WFLY-12057 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 17.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 May 2019