Description of problem: In drools-camel-server, memory allocation during request/response message handling is quite larger than actual request/response size. For example, with attached numbers.drl and JBoss_Benchmark_Request.xml, one SOAP request results in 45MB+ object allocation while the actual request size is 200KB and the response size is 650KB. They are short-lived objects so wouldn't be a memory leak but affect performance especially under high load.
Created attachment 654913 [details] JBoss_Benchmark_Request.xml
Created attachment 654914 [details] numbers.drl
Toshiya Kobayashi <tkobayas> made a comment on jira JBRULES-3699 They are likely String operations (e.g. byte array <-> String conversion). Probably they are required anyway. But I hope some memory conscious solution can be found. for example, https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-camel/src/main/java/org/drools/camel/component/DroolsPolicy.java#L322 https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-camel/src/main/java/org/drools/jax/soap/PostCxfTransportSoapProcessor.java#L52 https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-camel/src/main/java/org/drools/jax/soap/PostCxfTransportSoapProcessor.java#L57 https://github.com/apache/camel/blob/camel-2.4.0/camel-core/src/main/java/org/apache/camel/converter/IOConverter.java#L140