I'm having some issues with the Service Desk integration agent. We seem to get timout and out of memory errors with java when Service Desk has to push a lot of incidents through. Does anyone know a way to control the timout settings or the memory settings in Java? Does anyone think this isn't a java issue? Here's a sample of a few errors. When this happens, the temp file from service desk doesn't get processed.
The reason given was: unable to create new native thread
Stack trace:
- java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
2012-11-07 00:02:24,266 [inbound.caservicedesk.caservicedesk.normal-1] ERROR - Integration Service (caservicedesk, caservicedesk) was unable to process a request due to an unexpected exception: java.net.SocketTimeoutException: Read timed out. Request: <?xml version="1.0" encoding="UTF-8"?>
<transaction id="1"><header><method>add</method><subclass>event</subclass></header><data><nx_ntf_persistent_id>cr:867483</nx_ntf_persistent_id><apia_priority type="string">normal</apia_priority><apia_source type="string">apclient: /127.0.0.1:57580</apia_source><apia_process_group type="string">apia_default_group</apia_process_group><agent_client_id>caservicedesk|caservicedesk</agent_client_id><notification_file type="string">C:\Windows\TEMP\3417</notification_file><nx_ntf_ref_num>468283</nx_ntf_ref_num></data></transaction>
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
type="string">C:\Windows\TEMP\4236</notification_file><nx_ntf_ref_num>468663</nx_ntf_ref_num></data></transaction>
java.lang.OutOfMemoryError: unable to create new native thread