E1:XML: XAPI is making the XML Dispatch kernel die and restarts a new Dispatch kernel.
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
XAPI is making the XML Dispatch kernel die and restarts a new Dispatch kernel.
This problem is a consequence of XML dispatch memory leak fix for BUG # 8095841 There is a delete statement which is causing Dispatch kernel to blow up (due to double delete) in a couple of scenarios not considered by mentioned fix. The fix takes care of freeing the original XMLDocument in XMLDocMsg when sending the response from dispatch to original requestor. This needed to be done because response to UTF8 is converted, which results in new document (which is later freed) and original document is left behindand not freed. The fix works fine in most scenarios. However it will fail under the following scenarios:
1. When the message sent from XMLDispatch to some XML kernel times out. This can happen if servicing kernel dies due to any reason.
2. When message sent from XMLDispatch is XAPI (or any other type that does not have response) and hence servicing kernel does not give response.
Although scenario 1 above is not normal, scenario 2 is.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms