[JBoss JIRA] (WFLY-9876) ActiveMQ Artemis with IPv6 and Scope fails
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-9876?page=com.atlassian.jira.plugin.... ]
Miroslav Novak commented on WFLY-9876:
--------------------------------------
[~poppjens] Hi Jens, I'm doing jira clean up. Could you confirm that this issue is still valid? Thanks
> ActiveMQ Artemis with IPv6 and Scope fails
> ------------------------------------------
>
> Key: WFLY-9876
> URL: https://issues.jboss.org/browse/WFLY-9876
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.1.0.Final, 11.0.0.Final
> Environment: CentOS 7 with IPv6 ULA Address as server for Wildfly 10.1.0Final
> Windows 10 as client
> Both with Java 8u161 (64bit)
> Reporter: Jens Popp
> Assignee: Jeff Mesnil
> Priority: Major
>
> Somehow Java behaves differently on Linux and Windows regarding the IPv6 Network Interfaces. With a small programm you can test this:
> {code}
> Enumeration<NetworkInterface> interfaces = NetworkInterface.getNetworkInterfaces();
> while (interfaces.hasMoreElements()) {
> NetworkInterface netInterface = interfaces.nextElement();
> Enumeration<InetAddress> address = netInterface.getInetAddresses();
> while (address.hasMoreElements()) {
> InetAddress addr = address.nextElement();
> if (addr instanceof Inet6Address) {
> Inet6Address inet6addr = (Inet6Address) addr;
> if (!inet6addr.isLinkLocalAddress() && !inet6addr.isLoopbackAddress())
> System.out.println(netInterface.getName() +":"+ inet6addr.isLinkLocalAddress() +":"+ inet6addr +" - "+ inet6addr.getScopedInterface());
> }
> }
> }
> {code}
> In windows the scope will only be set for Link Local, in CentOS also for ULA addresses.
> If I lookup the JMS from a ULA address (without scope) e.g. with:
> {code}
> String JMS_CONNECTION_FACTORY_JNDI = "jms/RemoteConnectionFactory";
> Context context = getApplicationManager().getConnectionHandler().getContext();
> TopicConnectionFactory cf = (TopicConnectionFactory) context.lookup(JMS_CONNECTION_FACTORY_JNDI);
> {code}
> The TopicConnectionFactory is ActiveMQJMSConnectionFactory. This factory receives a TransportConfiguration from the server that includes the server scope (IPv6 Address with NetworkInterface after % e.g. [fd00::d7dc:b4cc:2e2a:ea1%enp0s3]). Trying to create a topic connection with the TopicConnectionFactory will fail, since the client does not know the scope (enp0s3).
> There is a bug fix in NettyConnector (HORNETQ-907) to strip this "%enp0s3" scope, but this BugFix does not work. The fix uses the standard InetAddress methods to parse the host String, which fails, if the host String contains a server scope (network interface) not available on the client. This will only cause an exception, if server and client have different names for the NetworkInterfaces! Testing e.g. on two identical Linux machines will not uncover the problem!
> I think the underlying problem is, that the lookup distributes the server scope in the IPv6 Address. The scope should only be distributed for Link-local Addresses, for all other addresses the scope should be stripped already on the server and not be distributed during lookup.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted
by Srinivas ev (Jira)
[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ]
Srinivas ev updated WFLY-11374:
-------------------------------
Priority: Critical (was: Major)
> Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted
> ------------------------------------------------------------------------------
>
> Key: WFLY-11374
> URL: https://issues.jboss.org/browse/WFLY-11374
> Project: WildFly
> Issue Type: Bug
> Reporter: Srinivas ev
> Assignee: Jason Greene
> Priority: Critical
> Attachments: master.xml, slave.xml
>
>
> I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work.
> This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine.
> master in standalone-full-ha.xml - refer master.xml
> slave in standalone-full-ha.xml - refer slave.xml
> In the startup script, I am passing all the values for placeholders of my server host ip's accordingly.
> Test scenario -
> 1. Bring master up.
> 2. Bring slave up.
> 3. slave will announce the backup. (AMQ221031: backup announced).
> 4. Make master down.
> 5. Replication is success.
> 6. Slave is acting as master/live.
> 7. Make master up.
> Issue - master is unable to announce the backup and starts normally as a standalone wildfly.
> This backup announcement works fine in windows and failover also works as expected.
> Please let me know if anything specific required along with this details.
> Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar
> in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted
by Srinivas ev (Jira)
[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ]
Srinivas ev updated WFLY-11374:
-------------------------------
Description:
I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work.
This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine.
master in standalone-full-ha.xml - refer master.xml
slave in standalone-full-ha.xml - refer slave.xml
In the startup script, I am passing all the values for placeholders of my server host ip's accordingly.
Test scenario -
1. Bring master up.
2. Bring slave up.
3. slave will announce the backup. (AMQ221031: backup announced).
4. Make master down.
5. Replication is success.
6. Slave is acting as master/live.
7. Make master up.
Issue - master is unable to announce the backup and starts normally as a standalone wildfly.
This backup announcement works fine in windows and failover also works as expected.
Please let me know if anything specific required along with this details.
Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar
in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main
was:
I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work.
This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine.
master in standalone-full-ha.xml - refer master.xml
slave in standalone-full-ha.xml - refer slave.xml
In the startup script, I am passing all the values for placeholders of my server host ip's accordingly.
Test scenario -
1. Bring master up.
2. Bring slave up.
3. slave will announce the backup. (AMQ221031: backup announced).
4. Make master down.
5. Replication is success.
6. Slave is acting as master/live.
7. Make master up.
Issue - master is unable to announce the backup and starts normally as a standalone wildfly.
This backup announcement works fine in windows and failover also works as expected.
Please let me know if anything specific required along with this details.
> Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted
> ------------------------------------------------------------------------------
>
> Key: WFLY-11374
> URL: https://issues.jboss.org/browse/WFLY-11374
> Project: WildFly
> Issue Type: Bug
> Reporter: Srinivas ev
> Assignee: Jason Greene
> Priority: Major
> Attachments: master.xml, slave.xml
>
>
> I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work.
> This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine.
> master in standalone-full-ha.xml - refer master.xml
> slave in standalone-full-ha.xml - refer slave.xml
> In the startup script, I am passing all the values for placeholders of my server host ip's accordingly.
> Test scenario -
> 1. Bring master up.
> 2. Bring slave up.
> 3. slave will announce the backup. (AMQ221031: backup announced).
> 4. Make master down.
> 5. Replication is success.
> 6. Slave is acting as master/live.
> 7. Make master up.
> Issue - master is unable to announce the backup and starts normally as a standalone wildfly.
> This backup announcement works fine in windows and failover also works as expected.
> Please let me know if anything specific required along with this details.
> Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar
> in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4213) CLIAuthenticationTestCase fails with Elytron profile in Testsuite
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-4213?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise reassigned WFCORE-4213:
--------------------------------------------
Assignee: Jean-Francois Denise
> CLIAuthenticationTestCase fails with Elytron profile in Testsuite
> -----------------------------------------------------------------
>
> Key: WFCORE-4213
> URL: https://issues.jboss.org/browse/WFCORE-4213
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Security, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Assignee: Jean-Francois Denise
> Priority: Major
>
> cd testsuite/manualmode/
> mvn test -Delytron -Dtest=CLIAuthenticationTestCase
> {code}
> [INFO] Running org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase
> [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 34.361 s <<< FAILURE! - in org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase
> [ERROR] testSaslAuth(org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase) Time elapsed: 21.797 s <<< ERROR!
> java.lang.Exception:
> ry-name=test-sasl-factory --new-security-domain-name=test-sasl-security-domainile-system-realm-name=fs-test-realm --new-auth-facto
> Server reloaded.
> Command success.
> Authentication configured for management http-interface
> sasl authentication-factory=management-sasl-authentication
> security-domain=ManagementDomain
> [standalone@127.0.0.1:9990 /]
> [standalone@127.0.0.1:9990 /]
> at org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase.testSaslAuth(CLIAuthenticationTestCase.java:298)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> Caused by: java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase.testSaslAuth(CLIAuthenticationTestCase.java:262)
> ... 40 more
> [ERROR] testHttpAuth(org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase) Time elapsed: 2.194 s <<< ERROR!
> org.wildfly.core.testrunner.UnsuccessfulOperationException:
> "WFLYCTL0367: Cannot remove capability 'org.wildfly.security.realm-mapper.fs-test-realm' as it is required by other capabilities:
> capability 'org.wildfly.security.sasl-authentication-factory.management-sasl-authentication' requires it for attribute 'realm-mapper' at address '/subsystem=elytron/sasl-authentication-factory=management-sasl-authentication'"
> at org.wildfly.core.testrunner.ManagementClient.checkSuccessful(ManagementClient.java:247)
> at org.wildfly.core.testrunner.ManagementClient.executeForResult(ManagementClient.java:235)
> at org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase.cleanTest(CLIAuthenticationTestCase.java:169)
> at org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase.testHttpAuth(CLIAuthenticationTestCase.java:228)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [ERROR] org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase Time elapsed: 12.56 s <<< ERROR!
> org.wildfly.core.testrunner.UnsuccessfulOperationException:
> "WFLYCTL0367: Cannot remove capability 'org.wildfly.security.security-realm.fs-test-realm' as it is required by other capabilities:
> capability 'org.wildfly.security.security-domain.ManagementDomain' requires it for attribute 'realm' at address '/subsystem=elytron/security-domain=ManagementDomain'"
> at org.wildfly.core.testrunner.ManagementClient.checkSuccessful(ManagementClient.java:247)
> at org.wildfly.core.testrunner.ManagementClient.executeForResult(ManagementClient.java:235)
> at org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase.cleanConfig(CLIAuthenticationTestCase.java:136)
> at org.jboss.as.test.manualmode.management.cli.CLIAuthenticationTestCase.afterClass(CLIAuthenticationTestCase.java:98)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] CLIAuthenticationTestCase.afterClass:98->cleanConfig:136 » UnsuccessfulOperation
> [ERROR] CLIAuthenticationTestCase.testHttpAuth:228->cleanTest:169 » UnsuccessfulOperation
> [ERROR] CLIAuthenticationTestCase.testSaslAuth:298 security enable-sasl-management --...
> [INFO]
> [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4218) ReloadSASLFactoryTestCase fails with Elytron profile
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-4218?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise reassigned WFCORE-4218:
--------------------------------------------
Assignee: Jean-Francois Denise
> ReloadSASLFactoryTestCase fails with Elytron profile
> ----------------------------------------------------
>
> Key: WFCORE-4218
> URL: https://issues.jboss.org/browse/WFCORE-4218
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Assignee: Jean-Francois Denise
> Priority: Major
>
> {noformat}
> cd testsuite/standalone/
> mvn test -Delytron -Dtest=ReloadSASLFactoryTestCase
> {noformat}
> {noformat}
> [INFO] Running org.jboss.as.test.integration.management.cli.ReloadSASLFactoryTestCase
> [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.446 s <<< FAILURE! - in null
> [ERROR] Failure when constructing test Time elapsed: 2.443 s <<< ERROR!
> java.lang.RuntimeException: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.wildfly.core.testrunner.ManagementClient.executeForResult(ManagementClient.java:238)
> at org.wildfly.core.testrunner.WildflyTestRunner.checkServerState(WildflyTestRunner.java:167)
> at org.wildfly.core.testrunner.WildflyTestRunner.runTearDownTasks(WildflyTestRunner.java:138)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:111)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerClient.java:63)
> at org.wildfly.core.testrunner.ManagementClient.executeForResult(ManagementClient.java:234)
> ... 21 more
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:60)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 24 more
> Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
> ANONYMOUS: javax.security.sasl.SaslException: ELY05092: Authentication name is empty
> at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:402)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:571)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:533)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:521)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:204)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> ... 34 more
> Suppressed: javax.security.sasl.SaslException: ELY05092: Authentication name is empty
> at org.wildfly.security.sasl.anonymous.AnonymousSaslClient.evaluateMessage(AnonymousSaslClient.java:74)
> at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:199)
> at org.wildfly.security.sasl.util.AbstractSaslClient.evaluateChallenge(AbstractSaslClient.java:79)
> at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.lambda$handleEvent$1(ClientConnectionOpenListener.java:460)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4220) SecurityCommandsTestCase fails with Elytron profile
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-4220?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise reassigned WFCORE-4220:
--------------------------------------------
Assignee: Jean-Francois Denise
> SecurityCommandsTestCase fails with Elytron profile
> ---------------------------------------------------
>
> Key: WFCORE-4220
> URL: https://issues.jboss.org/browse/WFCORE-4220
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Assignee: Jean-Francois Denise
> Priority: Major
>
> {noformat}
> cd testsuite/standalone/
> mvn test -Delytron -Dtest=SecurityCommandsTestCase
> {noformat}
> {noformat}
> [INFO] Running org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase
> [ERROR] Tests run: 17, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 22.482 s <<< FAILURE! - in org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase
> [ERROR] testEnableSSLInteractiveConfirmNative(org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase) Time elapsed: 0.17 s <<< ERROR!
> org.jboss.as.cli.CommandLineException:
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.core.management.security.realm.ManagementRealm"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.core.management.security.realm.ManagementRealm]"]
> },
> "rolled-back" => true
> }
> at org.jboss.as.cli.handlers.OperationRequestHandler.handle(OperationRequestHandler.java:94)
> at org.jboss.as.cli.impl.CommandContextImpl.handleOperation(CommandContextImpl.java:1800)
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:809)
> at org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase.enableNative(SecurityCommandsTestCase.java:678)
> at org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase.testEnableSSLInteractiveConfirmNative(SecurityCommandsTestCase.java:482)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [ERROR] testEnableSSLNative(org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase) Time elapsed: 0.148 s <<< ERROR!
> org.jboss.as.cli.CommandLineException:
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0212: Duplicate resource [
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"management-native\")
> ]",
> "rolled-back" => true
> }
> at org.jboss.as.cli.handlers.OperationRequestHandler.handle(OperationRequestHandler.java:94)
> at org.jboss.as.cli.impl.CommandContextImpl.handleOperation(CommandContextImpl.java:1800)
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:809)
> at org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase.enableNative(SecurityCommandsTestCase.java:677)
> at org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase.testEnableSSLNative(SecurityCommandsTestCase.java:396)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [INFO]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted
by Srinivas ev (Jira)
Srinivas ev created WFLY-11374:
----------------------------------
Summary: Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted
Key: WFLY-11374
URL: https://issues.jboss.org/browse/WFLY-11374
Project: WildFly
Issue Type: Bug
Reporter: Srinivas ev
Assignee: Jason Greene
Attachments: master.xml, slave.xml
I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work.
This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine.
master in standalone-full-ha.xml - refer master.xml
slave in standalone-full-ha.xml - refer slave.xml
In the startup script, I am passing all the values for placeholders of my server host ip's accordingly.
Test scenario -
1. Bring master up.
2. Bring slave up.
3. slave will announce the backup. (AMQ221031: backup announced).
4. Make master down.
5. Replication is success.
6. Slave is acting as master/live.
7. Make master up.
Issue - master is unable to announce the backup and starts normally as a standalone wildfly.
This backup announcement works fine in windows and failover also works as expected.
Please let me know if anything specific required along with this details.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11373) EE naming context not set when @Initialized(ApplicationScoped.class) event is fired in some cases
by Ladislav Thon (Jira)
[ https://issues.jboss.org/browse/WFLY-11373?page=com.atlassian.jira.plugin... ]
Ladislav Thon updated WFLY-11373:
---------------------------------
Description:
Since [this commit|https://github.com/wildfly/wildfly/commit/3659f4738aa3b08515b93ca3...] (which fixed WFLY-9732), the EE naming context is not set up properly when {{WeldBootstrap.endInitialization()}} is called. This is because the naming context is set up by the {{SetupAction}} executed in {{WeldStartService}}. ({{WeldBootstrap.endInitialization()}} used to be invoked from {{WeldStartService}} as well, but the commit linked above moved the invocation to a separate {{WeldStartCompletionService}}.)
That is a problem because {{endInitialization()}} is where the {{(a)Initialized(ApplicationScoped.class)}} event is fired from (in some cases). If there's a bean that's being eagerly-initialized by listening for this event and the bean also requires the EE naming context (e.g. for injecting {{@Resource(lookup = "java:comp/DefaultManagedThreadFactory")}}), deployment now fails (because the resource injection fails).
I can see this problem in Thorntail, because the pattern described above is used in SmallRye Fault Tolerance (see [HystrixInitializer|https://github.com/smallrye/smallrye-fault-tolerance/b...] and [DefaultHystrixConcurrencyStrategy|https://github.com/smallrye/smallrye-fa...]).
was:
Since [this commit|https://github.com/wildfly/wildfly/commit/3659f4738aa3b08515b93ca3...] (which fixed WFLY-9732), the EE naming context is not set up properly when {{WeldBootstrap.endInitialization()}} is called. This is because the naming context is set up by the {{SetupAction}} executed in {{WeldStartService}}. ({{WeldBootstrap.endInitialization()}} used to be invoked from {{WeldStartService}} as well, but the commit linked above moved the invocation to a separate {{WeldStartCompletionService}}.)
That is a problem because {{endInitialization()}} is where the {{(a)Initialized(ApplicationScoped.class)}} event is fired from (in some cases). If there's a bean that's being eagerly-initialized by listening for this event and the bean also requires the EE naming context (e.g. for injecting {{@Resource(lookup = "java:comp/DefaultManagedThreadFactory")}}), deployment now fails (because the resource injection fails).
I can see this problem in Thorntail, because the pattern described above is used by SmallRye FaultTolerance (see [HystrixInitializer|https://github.com/smallrye/smallrye-fault-tolerance/b...] and [DefaultHystrixConcurrencyStrategy|https://github.com/smallrye/smallrye-fa...]).
> EE naming context not set when @Initialized(ApplicationScoped.class) event is fired in some cases
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-11373
> URL: https://issues.jboss.org/browse/WFLY-11373
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 14.0.1.Final
> Reporter: Ladislav Thon
> Assignee: Ladislav Thon
> Priority: Major
>
> Since [this commit|https://github.com/wildfly/wildfly/commit/3659f4738aa3b08515b93ca3...] (which fixed WFLY-9732), the EE naming context is not set up properly when {{WeldBootstrap.endInitialization()}} is called. This is because the naming context is set up by the {{SetupAction}} executed in {{WeldStartService}}. ({{WeldBootstrap.endInitialization()}} used to be invoked from {{WeldStartService}} as well, but the commit linked above moved the invocation to a separate {{WeldStartCompletionService}}.)
> That is a problem because {{endInitialization()}} is where the {{(a)Initialized(ApplicationScoped.class)}} event is fired from (in some cases). If there's a bean that's being eagerly-initialized by listening for this event and the bean also requires the EE naming context (e.g. for injecting {{@Resource(lookup = "java:comp/DefaultManagedThreadFactory")}}), deployment now fails (because the resource injection fails).
> I can see this problem in Thorntail, because the pattern described above is used in SmallRye Fault Tolerance (see [HystrixInitializer|https://github.com/smallrye/smallrye-fault-tolerance/b...] and [DefaultHystrixConcurrencyStrategy|https://github.com/smallrye/smallrye-fa...]).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months