June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4506) Upgrade JBoss MSC to 1.4.6.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4506?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4506: --------------------------------------- Diff https://github.com/jboss-msc/jboss-msc/compare/1.4.5.Final...1.4.6.Final > Upgrade JBoss MSC to 1.4.6.Final > -------------------------------- > > Key: WFCORE-4506 > URL: https://issues.jboss.org/browse/WFCORE-4506 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 9.0.0.Beta8 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4506) Upgrade JBoss MSC to 1.4.6.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4506?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4506: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3802 > Upgrade JBoss MSC to 1.4.6.Final > -------------------------------- > > Key: WFCORE-4506 > URL: https://issues.jboss.org/browse/WFCORE-4506 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 9.0.0.Beta8 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-196) Refactor Pipeline To Use IstioOC Client

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-196?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo closed SWSQE-196. ----------------------------------------- Resolution: Out of Date > Refactor Pipeline To Use IstioOC Client > --------------------------------------- > > Key: SWSQE-196 > URL: https://issues.jboss.org/browse/SWSQE-196 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matthew Mahoney > Assignee: Michael Foley > Priority: Major > > Refactor the Pipeline to use IstioOC Client -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4123) Drools project build failure with kjar packaging starting from version 7.7

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4123?page=com.atlassian.jira.plugi... ] Luca Molteni reassigned DROOLS-4123: ------------------------------------ Assignee: Luca Molteni (was: Ant Stephenson) > Drools project build failure with kjar packaging starting from version 7.7 > -------------------------------------------------------------------------- > > Key: DROOLS-4123 > URL: https://issues.jboss.org/browse/DROOLS-4123 > Project: Drools > Issue Type: Bug > Components: build > Affects Versions: 7.7.0.Final, 7.22.0.Final > Environment: ubuntu18.04 > Reporter: Bekarys Kuspan > Assignee: Luca Molteni > Priority: Major > Attachments: testProject.zip > > > When I want to build a project using kjar packaging type, with drools versions higher than 7.7.0,by typing the command "mvn clean package" it throws an error message. However, for lower versions of drools, for example 7.6.0, build is successful. I tried all versions up to 7.22.0 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12161) The expression for the value of share-prepared-statements does not work in XA datasource .

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-12161?page=com.atlassian.jira.plugin... ] Tomas Hofman updated WFLY-12161: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12338 > The expression for the value of share-prepared-statements does not work in XA datasource . > ------------------------------------------------------------------------------------------ > > Key: WFLY-12161 > URL: https://issues.jboss.org/browse/WFLY-12161 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 17.0.0.Beta1 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > > - Although , the "expressions-allowed" is true for "share-prepared-statements" , the expression for it does not work . > -------------------------------------------- > [standalone@localhost:9990 /] /subsystem=datasources/xa-data-source=ExampleXADS:read-resource-description() > "share-prepared-statements" => { > "type" => BOOLEAN, > "description" => "Whether to share prepared statements, i.e. whether asking for same statement twice without closing uses the same underlying prepared statement", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > --------------------------------------------- > - It shows below error if we set expression for share-prepared-statements . > --------------------------------------------- > 18:32:07,698 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 41) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("xa-data-source" => "ExampleXADS") > ]): java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.asBoolean(ModelValue.java:69) > at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:324) > at org.jboss.as.connector.subsystems.datasources.DataSourceModelNodeUtil.xaFrom(DataSourceModelNodeUtil.java:292) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceAdd.secondRuntimeStep(AbstractDataSourceAdd.java:298) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceAdd$1.execute(AbstractDataSourceAdd.java:134) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > --------------------------------------------- > - However , it works in a non-xa datasource . -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2353) Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from" during normal operation

by Radoslav Husar (Jira)

