[JBoss JIRA] (WFLY-3335) JAXB transformer initiation
by Ghet Ghetolay (JIRA)
[ https://issues.jboss.org/browse/WFLY-3335?page=com.atlassian.jira.plugin.... ]
Ghet Ghetolay commented on WFLY-3335:
-------------------------------------
Sorry this is a very old issue, the project mentioned has been discontinued and I can't find the minimal repro I made at that time.
I'm not a Java dev anymore at the moment so I don't think I even have a jvm on my computer to retest this.
Hopefully someone else can test it or we could just close the issue.
> JAXB transformer initiation
> ---------------------------
>
> Key: WFLY-3335
> URL: https://issues.jboss.org/browse/WFLY-3335
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 8.0.0.Final, 8.1.0.CR1
> Environment: Ubuntu 14.04 with java 7 openjdk
> Reporter: Ghet Ghetolay
> Assignee: David Lloyd
> Priority: Critical
>
> I'm not directly using JAXB and SaxTransformer, it's part of a the [dcm4chee-arc project|https://github.com/dcm4che/dcm4chee-arc] which I tried to use on Wildfly. It's a rather big and complicated project so I've create a test application to illustrate the bug. I've used a JAR-RS application to illustrate the bug (like the original case) but this should not be related to it.
> {code:title=TestRS.java}
> @Path("test")
> public class TestRS {
>
> private static SAXTransformerFactory factory =
> (SAXTransformerFactory) TransformerFactory.newInstance();
>
> @GET
> public Response test(){
> try {
> Templates template = factory.newTemplates(new StreamSource(
> TestRS.class.getResource("json_compact.xsl").toString()));
>
> factory.newTransformerHandler(template);
>
> } catch (TransformerConfigurationException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
>
> return Response.ok().build();
> }
> }
> {code}
> {code:title=json_compact.xsl}
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
> <xsl:output method="text"/>
> <xsl:template match="/">
> <xsl:text>Test</xsl:text>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> {quote}
> 15:24:48,564 ERROR [stderr] (default task-1) javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance.
> 15:24:48,564 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformerHandler(TransformerFactoryImpl.java:1062)
> 15:24:48,565 ERROR [stderr] (default task-1) at __redirected.__TransformerFactory.newTransformerHandler(__TransformerFactory.java:193)
> 15:24:48,566 ERROR [stderr] (default task-1) at test.TestRS.test(TestRS.java:25)
> {quote}
> I've discovered that the initial exception is :
> {quote}
> java.lang.NoClassDefFoundError: com/sun/org/apache/xalan/internal/xsltc/runtime/AbstractTranslet
> {quote}
> Both my test case and dcm4che-arc project works fine on JBoss 7.1.1.Final.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9943) Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-9943?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFLY-9943:
---------------------------------
Description:
Sometimes happens that WF12 process does not exit when :shutdown CLI operation called and hangs indefinitely. This happens only RHEL 6 (32/64 bit) with IBM SDK8.
Calling kill -3 does not create any javacore dump and only output could be gathered from pstack (attached). It indicates that JVM shutdown thread is hanging on:
{code}
Thread 25 (Thread 0xb7792b70 (LWP 25507)):
#0 0x00bd4424 in __kernel_vsyscall ()
#1 0x00b2243c in pthread_cond_wait@(a)GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0x004f8b1f in monitor_wait_original () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
#3 0x004f9957 in omrthread_monitor_wait () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
#4 0x0033e217 in protectedDestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
#5 0x0042cf6e in omrsig_protect () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9prt29.so
#6 0x0033db93 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
#7 0x00815999 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libjvm.so
#8 0x00528649 in JavaMain () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/bin/../lib/i386/jli/libjli.so
#9 0x00b1ebc9 in start_thread () from /lib/libpthread.so.0
#10 0x001fc04e in clone () from /lib/libc.so.6
{code}
There are other 24 threads which might be blocking this thread or a dead lock. This appears to be problem in IBM SDK 8 in combination RHEL 6 GLIBC_2.3.2 library.
was:
Sometimes happens that WF12 process does not exit when :shutdown CLI operation called and hangs indefinitely. This happens only RHEL 6 (32/64 bit) with IBM SDK8.
Calling kill -3 does not create any javacore dump and only output could be gathered from pstack (attached). It indicates that JVM shutdown thread is hanging on:
{code}
Thread 25 (Thread 0xb7792b70 (LWP 25507)):
#0 0x00bd4424 in __kernel_vsyscall ()
#1 0x00b2243c in pthread_cond_wait@(a)GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0x004f8b1f in monitor_wait_original () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
#3 0x004f9957 in omrthread_monitor_wait () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
#4 0x0033e217 in protectedDestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
#5 0x0042cf6e in omrsig_protect () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9prt29.so
#6 0x0033db93 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
#7 0x00815999 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libjvm.so
#8 0x00528649 in JavaMain () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/bin/../lib/i386/jli/libjli.so
#9 0x00b1ebc9 in start_thread () from /lib/libpthread.so.0
#10 0x001fc04e in clone () from /lib/libc.so.6
{code}
There are other 24 threads which be blocking it. This appears to be problem in IBM SDK 8 in combination RHEL 6 GLIBC_2.3.2 library.
> Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8
> ----------------------------------------------------------------------
>
> Key: WFLY-9943
> URL: https://issues.jboss.org/browse/WFLY-9943
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 12.0.0.Final
> Environment: RHEL 6 32/64 bit
> IBM SDK 8.0.5.10:
> {code}java version "1.8.0_161
> Java(TM) SE Runtime Environment (build 8.0.5.10 - pxi3280sr5fp10-20180214_01(SR5 FP10))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux x86-32 20180208_378436 (JIT enabled, AOT enabled)
> OpenJ9 - 39bb844
> OMR - c04ccb2
> IBM - 2321a81)
> JCL - 20180209_01 based on Oracle jdk8u161-b12
> {code}
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Attachments: pstack.txt
>
>
> Sometimes happens that WF12 process does not exit when :shutdown CLI operation called and hangs indefinitely. This happens only RHEL 6 (32/64 bit) with IBM SDK8.
> Calling kill -3 does not create any javacore dump and only output could be gathered from pstack (attached). It indicates that JVM shutdown thread is hanging on:
> {code}
> Thread 25 (Thread 0xb7792b70 (LWP 25507)):
> #0 0x00bd4424 in __kernel_vsyscall ()
> #1 0x00b2243c in pthread_cond_wait@(a)GLIBC_2.3.2 () from /lib/libpthread.so.0
> #2 0x004f8b1f in monitor_wait_original () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
> #3 0x004f9957 in omrthread_monitor_wait () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
> #4 0x0033e217 in protectedDestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
> #5 0x0042cf6e in omrsig_protect () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9prt29.so
> #6 0x0033db93 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
> #7 0x00815999 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libjvm.so
> #8 0x00528649 in JavaMain () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/bin/../lib/i386/jli/libjli.so
> #9 0x00b1ebc9 in start_thread () from /lib/libpthread.so.0
> #10 0x001fc04e in clone () from /lib/libc.so.6
> {code}
> There are other 24 threads which might be blocking this thread or a dead lock. This appears to be problem in IBM SDK 8 in combination RHEL 6 GLIBC_2.3.2 library.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9943) Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-9943?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFLY-9943:
---------------------------------
Attachment: pstack.txt
> Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8
> ----------------------------------------------------------------------
>
> Key: WFLY-9943
> URL: https://issues.jboss.org/browse/WFLY-9943
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 12.0.0.Final
> Environment: RHEL 6 32/64 bit
> IBM SDK 8.0.5.10:
> {code}java version "1.8.0_161
> Java(TM) SE Runtime Environment (build 8.0.5.10 - pxi3280sr5fp10-20180214_01(SR5 FP10))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux x86-32 20180208_378436 (JIT enabled, AOT enabled)
> OpenJ9 - 39bb844
> OMR - c04ccb2
> IBM - 2321a81)
> JCL - 20180209_01 based on Oracle jdk8u161-b12
> {code}
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Attachments: pstack.txt
>
>
> Sometimes happens that WF12 process does not exit when :shutdown CLI operation called and hangs indefinitely. This happens only RHEL 6 (32/64 bit) with IBM SDK8.
> Calling kill -3 does not create any javacore dump and only output could be gathered from pstack (attached). It indicates that JVM shutdown thread is hanging on:
> {code}
> Thread 25 (Thread 0xb7792b70 (LWP 25507)):
> #0 0x00bd4424 in __kernel_vsyscall ()
> #1 0x00b2243c in pthread_cond_wait@(a)GLIBC_2.3.2 () from /lib/libpthread.so.0
> #2 0x004f8b1f in monitor_wait_original () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
> #3 0x004f9957 in omrthread_monitor_wait () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
> #4 0x0033e217 in protectedDestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
> #5 0x0042cf6e in omrsig_protect () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9prt29.so
> #6 0x0033db93 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
> #7 0x00815999 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libjvm.so
> #8 0x00528649 in JavaMain () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/bin/../lib/i386/jli/libjli.so
> #9 0x00b1ebc9 in start_thread () from /lib/libpthread.so.0
> #10 0x001fc04e in clone () from /lib/libc.so.6
> {code}
> There are other 24 threads which be blocking it. This appears to be problem in IBM SDK 8 in combination RHEL 6 GLIBC_2.3.2 library.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9943) Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-9943?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFLY-9943:
---------------------------------
Steps to Reproduce:
*Hard to reproduce -- in less than 1% of cases in our testing environment*
*Steps to reproduce: (RHEL 6, IBM SDK 8)*
Call :shutdown CLI operation on WF12 (started with default standalone-full.xml).
Server logs that it stopped:
{code}2018-03-02 04:17:36,879 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: JBoss EAP 7.2.0.EL12-Beta1 (WildFly Core 4.0.0.Beta1-redhat-1) stopped in 82ms{code}
but {{ps aux | grep java}} still shows that process is running:
{code}
[hudson@rhel6-x86-medium-6746 ~]$ ps aux | grep java
hudson 25506 0.2 5.6 703128 227560 ? Sl 04:17 0:09 /qa/tools/opt/ibm-java-80/bin/java -D[Standalone] -server -verbose:gc -Xloggc:/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/standalone/log/gc.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms512m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.default.multicast.address=227.0.130.48 -Djboss.messaging.cluster.password=myGreatPasswd -Djboss.messaging.group.address=227.0.130.48 -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Dorg.jboss.boot.log.file=/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/standalone/log/server.log -Dlogging.configuration=file:/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/standalone/configuration/logging.properties -jar /home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/jboss-modules.jar -mp /home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/modules org.jboss.as.standalone -Djboss.home.dir=/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2 -Djboss.server.base.dir=/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/standalone -Djboss.bind.address=172.16.130.48 -Djboss.bind.address.unsecure=172.16.130.48 -Djboss.bind.address.management=172.16.130.48 -Djboss.bind.address.private=172.16.130.48 -c standalone-full.xml
{code}
was:
*Hard to reproduce -- in 1% of cases in our testing environment*
*Steps to reproduce: (RHEL 6, IBM SDK 8)*
Call :shutdown CLI operation on WF12 (started with default standalone-full.xml).
Server logs that it stopped:
{code}2018-03-02 04:17:36,879 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: JBoss EAP 7.2.0.EL12-Beta1 (WildFly Core 4.0.0.Beta1-redhat-1) stopped in 82ms{code}
but {{ps aux | grep java}} still shows that process is running:
{code}
[hudson@rhel6-x86-medium-6746 ~]$ ps aux | grep java
hudson 25506 0.2 5.6 703128 227560 ? Sl 04:17 0:09 /qa/tools/opt/ibm-java-80/bin/java -D[Standalone] -server -verbose:gc -Xloggc:/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/standalone/log/gc.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms512m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.default.multicast.address=227.0.130.48 -Djboss.messaging.cluster.password=myGreatPasswd -Djboss.messaging.group.address=227.0.130.48 -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Dorg.jboss.boot.log.file=/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/standalone/log/server.log -Dlogging.configuration=file:/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/standalone/configuration/logging.properties -jar /home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/jboss-modules.jar -mp /home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/modules org.jboss.as.standalone -Djboss.home.dir=/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2 -Djboss.server.base.dir=/home/hudson/hudson_workspace/workspace/eap-7.x-acceptance-multinode-rhel-mnovak/4a508515/manu-eap-1.1.91/out/downloadEap1/workspace/jboss-eap-7.2/standalone -Djboss.bind.address=172.16.130.48 -Djboss.bind.address.unsecure=172.16.130.48 -Djboss.bind.address.management=172.16.130.48 -Djboss.bind.address.private=172.16.130.48 -c standalone-full.xml
{code}
> Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8
> ----------------------------------------------------------------------
>
> Key: WFLY-9943
> URL: https://issues.jboss.org/browse/WFLY-9943
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 12.0.0.Final
> Environment: RHEL 6 32/64 bit
> IBM SDK 8.0.5.10:
> {code}java version "1.8.0_161
> Java(TM) SE Runtime Environment (build 8.0.5.10 - pxi3280sr5fp10-20180214_01(SR5 FP10))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux x86-32 20180208_378436 (JIT enabled, AOT enabled)
> OpenJ9 - 39bb844
> OMR - c04ccb2
> IBM - 2321a81)
> JCL - 20180209_01 based on Oracle jdk8u161-b12
> {code}
> Reporter: Miroslav Novak
> Assignee: Jason Greene
>
> Sometimes happens that WF12 process does not exit when :shutdown CLI operation called and hangs indefinitely. This happens only RHEL 6 (32/64 bit) with IBM SDK8.
> Calling kill -3 does not create any javacore dump and only output could be gathered from pstack (attached). It indicates that JVM shutdown thread is hanging on:
> {code}
> Thread 25 (Thread 0xb7792b70 (LWP 25507)):
> #0 0x00bd4424 in __kernel_vsyscall ()
> #1 0x00b2243c in pthread_cond_wait@(a)GLIBC_2.3.2 () from /lib/libpthread.so.0
> #2 0x004f8b1f in monitor_wait_original () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
> #3 0x004f9957 in omrthread_monitor_wait () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
> #4 0x0033e217 in protectedDestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
> #5 0x0042cf6e in omrsig_protect () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9prt29.so
> #6 0x0033db93 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
> #7 0x00815999 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libjvm.so
> #8 0x00528649 in JavaMain () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/bin/../lib/i386/jli/libjli.so
> #9 0x00b1ebc9 in start_thread () from /lib/libpthread.so.0
> #10 0x001fc04e in clone () from /lib/libc.so.6
> {code}
> There are other 24 threads which be blocking it. This appears to be problem in IBM SDK 8 in combination RHEL 6 GLIBC_2.3.2 library.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9943) Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8
by Miroslav Novak (JIRA)
Miroslav Novak created WFLY-9943:
------------------------------------
Summary: Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8
Key: WFLY-9943
URL: https://issues.jboss.org/browse/WFLY-9943
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 12.0.0.Final
Environment: RHEL 6 32/64 bit
IBM SDK 8.0.5.10:
{code}java version "1.8.0_161
Java(TM) SE Runtime Environment (build 8.0.5.10 - pxi3280sr5fp10-20180214_01(SR5 FP10))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux x86-32 20180208_378436 (JIT enabled, AOT enabled)
OpenJ9 - 39bb844
OMR - c04ccb2
IBM - 2321a81)
JCL - 20180209_01 based on Oracle jdk8u161-b12
{code}
Reporter: Miroslav Novak
Assignee: Jason Greene
Sometimes happens that WF12 process does not exit when :shutdown CLI operation called and hangs indefinitely. This happens only RHEL 6 (32/64 bit) with IBM SDK8.
Calling kill -3 does not create any javacore dump and only output could be gathered from pstack (attached). It indicates that JVM shutdown thread is hanging on:
{code}
Thread 25 (Thread 0xb7792b70 (LWP 25507)):
#0 0x00bd4424 in __kernel_vsyscall ()
#1 0x00b2243c in pthread_cond_wait@(a)GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0x004f8b1f in monitor_wait_original () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
#3 0x004f9957 in omrthread_monitor_wait () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so
#4 0x0033e217 in protectedDestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
#5 0x0042cf6e in omrsig_protect () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9prt29.so
#6 0x0033db93 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so
#7 0x00815999 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libjvm.so
#8 0x00528649 in JavaMain () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/bin/../lib/i386/jli/libjli.so
#9 0x00b1ebc9 in start_thread () from /lib/libpthread.so.0
#10 0x001fc04e in clone () from /lib/libc.so.6
{code}
There are other 24 threads which be blocking it. This appears to be problem in IBM SDK 8 in combination RHEL 6 GLIBC_2.3.2 library.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9942) Remove hornetq-native and -journal dependencies
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-9942:
---------------------------------
Summary: Remove hornetq-native and -journal dependencies
Key: WFLY-9942
URL: https://issues.jboss.org/browse/WFLY-9942
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 12.0.0.Final
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
WildFly pom.xml and its feature-pack still have dependencies for hornetq-native and hornet-journal jars.
They are no longer used (since they were only required when HornetQ broker was integrated) and should be removed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9941) :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-9941?page=com.atlassian.jira.plugin.... ]
Miroslav Novak commented on WFLY-9941:
--------------------------------------
Attaching trace logs from client (manu-trace-log). Exception was thrown in time 2018-03-01 09:36:59,188.
> :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-9941
> URL: https://issues.jboss.org/browse/WFLY-9941
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Jean-Francois Denise
> Attachments: manu-trace.log
>
>
> There is intermittent failure on CLI client when CLI operation {{ :shutdown() }} is called. Sometimes happens that CancellationException is thrown:
> {code}
> 2018-03-01 09:36:59,188 ERROR pool-1-thread-1 org.jboss.manu.eap.services.server.EapModularServerBase - Can't stop server gracefully
> java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.execute(OnlineManagementClientImpl.java:180) ~[creaper-core-1.6.1.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:600) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:638) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapServerStandalone.executeStopOperation(EapServerStandalone.java:348) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.stop(EapModularServerBase.java:238) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.units.server.StopServer.execute(StopServer.java:57) [manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:33) [manu-core-impl-1.1.43.jar:na]
> at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:14) [manu-core-impl-1.1.43.jar:na]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_151]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
> Caused by: java.util.concurrent.CancellationException: Operation was cancelled
> at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final]
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final]
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> ... 13 common frames omitted
> {code}
> WF12 server shutdowns but it seems that it does not send response for {{:shutdown}} call to client before shutdwon and closes connection. This causes that AsyncFutureTask on client is cancelled.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9941) :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-9941?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFLY-9941:
---------------------------------
Attachment: manu-trace.log
> :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-9941
> URL: https://issues.jboss.org/browse/WFLY-9941
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Jean-Francois Denise
> Attachments: manu-trace.log
>
>
> There is intermittent failure on CLI client when CLI operation {{ :shutdown() }} is called. Sometimes happens that CancellationException is thrown:
> {code}
> 2018-03-01 09:36:59,188 ERROR pool-1-thread-1 org.jboss.manu.eap.services.server.EapModularServerBase - Can't stop server gracefully
> java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.execute(OnlineManagementClientImpl.java:180) ~[creaper-core-1.6.1.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:600) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:638) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapServerStandalone.executeStopOperation(EapServerStandalone.java:348) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.services.server.EapModularServerBase.stop(EapModularServerBase.java:238) ~[manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.eap.units.server.StopServer.execute(StopServer.java:57) [manu-eap-lib-1.1.54.jar:na]
> at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:33) [manu-core-impl-1.1.43.jar:na]
> at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:14) [manu-core-impl-1.1.43.jar:na]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_151]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
> Caused by: java.util.concurrent.CancellationException: Operation was cancelled
> at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final]
> at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final]
> at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
> ... 13 common frames omitted
> {code}
> WF12 server shutdowns but it seems that it does not send response for {{:shutdown}} call to client before shutdwon and closes connection. This causes that AsyncFutureTask on client is cancelled.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9941) :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled
by Miroslav Novak (JIRA)
Miroslav Novak created WFLY-9941:
------------------------------------
Summary: :shutdown cli operation throws java.util.concurrent.CancellationException: Operation was cancelled
Key: WFLY-9941
URL: https://issues.jboss.org/browse/WFLY-9941
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 12.0.0.Final
Reporter: Miroslav Novak
Assignee: Jean-Francois Denise
There is intermittent failure on CLI client when CLI operation {{ :shutdown() }} is called. Sometimes happens that CancellationException is thrown:
{code}
2018-03-01 09:36:59,188 ERROR pool-1-thread-1 org.jboss.manu.eap.services.server.EapModularServerBase - Can't stop server gracefully
java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.execute(OnlineManagementClientImpl.java:180) ~[creaper-core-1.6.1.jar:na]
at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:600) ~[manu-eap-lib-1.1.54.jar:na]
at org.jboss.manu.eap.services.server.EapModularServerBase.executeOnlineManagementOperation(EapModularServerBase.java:638) ~[manu-eap-lib-1.1.54.jar:na]
at org.jboss.manu.eap.services.server.EapServerStandalone.executeStopOperation(EapServerStandalone.java:348) ~[manu-eap-lib-1.1.54.jar:na]
at org.jboss.manu.eap.services.server.EapModularServerBase.stop(EapModularServerBase.java:238) ~[manu-eap-lib-1.1.54.jar:na]
at org.jboss.manu.eap.units.server.StopServer.execute(StopServer.java:57) [manu-eap-lib-1.1.54.jar:na]
at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:33) [manu-core-impl-1.1.43.jar:na]
at org.jboss.manu.core.execute.UnitExecuteTask.call(UnitExecuteTask.java:14) [manu-core-impl-1.1.43.jar:na]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
Caused by: java.util.concurrent.CancellationException: Operation was cancelled
at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final]
at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267) ~[jboss-threads-2.2.1.Final.jar:2.2.1.Final]
at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) ~[wildfly-controller-client-2.0.0.CR5.jar:2.0.0.CR5]
... 13 common frames omitted
{code}
WF12 server shutdowns but it seems that it does not send response for {{:shutdown}} call to client before shutdwon and closes connection. This causes that AsyncFutureTask on client is cancelled.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months