June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10633) Update the testsuite to make use of the utilities for certificate generation instead of using pre-generated CAs and certs

by Justin Cook (JIRA)

Justin Cook created WFLY-10633: ---------------------------------- Summary: Update the testsuite to make use of the utilities for certificate generation instead of using pre-generated CAs and certs Key: WFLY-10633 URL: https://issues.jboss.org/browse/WFLY-10633 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Justin Cook Assignee: Justin Cook Our testsuite currently makes use of pre-generated CAs and certs. This results in issues when the certificates expire since the testsuite then needs to be updated with newly generated CAs and certs. This task is to update our testsuite to dynamically generate the needed certificates using Elytron's certificate generation utilities (e.g., org.wildfly.security.x500.cert.X509CertificateBuilder, org.wildfly.security.x500.cert.SelfSignedX509CertificateAndSigningKey.builder(), etc.). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2649) Executable model - IndexingTest, RuleUnitTest + few other test classes fail with executable model

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2649?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2649: ---------------------------------- Description: When running tests from PR [1] with executable model, 220 out of 732 test cases fail. [1] https://github.com/kiegroup/drools/pull/1959 was:When running tests from PR [1] (TODO) with executable model, 220 out of 732 test cases fail. > Executable model - IndexingTest, RuleUnitTest + few other test classes fail with executable model > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-2649 > URL: https://issues.jboss.org/browse/DROOLS-2649 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When running tests from PR [1] with executable model, 220 out of 732 test cases fail. > [1] https://github.com/kiegroup/drools/pull/1959 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2649) Executable model - IndexingTest, RuleUnitTest + few other test classes fail with executable model

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2649: ------------------------------------- Summary: Executable model - IndexingTest, RuleUnitTest + few other test classes fail with executable model Key: DROOLS-2649 URL: https://issues.jboss.org/browse/DROOLS-2649 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final Reporter: Tibor Zimányi Assignee: Mario Fusco When running tests from PR [1] (TODO) with executable model, 220 out of 732 test cases fail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3944) Backup slave not reconnecting after master shutdown

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3944?page=com.atlassian.jira.plugi... ] Tomas Hofman updated WFCORE-3944: --------------------------------- Attachment: test-case.zip > Backup slave not reconnecting after master shutdown > --------------------------------------------------- > > Key: WFCORE-3944 > URL: https://issues.jboss.org/browse/WFCORE-3944 > Project: WildFly Core > Issue Type: Bug > Components: Management > Environment: EAP 7.1.2 > Windows > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Critical > Attachments: test-case.zip > > > The problem only occurs when backup mode (--backup flag) is on, and it actually is unrelated to patching. (I only noticed it when patching because that's usually when I restart the host.) I will attach an example you can use to verify the bug. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3944) Backup slave not reconnecting after master shutdown

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3944?page=com.atlassian.jira.plugi... ] Tomas Hofman updated WFCORE-3944: --------------------------------- Description: The problem only occurs when backup mode (--backup flag) is on, and it actually is unrelated to patching. (I only noticed it when patching because that's usually when I restart the host.) I will attach an example you can use to verify the bug. was: The problem only occurs when backup mode (--backup flag) is on, and it actually is unrelated to patching. (I only noticed it when patching because that's usually when I restart the host.) I will attach an example you can use to verify the bug. Below is where I think the problem is: {code:java} if (endRoot.hasDefined(SERVER_GROUP)) { for (final Property serverGroup : endRoot.get(SERVER_GROUP).asPropertyList()) { if (serverGroup.getValue().hasDefined(deploymentElement.getKey(), deploymentElement.getValue())) { affectedGroups.add(serverGroup.getName()); relevantDeployments.add(deploymentElement.getValue()); } } } {code} It should be like this: {code:java} if (endRoot.hasDefined(SERVER_GROUP)) { for (final Property serverGroup : endRoot.get(SERVER_GROUP).asPropertyList()) { if (serverGroup.getValue().hasDefined(deploymentElement.getKey(), deploymentElement.getValue())) { if (serversByGroup.containsKey(serverGroup.getName())) { affectedGroups.add(serverGroup.getName()); } relevantDeployments.add(deploymentElement.getValue()); } } } {code} > Backup slave not reconnecting after master shutdown > --------------------------------------------------- > > Key: WFCORE-3944 > URL: https://issues.jboss.org/browse/WFCORE-3944 > Project: WildFly Core > Issue Type: Bug > Components: Management > Environment: EAP 7.1.2 > Windows > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Critical > Attachments: test-case.zip > > > The problem only occurs when backup mode (--backup flag) is on, and it actually is unrelated to patching. (I only noticed it when patching because that's usually when I restart the host.) I will attach an example you can use to verify the bug. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3944) Backup slave not reconnecting after master shutdown

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3944?page=com.atlassian.jira.plugi... ] Tomas Hofman moved JBEAP-14937 to WFCORE-3944: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3944 (was: JBEAP-14937) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Management (was: Management) Affects Version/s: (was: 7.1.2.GA) > Backup slave not reconnecting after master shutdown > --------------------------------------------------- > > Key: WFCORE-3944 > URL: https://issues.jboss.org/browse/WFCORE-3944 > Project: WildFly Core > Issue Type: Bug > Components: Management > Environment: EAP 7.1.2 > Windows > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Critical > > The problem only occurs when backup mode (--backup flag) is on, and it actually is unrelated to patching. (I only noticed it when patching because that's usually when I restart the host.) I will attach an example you can use to verify the bug. > Below is where I think the problem is: > {code:java} > if (endRoot.hasDefined(SERVER_GROUP)) { > for (final Property serverGroup : endRoot.get(SERVER_GROUP).asPropertyList()) { > if (serverGroup.getValue().hasDefined(deploymentElement.getKey(), deploymentElement.getValue())) { > affectedGroups.add(serverGroup.getName()); > relevantDeployments.add(deploymentElement.getValue()); > } > } > } > {code} > It should be like this: > {code:java} > if (endRoot.hasDefined(SERVER_GROUP)) { > for (final Property serverGroup : endRoot.get(SERVER_GROUP).asPropertyList()) { > if (serverGroup.getValue().hasDefined(deploymentElement.getKey(), deploymentElement.getValue())) { > if (serversByGroup.containsKey(serverGroup.getName())) { > affectedGroups.add(serverGroup.getName()); > } > relevantDeployments.add(deploymentElement.getValue()); > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10365) Generate component-matrix as part of the build

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-10365?page=com.atlassian.jira.plugin... ] Carlo de Wolf commented on WFLY-10365: -------------------------------------- The WildFly 13 result is: https://repository.jboss.org/nexus/content/groups/public/org/wildfly/wild... > Generate component-matrix as part of the build > ---------------------------------------------- > > Key: WFLY-10365 > URL: https://issues.jboss.org/browse/WFLY-10365 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: David Lloyd > Assignee: Kabir Khan > Fix For: 13.0.0.Beta1, 13.0.0.Final > > > Revert the change described in WFLY-9911. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3937: ------------------------------------------ [~sixcorners] Your approach looks better. It's not a huge problem if the containers have the same process-uuid. That value is only used on some diagnostic reporting tools we provide (see WFCORE-620) as a means to help differentiate between different servers in an environment. It doesn't affect the normal functioning of the server. Still, even though it's minor if you can avoid having it be the same, that's better. > Error when running configured wildfly > ------------------------------------- > > Key: WFCORE-3937 > URL: https://issues.jboss.org/browse/WFCORE-3937 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Final > Reporter: Stephen Buergler > Assignee: Jeff Mesnil > Priority: Minor > Attachments: Dockerfile > > > 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current > ... > 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot. > To reproduce: > docker build -t testing . > docker run --rm -it testing -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2625) Executable model - AccumulateTest and other tests fail with the model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2625?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2625: ------------------------------------- 6th fix https://github.com/kiegroup/drools/commit/49a092b1f06b68828c12b4ca5f3181b... > Executable model - AccumulateTest and other tests fail with the model > --------------------------------------------------------------------- > > Key: DROOLS-2625 > URL: https://issues.jboss.org/browse/DROOLS-2625 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > Tests from these test classes from drools-compiler module fail (350 out of 1014 cases) with the executable model: > - AccumulateTest > - AlphaNetworkModifyTest > - AlphaTest > - AnnotationsTest > - ArrayTest > - BackwardChainingTest > PR with tests: https://github.com/kiegroup/drools/pull/1941 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10629) Server startup wrongly deploys all xml files and never stops

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10629?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10629: ----------------------------------------- It sounds like somehow your $JBOSS_HOME/standalone/deployments/ is pointing to your $JBOSS_HOME/standalone/configuration dir. The deployment scanner is seeing the config files and trying to deploy them. > Server startup wrongly deploys all xml files and never stops > ------------------------------------------------------------ > > Key: WFLY-10629 > URL: https://issues.jboss.org/browse/WFLY-10629 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Reporter: Arnie Morein > Assignee: Jason Greene > > I have downloaded WF 12 and 13, then imported each into Eclipse (Oxygen.3a Release (4.7.3a)), OS is Win 7/x64; then used add-user to set up admin user. Then from both the command line and from within Eclipse, when the software starts up all of the xml configuration files get deployed at the same time despite the fact that the --server-config=standalone.xml parameter is present in either environment. What's worse, it starts versioning them and re-deploying them over and over and over again. > {quote} > 15:45:42,229 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container > 15:45:42,319 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml") > 15:45:42,320 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-load-balancer.xml" (runtime-name : "standalone-load-balancer.xml") > 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ha.xml" (runtime-name : "standalone-ha.xml") > 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full.xml" (runtime-name : "standalone-full.xml") > 15:45:42,325 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full-ha.xml" (runtime-name : "standalone-full-ha.xml") > 15:45:42,326 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ee8.xml" (runtime-name : "standalone-ee8.xml") > 15:45:42,407 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server > 15:45:42,410 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) started in 6285ms - Started 549 of 746 services (326 se > rvices are lazy, passive or on-demand) > 15:45:42,575 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:45:42,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone.boot.xml" (runtime-name: "standalone.boot.xml") > 15:45:42,581 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.initial.xml" (runtime-name: "standalone.initial.xml") > 15:45:42,724 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml") > 15:45:42,725 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.initial.xml" (runtime-name : "standalone.initial.xml") > 15:45:42,726 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.boot.xml" (runtime-name : "standalone.boot.xml") > 15:45:47,921 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 28ms > 15:45:47,928 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:45:47,930 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "standalone.v1.xml" (runtime-name: "standalone.v1.xml") > 15:45:47,982 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 55ms > 15:45:47,984 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:45:48,059 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml" > 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml") > 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml" > 15:45:53,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 13ms > 15:45:53,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml") > 15:45:53,237 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:45:53,249 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 15ms > 15:45:53,252 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:45:53,340 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml" > 15:45:53,341 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml") > 15:45:53,342 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"{quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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