March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3665) Bump the kernel management API version to 7.0.0 and the xsd to 7.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3665?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFCORE-3665: ----------------------------------- Assignee: Jeff Mesnil (was: Brian Stansberry) > Bump the kernel management API version to 7.0.0 and the xsd to 7.0 > ------------------------------------------------------------------ > > Key: WFCORE-3665 > URL: https://issues.jboss.org/browse/WFCORE-3665 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 5.0.0.Alpha1 > > > We know there are going to be API changes in WF Core 4, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3665) Bump the kernel management API version to 7.0.0 and the xsd to 7.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3665?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3665: -------------------------------- Fix Version/s: 5.0.0.Alpha1 (was: 4.0.0.Alpha1) > Bump the kernel management API version to 7.0.0 and the xsd to 7.0 > ------------------------------------------------------------------ > > Key: WFCORE-3665 > URL: https://issues.jboss.org/browse/WFCORE-3665 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 5.0.0.Alpha1 > > > We know there are going to be API changes in WF Core 4, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3665) Bump the kernel management API version to 7.0.0 and the xsd to 7.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3665?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3665: -------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/2837, https://github.com/wildfly/wildfly-core/pull/2892) > Bump the kernel management API version to 7.0.0 and the xsd to 7.0 > ------------------------------------------------------------------ > > Key: WFCORE-3665 > URL: https://issues.jboss.org/browse/WFCORE-3665 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 5.0.0.Alpha1 > > > We know there are going to be API changes in WF Core 4, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3665) Bump the kernel management API version to 7.0.0 and the xsd to 7.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3665?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3665: -------------------------------- Description: We know there are going to be API changes in WF Core 5, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. (was: We know there are going to be API changes in WF Core 4, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version.) > Bump the kernel management API version to 7.0.0 and the xsd to 7.0 > ------------------------------------------------------------------ > > Key: WFCORE-3665 > URL: https://issues.jboss.org/browse/WFCORE-3665 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 5.0.0.Alpha1 > > > We know there are going to be API changes in WF Core 5, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9941) :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-9941?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-9941: -------------------------------------- [~jdenise] Shutdown command is invoked in: {code} 2018-03-01 09:36:59,126 DEBUG pool-1-thread-1 org.wildfly.extras.creaper.core.online.OnlineManagementClient - Executing operation :shutdown(timeout=200000) {code} and exception is thrown in: {code} 2018-03-01 09:36:59,188 ERROR pool-1-thread-1 org.jboss.manu.eap.services.server.EapModularServerBase - Can't stop server gracefully java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.execute(OnlineManagementClientImpl.java:180) ~[creaper-core-1.6.1.jar:na] at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:600) ~[manu-eap-lib-1.1.54.jar:na] at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:638) ~[manu-eap-lib-1.1.54.jar:na] at org.jboss.manu.eap.services.server.EapServerStandalone.executeStopOperation(EapServerStandalone.java:348) ~[manu-eap-lib-1.1.54.jar:na] at org.jboss.manu.eap.services.server.EapModularServerBase.stop(EapModularServerBase.java:238) ~[manu-eap-lib-1.1.54.jar:na] at org.jboss.manu.eap.units.server.StopServer.execute(StopServer.java:57) [manu-eap-lib-1.1.54.jar:na] at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:33) [manu-core-impl-1.1.43.jar:na] at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:14) [manu-core-impl-1.1.43.jar:na] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_151] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151] at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151] Caused by: java.util.concurrent.CancellationException: Operation was cancelled at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final] at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] ... 13 common frames omitted {code} [~brian.stansberry] Thanks, I'll change the test and do another round of testing to check whether this issue disappears. Could you elaborate further what is the difference between {{:shutdown}} and {{shutdown}}, please? I guess I'll need it to justify this test change in PR. > :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled > -------------------------------------------------------------------------------------------------- > > Key: WFLY-9941 > URL: https://issues.jboss.org/browse/WFLY-9941 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 12.0.0.Final > Reporter: Miroslav Novak > Assignee: Jean-Francois Denise > Attachments: manu-trace.log > > > There is intermittent failure on CLI client when CLI operation {{ :shutdown() }} is called. Sometimes happens that CancellationException is thrown: > {code} > 2018-03-01 09:36:59,188 ERROR pool-1-thread-1 org.jboss.manu.eap.services.server.EapModularServerBase - Can't stop server gracefully > java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] > at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.execute(OnlineManagementClientImpl.java:180) ~[creaper-core-1.6.1.jar:na] > at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:600) ~[manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:638) ~[manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.eap.services.server.EapServerStandalone.executeStopOperation(EapServerStandalone.java:348) ~[manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.eap.services.server.EapModularServerBase.stop(EapModularServerBase.java:238) ~[manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.eap.units.server.StopServer.execute(StopServer.java:57) [manu-eap-lib-1.1.54.jar:na] > at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:33) [manu-core-impl-1.1.43.jar:na] > at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:14) [manu-core-impl-1.1.43.jar:na] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_151] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151] > Caused by: java.util.concurrent.CancellationException: Operation was cancelled > at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final] > at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final] > at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5] > ... 13 common frames omitted > {code} > WF12 server shutdowns but it seems that it does not send response for {{:shutdown}} call to client before shutdwon and closes connection. This causes that AsyncFutureTask on client is cancelled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-191) Amend NullPointerException in RegexFilter.isLoggable()

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-191?page=com.atlassian.jira.plugin... ] Masafumi Miura updated LOGMGR-191: ---------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/172 > Amend NullPointerException in RegexFilter.isLoggable() > ------------------------------------------------------ > > Key: LOGMGR-191 > URL: https://issues.jboss.org/browse/LOGMGR-191 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Affects Versions: 2.1.0.Alpha5 > Reporter: Toshiya Kobayashi > Labels: support > > When log message is null, RegexFilter.isLoggable() throws NullPointerException. > https://github.com/jboss-logging/jboss-logmanager/blob/master/src/main/ja... > It often results in unexpected outcomes. For example, assuming you have a filter-spec with "not(match(xxx))" to suppress some messages in your logger configuration: > {code:xml} > <subsystem xmlns="urn:jboss:domain:logging:3.0"> > <console-handler name="CONSOLE"> > <level name="INFO"/> > <filter-spec value="not(match("SOME_MESSAGE"))"/> > <formatter> > <named-formatter name="COLOR-PATTERN"/> > </formatter> > </console-handler> > {code} > and an application has a code like this: > {code:java} > try { > ... > } catch (Exception e) { > logger.error(e.getMessage(), e); > } > {code} > "e.getMessage()" could be null. But you want to log the stacktrace 'e' anyway. > In this case, NullPointerException is thrown from RegexFilter and reaches to LoggerNode and disappears. ConsoleHandler cannot publish the log at all. > https://github.com/jboss-logging/jboss-logmanager/blob/master/src/main/ja... > I think 'null' message should simply return 'false' in RegexFilter.isLoggable(). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-1825: -------------------------------------- Ok. And my comments above were did no include the move of the "Edit Columns" to the right hand side. I tried to move the analysis panel to that location at one point, but the code was not ready for it. Basically the Data Modeler options are stealing that right hand side icon column. To properly manage the change between different editors there needs to be few days spent in appformer to add support for it. After that there is additional UI work to change the DTables to use that icon column space. > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX, UXTeam > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-191) Amend NullPointerException in RegexFilter.isLoggable()

