[JBoss JIRA] (JGRP-2307) Jgroup crashes when slf4j is used
by Daan Wendelen (Jira)
[ https://issues.jboss.org/browse/JGRP-2307?page=com.atlassian.jira.plugin.... ]
Daan Wendelen updated JGRP-2307:
--------------------------------
Attachment: jgroups-bug.zip
> Jgroup crashes when slf4j is used
> ---------------------------------
>
> Key: JGRP-2307
> URL: https://issues.jboss.org/browse/JGRP-2307
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.6, 4.0.15
> Environment: - I only tested 4.0.6 and 4.0.15 but I suspect all 4.0.x version are affected
> - Only happens in docker (our image is based on "java:8")
> Reporter: Daan Wendelen
> Assignee: Bela Ban
> Priority: Major
> Attachments: jgroups-bug.zip
>
>
> When running our application, it crashes with the following stacktrace.
> {code}
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> 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.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
> at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
> Caused by: java.lang.ExceptionInInitializerError
> at Bug.main(Bug.java:5)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at java.util.Locale.<init>(Locale.java:648)
> at java.util.Locale.<init>(Locale.java:677)
> at org.jgroups.logging.Slf4jLogImpl.<clinit>(Slf4jLogImpl.java:20)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (JGRP-2307) Jgroup crashes when slf4j is used
by Daan Wendelen (Jira)
[ https://issues.jboss.org/browse/JGRP-2307?page=com.atlassian.jira.plugin.... ]
Daan Wendelen updated JGRP-2307:
--------------------------------
Steps to Reproduce:
This requires a system with docker
- Download and unpack the the following zip [^jgroups-bug.zip]
- Go to jgroups-bug
- To build the docker image run "./gradlew buildDocker" (or something similar on windows)
- Then run the docker image "docker run jgroups-bug-reported-by-daan:latest"
was:
This requires a system with docker
- Download and unpack the the following zip (hmmm, I can't attach the zip)
- Go to jgroups-bug
- To build the docker image run "./gradlew buildDocker" (or something similar on windows)
- Then run the docker image "docker run jgroups-bug-reported-by-daan:latest"
> Jgroup crashes when slf4j is used
> ---------------------------------
>
> Key: JGRP-2307
> URL: https://issues.jboss.org/browse/JGRP-2307
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.6, 4.0.15
> Environment: - I only tested 4.0.6 and 4.0.15 but I suspect all 4.0.x version are affected
> - Only happens in docker (our image is based on "java:8")
> Reporter: Daan Wendelen
> Assignee: Bela Ban
> Priority: Major
> Attachments: jgroups-bug.zip
>
>
> When running our application, it crashes with the following stacktrace.
> {code}
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> 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.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
> at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
> Caused by: java.lang.ExceptionInInitializerError
> at Bug.main(Bug.java:5)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at java.util.Locale.<init>(Locale.java:648)
> at java.util.Locale.<init>(Locale.java:677)
> at org.jgroups.logging.Slf4jLogImpl.<clinit>(Slf4jLogImpl.java:20)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (JGRP-2307) Jgroup crashes when slf4j is used
by Daan Wendelen (Jira)
Daan Wendelen created JGRP-2307:
-----------------------------------
Summary: Jgroup crashes when slf4j is used
Key: JGRP-2307
URL: https://issues.jboss.org/browse/JGRP-2307
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.15, 4.0.6
Environment: - I only tested 4.0.6 and 4.0.15 but I suspect all 4.0.x version are affected
- Only happens in docker (our image is based on "java:8")
Reporter: Daan Wendelen
Assignee: Bela Ban
When running our application, it crashes with the following stacktrace.
{code}
Exception in thread "main" java.lang.reflect.InvocationTargetException
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.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
Caused by: java.lang.ExceptionInInitializerError
at Bug.main(Bug.java:5)
... 8 more
Caused by: java.lang.NullPointerException
at java.util.Locale.<init>(Locale.java:648)
at java.util.Locale.<init>(Locale.java:677)
at org.jgroups.logging.Slf4jLogImpl.<clinit>(Slf4jLogImpl.java:20)
... 9 more
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11026) Journal compacting doesn't work with JDK 11
by Francesco Nigro (Jira)
[ https://issues.jboss.org/browse/WFLY-11026?page=com.atlassian.jira.plugin... ]
Francesco Nigro commented on WFLY-11026:
----------------------------------------
[~iweiss] Good idea!!
FYI Seems that my new patch on journal compaction (that will address another issue re native memory utilisation) is already on master (y)
> Journal compacting doesn't work with JDK 11
> -------------------------------------------
>
> Key: WFLY-11026
> URL: https://issues.jboss.org/browse/WFLY-11026
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Environment: {noformat}
> java 11-ea 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11-ea+21)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {noformat}
> Reporter: Martin Styk
> Assignee: Ingo Weiss
> Priority: Critical
> Labels: Java11, jdk10, jdk11
>
> Journal compacting doesn't work with Artemis 1.5 and JDK 11
> It fails with following stack trace:
> {noformat}
> 12:34:58,017 ERROR [org.apache.activemq.artemis.journal] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$4@5483fda8)) AMQ144003: Error compacting: java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at io.netty@4.1.25.Final//io.netty.util.internal.CleanerJava9.freeDirectBuffer(CleanerJava9.java:77)
> at io.netty@4.1.25.Final//io.netty.util.internal.PlatformDependent.freeDirectBuffer(PlatformDependent.java:388)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFileFactory.releaseBuffer(NIOSequentialFileFactory.java:175)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.doInternalWrite(NIOSequentialFile.java:312)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.internalWrite(NIOSequentialFile.java:282)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.writeDirect(NIOSequentialFile.java:255)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.AbstractJournalUpdateTask.flush(AbstractJournalUpdateTask.java:217)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.compact(JournalImpl.java:1520)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl$14.run(JournalImpl.java:2060)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalArgumentException: duplicate or slice
> at jdk.unsupported/sun.misc.Unsafe.invokeCleaner(Unsafe.java:1238)
> {noformat}
> This causes issues also in scenario with journal replication.
> {noformat}
> 13:09:32,133 WARN [org.apache.activemq.artemis.core.server] (Thread-173) AMQ222013: Error when trying to start replication: java.lang.RuntimeException: Error during compact, look at the logs
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.scheduleCompactAndBlock(JournalImpl.java:1428)
> at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.startReplication(JournalStorageManager.java:540)
> at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation$2.run(SharedNothingLiveActivation.java:166)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11226) Maven Wildfly plugin should be working with Java 9+
by Michal Jurc (Jira)
[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ]
Michal Jurc updated WFLY-11226:
-------------------------------
Affects Version/s: 14.0.1.Final
> Maven Wildfly plugin should be working with Java 9+
> ---------------------------------------------------
>
> Key: WFLY-11226
> URL: https://issues.jboss.org/browse/WFLY-11226
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 14.0.1.Final
> Reporter: Michal Jurc
> Assignee: James Perkins
> Priority: Blocker
> Labels: java11
>
> Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin:
> {code}21:35:19 [INFO] STANDALONE server is starting up.
> 21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
> 21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
> 21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
> 21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> 21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> 21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
> This is pretty cumbersome and a blocker to migrating application without change of configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11227) Maven Wildfly plugin should be working with Java 9+
by Michal Jurc (Jira)
Michal Jurc created WFLY-11227:
----------------------------------
Summary: Maven Wildfly plugin should be working with Java 9+
Key: WFLY-11227
URL: https://issues.jboss.org/browse/WFLY-11227
Project: WildFly
Issue Type: Bug
Affects Versions: 14.0.1.Final
Reporter: Michal Jurc
Assignee: James Perkins
Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin:
{code}21:35:19 [INFO] STANDALONE server is starting up.
21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
This is pretty cumbersome and a blocker to migrating application without change of configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11226) Maven Wildfly plugin should be working with Java 9+
by Michal Jurc (Jira)
[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ]
Michal Jurc updated WFLY-11226:
-------------------------------
Description:
Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin:
{code}21:35:19 [INFO] STANDALONE server is starting up.
21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
This is pretty cumbersome and a blocker to migrating application without change of configuration.
was:
Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin:
{code}21:35:19 [INFO] STANDALONE server is starting up.
21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
> Maven Wildfly plugin should be working with Java 9+
> ---------------------------------------------------
>
> Key: WFLY-11226
> URL: https://issues.jboss.org/browse/WFLY-11226
> Project: WildFly
> Issue Type: Bug
> Reporter: Michal Jurc
> Assignee: James Perkins
> Priority: Blocker
> Labels: java11
>
> Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin:
> {code}21:35:19 [INFO] STANDALONE server is starting up.
> 21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
> 21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
> 21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
> 21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> 21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> 21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
> This is pretty cumbersome and a blocker to migrating application without change of configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11226) Maven Wildfly plugin should be working with Java 9+
by Michal Jurc (Jira)
[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ]
Michal Jurc updated WFLY-11226:
-------------------------------
Description:
Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI from the plugin:
{code}21:35:19 [INFO] STANDALONE server is starting up.
21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
was:The plugin needs to be reviewed and ensured it works with Java 9+.
> Maven Wildfly plugin should be working with Java 9+
> ---------------------------------------------------
>
> Key: WFLY-11226
> URL: https://issues.jboss.org/browse/WFLY-11226
> Project: WildFly
> Issue Type: Bug
> Reporter: Michal Jurc
> Assignee: James Perkins
> Priority: Blocker
> Labels: java11
>
> Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI from the plugin:
> {code}21:35:19 [INFO] STANDALONE server is starting up.
> 21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
> 21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
> 21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
> 21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> 21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> 21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11226) Maven Wildfly plugin should be working with Java 9+
by Michal Jurc (Jira)
[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ]
Michal Jurc updated WFLY-11226:
-------------------------------
Description:
Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin:
{code}21:35:19 [INFO] STANDALONE server is starting up.
21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
was:
Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI from the plugin:
{code}21:35:19 [INFO] STANDALONE server is starting up.
21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
> Maven Wildfly plugin should be working with Java 9+
> ---------------------------------------------------
>
> Key: WFLY-11226
> URL: https://issues.jboss.org/browse/WFLY-11226
> Project: WildFly
> Issue Type: Bug
> Reporter: Michal Jurc
> Assignee: James Perkins
> Priority: Blocker
> Labels: java11
>
> Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin:
> {code}21:35:19 [INFO] STANDALONE server is starting up.
> 21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
> 21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
> 21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
> 21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> 21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> 21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months