November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1123) Recreate HttpPostMgmtOpsTestCase.testAddRemove

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1123: ---------------------------------------- Summary: Recreate HttpPostMgmtOpsTestCase.testAddRemove Key: WFCORE-1123 URL: https://issues.jboss.org/browse/WFCORE-1123 Project: WildFly Core Issue Type: Task Components: Domain Management, Test Suite Reporter: Brian Stansberry Priority: Minor HttpPostMgmtOpsTestCase.testAddRemove was ignored when the test was moved from full to core because the test impl used undertow subsystem resources. We should resurrect this test, using resources in core. The goal of the test is to execute add and remove ops via POST, not to test add/remove of a particular resource. So the task is not to move the test to full and test undertow subsystem, it's to make POST calls against core that add/remove. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1120) Louncher sets "-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: Louncher sets "-Djava.net.preferIPv4Stack=true" also with IPv6 profile (was: Domain tests use "-Djava.net.preferIPv4Stack=true" also with IPv6 profile) > Louncher sets "-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) Launcher sets "-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: Launcher sets "-Djava.net.preferIPv4Stack=true" also with IPv6 profile (was: Louncher sets "-Djava.net.preferIPv4Stack=true" also with IPv6 profile) > Launcher sets "-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-1122) Attribute defined as ObjectListAttributeDefinition always mandatory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1122?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-1122. -------------------------------------- Resolution: Rejected Both the ObjectListAttributeDefinition and the ObjectTypeAttributeDefinition need to be set to allow null. > Attribute defined as ObjectListAttributeDefinition always mandatory > ------------------------------------------------------------------- > > Key: WFCORE-1122 > URL: https://issues.jboss.org/browse/WFCORE-1122 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.1.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 3.0.0.Alpha1 > > > Take the following attribute definition: - > {noformat} > static final ObjectListAttributeDefinition CREDENTIALS = new ObjectListAttributeDefinition.Builder(ElytronDescriptionConstants.CREDENTIALS, CREDENTIAL) > .setAllowNull(true) > .setFlags(AttributeAccess.Flag.RESTART_RESOURCE_SERVICES) > .build(); > {noformat} > Existing subsystem tests do not set this and the following error is reported: - > {noformat} > Tests run: 12, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.8 sec <<< FAILURE! - in org.wildfly.extension.elytron.SubsystemParsingTestCase > testParseAndMarshalModel_Realms(org.wildfly.extension.elytron.SubsystemParsingTestCase) Time elapsed: 0.015 sec <<< ERROR! > java.lang.IllegalArgumentException: WFLYCTL0231: Required parameter credentials is not present. {"operation" => "add","address" => [("subsystem" => "elytron"),("properties-realm" => "RealmFive")],"users-properties" => {"path" => "my.properties"}} > at org.jboss.as.controller.operations.validation.OperationValidator.checkAllRequiredPropertiesArePresent(OperationValidator.java:207) > at org.jboss.as.controller.operations.validation.OperationValidator.validateOperation(OperationValidator.java:138) > at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:334) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:336) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1122) Attribute defined as ObjectListAttributeDefinition always mandatory

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1122: ---------------------------------------- Summary: Attribute defined as ObjectListAttributeDefinition always mandatory Key: WFCORE-1122 URL: https://issues.jboss.org/browse/WFCORE-1122 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 2.0.1.Final Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha1 Take the following attribute definition: - {noformat} static final ObjectListAttributeDefinition CREDENTIALS = new ObjectListAttributeDefinition.Builder(ElytronDescriptionConstants.CREDENTIALS, CREDENTIAL) .setAllowNull(true) .setFlags(AttributeAccess.Flag.RESTART_RESOURCE_SERVICES) .build(); {noformat} Existing subsystem tests do not set this and the following error is reported: - {noformat} Tests run: 12, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.8 sec <<< FAILURE! - in org.wildfly.extension.elytron.SubsystemParsingTestCase testParseAndMarshalModel_Realms(org.wildfly.extension.elytron.SubsystemParsingTestCase) Time elapsed: 0.015 sec <<< ERROR! java.lang.IllegalArgumentException: WFLYCTL0231: Required parameter credentials is not present. {"operation" => "add","address" => [("subsystem" => "elytron"),("properties-realm" => "RealmFive")],"users-properties" => {"path" => "my.properties"}} at org.jboss.as.controller.operations.validation.OperationValidator.checkAllRequiredPropertiesArePresent(OperationValidator.java:207) at org.jboss.as.controller.operations.validation.OperationValidator.validateOperation(OperationValidator.java:138) at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:334) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:336) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) at java.lang.Thread.run(Thread.java:745) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1074) Intermittent failure in DeploymentScannerUnitTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1074?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1074: ------------------------------------------ This failed again: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=78357&buildTyp... > Intermittent failure in DeploymentScannerUnitTestCase > ----------------------------------------------------- > > Key: WFCORE-1074 > URL: https://issues.jboss.org/browse/WFCORE-1074 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Alpha1 > > > DeploymentScannerUnitTestCase occasionally fails, 4 times in the last six weeks or so per Team City records: > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WildFlyCore&... > May not be relevant but the change log associated with the first failure shows WFCORE-903 / WFCORE-860 as part of the change set: > > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=70465&tab=buil... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1121) Use script name for file related to Wildfly to allow multiple instances easily

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1121?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-5645 to WFCORE-1121: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1121 (was: WFLY-5645) Component/s: Scripts (was: Scripts) Affects Version/s: 2.0.1.Final (was: 10.0.0.CR4) > Use script name for file related to Wildfly to allow multiple instances easily > ------------------------------------------------------------------------------ > > Key: WFCORE-1121 > URL: https://issues.jboss.org/browse/WFCORE-1121 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 2.0.1.Final > Reporter: Romain Pelisse > Assignee: Tomaz Cerar > Priority: Optional > Original Estimate: 1 day > Remaining Estimate: 1 day > > With the current provided init.d script, one cannot start several instances of Wildfly. Indeed, the script will associate the same files (pid file, log) to both instance. If we rename those files using, for instance, the name of the script we can easily use the *exact same script* for all local instances: > {code:bash} > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-1 > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-2 > {code} > And to take the example of the PIDFILE: > {code:bash} > JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid > {code} > Each links will then look up and creates its own separate file: > /var/run/wildfly-1/jboss-as-domain.pid > /var/run/wildfly-2/jboss-as-domain.pid -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1121) Use script name for file related to Wildfly to allow multiple instances easily

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1121?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1121: ------------------------------------- Fix Version/s: 3.0.0.Alpha1 > Use script name for file related to Wildfly to allow multiple instances easily > ------------------------------------------------------------------------------ > > Key: WFCORE-1121 > URL: https://issues.jboss.org/browse/WFCORE-1121 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 2.0.1.Final > Reporter: Romain Pelisse > Assignee: Tomaz Cerar > Priority: Optional > Fix For: 3.0.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > With the current provided init.d script, one cannot start several instances of Wildfly. Indeed, the script will associate the same files (pid file, log) to both instance. If we rename those files using, for instance, the name of the script we can easily use the *exact same script* for all local instances: > {code:bash} > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-1 > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-2 > {code} > And to take the example of the PIDFILE: > {code:bash} > JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid > {code} > Each links will then look up and creates its own separate file: > /var/run/wildfly-1/jboss-as-domain.pid > /var/run/wildfly-2/jboss-as-domain.pid -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1121) Use script name for file related to Wildfly to allow multiple instances easily

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1121?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1121: ---------------------------------------- Assignee: Romain Pelisse (was: Tomaz Cerar) > Use script name for file related to Wildfly to allow multiple instances easily > ------------------------------------------------------------------------------ > > Key: WFCORE-1121 > URL: https://issues.jboss.org/browse/WFCORE-1121 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 2.0.1.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Optional > Fix For: 3.0.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > With the current provided init.d script, one cannot start several instances of Wildfly. Indeed, the script will associate the same files (pid file, log) to both instance. If we rename those files using, for instance, the name of the script we can easily use the *exact same script* for all local instances: > {code:bash} > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-1 > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-2 > {code} > And to take the example of the PIDFILE: > {code:bash} > JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid > {code} > Each links will then look up and creates its own separate file: > /var/run/wildfly-1/jboss-as-domain.pid > /var/run/wildfly-2/jboss-as-domain.pid -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5274) EJB IOR contains wrong port (non-SSL port) information when SSL is required

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-5274?page=com.atlassian.jira.plugin.... ] Tomasz Adamski closed WFLY-5274. -------------------------------- Resolution: Out of Date This issue cannot be fixed in upstream WildFly. The reason is that after orb implementation switch server_requires security settings is no longer supported (it is deprecated and will be removed in WF11) and setting it has no effect. I have already prepared the fix but it has to merged directly to the eap. > EJB IOR contains wrong port (non-SSL port) information when SSL is required > --------------------------------------------------------------------------- > > Key: WFLY-5274 > URL: https://issues.jboss.org/browse/WFLY-5274 > Project: WildFly > Issue Type: Bug > Components: IIOP > Reporter: Derek Horton > Assignee: Tomasz Adamski > > Description of problem: > - Configure JBoss to only allow IIOP connections over SSL > - It is possible to do this, but the configuration is confusing (possibly a bug) > Details of the setup/issue: > - When enabling SSL for jacorb, it normally listens on both the non-ssl port and the ssl port > - Setting server-requires="ServerAuth" causes the server to stop listening on non-ssl port > - However, the IOR tells client to connect to non-ssl port ...even though its not listening on it > String lookup = "corbaname:iiop:" + host + ":" + port +"#" + ejbLookupPath; > // lookup the IIOP EJB > Object iiopObj = ctx.lookup(lookup); > // the call to the EJB will fail due to the port being wrong non-ssl vs ssl > - The workaround is to use the following ior-setting to correct the port settings in the IOR > /subsystem=jacorb/ior-settings=default/setting=transport-config:add(confidentiality=required) > - Shouldn't setting "server-requires=ServerAuth" change the port info in the IOR? -- 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