Summary This article clarifies an issue where requestst containing many namespace prefixes which are never used is failing. Environment Artix 5.5 JAX-RPC Solaris Operating System Question/Problem Description Request containing many namespace prefixes, which are never used, is failing with MARSHAL_ERROR Clarifying Information Error Message SOAP-ENV:Envelope xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:m1="http://schemas.iona.com/faults" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:Body SOAP-ENV:Fault faultcode xmlns:m2="http://schemas.iona.com/exceptions" m2:Caught exception while parsing the XML document containing message: An exception occurred! Type:RuntimeException, Message:The buffer manager cannot provide any more buffers /faultcode faultstring Caught exception while parsing the XML document containing message: An exception occurred! Type:RuntimeException, Message:The buffer manager cannot provide any more buffers /faultstring detail m1:FaultException xsi:type="m1:FaultException" m1:category MARSHAL_ERROR /m1:category m1:namespace_uri http://schemas.iona.com/exceptions /m1:namespace_uri m1:code Caught exception while parsing the XML document containing message: An exception occurred! Type:RuntimeException, Message:The buffer manager cannot provide any more buffers /m1:code m1:detail/ m1:source CLIENT /m1:source m1:completion_status NO /m1:completion_status m1:description Caught exception while parsing the XML document containing message: An exception occurred! Type:RuntimeException, Message:The buffer manager cannot provide any more buffers /m1:description m1:server_id/ /m1:FaultException /detail /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope Defect/Enhancement Number Cause The issue is related to the XercesC 2.4 version shipped in Orbix 5.5. This has been fixed in XercesC 2.7: https://issues.apache.org/jira/browse/XERCESC-1338 https://issues.apache.org/jira/browse/XERCESC-866 Resolution Upgrade to the latest available Artix JAX-WS version. Workaround Removing the unused namespaces from the request works around this issue. Notes Attachment
↧