November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1105) Not able to enable JMX Remote access

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1105?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet edited comment on WFCORE-1105 at 11/10/15 8:55 AM: --------------------------------------------------------------------- My mistake was (Author: ehugonnet): Works perfectly on 10.0RC4 > Not able to enable JMX Remote access > ------------------------------------ > > Key: WFCORE-1105 > URL: https://issues.jboss.org/browse/WFCORE-1105 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Logging > Environment: windows & linux > Reporter: Shark Xu > Assignee: David Lloyd > Fix For: 2.0.2.Final (EAP 7) > > > Can not enable JMX remote access port. > Config in domain.xml: > <jvm-options> > <option value="-Dcom.sun.management.jmxremote.port=19999"/> > <option value="-Dcom.sun.management.jmxremote.authenticate=false"/> > <option value="-Dcom.sun.management.jmxremote.ssl=false"/> > </jvm-options> > java.lang.IllegalStateException raised during startup. > Logs: > [Server:server-one] Exception in thread "main" java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util > .logging.manager" system property to "org.jboss.logmanager.LogManager") > [Server:server-one] at org.jboss.logmanager.Logger.getLogger(Logger.java:61) > [Server:server-one] at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:86) > [Server:server-one] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [Server:server-one] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > [Server:server-one] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [Server:server-one] at java.lang.reflect.Method.invoke(Method.java:606) > [Server:server-one] at org.jboss.modules.Module.run(Module.java:312) > [Server:server-one] at org.jboss.modules.Main.main(Main.java:460) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1105) Not able to enable JMX Remote access

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1105?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet resolved WFCORE-1105. --------------------------------------- Fix Version/s: 2.0.2.Final (EAP 7) Resolution: Cannot Reproduce Works perfectly on 10.0RC4 > Not able to enable JMX Remote access > ------------------------------------ > > Key: WFCORE-1105 > URL: https://issues.jboss.org/browse/WFCORE-1105 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Logging > Environment: windows & linux > Reporter: Shark Xu > Assignee: David Lloyd > Fix For: 2.0.2.Final (EAP 7) > > > Can not enable JMX remote access port. > Config in domain.xml: > <jvm-options> > <option value="-Dcom.sun.management.jmxremote.port=19999"/> > <option value="-Dcom.sun.management.jmxremote.authenticate=false"/> > <option value="-Dcom.sun.management.jmxremote.ssl=false"/> > </jvm-options> > java.lang.IllegalStateException raised during startup. > Logs: > [Server:server-one] Exception in thread "main" java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util > .logging.manager" system property to "org.jboss.logmanager.LogManager") > [Server:server-one] at org.jboss.logmanager.Logger.getLogger(Logger.java:61) > [Server:server-one] at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:86) > [Server:server-one] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [Server:server-one] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > [Server:server-one] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [Server:server-one] at java.lang.reflect.Method.invoke(Method.java:606) > [Server:server-one] at org.jboss.modules.Module.run(Module.java:312) > [Server:server-one] at org.jboss.modules.Main.main(Main.java:460) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1120) Domain tests use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1120?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-1120: ------------------------------------- Just heads up, WildFly core doesn't use arquillian anywhere. Issue itself is still valid. > Domain tests use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile > ------------------------------------------------------------------------- > > Key: WFCORE-1120 > URL: https://issues.jboss.org/browse/WFCORE-1120 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.0.1.Final > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Domain tests "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core: > https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav... > There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke > *Actual results:* > {noformat} > 07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java, > ... > -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false > ... > {noformat} > *Expected results:* > EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile > *Additional info:* > Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1120) Domain tests use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1120?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1120: -------------------------------- Summary: Domain tests use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile (was: Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile) > Domain tests use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile > ------------------------------------------------------------------------- > > Key: WFCORE-1120 > URL: https://issues.jboss.org/browse/WFCORE-1120 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.0.1.Final > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core: > https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav... > There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke > *Actual results:* > {noformat} > 07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java, > ... > -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false > ... > {noformat} > *Expected results:* > EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile > *Additional info:* > Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1120) Domain tests use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1120?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1120: -------------------------------- Description: *Description of problem:* Domain tests "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core: https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav... There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile. *How reproducible:* Always *Steps to Reproduce:* # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke *Actual results:* {noformat} 07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java, ... -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false ... {noformat} *Expected results:* EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile *Additional info:* Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T... was: *Description of problem:* Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core: https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav... There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile. *How reproducible:* Always *Steps to Reproduce:* # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke *Actual results:* {noformat} 07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java, ... -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false ... {noformat} *Expected results:* EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile *Additional info:* Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T... > Domain tests use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile > ------------------------------------------------------------------------- > > Key: WFCORE-1120 > URL: https://issues.jboss.org/browse/WFCORE-1120 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.0.1.Final > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Domain tests "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core: > https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav... > There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke > *Actual results:* > {noformat} > 07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java, > ... > -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false > ... > {noformat} > *Expected results:* > EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile > *Additional info:* > Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1120) Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1120?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-5653 to WFCORE-1120: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1120 (was: WFLY-5653) Component/s: Test Suite (was: Test Suite) Affects Version/s: 2.0.1.Final (was: 10.0.0.CR4) > Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile > ----------------------------------------------------------------------- > > Key: WFCORE-1120 > URL: https://issues.jboss.org/browse/WFCORE-1120 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.0.1.Final > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core: > https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav... > There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke > *Actual results:* > {noformat} > 07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java, > ... > -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false > ... > {noformat} > *Expected results:* > EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile > *Additional info:* > Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5653) Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5653?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-5653: --------------------------------- Assignee: Tomaz Cerar (was: Marek Kopecký) > Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile > ----------------------------------------------------------------------- > > Key: WFLY-5653 > URL: https://issues.jboss.org/browse/WFLY-5653 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.0.CR4 > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Arquillian use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile. This property is set in AbstractCommandBuilder of WildFly-Core: > https://github.com/wildfly/wildfly-core/blob/master/launcher/src/main/jav... > There should be option for disable of this option in arquillian.xml file. And testsuite should use this option with IPv6 profile. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIPV6_1 -Dnode1=$MYTESTIPV6_2 -Dipv6 -Dts.manualmode -Dtest=OutboundLdapConnectionTestCase -DtestLogToFile=false -Djboss.dist=$JBOSS_DIST -Dts.noSmoke > *Actual results:* > {noformat} > 07:04:26,054 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/qa/tools/opt/jdk1.8.0_last/bin/java, > ... > -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv4Stack=false > ... > {noformat} > *Expected results:* > EAP is not started with "-Djava.net.preferIPv4Stack=true" property with IPv6 profile > *Additional info:* > Jenkins reproducer job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-AS-T... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5655) Clustering performance regression in read-heavy scenarios

