Alessio Soldano commented on WFLY-5432:
I've tried but could not reproduce this issue (I'm on fedora, oracle jdk
1.8.0_40). I had to modify SubmitOrder in your war as the reference to the wsdl was broken
(the war as is fails deployment on WildFly), used a simple @WebService annotation in it,
hence full code-first-approach.
Then I deployed the modified war on a vanilla WildFly 9.0.1.Final (didn't change
anything in the configuration) and started the container.
I downloaded SOAPUI 5.2.0 and created a test project using the wsdl of the deployed
application. Then I modified the request message to have valid data (no "?") and
started the load test with 10 threads, 1ms delay, 1200 sec limit.
I've got 1.680.520 successful invocations (no error/failure) with an average of ~1400
tps (clearly, I could have had far better results by tuning logging, etc....)
To be honest, as part of our perf tests, we've gone way further than the numbers
reported in this jira.
So, unless you can provide a way for reproducing, I'm not sure how to help here and
would likely close this jira as cannot reproduce, sorry.
Wildfly SOAP webservice causes JVM crash
Issue Type: Bug
Components: Web Services
Affects Versions: 9.0.1.Final, 10.0.0.CR2
Environment: Tested on Mac OSX 10.10.2, jdk 1.8.60, wildfly 9.0.1. Final /
Also tested on Centos 6.5, jdk 1.7.51, wildfly 9.0.1. Final
Reporter: Davide Marchetti
Assignee: Alessio Soldano
Labels: crash, jvm, soap, webservice
The JVM crashes with either a sigsegv or sigbus error when performing a SOAP load test.
The error printed is:
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00007f5da922afb8, pid=75645, tid=140039627204352
# JRE version: OpenJDK Runtime Environment (7.0_51-b02) (build
# Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J org.apache.cxf.message.ExchangeImpl.get(Ljava/lang/Class;)Ljava/lang/Object;
# 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 include
# instructions on how to reproduce the bug and visit:
# 15:56:03,314 INFO [stdout] (default task-17) Submitted order request received with
transId: <XXXXX>, opId: <SCO>, ...
The webservice does nothing, just a System.out.print("xxxxx").
This message was sent by Atlassian JIRA