[
https://issues.apache.org/jira/browse/AXIS2C-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1565.
-------------------------------------
Fix Version/s: 2.0.0
(was: 1.7.0)
Resolution: Fixed
AXIS2C-1482: Fix busy-loop when server worker not ready
When the server thread accepted connections but the worker wasn't ready yet,
it would log a warning, close the socket, and immediately continue the loop.
This caused a tight busy-loop that consumed 100% CPU and flooded the log
with "Worker not ready yet" messages (reported as 6209 times in one case).
Add a 10ms sleep before continuing when the worker isn't ready. This
prevents
CPU spinning while still being responsive when the worker becomes available.
Apply the same fix to both HTTP and TCP server threads.
This also addresses AXIS2C-1565 (100% CPU for synchronous calls) which is
a related symptom of the same busy-waiting issue.
> CPU utilization is 100% for SOAP queries for synchronous calls
> --------------------------------------------------------------
>
> Key: AXIS2C-1565
> URL: https://issues.apache.org/jira/browse/AXIS2C-1565
> Project: Axis2-C
> Issue Type: Improvement
> Affects Versions: 1.6.0
> Environment: Axis2c built with LibXML
> Reporter: Prashant
> Priority: Major
> Labels: test
> Fix For: 2.0.0
>
>
> For SOAP queries, the following call on axis library utilizes the cpu around
> 100%. The same is resolved in Axis Java version. But it seems to be still
> available in Axis2C.
> CPU utilization seems to be normal before and after this call.
> ret_node = axis2_svc_client_send_recieve(svc_client,env,payload);
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
