memmalloc called for big allocation of 2181909 bytes - WSDL - problem with integration
We have integration with another tool for Change Management process which when we try to call a function we get a payload which is too big for SM to accept.
We have increased shared memory, and this parameter, did anyone had this problem?
Thanks for contacting us on this problem.
I was looking at the information and the links that you sent to us and found out this (this investigation was done with the assumption that you are using SOAP for the integration).
it shows that the first parameter doesn't affect the size of SOAPRequest. so I was looking for another option that will be similar to this one and found the next one.
Please, review it and let us know if this what you need or if it helps you.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
It will be useful if you share the specific error you are having, the scenario and one request/response example.
If you feel this was helpful please click the KUDOS! thumb below!
We are having a problem with the response from another system, we request data with SOAP request and when data (payload) is returned to Service Manager we get this error like data which we are requesting is too big for SM to load it.
We know that payload is big and we are aware of this, this is important for our customer and project is of big value for us.