[
http://jira.jboss.com/jira/browse/JBESB-1294?page=comments#action_12385479 ]
Tom Fennelly commented on JBESB-1294:
-------------------------------------
I'm very sure this is fixed in JBESB-1269, which only went in on Tuesday. This should
be fixed in the GA.
Basically what was happening was that the request headers were getting mapped onto the
response (in error). In the case of HTTP, one of those headers can be the Content-Length,
meaning that the wrong content length was getting sent back in the response... if that was
greater than the actual content length, the client will sit there trying to read until a
timeout, hence the long delay you're seeing for HTTP.
I'm closing this for now, if that's OK.
WebService response takes a long time
-------------------------------------
Key: JBESB-1294
URL:
http://jira.jboss.com/jira/browse/JBESB-1294
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.2.1 IR2
Environment: [4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200709191615)]
Reporter: Jiri Pechanec
Attachments: wscf.tgz
See attached example that uses SOAPProcessor. When I try to use socket JBR, the response
is immediate. If I try to use HTTP JBR or then the response is delivered after one minute
or is not delivered at all.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira