[Red Hat JIRA] (WFLY-13875) Resolve missing dependency jboss.naming.context.java.jboss.DefaultJMSConnectionFactory
by Scott Marlow (Jira)
[ https://issues.redhat.com/browse/WFLY-13875?page=com.atlassian.jira.plugi... ]
Scott Marlow commented on WFLY-13875:
-------------------------------------
need to update our jacc configuration settings from javax.security.jacc.policy.provider to jakarta.security.jacc.policy.provider.
> Resolve missing dependency jboss.naming.context.java.jboss.DefaultJMSConnectionFactory
> --------------------------------------------------------------------------------------
>
> Key: WFLY-13875
> URL: https://issues.redhat.com/browse/WFLY-13875
> Project: WildFly
> Issue Type: Sub-task
> Components: JMS
> Reporter: Scott Marlow
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Labels: EE9
>
> server.log output from running Jakarta EE 9 Platform TCK JACC tests against Brian's WildFly ee-9 branch:
> {code}
> 020-09-15 15:48:46,120 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "greenmail-jboss-service.sar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.\"greenmail-jboss-service.sar\".\"greenmail-jboss-service.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> ...
> 2020-09-15 15:49:21,610 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jacc_util.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.jacc_util.jacc_util_web.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> ...
> 2020-09-15 15:49:27,418 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jacc_ejb_methodperm.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.naming.context.java.module.jacc_ejb_methodperm.jacc_ejb_methodperm_ejb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
> "jboss.naming.context.java.module.jacc_ejb_methodperm.jacc_ejb_methodperm_client.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
> "jboss.naming.context.java.comp.jacc_ejb_methodperm.jacc_ejb_methodperm_ejb.jacc_ejb_methodperm_MethodPermBean.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"
> ]
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[Red Hat JIRA] (AG-150) Update dependencies
by Luis Barreiro (Jira)
Luis Barreiro created AG-150:
--------------------------------
Summary: Update dependencies
Key: AG-150
URL: https://issues.redhat.com/browse/AG-150
Project: Agroal
Issue Type: Task
Components: build
Affects Versions: 1.8
Reporter: Luis Barreiro
Assignee: Luis Barreiro
Fix For: 1.9
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[Red Hat JIRA] (WFLY-13956) TwoConnectorsEJBFailoverTestCase sometimes hangs when running with jboss-ejb-client 4.0.35
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13956?page=com.atlassian.jira.plugi... ]
Cheng Fang commented on WFLY-13956:
-----------------------------------
In addition to the ejb client hanging at awaitResponse, I've also seen intermittent hanging during discovery (either at firstMatchDiscovery or clusterDiscovery) when running this test locally.
> TwoConnectorsEJBFailoverTestCase sometimes hangs when running with jboss-ejb-client 4.0.35
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-13956
> URL: https://issues.redhat.com/browse/WFLY-13956
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 21.0.0.Beta1
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
> Attachments: Screen Shot 2020-10-12 at 9.57.36 AM.png
>
>
> When upgrading jboss-ejb-client to version 4.0.35.Final, we noticed some WildFly CI jobs sometimes hang when running {{TwoConnectorsEJBFailoverTestCase}}, causing 100+ (e.g., 466) tests to fail:
> {code}
> RemoteElytronSingleSignOnTestCase.testSessionTimeoutDestroysSSOorg.jboss.as.test.clustering.cluster.sso.remote
> RemoteElytronSingleSignOnTestCase.testFormAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote
> RemoteElytronSingleSignOnTestCase.testNoAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote
> RemoteSingleSignOnTestCase.testSessionTimeoutDestroysSSOorg.jboss.as.test.clustering.cluster.sso.remote
> RemoteSingleSignOnTestCase.testFormAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote
> RemoteSingleSignOnTestCase.testNoAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote
> CoarseHotRodPersistenceWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote
> CoarseHotRodPersistenceWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote
> CoarseHotRodPersistenceWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote
> CoarseHotRodSessionActivationTestCase.testorg.jboss.as.test.clustering.cluster.web.remote
> CoarseHotRodWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote
> CoarseHotRodWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote
> CoarseHotRodWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote
> CoarseTransactionalHotRodWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote
> CoarseTransactionalHotRodWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote
> CoarseTransactionalHotRodWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote
> FineHotRodPersistenceWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote
> {code}
> The error messages are like:
> {code}
> org.jboss.arquillian.container.spi.client.container.LifecycleException: The port 9990 is already in use. It means that either the server might be already running or there is another process using port 9990.
> Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server.
> Please stop server (or another process) before running, change to another type of container (e.g. remote) or use jboss.socket.binding.port-offset variable to change the default port.
> To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> {code}
> In a [successful CI job|https://ci.wildfly.org/buildConfiguration/WFPR/226438?], {{TwoConnectorsEJBFailoverTestCase}} runs 2 tests: {{testEJBClientUsingLegacyRemotingProtocol}} and {{testEJBClientUsingHttpUpgradeProtocol}}, each taking ~25 seconds to complete. See attached screenshot.
> But in a [failed CI job|https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxJdk11/2...], filtering by {{TwoConnectorsEJBFailoverTestCase}} gives no result, which means the test hangs at {{testEJBClientUsingLegacyRemotingProtocol}} and so the test runner hasn't been able to collect the result from either test.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[Red Hat JIRA] (WFLY-13967) Provide an simple overview of what a layer is at the start of the layers table
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13967?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13967:
------------------------------------
Description:
At the start of https://docs.wildfly.org/21/Bootable_Guide.html#wildfly_layers a couple sentences stating what a layer is would be good. Assume that someone has followed a link to that section and is coming to it without much context. (I'm thinking about adding such a link to the WF 21 release announcement blog post, which is what inspired me to file this.)
That's shared content with other guides, so my intent is those couple sentences would be in the other guides too.
This is a bit tricky as it should be brief, clear and accurate. Doesn't need to be complete though; i.e. the idea is to give basic context, not a detail explanation.
was:
At the start of https://docs.wildfly.org/21/Bootable_Guide.html#wildfly_layers a couple sentences stating what a layer is would be good. Assume that someone has followed a link to that section and is coming too it without much context. (I'm thinking about adding such a link to the WF 21 release announcement blog post, which is what inspired me to file this.)
That's shared content with other guides, so my intent is those couple sentences would be in the other guides too.
This is a bit tricky as it should be brief, clear and accurate. Doesn't need to be complete though; i.e. the idea is to give basic context, not a detail explanation.
> Provide an simple overview of what a layer is at the start of the layers table
> ------------------------------------------------------------------------------
>
> Key: WFLY-13967
> URL: https://issues.redhat.com/browse/WFLY-13967
> Project: WildFly
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Brian Stansberry
> Assignee: Jean Francois Denise
> Priority: Major
> Fix For: 22.0.0.Beta1
>
>
> At the start of https://docs.wildfly.org/21/Bootable_Guide.html#wildfly_layers a couple sentences stating what a layer is would be good. Assume that someone has followed a link to that section and is coming to it without much context. (I'm thinking about adding such a link to the WF 21 release announcement blog post, which is what inspired me to file this.)
> That's shared content with other guides, so my intent is those couple sentences would be in the other guides too.
> This is a bit tricky as it should be brief, clear and accurate. Doesn't need to be complete though; i.e. the idea is to give basic context, not a detail explanation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[Red Hat JIRA] (WFLY-13875) Resolve missing dependency jboss.naming.context.java.jboss.DefaultJMSConnectionFactory
by Scott Marlow (Jira)
[ https://issues.redhat.com/browse/WFLY-13875?page=com.atlassian.jira.plugi... ]
Scott Marlow commented on WFLY-13875:
-------------------------------------
{color:#000000}com.sun.tsprovider test classes seems to be specified via:
{color}
{color:#000000} \{quote}{color}
{color:#000000}grep -ri com.sun.tsprovider . {color}
{color:#b218b2}./system/layers/base/com/sun/tsprovider/main/module.xml{color}{color:#18b2b2}:{color}{color:#000000}<module xmlns="urn:jboss:module:1.0" name="{color}{color:#ff5454}com.sun.tsprovider{color}{color:#000000}"> {color}
{color:#b218b2}./system/layers/base/org/jboss/as/security/main/module.xml{color}{color:#18b2b2}:{color}{color:#000000} <module name="{color}{color:#ff5454}com.sun.tsprovider{color}{color:#000000}" />{color}
\{quote}
The missing com.sun.ts.lib.util.sec.misc.Unsafe class is in the {color:#000000}tsharness.jar {color}in com.sun.tsprovider:main module.
The UnsatisfiedLinkError is thrown from:
{quote}
"ServerService Thread Pool -- 58@6945" prio=5 tid=0x56 nid=NA runnable
java.lang.Thread.State: RUNNABLE
at sun.security.provider.DigestBase.implCompressMultiBlock(DigestBase.java:140)
at sun.security.provider.DigestBase.engineUpdate(DigestBase.java:128)
at java.security.MessageDigest$Delegate.engineUpdate(MessageDigest.java:584)
at java.security.MessageDigest.update(MessageDigest.java:325)
at sun.security.util.ManifestDigester.manifestDigest(ManifestDigester.java:293)
at sun.security.util.SignatureFileVerifier.verifyManifestHash(SignatureFileVerifier.java:465)
at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:326)
at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:263)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:318)
at java.util.jar.JarVerifier.update(JarVerifier.java:230)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:384)
at java.util.jar.JarFile.getInputStream(JarFile.java:451)
- locked <0x214e> (a java.util.jar.JarFile)
at org.jboss.modules.JarEntryResource.openStream(JarEntryResource.java:53)
at org.jboss.modules.VersionDetection.detectVersion(VersionDetection.java:43)
at org.jboss.modules.xml.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:1125)
at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:932)
at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:697)
at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:469)
at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:335)
at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:293)
at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:254)
at org.jboss.modules.LocalModuleFinder.parseModuleXmlFile(LocalModuleFinder.java:250)
at org.jboss.modules.LocalModuleFinder.lambda$findModule$1(LocalModuleFinder.java:195)
at org.jboss.modules.LocalModuleFinder$$Lambda$2.853993923.run(Unknown Source:-1)
at java.security.AccessController.doPrivileged(AccessController.java:-1)
at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:195)
at org.jboss.modules.ModuleLoader.findModule0(ModuleLoader.java:696)
at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:689)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:499)
at org.jboss.modules.DelegatingModuleLoader.preloadModule(DelegatingModuleLoader.java:57)
at org.jboss.modules.Module.addPaths(Module.java:1252)
at org.jboss.modules.Module.link(Module.java:1622)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:299)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:283)
at org.jboss.as.webservices.util.ModuleClassLoaderProvider.getServerIntegrationClassLoader(ModuleClassLoaderProvider.java:51)
at org.jboss.as.webservices.dmr.WSDeploymentActivator.isModularEnvironment(WSDeploymentActivator.java:97)
at org.jboss.as.webservices.dmr.WSDeploymentActivator.activate(WSDeploymentActivator.java:59)
at org.jboss.as.webservices.dmr.WSSubsystemAdd$1.execute(WSSubsystemAdd.java:81)
at org.jboss.as.server.AbstractDeploymentChainStep.execute(AbstractDeploymentChainStep.java:58)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
{quote}
> Resolve missing dependency jboss.naming.context.java.jboss.DefaultJMSConnectionFactory
> --------------------------------------------------------------------------------------
>
> Key: WFLY-13875
> URL: https://issues.redhat.com/browse/WFLY-13875
> Project: WildFly
> Issue Type: Sub-task
> Components: JMS
> Reporter: Scott Marlow
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Labels: EE9
>
> server.log output from running Jakarta EE 9 Platform TCK JACC tests against Brian's WildFly ee-9 branch:
> {code}
> 020-09-15 15:48:46,120 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "greenmail-jboss-service.sar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.\"greenmail-jboss-service.sar\".\"greenmail-jboss-service.sar\".DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> ...
> 2020-09-15 15:49:21,610 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jacc_util.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.jacc_util.jacc_util_web.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> ...
> 2020-09-15 15:49:27,418 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jacc_ejb_methodperm.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.naming.context.java.module.jacc_ejb_methodperm.jacc_ejb_methodperm_ejb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
> "jboss.naming.context.java.module.jacc_ejb_methodperm.jacc_ejb_methodperm_client.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
> "jboss.naming.context.java.comp.jacc_ejb_methodperm.jacc_ejb_methodperm_ejb.jacc_ejb_methodperm_MethodPermBean.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"
> ]
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[Red Hat JIRA] (WFLY-13967) Provide an simple overview of what a layer is at the start of the layers table
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-13967:
---------------------------------------
Summary: Provide an simple overview of what a layer is at the start of the layers table
Key: WFLY-13967
URL: https://issues.redhat.com/browse/WFLY-13967
Project: WildFly
Issue Type: Enhancement
Components: Documentation
Reporter: Brian Stansberry
Assignee: Jean Francois Denise
Fix For: 22.0.0.Beta1
At the start of https://docs.wildfly.org/21/Bootable_Guide.html#wildfly_layers a couple sentences stating what a layer is would be good. Assume that someone has followed a link to that section and is coming too it without much context. (I'm thinking about adding such a link to the WF 21 release announcement blog post, which is what inspired me to file this.)
That's shared content with other guides, so my intent is those couple sentences would be in the other guides too.
This is a bit tricky as it should be brief, clear and accurate. Doesn't need to be complete though; i.e. the idea is to give basic context, not a detail explanation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months