April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1509) ServiceResponse XStream marshalling inconsistencies with JAXB

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1509?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1509: ----------------------------------- Summary: ServiceResponse XStream marshalling inconsistencies with JAXB (was: ServiceResponse XStream marshalling is with canonical name) > ServiceResponse XStream marshalling inconsistencies with JAXB > ------------------------------------------------------------- > > Key: DROOLS-1509 > URL: https://issues.jboss.org/browse/DROOLS-1509 > Project: Drools > Issue Type: Bug > Components: kie server > Reporter: Matteo Mortari > Assignee: Matteo Mortari > > ... instead of being consistent with JAXB, for "response". > Additionally in JAXB marshalling the -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1509) ServiceResponse XStream marshalling is with canonical name

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1509?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1509: ----------------------------------- Description: ... instead of being consistent with JAXB, for "response". Additionally in JAXB marshalling the was:... instead of being consistent with JAXB, for "response". > ServiceResponse XStream marshalling is with canonical name > ---------------------------------------------------------- > > Key: DROOLS-1509 > URL: https://issues.jboss.org/browse/DROOLS-1509 > Project: Drools > Issue Type: Bug > Components: kie server > Reporter: Matteo Mortari > Assignee: Matteo Mortari > > ... instead of being consistent with JAXB, for "response". > Additionally in JAXB marshalling the -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2622) Logging handler lost due to conflict handlers in logging.properties and standalone.xml

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-2622: ---------------------------------- Summary: Logging handler lost due to conflict handlers in logging.properties and standalone.xml Key: WFCORE-2622 URL: https://issues.jboss.org/browse/WFCORE-2622 Project: WildFly Core Issue Type: Bug Components: Logging Affects Versions: 2.0.10.Final Reporter: Takayoshi Kimura Assignee: James Perkins Fix For: 3.0.0.Beta11 Console logging doesn't work after logging subsystem init with the following configuration. * logging.properties is configured with ASYNC with CONSOLE handlers. * standalone.xml is configured with stock FILE and CONSOLE handlers. Background of why there is a mismatch between logging.properties and standalone.xml, EAP image for OpenShift is configured with ASYNC with CONSOLE handlers by default. But users can customize standalone.xml and apply custom configuration based on the stock standalone.xml. Expected result is logging configuration from standalone.xml is applied once logging subsystem come up regardless the mismatch. Most likely related to WFCORE-159. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2621) Upgrade jboss-logmanager from 2.0.5.Final to 2.0.6.Final

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-2621: ---------------------------------- Summary: Upgrade jboss-logmanager from 2.0.5.Final to 2.0.6.Final Key: WFCORE-2621 URL: https://issues.jboss.org/browse/WFCORE-2621 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 3.0.0.Beta11 An upgrade to the log manager will be required to resolve WFCORE-1585. An enhancement was made as part of LOGMGR-147 to allow child handlers to not be closed when the parent handler is closed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1507) Error message "unable to invole method" should mention DRL line

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1507?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1507: ------------------------------------- Affects Version/s: 6.5.0.Final > Error message "unable to invole method" should mention DRL line > --------------------------------------------------------------- > > Key: DROOLS-1507 > URL: https://issues.jboss.org/browse/DROOLS-1507 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > In a complex DRL file we wrote something like this: > {code} > when > Visit(foo != null, $w : foo.weekOfYear) > not Visit(foo.weekOfYear < $w) > then > ... > end > {code} > throws this exception: > {code} > java.lang.RuntimeException: cannot invoke getter: getFoo ... > at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:74) > ... > Caused by: java.lang.RuntimeException: unable to invoke method: ....foo.getWeekOfYear: target of method is null > at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:66) > at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:40) > ... > Caused by: java.lang.NullPointerException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:43) > {code} > with no DRL line. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1509) ServiceResponse XStream marshalling is with canonical name

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1509: -------------------------------------- Summary: ServiceResponse XStream marshalling is with canonical name Key: DROOLS-1509 URL: https://issues.jboss.org/browse/DROOLS-1509 Project: Drools Issue Type: Bug Components: kie server Reporter: Matteo Mortari Assignee: Matteo Mortari ... instead of being consistent with JAXB, for "response". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1054) CS tool, There is possibility add EMPTY alias name and EMPTY secret value to credential store storage file through wildfly-elytron-tool.

