[jboss-jira] [JBoss JIRA] (WFLY-5374) Server start-up fails on IBM JDK 1.8 (64-bit) on RHEL 6/7 in full/full-ha profile
Dimitris Andreadis (JIRA)
issues at jboss.org
Tue Oct 6 13:10:00 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimitris Andreadis reassigned WFLY-5374:
----------------------------------------
Assignee: Clebert Suconic (was: Jeff Mesnil)
> Server start-up fails on IBM JDK 1.8 (64-bit) on RHEL 6/7 in full/full-ha profile
> ---------------------------------------------------------------------------------
>
> Key: WFLY-5374
> URL: https://issues.jboss.org/browse/WFLY-5374
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.CR1, 10.0.0.CR2
> Environment: IBM 1.8 - 64-bit:
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr1fp10-20150711_01(SR1 FP10))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150630_255633 (JIT enabled, AOT enabled)
> J9VM - R28_jvm.28_20150630_1742_B255633
> JIT - tr.r14.java_20150625_95081.01
> GC - R28_jvm.28_20150630_1742_B255633_CMPRSS
> J9CL - 20150630_255633)
> JCL - 20150711_01 based on Oracle jdk8u51-b15
> Reporter: Miroslav Novak
> Assignee: Clebert Suconic
> Priority: Blocker
> Attachments: javacore.20150921.051514.4815.0002.txt
>
>
> EAP 7.0.0.DR10/Wildfly 10 CR1 fails to start on IBM 1.8 (64) on RHEL 6/7. This is regression against previous version.
> Console log:
> {code}[hudson at messaging-20 bin]$ sh standalone.sh -c standalone-full-ha.xml
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /tmp/dr10/jboss-eap-7.0
> JAVA: /qa/tools/opt/x86_64/ibm-java-x86_64-80_2015_07_28//bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 05:15:10,530 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
> 05:15:10,915 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> 05:15:11,052 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.CR1) starting
> 05:15:12,492 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 30) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 05:15:12,726 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 05:15:12,760 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.2.Final
> 05:15:12,771 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.2.Final
> 05:15:12,814 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 44) WFLYCLINF0001: Activating Infinispan subsystem.
> 05:15:12,839 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 45) WFLYIIOP0001: Activating IIOP Subsystem
> 05:15:12,842 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 66) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> 05:15:12,874 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 68) WFLYWS0002: Activating WebServices Extension
> 05:15:12,858 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 05:15:12,880 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 49) WFLYCLJG0001: Activating JGroups subsystem.
> 05:15:12,886 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 43) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
> 05:15:12,890 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 57) WFLYNAM0001: Activating Naming Subsystem
> 05:15:12,961 INFO [org.jboss.as.security] (ServerService Thread Pool -- 64) WFLYSEC0002: Activating Security Subsystem
> 05:15:12,973 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=4.9.3.Final
> 05:15:12,990 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.0.Final)
> 05:15:13,061 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0003: Undertow 1.3.0.CR1 starting
> 05:15:13,062 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 39) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 05:15:13,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.3.0.CR1 starting
> 05:15:13,078 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
> 05:15:13,150 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.10.Final
> 05:15:13,218 INFO [org.jboss.as.naming] (MSC service thread 1-7) WFLYNAM0003: Starting Naming Service
> 05:15:13,218 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 05:15:13,361 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
> 05:15:13,361 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
> 05:15:13,463 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0014: Creating file handler for path '/tmp/dr10/jboss-eap-7.0/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 05:15:13,492 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.
> 05:15:13,499 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting
> 05:15:13,598 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
> 05:15:13,598 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow AJP listener ajp listening on 127.0.0.1:8009
> 05:15:13,656 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 71) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final
> 05:15:13,680 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 71) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
> 05:15:13,826 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 05:15:13,928 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started
> 05:15:13,938 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory /tmp/dr10/jboss-eap-7.0/standalone/deployments
> 05:15:14,053 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.1.0.Final
> 05:15:14,163 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/dr10/jboss-eap-7.0/standalone/data/activemq/journal,bindingsDirectory=/tmp/dr10/jboss-eap-7.0/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/dr10/jboss-eap-7.0/standalone/data/activemq/largemessages,pagingDirectory=/tmp/dr10/jboss-eap-7.0/standalone/data/activemq/paging)
> 05:15:14,187 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221012: Using AIO Journal
> 05:15:14,296 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
> 05:15:14,302 WARN [org.jgroups.protocols.UDP] (Thread-0 (ActiveMQ-server-ActiveMQServerImpl::serverUUID=446a359f-6041-11e5-895c-5dd24064fdad-953422266)) JGRP000015: the send buffer of socket DatagramSocket was set to 1MB, but the OS only allocated 212.99KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
> 05:15:14,303 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
> 05:15:14,303 WARN [org.jgroups.protocols.UDP] (Thread-0 (ActiveMQ-server-ActiveMQServerImpl::serverUUID=446a359f-6041-11e5-895c-5dd24064fdad-953422266)) JGRP000015: the receive buffer of socket DatagramSocket was set to 20MB, but the OS only allocated 212.99KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
> 05:15:14,304 WARN [org.jgroups.protocols.UDP] (Thread-0 (ActiveMQ-server-ActiveMQServerImpl::serverUUID=446a359f-6041-11e5-895c-5dd24064fdad-953422266)) JGRP000015: the send buffer of socket MulticastSocket was set to 1MB, but the OS only allocated 212.99KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
> 05:15:14,305 WARN [org.jgroups.protocols.UDP] (Thread-0 (ActiveMQ-server-ActiveMQServerImpl::serverUUID=446a359f-6041-11e5-895c-5dd24064fdad-953422266)) JGRP000015: the receive buffer of socket MulticastSocket was set to 25MB, but the OS only allocated 212.99KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
> 05:15:14,315 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
> 05:15:14,317 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
> Unhandled exception
> Type=Segmentation error vmState=0x00000000
> J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001
> Handler1=00007F100C601D90 Handler2=00007F1007DD03F0 InaccessibleAddress=0000000000000000
> RDI=0000000002C82D00 RSI=0000000000000000 RAX=00007F0FDCB3977F RBX=0000000000000000
> RCX=0000000000000000 RDX=00007F0FDCB39780 R8=00007F0FDCB39780 R9=00007F100C667A58
> R10=00007F0FD03885C0 R11=0000000000200246 R12=0000000002C82D00 R13=00000000000001F4
> R14=00007F0FD02A9020 R15=0000000000000000
> RIP=00007F100C606C45 GS=0000 FS=0000 RSP=00007F0FDCB394C0
> EFlags=0000000000210246 CS=0033 RBP=00007F0FDCB39770 ERR=0000000000000004
> TRAPNO=000000000000000E OLDMASK=0000000000000000 CR2=0000000000000000
> xmm0 00007f1008067fe0 (f: 134643680.000000, d: 6.902435e-310)
> xmm1 0000000002c82d00 (f: 46673152.000000, d: 2.305960e-316)
> xmm2 0000000002c82a78 (f: 46672504.000000, d: 2.305928e-316)
> xmm3 00000000029a16c8 (f: 43652808.000000, d: 2.156735e-316)
> xmm4 0000000000000005 (f: 5.000000, d: 2.470328e-323)
> xmm5 00000000029a1828 (f: 43653160.000000, d: 2.156753e-316)
> xmm6 0000000000000001 (f: 1.000000, d: 4.940656e-324)
> xmm7 0000000000000001 (f: 1.000000, d: 4.940656e-324)
> xmm8 4169e3bd00000000 (f: 0.000000, d: 1.357361e+07)
> xmm9 3fcb1f59ad7ad780 (f: 2910509056.000000, d: 2.118942e-01)
> xmm10 3ff0000000000000 (f: 0.000000, d: 1.000000e+00)
> xmm11 be88000000000000 (f: 0.000000, d: -1.788139e-07)
> xmm12 bcd2800000000000 (f: 0.000000, d: -1.026956e-15)
> xmm13 bc34000000000000 (f: 0.000000, d: -1.084202e-18)
> xmm14 3c66353ab386a94d (f: 3011946752.000000, d: 9.631153e-18)
> xmm15 4030a2b23f3baa00 (f: 1060874752.000000, d: 1.663553e+01)
> Module=/qa/tools/opt/x86_64/ibm-java-x86_64-80_2015_07_28/jre/lib/amd64/compressedrefs/libj9vm28.so
> Module_base_address=00007F100C58E000
> Target=2_80_20150630_255633 (Linux 3.10.0-229.1.2.el7.x86_64)
> CPU=amd64 (8 logical CPUs) (0x4dce1d000 RAM)
> ----------- Stack Backtrace -----------
> (0x00007F100C606C45 [libj9vm28.so+0x78c45])
> (0x00007F100C61BECA [libj9vm28.so+0x8deca])
> ---------------------------------------
> JVMDUMP039I Processing dump event "gpf", detail "" at 2015/09/21 05:15:14 - please wait.
> JVMDUMP032I JVM requested System dump using '/tmp/dr10/jboss-eap-7.0/bin/core.20150921.051514.4815.0001.dmp' in response to an event
> JVMDUMP010I System dump written to /tmp/dr10/jboss-eap-7.0/bin/core.20150921.051514.4815.0001.dmp
> JVMDUMP032I JVM requested Java dump using '/tmp/dr10/jboss-eap-7.0/bin/javacore.20150921.051514.4815.0002.txt' in response to an event
> JVMDUMP010I Java dump written to /tmp/dr10/jboss-eap-7.0/bin/javacore.20150921.051514.4815.0002.txt
> JVMDUMP032I JVM requested Snap dump using '/tmp/dr10/jboss-eap-7.0/bin/Snap.20150921.051514.4815.0003.trc' in response to an event
> JVMDUMP010I Snap dump written to /tmp/dr10/jboss-eap-7.0/bin/Snap.20150921.051514.4815.0003.trc
> JVMDUMP007I JVM Requesting JIT dump using '/tmp/dr10/jboss-eap-7.0/bin/jitdump.20150921.051514.4815.0004.dmp'
> JVMDUMP010I JIT dump written to /tmp/dr10/jboss-eap-7.0/bin/jitdump.20150921.051514.4815.0004.dmp
> JVMDUMP013I Processed dump event "gpf", detail "".
> {code}
> Java version:
> {code}java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr1fp10-20150711_01(SR1 FP10))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150630_255633 (JIT enabled, AOT enabled)
> J9VM - R28_jvm.28_20150630_1742_B255633
> JIT - tr.r14.java_20150625_95081.01
> GC - R28_jvm.28_20150630_1742_B255633_CMPRSS
> J9CL - 20150630_255633)
> JCL - 20150711_01 based on Oracle jdk8u51-b15
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list