[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13629?page=com.atlassian.jira.plugi... ]
Eduardo Martins closed WFLY-13629.
----------------------------------
Resolution: Explained
As [~soul2zimate] explained, these are Arquillian tests which are run with specific Maven profiles.
[https://github.com/wildfly/quickstart/blob/master/shared-doc/run-arquilli...
> WildFly kitchensink quickstart doesn't run test when started by Maven
> ---------------------------------------------------------------------
>
> Key: WFLY-13629
> URL: https://issues.redhat.com/browse/WFLY-13629
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 20.0.0.Final
> Reporter: Norbert Kawiński
> Assignee: Eduardo Martins
> Priority: Major
>
> Problem:
> When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
>
> Cause:
> {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
> Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
> ??{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}??
> * ??{color:#505f79}_{{**/Test*.java}}_{color}??
> * ??{color:#505f79}_{{**/*Test.java}}_{color}??
> * ??{color:#505f79}_{{**/*Tests.java}}_{color}??
> * ??{color:#505f79}{{_**/*TestCase.java_}}{color}??
> {color:#172b4d}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color}
>
> {color:#172b4d}Solution:{color}
> {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (WFLY-12018) WebSocket13Channel not Serializable
by Chao Wang (Jira)
[ https://issues.redhat.com/browse/WFLY-12018?page=com.atlassian.jira.plugi... ]
Chao Wang updated WFLY-12018:
-----------------------------
Labels: downstream_dependency (was: )
> WebSocket13Channel not Serializable
> -----------------------------------
>
> Key: WFLY-12018
> URL: https://issues.redhat.com/browse/WFLY-12018
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 16.0.0.Final
> Environment: wildfly16 full-ha domain mode
> Reporter: georges goebel
> Assignee: Paul Ferraro
> Priority: Major
> Labels: downstream_dependency
> Fix For: 20.0.0.Beta1, 20.0.0.Final
>
>
> I have running an webapplication in a clustered wildfly16 environment (*full-ha domain* mode) with the *distributable*-web.xml tag.
> I want to add websocket support to it, but as soon as I use it in a JSF-page, I'm getting a *NotSerializableException* for the "* io.undertow.websockets.core.protocol.version13.WebSocket13Channel*".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (WFLY-9129) Setting env var SECMGR=true no longer works
by Lukas Vydra (Jira)
[ https://issues.redhat.com/browse/WFLY-9129?page=com.atlassian.jira.plugin... ]
Lukas Vydra resolved WFLY-9129.
-------------------------------
Resolution: Cannot Reproduce
Closing as we are not able to reproduce it and we have no input from reporter
> Setting env var SECMGR=true no longer works
> -------------------------------------------
>
> Key: WFLY-9129
> URL: https://issues.redhat.com/browse/WFLY-9129
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager
> Affects Versions: 10.0.0.Final, 10.1.0.Final, 11.0.0.Alpha1
> Reporter: r searls
> Assignee: Lukas Vydra
> Priority: Major
>
> Setting env var SECMGR=true is suppose to enable the security manager.
> It is not working. I've tried the following and none of them enable
> the security manager.
> export SECMGR=true;
> on the cmd-line -DSECMGR=true
> edit bin/standalone.conf and uncomment line SECMGR="true"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (WFCORE-5048) Tests HTTPSManagementInterfaceTestCase/HTTPSManagementInterfacePKCS12TestCase fail with -Delytron
by Ricardo Martin Camarero (Jira)
Ricardo Martin Camarero created WFCORE-5048:
-----------------------------------------------
Summary: Tests HTTPSManagementInterfaceTestCase/HTTPSManagementInterfacePKCS12TestCase fail with -Delytron
Key: WFCORE-5048
URL: https://issues.redhat.com/browse/WFCORE-5048
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Affects Versions: 13.0.0.Beta1
Reporter: Ricardo Martin Camarero
Assignee: Ricardo Martin Camarero
Tests org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfacePKCS12TestCase and HTTPSManagementInterfaceTestCase fail when -Delytron is set.
{code:java}
org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfacePKCS12TestCase Time elapsed: 0.003 s <<< ERROR!org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfacePKCS12TestCase Time elapsed: 0.003 s <<< ERROR!java.lang.RuntimeException:
{ "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]"]}
at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:271) at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.serverSetup(HTTPSManagementInterfaceTestCase.java:346) at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.startAndSetupContainer(HTTPSManagementInterfaceTestCase.java:125) at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfacePKCS12TestCase.startAndSetupContainer(HTTPSManagementInterfacePKCS12TestCase.java:41) 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.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) 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.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfacePKCS12TestCase Time elapsed: 0.004 s <<< ERROR!java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remoting://127.0.0.1:9999. 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:80) at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:263) at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.resetHttpInterfaceConfiguration(HTTPSManagementInterfaceTestCase.java:398) at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.stopContainer(HTTPSManagementInterfaceTestCase.java:241) 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.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.net.ConnectException: WFLYPRT0053: Could not connect to remoting://127.0.0.1:9999. The connection failed at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129) 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:132) at org.jboss.as.controller.client.impl.RemotingModelControllerClient$2.getChannel(RemotingModelControllerClient.java:85) 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) ... 32 moreCaused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327) at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:599) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:561) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:549) at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:209) at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:121) ... 42 more
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven
by Chao Wang (Jira)
[ https://issues.redhat.com/browse/WFLY-13629?page=com.atlassian.jira.plugi... ]
Chao Wang commented on WFLY-13629:
----------------------------------
That is an integration test which is supposed to run with arquillian managed / remote server.
please refer to https://github.com/wildfly/quickstart/blob/master/guide/KitchensinkQuicks...
> WildFly kitchensink quickstart doesn't run test when started by Maven
> ---------------------------------------------------------------------
>
> Key: WFLY-13629
> URL: https://issues.redhat.com/browse/WFLY-13629
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 20.0.0.Final
> Reporter: Norbert Kawiński
> Assignee: Eduardo Martins
> Priority: Major
>
> Problem:
> When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
>
> Cause:
> {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
> Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
> ??{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}??
> * ??{color:#505f79}_{{**/Test*.java}}_{color}??
> * ??{color:#505f79}_{{**/*Test.java}}_{color}??
> * ??{color:#505f79}_{{**/*Tests.java}}_{color}??
> * ??{color:#505f79}{{_**/*TestCase.java_}}{color}??
> {color:#172b4d}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color}
>
> {color:#172b4d}Solution:{color}
> {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (DROOLS-5329) Review externalizing lambda failure case
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5329?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi resolved DROOLS-5329.
---------------------------------------
Fix Version/s: 7.41.0.Final
Resolution: Done
Finished all sub-tasks.
Split 3 minor JIRAs to be done later:
https://issues.redhat.com/browse/DROOLS-5463
https://issues.redhat.com/browse/DROOLS-5474
https://issues.redhat.com/browse/DROOLS-5475
> Review externalizing lambda failure case
> ----------------------------------------
>
> Key: DROOLS-5329
> URL: https://issues.redhat.com/browse/DROOLS-5329
> Project: Drools
> Issue Type: Task
> Components: executable model
> Affects Versions: 7.37.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
> Fix For: 7.41.0.Final
>
>
> In CompilerTest#testStringValueOf, there is a case where MaterializedLambdaPredicate is not created.
> {code:java}
> public static org.drools.model.Rule rule_R() {
> final org.drools.model.Variable<java.lang.Integer> var_GENERATED_$pattern_Integer$1$ = D.declarationOf(java.lang.Integer.class,
> DomainClassesMetadata81A66AD685F7689036AAA5128956C14B.java_lang_Integer_Metadata_INSTANCE,
> "GENERATED_$pattern_Integer$1$");
> final org.drools.model.Variable<Integer> var_$i = D.declarationOf(Integer.class, "$i");
> final org.drools.model.Variable<org.drools.modelcompiler.domain.Person> var_GENERATED_$pattern_Person$1$ = D.declarationOf(org.drools.modelcompiler.domain.Person.class,
> DomainClassesMetadata81A66AD685F7689036AAA5128956C14B.org_drools_modelcompiler_domain_Person_Metadata_INSTANCE,
> "GENERATED_$pattern_Person$1$");
> org.drools.model.Rule rule = D.rule("R").build(D.pattern(var_GENERATED_$pattern_Integer$1$).bind(var_$i, (java.lang.Integer _this) -> _this.intValue()),
> D.pattern(var_GENERATED_$pattern_Person$1$).expr("476633DA7C4638FC84A32859E0C843E6",
> var_$i,
> (_this, $i) -> org.drools.modelcompiler.util.EvaluationUtil.areNullSafeEquals(_this.getName(),
> (String.valueOf($i))),
> D.reactOn("name")),
> D.on(var_$i).execute(defaultpkg.P1D.LambdaConsequence1D5F4C5CA006007B1D3974ED5A5A05B6.INSTANCE));
> return rule;
> }
> {code}
> See
> {code:java}
> expr("476633DA7C4638FC84A32859E0C843E6",
> var_$i,
> (_this, $i) -> org.drools.modelcompiler.util.EvaluationUtil.areNullSafeEquals(_this.getName(),
> (String.valueOf($i)))
> {code}
> It throws DoNotConvertLambdaException in ExecModelLambdaPostProcessor.
> {code:java}
> private void extractLambdaFromMethodCall(MethodCallExpr methodCallExpr, Supplier<MaterializedLambda> lambdaExtractor) {
> methodCallExpr.getArguments().forEach(a -> {
> if (a.isLambdaExpr()) {
> LambdaExpr lambdaExpr = a.asLambdaExpr();
> try {
> CreatedClass aClass = lambdaExtractor.get().create(lambdaExpr.toString(), imports, staticImports);
> lambdaClasses.put(aClass.getClassNameWithPackage(), aClass);
> ClassOrInterfaceType type = StaticJavaParser.parseClassOrInterfaceType(aClass.getClassNameWithPackage());
> a.replace(lambdaInstance(type));
> } catch(DoNotConvertLambdaException e) {
> logger.debug("Cannot externalize lambdas {}", e.getMessage());
> }
> }
> });
> }
> {code}
> Review if it's something can be fixed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months