May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3891) Cannot create xml-formatter and json-formatter with the same name as existing resources in logging subsystem

by Nikoleta Žiaková (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3891?page=com.atlassian.jira.plugi... ] Nikoleta Žiaková commented on WFCORE-3891: ------------------------------------------ [~jamezp] thank you for the explanation, I did not realize! This behaviour is hidden when using CLI - {{file}} is the only mandatory attribute for file-handler, default (pattern) formatter is used when left undefined. In the CLI, you don't see the created {{test}} pattern-formatter, which is why I consider the inability to create a different formatter with name {{test}} a bug from UX perspective. WDYT? {code} [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=logging:read-resource { "outcome" => "success", "result" => { "add-logging-api-dependencies" => true, "use-deployment-logging-config" => true, "async-handler" => undefined, "console-handler" => {"CONSOLE" => undefined}, "custom-formatter" => undefined, "custom-handler" => undefined, "file-handler" => {"test" => undefined}, "json-formatter" => undefined, "log-file" => {"server.log" => undefined}, "logger" => { "com.arjuna" => undefined, "org.jboss.as.config" => undefined, "sun.rmi" => undefined }, "logging-profile" => undefined, "pattern-formatter" => { "PATTERN" => undefined, "COLOR-PATTERN" => undefined }, "periodic-rotating-file-handler" => {"FILE" => undefined}, "periodic-size-rotating-file-handler" => undefined, "root-logger" => {"ROOT" => undefined}, "size-rotating-file-handler" => undefined, "syslog-handler" => undefined, "xml-formatter" => undefined } } {code} > Cannot create xml-formatter and json-formatter with the same name as existing resources in logging subsystem > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3891 > URL: https://issues.jboss.org/browse/WFCORE-3891 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Nikoleta Žiaková > Assignee: James Perkins > > When trying to create an {{xml-formatter}} or {{json-formatter}} with the same name as another resource (e.g. a {{file-handler}}), the operation fails: > {code} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=aaa.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/xml-formatter=test:add > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No property \"dateFormat\" setter found for formatter \"test\"", > "rolled-back" => true > } > {code} > Similarly vice-versa, when trying to create another resource in logging subsystem with the same name as an {{xml-formatter}} or a {{json-formatter}}, the operation fails: > {code} > [standalone@localhost:9990 /] /subsystem=logging/json-formatter=test:add > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No property \"pattern\" setter found for formatter \"test\"", > "rolled-back" => true > } > {code} > The same scenario works for e.g. {{pattern-formatter}}: > {code} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/pattern-formatter=test:add > {"outcome" => "success"} > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2591) Re-Loading of updated SNAPSHOT KJars is broken

by Nils Meyer (JIRA)

Nils Meyer created DROOLS-2591: ---------------------------------- Summary: Re-Loading of updated SNAPSHOT KJars is broken Key: DROOLS-2591 URL: https://issues.jboss.org/browse/DROOLS-2591 Project: Drools Issue Type: Bug Affects Versions: 7.7.0.Final, 7.1.0.Final Reporter: Nils Meyer Assignee: Edson Tirelli Re-loading updated SNAPSHOT versions of a KJar from a remote maven repository seems to be broken since 7.1.0. My code is working for 7.0.0 but not for 7.1.0 and 7.7.0. I did not test versions in between. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3894) Undertow 2.0.9.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3894?page=com.atlassian.jira.plugi... ] Stuart Douglas reassigned WFCORE-3894: -------------------------------------- Assignee: Stuart Douglas > Undertow 2.0.9.Final > -------------------- > > Key: WFCORE-3894 > URL: https://issues.jboss.org/browse/WFCORE-3894 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3894) Undertow 2..9.Final

