Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.6.0
-
None
Description
Have a SOAP server + client. Normally everything works nicely, but if the server is very busy doing other things (or the SOAP worker thread must wait for a mutex), the following appears in the log:
[Mon Jun 21 20:36:32 2010] [error] network_handler.c(259)
[Axis2][network_handler] Socket accept failed
[Mon Jun 21 20:36:32 2010] [warning] http_svr_thread.c(133) Worker not
ready yet. Cannot serve the request
The text above appears 6209 times (!!!), then eventually:
[Mon Jun 21 20:36:32 2010] [warning] http_svr_thread.c(133) Worker not
ready yet. Cannot serve the request
[Mon Jun 21 20:36:32 2010] [error] network_handler.c(259)
[Axis2][network_handler] Socket accept failed
[Mon Jun 21 20:39:28 2010] [error] http_client.c(574) Response timed out
[Mon Jun 21 20:39:28 2010] [error] http_sender.c(1381) status_code < 0
[Mon Jun 21 20:39:28 2010] [error] engine.c(179) Transport sender invoke
failed
Attachments
Issue Links
- blocks
-
AXIS2C-1681 Apache Axis2C Roadmap 1.7 Planning
- Open
- is related to
-
AXIS2C-1565 CPU utilization is 100% for SOAP queries for synchronous calls
- Open