Radoslav Husar created JGRP-2353: ------------------------------------ Summary: Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from" during normal operation Key: JGRP-2353 URL: https://issues.jboss.org/browse/JGRP-2353 Project: JGroups Issue Type: Bug Affects Versions: 4.0.19 Reporter: Radoslav Husar Assignee: Bela Ban The problem is in design, when a message with out of date key is received, its dropped and retransmitted with the new key, however, logging the "WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-3,null,null) Y: unrecognized cipher; discarding message from X". Unless a better solution is implemented, the least we could do, is improve the message to indicate this is part of normal operation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2353) Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from X" during normal operation

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2353?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2353: --------------------------------- Summary: Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from X" during normal operation (was: Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from" during normal operation) > Enabling ASYM_ENCRYPT#change_key_on_leave logs "unrecognized cipher; discarding message from X" during normal operation > ----------------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2353 > URL: https://issues.jboss.org/browse/JGRP-2353 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.19 > Reporter: Radoslav Husar > Assignee: Bela Ban > Priority: Major > > The problem is in design, when a message with out of date key is received, its dropped and retransmitted with the new key, however, logging the "WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-3,null,null) Y: unrecognized cipher; discarding message from X". > Unless a better solution is implemented, the least we could do, is improve the message to indicate this is part of normal operation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11983) Unify line-endings of bat scripts (regression against WF15)

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11983?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11983: --------------------------------- Priority: Major (was: Critical) > Unify line-endings of bat scripts (regression against WF15) > ----------------------------------------------------------- > > Key: WFLY-11983 > URL: https://issues.jboss.org/browse/WFLY-11983 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 16.0.0.Final > Reporter: Marek Kopecky > Assignee: Radoslav Husar > Priority: Major > > Line-endings of bat scripts should be unified. This is regression against WF15. > Some files in WF16 uses CRLF, another LF only. We need to clarify the recommended line ending and use this line ending in all Windows scripts. > WF16: > {noformat} > $ find | grep bat$ | xargs file > ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jboss-cli.bat: DOS batch file, ASCII text > ./elytron-tool.bat: DOS batch file, ASCII text > ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators > ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators > ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators > ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.conf.bat: ASCII text, with CRLF line terminators > ./common.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jdr.bat: DOS batch file, ASCII text > ./jconsole.bat: DOS batch file, ASCII text > ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.conf.bat: ASCII text, with CRLF line terminators > ./standalone.conf.bat: ASCII text, with CRLF line terminators > ./add-user.bat: DOS batch file, ASCII text > $ > {noformat} > WF15: > {noformat} > $ find | grep bat$ | xargs file > ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jboss-cli.bat: DOS batch file, ASCII text, with CRLF line terminators > ./elytron-tool.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators > ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators > ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators > ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.conf.bat: ASCII text, with CRLF line terminators > ./common.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jdr.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jconsole.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.conf.bat: ASCII text, with CRLF line terminators > ./standalone.conf.bat: ASCII text, with CRLF line terminators > ./add-user.bat: DOS batch file, ASCII text, with CRLF line terminators > $ > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4502) Unify line-endings of bat and ps1 scripts (regression against WF15)

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4502?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4502: ---------------------------------- Priority: Major (was: Critical) > Unify line-endings of bat and ps1 scripts (regression against WF15) > ------------------------------------------------------------------- > > Key: WFCORE-4502 > URL: https://issues.jboss.org/browse/WFCORE-4502 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 9.0.0.Beta7 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Line-endings of bat scripts should be unified. This is regression against WF15. > Some files in WF16 uses CRLF, another LF only. We need to clarify the recommended line ending and use this line ending in all Windows scripts. > WF16: > {noformat} > $ find | grep bat$ | xargs file > ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jboss-cli.bat: DOS batch file, ASCII text > ./elytron-tool.bat: DOS batch file, ASCII text > ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators > ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators > ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators > ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.conf.bat: ASCII text, with CRLF line terminators > ./common.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jdr.bat: DOS batch file, ASCII text > ./jconsole.bat: DOS batch file, ASCII text > ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.conf.bat: ASCII text, with CRLF line terminators > ./standalone.conf.bat: ASCII text, with CRLF line terminators > ./add-user.bat: DOS batch file, ASCII text > $ > {noformat} > WF15: > {noformat} > $ find | grep bat$ | xargs file > ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jboss-cli.bat: DOS batch file, ASCII text, with CRLF line terminators > ./elytron-tool.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators > ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators > ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators > ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators > ./domain.conf.bat: ASCII text, with CRLF line terminators > ./common.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jdr.bat: DOS batch file, ASCII text, with CRLF line terminators > ./jconsole.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators > ./appclient.conf.bat: ASCII text, with CRLF line terminators > ./standalone.conf.bat: ASCII text, with CRLF line terminators > ./add-user.bat: DOS batch file, ASCII text, with CRLF line terminators > $ > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12167) Memory leak in metrics in standalone-ha configuration

by Bernd Stolle (Jira)

Bernd Stolle created WFLY-12167: ----------------------------------- Summary: Memory leak in metrics in standalone-ha configuration Key: WFLY-12167 URL: https://issues.jboss.org/browse/WFLY-12167 Project: WildFly Issue Type: Bug Components: MP Metrics Affects Versions: 16.0.0.Final Reporter: Bernd Stolle Assignee: Jeff Mesnil When started in standalone HA configuration every request to the recently added metrics endpoint ({{<management-if>:9990/metrics}}) lead to an increase in memory consumption until the JVM is slowed down significantly by GC to a point where even the requests to {{/health}} fail within a reasonable timeout (2s) and untlimately lead to OOM. The same issue does not occur when WildFly is started in the default standalone configuration (non HA). I can provide a (compressed) heap dump if required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019