by Stuart Douglas (JIRA)

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

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3894) Undertow 2.0.9.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3894?page=com.atlassian.jira.plugi... ] Stuart Douglas updated WFCORE-3894: ----------------------------------- Summary: Undertow 2.0.9.Final (was: Undertow 2..9.Final) > Undertow 2.0.9.Final > -------------------- > > Key: WFCORE-3894 > URL: https://issues.jboss.org/browse/WFCORE-3894 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1294) Wildfly Elytron Tool, Credential-store command, --salt option is validated only when --summary is used too.

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/ELY-1294?page=com.atlassian.jira.plugin.s... ] Chao Wang updated ELY-1294: --------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron-tool/pull/90, https://github.com/wildfly-security/wildfly-elytron-tool/pull/99, https://github.com/wildfly-security/wildfly-elytron-tool/pull/149 (was: https://github.com/wildfly-security/wildfly-elytron-tool/pull/90, https://github.com/wildfly-security/wildfly-elytron-tool/pull/99, https://github.com/wildfly-security/wildfly-elytron-tool/pull/148, https://github.com/wildfly-security/wildfly-elytron-tool/pull/149) > Wildfly Elytron Tool, Credential-store command, --salt option is validated only when --summary is used too. > ----------------------------------------------------------------------------------------------------------- > > Key: ELY-1294 > URL: https://issues.jboss.org/browse/ELY-1294 > Project: WildFly Elytron > Issue Type: Bug > Components: Command-Line Tool, Credential Store > Reporter: Hynek Švábek > Assignee: Chao Wang > > Credential-store command \-\-salt option is validated only when is \-\-summary is used too. > It is caused by generation MASKed password for summary output[1]. > It is at least strange and confusing to user: without \-\-summary is passed, with \-\-summary is failed (entry is stored in storage successfully). > *How to reproduce* > {code} > [hsvabek@dhcp-10-40-5-17 bin]$ ./elytron-tool.sh credential-store --add secret_alias --password pass123 --create -x secret_password -l store005.jceks -s 1234567890 -i 230 --summary --debug > Alias "secret_alias" has been successfully stored > Exception encountered executing the command: > java.security.InvalidAlgorithmParameterException: Salt must be 8 bytes long > at com.sun.crypto.provider.PBES1Core.init(PBES1Core.java:234) > at com.sun.crypto.provider.PBES1Core.init(PBES1Core.java:331) > at com.sun.crypto.provider.PBEWithMD5AndDESCipher.engineInit(PBEWithMD5AndDESCipher.java:228) > at javax.crypto.Cipher.implInit(Cipher.java:810) > at javax.crypto.Cipher.chooseProvider(Cipher.java:864) > at javax.crypto.Cipher.init(Cipher.java:1539) > at javax.crypto.Cipher.init(Cipher.java:1470) > at org.wildfly.security.util.PasswordBasedEncryptionUtil$Builder.createAndInitCipher(PasswordBasedEncryptionUtil.java:506) > at org.wildfly.security.util.PasswordBasedEncryptionUtil$Builder.build(PasswordBasedEncryptionUtil.java:589) > at org.wildfly.security.tool.MaskCommand.computeMasked(MaskCommand.java:117) > at org.wildfly.security.tool.CredentialStoreCommand.execute(CredentialStoreCommand.java:287) > at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:81) > {code} > [1] https://github.com/wildfly-security/wildfly-elytron-tool/blob/1.0.0.CR2/s... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3830) JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1

by R Searls (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3830?page=com.atlassian.jira.plugi... ] R Searls commented on WFCORE-3830: ---------------------------------- what is DC and HC? > JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1 > ------------------------------------------------------- > > Key: WFCORE-3830 > URL: https://issues.jboss.org/browse/WFCORE-3830 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Priority: Critical > > JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1 > Steps to reproduce: > # start powershell > # $env:JAVA_OPTS = "-Da=b" > # ./domain.bat > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is present in DC or HC > # exit domain.bat > # ./domain.ps1 > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is *not* present in DC or HC > cc: [~jamezp] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3830) JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1

by R Searls (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3830?page=com.atlassian.jira.plugi... ] R Searls commented on WFCORE-3830: ---------------------------------- domian.ps1 had been designed such that one must edit domain.conf.ps1 and uncomment line 30 {code:java} # Uncomment the following line to disable manipulation of JAVA_OPTS (JVM parameters) # $PRESERVE_JAVA_OPTS=true {code} When that is done the users JAVA_OPTS will be used. > JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1 > ------------------------------------------------------- > > Key: WFCORE-3830 > URL: https://issues.jboss.org/browse/WFCORE-3830 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Priority: Critical > > JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1 > Steps to reproduce: > # start powershell > # $env:JAVA_OPTS = "-Da=b" > # ./domain.bat > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is present in DC or HC > # exit domain.bat > # ./domain.ps1 > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is *not* present in DC or HC > cc: [~jamezp] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3831) jboss-cli.ps1 script doesn't return exit value correctly

by R Searls (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3831?page=com.atlassian.jira.plugi... ] R Searls reassigned WFCORE-3831: -------------------------------- Assignee: R Searls > jboss-cli.ps1 script doesn't return exit value correctly > -------------------------------------------------------- > > Key: WFCORE-3831 > URL: https://issues.jboss.org/browse/WFCORE-3831 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: R Searls > > jboss-cli.ps1 script doesn't return exit value correctly > Steps to reproduce: > # start Command prompt in Windows > # PowerShell \-ExecutionPolicy Bypass -File jboss-cli.ps1 "\-\-commands=nonsence" \-\-timeout=10000 > # echo %ERRORLEVEL% > #* "0" is printed, "1" should be printed > # add "exit 5" to the end of jboss-cli.ps1 file > # PowerShell \-ExecutionPolicy Bypass -File jboss-cli.ps1 "\-\-commands=nonsence" \-\-timeout=10000 > # echo %ERRORLEVEL% > #* "5" is printed > cc: [~jamezp], [~eduda], [~jdenise] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10462) Upgrade to Galleon 1.0.0.Final and Galleon Plugins 1.0.0.Final

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFLY-10462: ---------------------------------------- Summary: Upgrade to Galleon 1.0.0.Final and Galleon Plugins 1.0.0.Final Key: WFLY-10462 URL: https://issues.jboss.org/browse/WFLY-10462 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Upgrade to final releases of Galleon and WildFly Galleon plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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