by Toshiya Kobayashi (JIRA)

Toshiya Kobayashi created LOGMGR-191: ---------------------------------------- Summary: Amend NullPointerException in RegexFilter.isLoggable() Key: LOGMGR-191 URL: https://issues.jboss.org/browse/LOGMGR-191 Project: JBoss Log Manager Issue Type: Bug Components: core Affects Versions: 2.1.0.Alpha5 Reporter: Toshiya Kobayashi When log message is null, RegexFilter.isLoggable() throws NullPointerException. https://github.com/jboss-logging/jboss-logmanager/blob/master/src/main/ja... It often results in unexpected outcomes. For example, assuming you have a filter-spec with "not(match(xxx))" to suppress some messages in your logger configuration: {code:xml} <subsystem xmlns="urn:jboss:domain:logging:3.0"> <console-handler name="CONSOLE"> <level name="INFO"/> <filter-spec value="not(match("SOME_MESSAGE"))"/> <formatter> <named-formatter name="COLOR-PATTERN"/> </formatter> </console-handler> {code} and an application has a code like this: {code:java} try { ... } catch (Exception e) { logger.error(e.getMessage(), e); } {code} "e.getMessage()" could be null. But you want to log the stacktrace 'e' anyway. In this case, NullPointerException is thrown from RegexFilter and reaches to LoggerNode and disappears. ConsoleHandler cannot publish the log at all. https://github.com/jboss-logging/jboss-logmanager/blob/master/src/main/ja... I think 'null' message should simply return 'false' in RegexFilter.isLoggable(). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3664) WildFly OpenSSL 1.0.4.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3664: -------------------------------------- Summary: WildFly OpenSSL 1.0.4.Final Key: WFCORE-3664 URL: https://issues.jboss.org/browse/WFCORE-3664 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9950) ConcurrentCoarseWebFailoverTestCase.testGracefulSimpleFailover fails intermittently

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9950?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-9950: -------------------------------------- Looking at the logs it appears to be an infinispan timeout issue, so maybe the infinispan upgrade that just went in will fix this. I was going to ignore the test but I will wait and see if the infinispan upgrade helps. > ConcurrentCoarseWebFailoverTestCase.testGracefulSimpleFailover fails intermittently > ----------------------------------------------------------------------------------- > > Key: WFLY-9950 > URL: https://issues.jboss.org/browse/WFLY-9950 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Stuart Douglas > Assignee: Paul Ferraro > > E.g. https://ci.wildfly.org/viewLog.html?buildId=93039&buildTypeId=WF_PullRequ... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 March 2018