Hi All,
We have implemented below logging for the Incoming request, Final response,
call mediator call, script call etc and could see that the memory
consumption has increased by 30 - 40%. We did testing with the same load
after removing logs and found that memory usage was very less.
<log level="custom">
<property expression="get-property('-Tracking-Id')"
name="Tracking-Id"/>
<property name="Event-Type" value="OUTBOUND"/>
<property name="System-Name" value="ABC"/>
<property name="Tag-Name" value="TBD"/>
<property expression="get-property('xyz')" name="xyz"/>
</log>
<call>
<endpoint key="conf:/endpoint/xyz"/>
</call>
<log level="custom">
<property expression="get-property('Tracking-Id')"
name="Tracking-Id"/>
<property name="Event-Type" value="INBOUND"/>
<property name="System-Name" value="ABC"/>
<property name="Tag-Name" value="TBD"/>
<property expression="get-property('axis2', 'HTTP_SC')"
name="Response-Code"/>
<property expression="json-eval($.)" name="XYZ"/>
</log>
We took a heap dump and below are the findings.
About 240MB of 1.06GB (21.7%) of used heap is used to store the tracking
header string "Tracking-Id = dddf3, Event-Type = INBOUND, System-Name = XYZ,
Tag-Name = CACHE, Response-Code = null, get ...[length 191]" by
org.wso2.carbon.utils.logging.TenantAwareLoggingEvent.message object
Please suggest a way to overcome this issue as we need above logging pattern
for the monitoring solution.
Thanks.
Lalit
--
Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development-f3.html
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
