[JBoss JIRA] (WFLY-12778) EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-12778?page=com.atlassian.jira.plugi... ]
Parul Sharma updated WFLY-12778:
--------------------------------
Comment: was deleted
(was: Thanks [~spyrkob], If you don't mind can I look into this issue?)
> EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12778
> URL: https://issues.redhat.com/browse/WFLY-12778
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Bartosz Spyrko-Smietanko
> Assignee: Bartosz Spyrko-Smietanko
> Priority: Major
>
> When an EAR containing MDBS is deployed in one of the colocated master/slave servers, the application does not wait for the embedded broker to start up and generates these errors in the logs:
> {code:java}
> /14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.ra.activemq-ra",
> "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"
> ],
> {code}
> When the broker is eventually started, these MDBs get deployed and start working fine without any redeployment but these errors are not desirable in the logs.
> Defining the resource-ref in ejb-jar.xml or annotating with @Resource does not help either.
> The application should wait for its dependencies to be available.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13621) GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT
by Loukas Kopanias (Jira)
Loukas Kopanias created WFLY-13621:
--------------------------------------
Summary: GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT
Key: WFLY-13621
URL: https://issues.redhat.com/browse/WFLY-13621
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Loukas Kopanias
This is a task of Loukas Kopanias for the 1st Phase of GSoC 2020.
All testcases and configuration files in EAT updated to run successfully on the latest released version of Wildfly (currently 20.0.0.Final).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13620) jaxrs-jwt: The parameters 'mainClass' are missing or invalid
by Wolfgang Mayer (Jira)
Wolfgang Mayer created WFLY-13620:
-------------------------------------
Summary: jaxrs-jwt: The parameters 'mainClass' are missing or invalid
Key: WFLY-13620
URL: https://issues.redhat.com/browse/WFLY-13620
Project: WildFly
Issue Type: Bug
Components: Quickstarts
Affects Versions: 20.0.0.Final
Reporter: Wolfgang Mayer
Assignee: Eduardo Martins
mvn exec:java fails
[INFO] Reactor Summary for Quickstart: jaxrs-jwt 20.0.0.Final:
[INFO]
[INFO] Quickstart: jaxrs-jwt .............................. FAILURE [ 0.361 s]
[INFO] Quickstart: jaxrs-jwt - client ..................... SKIPPED
[INFO] Quickstart: jaxrs-jwt - service .................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.056 s
[INFO] Finished at: 2020-06-27T13:39:17+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java (default-cli) on project jaxrs-jwt: The parameters 'mainClass' for goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java are missing or invalid -> [Help 1]
[ERROR]
mvn -v
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 14.0.1, vendor: Private Build, runtime: /usr/lib/jvm/java-14-openjdk-amd64
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-39-generic", arch: "amd64", family: "unix"
Executing the clent directly via:
$JAVA_HOME/bin/java -classpath $CLASSPATH org.jboss.quickstarts.jaxrsjwt.client.JwtRestClient
Euns successfully indeed. So this seems to be an issue with the pom.xml
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13603) Cache associated with default module throws NPE on start
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13603?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13603:
------------------------------------
Fix Version/s: 20.0.1.Final
> Cache associated with default module throws NPE on start
> --------------------------------------------------------
>
> Key: WFLY-13603
> URL: https://issues.redhat.com/browse/WFLY-13603
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
> Fix For: 21.0.0.Beta1, 20.0.1.Final
>
>
> {noformat}
> 2020-06-11 13:57:16,198 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 90) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache.security.MyApplicationRealm: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache.security.MyApplicationRealm: org.infinispan.commons.CacheConfigurationException: Failed to construct component org.infinispan.container.impl.InternalDataContainer, path org.infinispan.container.impl.InternalDataContainer
> << org.infinispan.stats.impl.StatsCollector
> << org.infinispan.AdvancedCache
> at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:66)
> at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: org.infinispan.commons.CacheConfigurationException: Failed to construct component org.infinispan.container.impl.InternalDataContainer, path org.infinispan.container.impl.InternalDataContainer
> << org.infinispan.stats.impl.StatsCollector
> << org.infinispan.AdvancedCache
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.doInstantiateWrapper(BasicComponentRegistryImpl.java:189)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.instantiateWrapper(BasicComponentRegistryImpl.java:176)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.getComponent0(BasicComponentRegistryImpl.java:141)
> at org.infinispan.factories.impl.WireContext.get(WireContext.java:20)
> at org.infinispan.stats.impl.CorePackageImpl$2.wire(CorePackageImpl.java:43)
> at org.infinispan.stats.impl.CorePackageImpl$2.wire(CorePackageImpl.java:39)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.doWireWrapper(BasicComponentRegistryImpl.java:231)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireWrapper(BasicComponentRegistryImpl.java:212)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.getComponent0(BasicComponentRegistryImpl.java:147)
> at org.infinispan.factories.impl.WireContext.get(WireContext.java:20)
> at org.infinispan.cache.impl.CorePackageImpl$3.wire(CorePackageImpl.java:75)
> at org.infinispan.cache.impl.CorePackageImpl$3.wire(CorePackageImpl.java:73)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireDependencies(BasicComponentRegistryImpl.java:242)
> at org.infinispan.cache.impl.EncoderCache.wireRealCache(EncoderCache.java:125)
> at org.infinispan.cache.impl.CorePackageImpl$4.wire(CorePackageImpl.java:94)
> at org.infinispan.cache.impl.CorePackageImpl$4.wire(CorePackageImpl.java:90)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.doWireWrapper(BasicComponentRegistryImpl.java:231)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireWrapper(BasicComponentRegistryImpl.java:212)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.registerComponent(BasicComponentRegistryImpl.java:371)
> at org.infinispan.factories.impl.BasicComponentRegistry.registerComponent(BasicComponentRegistry.java:100)
> at org.infinispan.factories.InternalCacheFactory.createSimpleCache(InternalCacheFactory.java:151)
> at org.infinispan.factories.InternalCacheFactory.createCache(InternalCacheFactory.java:81)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:696)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:645)
> at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:530)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:511)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:504)
> at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:92)
> at org.wildfly.clustering.infinispan.spi.service.CacheServiceConfigurator.get(CacheServiceConfigurator.java:77)
> at org.wildfly.clustering.infinispan.spi.service.CacheServiceConfigurator.get(CacheServiceConfigurator.java:55)
> at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:63)
> ... 7 more
> Caused by: java.lang.NullPointerException
> at org.wildfly.clustering.infinispan.spi.DataContainerFactory.createBoundedDataContainer(DataContainerFactory.java:113)
> at org.wildfly.clustering.infinispan.spi.DataContainerFactory.construct(DataContainerFactory.java:72)
> at org.infinispan.factories.impl.BasicComponentRegistryImpl.doInstantiateWrapper(BasicComponentRegistryImpl.java:186)
> ... 40 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13613) SIGSEGV in libaio when running RHEL 7.8
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13613?page=com.atlassian.jira.plugi... ]
Brian Stansberry resolved WFLY-13613.
-------------------------------------
Fix Version/s: 21.0.0.Beta1
Resolution: Done
[~ehugonnet] I'm resolving under the assumption the artemis native upgrade fixes this
> SIGSEGV in libaio when running RHEL 7.8
> ---------------------------------------
>
> Key: WFLY-13613
> URL: https://issues.redhat.com/browse/WFLY-13613
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Bartosz Spyrko-Smietanko
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> AMQ 7 sporadically crashes with a SIGSEGV in the libaio native library in method SubmitInfo:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f3e985c6855, pid=113988, tid=0x00007f3e30aa8700
> #
> # JRE version: OpenJDK Runtime Environment (8.0_252-b09) (build 1.8.0_252-b09)
> # Java VM: OpenJDK 64-Bit Server VM (25.252-b09 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # j org.apache.activemq.artemis.nativo.jlibaio.LibaioContext.done(Lorg/apache/activemq/artemis/nativo/jlibaio/SubmitInfo;)V+1
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> #
> {code}
> This appears to be related to the JVM version and / or virtualization environments.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months