November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1983) Root cause of failing parsing should be used as failure description

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1983?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1983: ------------------------------------- Component/s: Domain Management (was: Server) [~jdenise] Thanks for digging into this! Please use "Domain Management" as the component for any server side management issues, unless the are subsystem-specific and there is a component for the subsystem, in which case you use that. > Root cause of failing parsing should be used as failure description > ------------------------------------------------------------------- > > Key: WFCORE-1983 > URL: https://issues.jboss.org/browse/WFCORE-1983 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Jean-Francois Denise > Assignee: Brian Stansberry > > It happens that the CLI does a custom parsing of the value in case ModelNode.fromString fails (whatever the exception). > The issue is that the custom parsing doesn't follow the ModelNode parsing syntax and parse everything as String. So the resulting ModelNode that is serialised and sent to the server has been transformed. > I am surprised that we don't have more of such failures. For example, when numbers are located inside custom complex structure such as: {mynumber=9999} that will be sent as an OBJECT containing a STRING although the valid DMR syntax {"my number"=>999} would be sent as an OBJECT containing an INT. > Some server side subsystems are smart enough to call into asXXX methods and not check the type? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7609) There is an extra dot in front of sentence ".CLI Command for Using a New Security Realm"

by Chuck Copello (JIRA)

[ https://issues.jboss.org/browse/WFLY-7609?page=com.atlassian.jira.plugin.... ] Chuck Copello reassigned WFLY-7609: ----------------------------------- Assignee: Zach Rhoads (was: Chuck Copello) > There is an extra dot in front of sentence ".CLI Command for Using a New Security Realm" > ---------------------------------------------------------------------------------------- > > Key: WFLY-7609 > URL: https://issues.jboss.org/browse/WFLY-7609 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Hynek Švábek > Assignee: Zach Rhoads > > Book: How to Configure Server Security > Revision: 8269434 > Section: 2.2.2. Configure the Management Interfaces for HTTPS > Issue description: > There is an extra dot in front of sentence ".CLI Command for Using a New Security Realm" > Suggestions for improvement: > Correct form is "CLI Command for Using a New Security Realm:" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7611) "Add a user to the master domain controller" format as title of paragraph and add dot at the end.

by Chuck Copello (JIRA)

[ https://issues.jboss.org/browse/WFLY-7611?page=com.atlassian.jira.plugin.... ] Chuck Copello reassigned WFLY-7611: ----------------------------------- Assignee: Zach Rhoads (was: Chuck Copello) > "Add a user to the master domain controller" format as title of paragraph and add dot at the end. > ------------------------------------------------------------------------------------------------- > > Key: WFLY-7611 > URL: https://issues.jboss.org/browse/WFLY-7611 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Hynek Švábek > Assignee: Zach Rhoads > > Book: How to Configure Server Security > Revision: 8269434 > Section: 3.1. Configure Password Authentication Between Slaves and the Domain Controller > Issue description: > There is missing dot "Add a user to the master domain controller" > This sentence should be title of paragraph. > Suggestions for improvement: > Correct form is "Add a user to the master domain controller." and make from this sentence title of paragraph. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-762) Add SaslClientDiscovery to AuthenticationConfiguration

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-762: ------------------------------------ Summary: Add SaslClientDiscovery to AuthenticationConfiguration Key: ELY-762 URL: https://issues.jboss.org/browse/ELY-762 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta15 We should have one option to support discovery using the configured Provider[] and a second option to support service loader discovery. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-761) Update mechanisms that use the PasswordFactory to be passed a Supplier<Provider[]>

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-761: ------------------------------------ Summary: Update mechanisms that use the PasswordFactory to be passed a Supplier<Provider[]> Key: ELY-761 URL: https://issues.jboss.org/browse/ELY-761 Project: WildFly Elytron Issue Type: Enhancement Components: SASL Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta15 Also update the WildFlyElytronProvider to pass itself to mechanism factories it creates if the support it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1326) Stateful working memory regression OCT-2016: nurserostering long_hint01.xml

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1326?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1326: ---------------------------------------- (also to confirm what discussed at Devoxx also with [~ge0ffrey], this is +not+ a regression, the test above is failing also with 6.1.0.Final..) > Stateful working memory regression OCT-2016: nurserostering long_hint01.xml > --------------------------------------------------------------------------- > > Key: DROOLS-1326 > URL: https://issues.jboss.org/browse/DROOLS-1326 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Blocker > Attachments: screenshot-1.png > > > Something regressed in Drools master between 27-SEP and 11-OCT. > See: > https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/optaplanner-turtl... > I 'll ask [~jlocker] to isolate. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1326) Stateful working memory regression OCT-2016: nurserostering long_hint01.xml

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1326?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1326: ---------------------------------------- Drools synthetic test: {code:java} @Test public void test() { String drl = "package "+this.getClass().getPackage().getName()+";\n" + "import "+MyPojo.class.getCanonicalName()+"\n" + "global java.util.Set controlSet;\n" + "rule R1\n" + "when\n" + " $my: MyPojo(\n" + " vBoolean == true,\n" + " $s : vString, vString != null,\n" + " $l : vLong\n" + " )\n" + " not MyPojo(\n" + " vBoolean == true,\n" + " vString == $s,\n" + " vLong > $l\n" + " )\n" + "then\n" + " System.out.println($my);\n" + " System.out.println($l);\n" + " controlSet.add($l);\n" + "end"; System.out.println(drl); KieSession session = new KieHelper().addContent(drl, ResourceType.DRL).build().newKieSession(); Set<Long> check = new HashSet<Long>(); session.setGlobal("controlSet", check); MyPojo a = new MyPojo(true, "x", 0); MyPojo b = new MyPojo(true, "x", 7); MyPojo c = new MyPojo(false, null, 7); System.out.println("a: "+a); System.out.println("b: "+b); System.out.println("c: "+c); FactHandle fh_a = session.insert(a); FactHandle fh_b = session.insert(b); FactHandle fh_c = session.insert(c); System.out.println("1st fireAllRules"); session.fireAllRules(); assertFalse( check.contains(0) ); // A should be blocked by B. c.setvBoolean(true); c.setvString("x"); session.update(fh_c, c); b.setvBoolean(false); b.setvString(null); session.update(fh_b, b); System.out.println("2nd fireAllRules"); session.fireAllRules(); assertFalse( check.contains(0L) ); // A is no longer blocked by B, *however* it is now blocked by C ! } public static class MyPojo { private boolean vBoolean; private String vString; private long vLong; public MyPojo(boolean vBoolean, String vString, long vLong) { super(); this.vBoolean = vBoolean; this.vString = vString; this.vLong = vLong; } public boolean isvBoolean() { return vBoolean; } public boolean getvBoolean() { return vBoolean; } public String getvString() { return vString; } public long getvLong() { return vLong; } public void setvBoolean(boolean vBoolean) { this.vBoolean = vBoolean; } public void setvString(String vString) { this.vString = vString; } public void setvLong(long vLong) { this.vLong = vLong; } } {code} > Stateful working memory regression OCT-2016: nurserostering long_hint01.xml > --------------------------------------------------------------------------- > > Key: DROOLS-1326 > URL: https://issues.jboss.org/browse/DROOLS-1326 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Blocker > Attachments: screenshot-1.png > > > Something regressed in Drools master between 27-SEP and 11-OCT. > See: > https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/optaplanner-turtl... > I 'll ask [~jlocker] to isolate. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1326) Stateful working memory regression OCT-2016: nurserostering long_hint01.xml

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1326?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1326: ---------------------------------------- Thanks for the feedback [~jlocker]. > Stateful working memory regression OCT-2016: nurserostering long_hint01.xml > --------------------------------------------------------------------------- > > Key: DROOLS-1326 > URL: https://issues.jboss.org/browse/DROOLS-1326 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Blocker > Attachments: screenshot-1.png > > > Something regressed in Drools master between 27-SEP and 11-OCT. > See: > https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/optaplanner-turtl... > I 'll ask [~jlocker] to isolate. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7616) Setting 'site' attribute of cache-container transport fails on WF 10.1.0

by Joe Siponen (JIRA)

Joe Siponen created WFLY-7616: --------------------------------- Summary: Setting 'site' attribute of cache-container transport fails on WF 10.1.0 Key: WFLY-7616 URL: https://issues.jboss.org/browse/WFLY-7616 Project: WildFly Issue Type: Feature Request Components: Documentation Affects Versions: 10.1.0.Final Reporter: Joe Siponen Priority: Minor The documentation for the Infinispan Subsystem in Wildfly 10 (https://docs.jboss.org/author/display/WFLY10/Infinispan+Subsystem) suggest that it should be possible to set the following attributes on the transport element of the cache-container: site: This attribute configures the site id of the cache container. rack: This attribute configures the rack id of the cache container. machine: This attribute configures the machine id of the cache container Setting these will fail due to parsing errors: [Host Controller] 14:32:41,557 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration [Host Controller] Message: WFLYCTL0197: Unexpected attribute 'machine' encountered Further investigation revealed that this configuration was moved to the transport element of the jgroups subsystem and, thus, it would nice if this was removed from the documentation in for infinispan. However, if these settings affect the server hinting for infinispan (http://infinispan.org/docs/stable/user_guide/user_guide.html#ServerHinting) it would still be nice if this was explained in this documentation page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4167) AS7Plugin dump-services command is failing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4167?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4167: ----------------------------------------------- Peter Mackay <pmackay(a)redhat.com> changed the Status of [bug 1195504|https://bugzilla.redhat.com/show_bug.cgi?id=1195504] from ON_QA to VERIFIED > AS7Plugin dump-services command is failing > ------------------------------------------ > > Key: WFLY-4167 > URL: https://issues.jboss.org/browse/WFLY-4167 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 9.0.0.Beta1 > > > Run JDR, the dump-services.json is always empty. This is because the operation is not being set when JDR tries to invoke the operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 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 November 2016