by Michal Vinkler (JIRA)

[ https://issues.jboss.org/browse/WFLY-5655?page=com.atlassian.jira.plugin.... ] Michal Vinkler updated WFLY-5655: --------------------------------- Labels: clustering_performance (was: ) > Clustering performance regression in read-heavy scenarios > --------------------------------------------------------- > > Key: WFLY-5655 > URL: https://issues.jboss.org/browse/WFLY-5655 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Michal Vinkler > Assignee: Paul Ferraro > Priority: Blocker > Labels: clustering_performance > > Our performance tests show regression in read-heavy scenarios with the default settings. Even with the JBEAP-1740 performance fix applied, the test progress is very different from the EAP6 tests. > Links: scenario heavyread-session-dist-sync > [EAP 6.4.0.GA|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-stres...] > [EAP7 DR13|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-stress-he...] > [EAP7 DR13 with applied JBEAP-1740|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > While changing max-unreplicated-interval to 0 in EAP 6 tests may change the test progress to be similar to the EAP 7 tests, performance results with EAP7 using the *default settings* have to be comparable with the results from EAP6. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5655) Clustering performance regression in read-heavy scenarios

by Michal Vinkler (JIRA)

[ https://issues.jboss.org/browse/WFLY-5655?page=com.atlassian.jira.plugin.... ] Michal Vinkler updated WFLY-5655: --------------------------------- Affects Version/s: 10.0.0.CR4 > Clustering performance regression in read-heavy scenarios > --------------------------------------------------------- > > Key: WFLY-5655 > URL: https://issues.jboss.org/browse/WFLY-5655 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Michal Vinkler > Assignee: Paul Ferraro > Priority: Blocker > Labels: clustering_performance > > Our performance tests show regression in read-heavy scenarios with the default settings. Even with the JBEAP-1740 performance fix applied, the test progress is very different from the EAP6 tests. > Links: scenario heavyread-session-dist-sync > [EAP 6.4.0.GA|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-stres...] > [EAP7 DR13|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-stress-he...] > [EAP7 DR13 with applied JBEAP-1740|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > While changing max-unreplicated-interval to 0 in EAP 6 tests may change the test progress to be similar to the EAP 7 tests, performance results with EAP7 using the *default settings* have to be comparable with the results from EAP6. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5655) Clustering performance regression in read-heavy scenarios

by Michal Vinkler (JIRA)

Michal Vinkler created WFLY-5655: ------------------------------------ Summary: Clustering performance regression in read-heavy scenarios Key: WFLY-5655 URL: https://issues.jboss.org/browse/WFLY-5655 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Michal Vinkler Assignee: Paul Ferraro Priority: Blocker Our performance tests show regression in read-heavy scenarios with the default settings. Even with the JBEAP-1740 performance fix applied, the test progress is very different from the EAP6 tests. Links: scenario heavyread-session-dist-sync [EAP 6.4.0.GA|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-stres...] [EAP7 DR13|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-stress-he...] [EAP7 DR13 with applied JBEAP-1740|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] While changing max-unreplicated-interval to 0 in EAP 6 tests may change the test progress to be similar to the EAP 7 tests, performance results with EAP7 using the *default settings* have to be comparable with the results from EAP6. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 2015