January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFCORE-5247) IllegalArgumentException and CLI crash with read-attribute in /system-property

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5247?page=com.atlassian.jira.plug... ] Jean Francois Denise reassigned WFCORE-5247: -------------------------------------------- Assignee: Parul Sharma (was: Jean Francois Denise) > IllegalArgumentException and CLI crash with read-attribute in /system-property > ------------------------------------------------------------------------------ > > Key: WFCORE-5247 > URL: https://issues.redhat.com/browse/WFCORE-5247 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: David Le Borgne > Assignee: Parul Sharma > Priority: Major > Attachments: stack_trace.txt > > > Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. > > {{/opt/wildfly/bin/jboss-cli.sh --connect}} > {{[standalone@localhost:9990 /] cd /system-property}} > {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} > {{Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5247) IllegalArgumentException and CLI crash with read-attribute in /system-property

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5247?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-5247: ---------------------------------------------- [~soul2zimate], [~parsharma] is starting to look into it as her first WF issue! I need to change the assignee. > IllegalArgumentException and CLI crash with read-attribute in /system-property > ------------------------------------------------------------------------------ > > Key: WFCORE-5247 > URL: https://issues.redhat.com/browse/WFCORE-5247 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: David Le Borgne > Assignee: Jean Francois Denise > Priority: Major > Attachments: stack_trace.txt > > > Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. > > {{/opt/wildfly/bin/jboss-cli.sh --connect}} > {{[standalone@localhost:9990 /] cd /system-property}} > {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} > {{Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5254) Kernel domain-management module has a couple OSHs populating the runtime with data from the operation, not the model

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5254: ---------------------------------------- Summary: Kernel domain-management module has a couple OSHs populating the runtime with data from the operation, not the model Key: WFCORE-5254 URL: https://issues.redhat.com/browse/WFCORE-5254 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry LegacyConfigurationChangeResourceDefinition and InMemoryAuditLogHandlerResourceDefinition populate the runtime from the operation. They should populate from the Resource tree's model. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-3307) Parameters passed to standalone.sh are not printed on startup

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-3307?page=com.atlassian.jira.plug... ] James Perkins closed WFCORE-3307. --------------------------------- Resolution: Rejected The parameters passed to scripts, with very few exceptions, are not processed by the script itself. They are passed to the main entry point and processed there after the JVM has been started. With the example {{-Djboss.socket.binding.port-offset=100}} that is not passed to the JVM in the {{JAVA_OPTS}}. That is passed to the entry point in the {{org.jboss.as.standalone}} module. > Parameters passed to standalone.sh are not printed on startup > ------------------------------------------------------------- > > Key: WFCORE-3307 > URL: https://issues.redhat.com/browse/WFCORE-3307 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 3.0.3.Final, 8.0.0.Beta5 > Environment: linux / windows > Reporter: jamie smith > Assignee: James Perkins > Priority: Minor > > Parameters passed to standalone.sh should also be printed on startup (like JAVA_OPTS). > Actually I think something like the output of `ps aux | grep "org.jboss.as.standalone"` should also be printed, when jboss starts. > Not printing them causes confusion between what is printed and what is actually applied. > If for example someone runs this: `standalone.sh -Djboss.socket.binding.port-offset=100` and at the same time `-Djboss.socket.binding.port-offset=0` exists in JAVA_OPTS, then the latter will be printed but the first will be used. > Someone might argue about setting only JAVA_OPTS before running standalone.sh. > The reason I avoid setting JAVA_OPTS is that if I set them before running standalone.sh, then the default Wildfly opts (-Djava.net.preferIPv4Stack=true" -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true") are never used, which causes other problems. This could be a bug byitself, but for now I consider it as expected behaviour. > So the most clean approach that I see for setting options in a single place (both with -D and custom flags (e.g. -b)) is appending them as params to standalone.sh (e.g. inside a wrapper script myapp-run.sh). > It should be possible however to be able to see them being printed somewhere. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14355) Move missing MP Opentracing and MP REST Client licenses from wildfly-ee to wildfly

by Roberto Oliveira (Jira)

