[Red Hat JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka edited comment on WFLY-13031 at 12/20/20 3:38 PM:
------------------------------------------------------------------
[~parsharma] I have to reopen this issue - one of the mentioned errors pop up again after import into CRS.
h2. Error msg:
Referenced file contains errors (jar:file:/Applications/codereadystudio-CF-ppp/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.9.104.v20201029-1407.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /messaging-clustering-singleton/src/main/webapp/WEB-INF
h2. CRS version:
Version: 12.18.0.AM1
Build id: AM1-v20201217-1630-B7316
Build date: 20201217-1630
!error.png|thumbnail!
was (Author: zcervink):
[~parsharma] I have to reopen this issue - one of the mentioned errors pop up again after import into CRS.
h2. Error msg:
Referenced file contains errors (jar:file:/Applications/codereadystudio-CF-ppp/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.9.104.v20201029-1407.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /messaging-clustering-singleton/src/main/webapp/WEB-INF
h2. CRS version:
Version: 12.18.0.AM1
Build id: AM1-v20201217-1630-B7316
Build date: 20201217-1630
> EAP quickstart 'messaging-clustering-singleton' shows errors after import
> -------------------------------------------------------------------------
>
> Key: WFLY-13031
> URL: https://issues.redhat.com/browse/WFLY-13031
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 18.0.1.Final
> Reporter: Zbyněk Červinka
> Assignee: Parul Sharma
> Priority: Major
> Fix For: 19.0.0.Beta2, 19.0.0.Final
>
> Attachments: Problems view.png, Project Explorer.png, error.png, jboss-ejb3.xml file.png
>
>
> h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import:
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[Red Hat JIRA] (WFLY-13031) EAP quickstart 'messaging-clustering-singleton' shows errors after import
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/WFLY-13031?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka reopened WFLY-13031:
------------------------------------
[~parsharma] I have to reopen this issue - one of the mentioned errors pop up again after import into CRS.
h2. Error msg:
Referenced file contains errors (jar:file:/Applications/codereadystudio-CF-ppp/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.9.104.v20201029-1407.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /messaging-clustering-singleton/src/main/webapp/WEB-INF
h2. CRS version:
Version: 12.18.0.AM1
Build id: AM1-v20201217-1630-B7316
Build date: 20201217-1630
> EAP quickstart 'messaging-clustering-singleton' shows errors after import
> -------------------------------------------------------------------------
>
> Key: WFLY-13031
> URL: https://issues.redhat.com/browse/WFLY-13031
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 18.0.1.Final
> Reporter: Zbyněk Červinka
> Assignee: Parul Sharma
> Priority: Major
> Fix For: 19.0.0.Beta2, 19.0.0.Final
>
> Attachments: Problems view.png, Project Explorer.png, jboss-ejb3.xml file.png
>
>
> h1. EAP quickstart 'messaging-clustering-singleton' shows 3 errors in the jboss-ejb3.xml file after import:
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb-delivery-active_1_1.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[Red Hat JIRA] (WFLY-14219) Utilize JBoss Modules version 1.9 in module descriptors
by Boris Unckel (Jira)
[ https://issues.redhat.com/browse/WFLY-14219?page=com.atlassian.jira.plugi... ]
Boris Unckel updated WFLY-14219:
--------------------------------
Attachment: 2020-12-16_wfjdep2_22.0.0.Beta1-SNAPSHOT.7z
> Utilize JBoss Modules version 1.9 in module descriptors
> -------------------------------------------------------
>
> Key: WFLY-14219
> URL: https://issues.redhat.com/browse/WFLY-14219
> Project: WildFly
> Issue Type: Task
> Components: Server
> Affects Versions: 22.0.0.Alpha1
> Reporter: Boris Unckel
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: 2020-12-13_wildfly-22.0.0.Beta1-SNAPSHOT_modules_15_16_17.txt, 2020-12-16_wfjdep2_22.0.0.Beta1-SNAPSHOT.7z, 2020-12-16_wfjdep_22.0.0.Beta1-SNAPSHOT.7z
>
>
> There are still modules which use 1.5, 1.6 or 1.7 and do not need that. The idea is to run jdeps on each artifact of a modul, add the relevant java.* and jdk.* modules to the dependencies of the module and upgrade to version 1.8. In a first change only none-jdk modules and none which depend on system dependency.
> List in 2020-12-13_wildfly-22.0.0.Beta1-SNAPSHOT_modules_15_16_17.txt
> Changes in a first set of modules in WildFly-Core [WFCORE-5229|https://issues.redhat.com/browse/WFCORE-5229] integration tests were successful.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[Red Hat JIRA] (WFLY-14244) Error in ee-9/feature-pack if a localRepository is defined in the maven settings.xml
by Richard Opalka (Jira)
[ https://issues.redhat.com/browse/WFLY-14244?page=com.atlassian.jira.plugi... ]
Richard Opalka commented on WFLY-14244:
---------------------------------------
Your analysis is correct [~rhn-support-rmartinc] it is bug in JBoss Modules maven integration - see https://issues.redhat.com/browse/MODULES-405
> Error in ee-9/feature-pack if a localRepository is defined in the maven settings.xml
> ------------------------------------------------------------------------------------
>
> Key: WFLY-14244
> URL: https://issues.redhat.com/browse/WFLY-14244
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Ricardo Martin Camarero
> Priority: Major
>
> If you have defined a local repository in your maven {{settings.xml}} like the following:
> {code:xml}
> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
> <localRepository>/path/to/repository</localRepository>
> ...
> </settings>
> {code}
> The folder {{ee-9/feature-path}} fails with the following error:
> {noformat}
> ...
> [INFO] --------------< org.wildfly:wildfly-preview-feature-pack >--------------
> [INFO] Building WildFly: EE 9 Preview Galleon Feature Pack 22.0.0.Final-SNAPSHOT [146/162]
> [INFO] --------------------------------[ pom ]---------------------------------
> ...
> [INFO] --- wildfly-galleon-maven-plugin:5.0.0.Final:build-feature-pack (feature-pack-build) @ wildfly-preview-feature-pack ---
> [INFO] EE9: transformed infinispan-hibernate-cache-v53-11.0.8.Final.jar
> ...
> [INFO] EE9: transformed jakarta.json-api-1.1.6.jar
> [INFO] EE9: transformed jakarta.json-1.1.6.jar
> Forked embedded process has failed with the following error:
> java.lang.IllegalStateException: WFLYEMB0022: Cannot invoke 'start' on embedded process
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:119)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
> at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
> org.wildfly.core.embedded.EmbeddedProcessStartException: WFLYEMB0021: Cannot start embedded process
> at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:324)
> 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.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
> at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
> java.util.concurrent.ExecutionException: JBTHR00005: Operation failed
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:253)
> at org.wildfly.core.embedded.EmbeddedStandaloneServerFactory$StandaloneServerImpl.start(EmbeddedStandaloneServerFactory.java:305)
> 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.wildfly.core.embedded.EmbeddedManagedProcessImpl.invokeOnServer(EmbeddedManagedProcessImpl.java:107)
> at org.wildfly.core.embedded.EmbeddedManagedProcessImpl.start(EmbeddedManagedProcessImpl.java:64)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.readFeatureSpecs(FeatureSpecGenerator.java:304)
> at org.wildfly.galleon.plugin.featurespec.generator.FeatureSpecGenerator.forkedForEmbedded(FeatureSpecGenerator.java:232)
> at org.wildfly.galleon.plugin.server.ForkedEmbeddedUtil.main(ForkedEmbeddedUtil.java:208)
> java.lang.Exception: WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> at org.jboss.as.server.BootstrapListener.bootFailure(BootstrapListener.java:87)
> at org.jboss.as.server.ServerService.boot(ServerService.java:426)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> If you use the -X option the initial exception is the following:
> {noformat}
> ERROR: WFLYSRV0055: Caught exception during boot
> org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
> at org.jboss.as.server.ServerService.boot(ServerService.java:395)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.jboss.as.mail
> at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:100)
> at org.jboss.as.server.parsing.StandaloneXml_6.readServerElement(StandaloneXml_6.java:221)
> at org.jboss.as.server.parsing.StandaloneXml_6.readElement(StandaloneXml_6.java:121)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:114)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:52)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
> ... 3 more
> Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/mail/Session
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:192)
> at org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:92)
> ... 10 more
> Caused by: java.lang.NoClassDefFoundError: javax/mail/Session
> at org.jboss.as.mail.extension.MailSessionDefinition.<clinit>(MailSessionDefinition.java:49)
> at org.jboss.as.mail.extension.MailSubsystemParser4_0.getParserDescription(MailSubsystemParser4_0.java:39)
> at org.jboss.as.controller.PersistentResourceXMLParser.cacheXMLDescription(PersistentResourceXMLParser.java:45)
> at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.preCacheParserDescription(ExtensionRegistry.java:522)
> at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.attemptCurrentParserInitialization(ExtensionRegistry.java:508)
> at org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl.access$200(ExtensionRegistry.java:434)
> at org.jboss.as.controller.extension.ExtensionRegistry.initializeParsers(ExtensionRegistry.java:249)
> at org.jboss.as.controller.parsing.DeferredExtensionContext.loadModule(DeferredExtensionContext.java:116)
> at org.jboss.as.controller.parsing.DeferredExtensionContext.access$000(DeferredExtensionContext.java:44)
> at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:74)
> at org.jboss.as.controller.parsing.DeferredExtensionContext$1.call(DeferredExtensionContext.java:71)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
> Caused by: java.lang.ClassNotFoundException: javax.mail.Session from [Module "org.jboss.as.mail" version 22.0.0.Final-SNAPSHOT from local module loader @3cb1ffe6 (finder: local module finder @3dfc5fb8 (roots: /home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules,/home/rmartinc/wildfly/ee-9/feature-pack/target/wildfly/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> ... 18 more
> {noformat}
> The feature spec generator fails because the server prefers the local repository in your settings than the one in the system property (jboss-modules does it). The artifact was located from the local repo in the settings, and it was not the ee9 jar. The ee9 folder is forced by the galleon plugin using a system prop but it was not used because of my {{settings.xml}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[Red Hat JIRA] (AG-153) Application blocked getting Connection from shared handler cache.
by Jeremy Whiting (Jira)
[ https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy... ]
Jeremy Whiting closed AG-153.
-----------------------------
Resolution: Done
This issue turned out to be caused by a mis-configured application.
> Application blocked getting Connection from shared handler cache.
> -----------------------------------------------------------------
>
> Key: AG-153
> URL: https://issues.redhat.com/browse/AG-153
> Project: Agroal
> Issue Type: Bug
> Components: pool
> Affects Versions: 1.8
> Reporter: Jeremy Whiting
> Assignee: Luis Barreiro
> Priority: Major
> Attachments: jstack-tree.txt, summary-of-getConnection-method-calls.txt
>
>
> I am inspecting an application that stopped nearly all processing.
> A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file.
> -There are no other threads that already have a connection leased out.-
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[Red Hat JIRA] (DROOLS-5908) NPE in IntervalTrigger when timestamp + delay > endTime
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5908?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5908:
--------------------------------
Sprint: 2020 Week 52-03 (from Dec 21) (was: 2020 Week 49-51 (from Nov 30))
> NPE in IntervalTrigger when timestamp + delay > endTime
> -------------------------------------------------------
>
> Key: DROOLS-5908
> URL: https://issues.redhat.com/browse/DROOLS-5908
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.47.0.Final
> Reporter: Thomas Huriaux
> Assignee: Mario Fusco
> Priority: Minor
>
> If using timer(expr: $d, $p; end=$e) with $e > now + $d
> We have the following stack trace:
> {code:java}
> Exception in thread "Thread-1" java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "this.nextFireTime" is null at org.drools.core.time.impl.IntervalTrigger.getTimeAfter(IntervalTrigger.java:224)
> {code}
> It should probably just not fire anything in that situation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months