by Hynek Švábek (JIRA)

Hynek Švábek created ELY-1054: --------------------------------- Summary: CS tool, There is possibility add EMPTY alias name and EMPTY secret value to credential store storage file through wildfly-elytron-tool. Key: ELY-1054 URL: https://issues.jboss.org/browse/ELY-1054 Project: WildFly Elytron Issue Type: Bug Reporter: Hynek Švábek Assignee: Darran Lofthouse There is possibility add EMPTY alias name and EMPTY secret value to credential store storage file through wildfly-elytron-tool. I expect consistent behaviour as through CLI where isn't possible to do it. *How to reproduce* {code} java -jar wildfly-elytron-tool.jar credential-store --add="" --secret="" --location="/tmp/store02.jceks" --uri "cr-store://store02.jceks?modifiable=true;create=true;keyStoreType=JCEKS" -p pass123 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8505) Adding Undertow application-security-domain requires reload but the operation outcome doesn't mention it

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8505: --------------------------------- Summary: Adding Undertow application-security-domain requires reload but the operation outcome doesn't mention it Key: WFLY-8505 URL: https://issues.jboss.org/browse/WFLY-8505 Project: WildFly Issue Type: Bug Components: Web (Undertow), Security Reporter: Josef Cacek Assignee: Stuart Douglas Priority: Critical Add operation for the {{application-security-domain}} configuration in Undertow doesn't report that reload is required, but without the reload the change doesn't take effect. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2620) Add ability to read computed runtime values of IO subsystem buffer-pool attributes

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2620?page=com.atlassian.jira.plugi... ] Romain Pelisse commented on WFCORE-2620: ---------------------------------------- I've reproduced the issue on the current master of Wildfly (core) so adding an upstream issue. > Add ability to read computed runtime values of IO subsystem buffer-pool attributes > ---------------------------------------------------------------------------------- > > Key: WFCORE-2620 > URL: https://issues.jboss.org/browse/WFCORE-2620 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 3.0.0.Beta13 > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Original Estimate: 2 days > Remaining Estimate: 2 days > > In IO subsystem there are some attributes which are calculated based on available system resources if not explicitly specified. These attributes are: > * worker > ** io-threads > ** task-max-threads > * buffer-pool > ** buffer-size > ** buffers-per-slice > ** direct-buffers > Currently these computed values are not visible for user in the subsystem configuration even with include-runtime=true. > To show these runtime values would definitely improve UX. > Worker attributes are covered by EAP7-616 . > This issue is about buffer-pool attributes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2620) Add ability to read computed runtime values of IO subsystem buffer-pool attributes

by Romain Pelisse (JIRA)

Romain Pelisse created WFCORE-2620: -------------------------------------- Summary: Add ability to read computed runtime values of IO subsystem buffer-pool attributes Key: WFCORE-2620 URL: https://issues.jboss.org/browse/WFCORE-2620 Project: WildFly Core Issue Type: Enhancement Affects Versions: 3.0.0.Beta13 Reporter: Romain Pelisse Assignee: Romain Pelisse In IO subsystem there are some attributes which are calculated based on available system resources if not explicitly specified. These attributes are: * worker ** io-threads ** task-max-threads * buffer-pool ** buffer-size ** buffers-per-slice ** direct-buffers Currently these computed values are not visible for user in the subsystem configuration even with include-runtime=true. To show these runtime values would definitely improve UX. Worker attributes are covered by EAP7-616 . This issue is about buffer-pool attributes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017