.jws service crashes when restarting with heavy load
----------------------------------------------------
Key: AXIS2-549
URL: http://issues.apache.org/jira/browse/AXIS2-549
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Environment: Solaris, Tomcat
Reporter: David López
Priority: Minor
Service Catalog.jws deployed with .jws method.
On a load test the application behaves ok with both light and heavy load. The
problem arises when restarting the application while the test load program goes
on working. The server must work ok when starting with heavy load, but looks
like many simultaneous requests spoil the .jws initialization.
Some requests work ok, while others respond error message:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/
envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.generalException</
faultcode><faultstring>Tried to invoke method public
es.tid.catalog.client1_0.Category
Catalog1_0.listByQuality(java.lang.String,java.lang.String,java.lang.String[],es.tid.catalog.client1_0.Filter[],es.tid.catalog.client1_0.Order[],int,int,int)
throws
es.tid.catalog.core.list.FilterNotFoundException,es.tid.catalog.core.list.OrderNotFoundException,es.tid.catalog.client1_0.ServerException,es.tid.catalog.core.EntityNotFoundException
with arguments
java.lang.String,java.lang.String,[Ljava.lang.String;,[Les.tid.catalog.client1_0.Filter;,[Les.tid.catalog.client1_0.Order;,java.lang.Integer,java.lang.Integer,java.lang.Integer.
The arguments do not match the signature.; nested exception is:
.java.lang.IllegalArgumentException: [EMAIL PROTECTED]</
faultstring><detail><ns1:hostname
xmlns:ns1="http://xml.apache.org/axis/";>nikita0</ns1:hostname></
detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
Even after many minutes the server doesn't seem to recover.
Everything works ok if we use wsdd file deployment instead of .jws
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