[ https://issues.redhat.com/browse/WFLY-14355?page=com.atlassian.jira.plugi... ] Roberto Oliveira updated WFLY-14355: ------------------------------------ Affects Version/s: 22.0.0.Final > Move missing MP Opentracing and MP REST Client licenses from wildfly-ee to wildfly > ---------------------------------------------------------------------------------- > > Key: WFLY-14355 > URL: https://issues.redhat.com/browse/WFLY-14355 > Project: WildFly > Issue Type: Task > Affects Versions: 22.0.0.Final > Reporter: Roberto Oliveira > Assignee: Roberto Oliveira > Priority: Major > > Jira WFLY-14148 moved MicroProfile Opentracing from wildfly-ee to wildfly but the following licenses missed to be moved: jaeger-core, jaeger-thrift, microprofile-opentracing-api > Jira WFLY-14156 moved MicroProfile REST Client from wildfly-ee to wildly but the following licenses missed to be moved: microprofile-rest-client-api, resteasy-client-microprofile -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14355) Move missing MP Opentracing and MP REST Client licenses from wildfly-ee to wildfly

by Roberto Oliveira (Jira)

Roberto Oliveira created WFLY-14355: --------------------------------------- Summary: Move missing MP Opentracing and MP REST Client licenses from wildfly-ee to wildfly Key: WFLY-14355 URL: https://issues.redhat.com/browse/WFLY-14355 Project: WildFly Issue Type: Task Reporter: Roberto Oliveira Assignee: Roberto Oliveira Jira WFLY-14148 moved MicroProfile Opentracing from wildfly-ee to wildfly but the following licenses missed to be moved: jaeger-core, jaeger-thrift, microprofile-opentracing-api Jira WFLY-14156 moved MicroProfile REST Client from wildfly-ee to wildly but the following licenses missed to be moved: microprofile-rest-client-api, resteasy-client-microprofile -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2073) Upgrade org.apache.directory.api to version 2.0.1

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-2073?page=com.atlassian.jira.plugin.... ] Sonia Zaldana updated ELY-2073: ------------------------------- Description: Currently, we are using version 1.0.0 We need to upgrade to version 2.0.1 to upgrade Apache DS to AM26. Otherwise we get some NoClassDefFound errors in the LdapTestSuite. was:Currently, we are using version 1.0.0 > Upgrade org.apache.directory.api to version 2.0.1 > ------------------------------------------------- > > Key: ELY-2073 > URL: https://issues.redhat.com/browse/ELY-2073 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: Testsuite > Reporter: Sonia Zaldana > Assignee: Sonia Zaldana > Priority: Major > Fix For: 1.15.0.CR1 > > > Currently, we are using version 1.0.0 We need to upgrade to version 2.0.1 to upgrade Apache DS to AM26. Otherwise we get some NoClassDefFound errors in the LdapTestSuite. > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2071) Upgrade Apache DS to version AM26

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2071?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2071: ---------------------------- Issue Type: Component Upgrade (was: Bug) > Upgrade Apache DS to version AM26 > --------------------------------- > > Key: ELY-2071 > URL: https://issues.redhat.com/browse/ELY-2071 > Project: WildFly Elytron > Issue Type: Component Upgrade > Reporter: Sonia Zaldana > Assignee: Sonia Zaldana > Priority: Major > > We are currently using version M24. We should upgrade to version AM26. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2071) Upgrade Apache DS to version AM26

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2071?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2071: ---------------------------- Fix Version/s: 1.15.0.CR1 > Upgrade Apache DS to version AM26 > --------------------------------- > > Key: ELY-2071 > URL: https://issues.redhat.com/browse/ELY-2071 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: Testsuite > Reporter: Sonia Zaldana > Assignee: Sonia Zaldana > Priority: Major > Fix For: 1.15.0.CR1 > > > We are currently using version M24. We should upgrade to version AM26. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2071) Upgrade Apache DS to version AM26

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2071?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2071: ---------------------------- Component/s: Testsuite > Upgrade Apache DS to version AM26 > --------------------------------- > > Key: ELY-2071 > URL: https://issues.redhat.com/browse/ELY-2071 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: Testsuite > Reporter: Sonia Zaldana > Assignee: Sonia Zaldana > Priority: Major > > We are currently using version M24. We should upgrade to version AM26. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 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 January 2021