certain requests just hang with 100% CPU

Hi!

hmm.. what kind of request? SOAP? REST? can you give any more details so we can try to reproduce?

regards!

/Ole
eviware.com

SOAP generated from SOAP12Binding.  It has basic auth which works.  It is going through TCPMON and what I see is first a request that doesn't send the auth then after the failure it automatically sends the request with the auth which TCPMON shows does send the response which looks like this in TCPMON:

HTTP/1.1 500 Internal Server Error

Cache-Control: no-cache="set-cookie"

Date: Tue, 30 Jun 2009 19:33:05 GMT

Transfer-Encoding: chunked

Content-Type: application/soap+xml; charset=UTF-8; action="urn:getCaseCommentsException"

Set-Cookie: JSESSIONID_AXIS=KKyStw8DrDGZvP1Lfs0KKPXr3n5hQM8NY2WxJCG4myGp2FDLy22v!1774783375; path=/

X-Powered-By: Servlet/2.4 JSP/2.0



034c

soapenv:ReceiverFor input string: "1XXXXBAD"

0000


But then soapui never shows the response, in fact, I have a 30 second socket timeout, too, which isn't working, it acts like it is just waiting waiting waiting and using CPU.  The soapui gui thread still responds.

Hi,

thanks for the details, it seems soapUI chokes on this xml for some reason.. I'll check it out and will get back to you..

regards!

/Ole
eviware.com

Hi again,

the problem is the following content in the xml:

.. xmlns="http://www.w3.org/XML/1998/namespace" ..

which causes soapUI to choke. If I remove this it works ok. I've validated the xml with several editors and they all give the following error for this:

The prefix "xml" cannot be bound to any namespace other than its usual namespace; neither can the namespace for "xml" be bound to any prefix other than "xml".

So ultimately it is a combination of invalid XML and bad handling of it.. Can you fix this XML? I'll see what can be done for the parsing..

regards!

/Ole
eviware.com

Huh.  Well, fixing it may be problematic for a couple of reasons, one being that that service is written and owned by a different team (same division at least...), the other being that really Axis2 is doing the generation, so it is probably an Axis2 bug.  Maybe when I rev the version of Axis2 jars which I'm going to do anyway it will just "go away"... I think it is Axis2-1.3 that generated the XML.

Any word on this?  Should I download a new daily build?