Hubert, Eric wrote:
Hi all,
today we conducted some performance measuring regarding response times
with low traffic (3-6 concurrent requests) using the Hessian protocol
support.
Unfortunately when using the ESB the response times increased by about
30% in comparison to direct invocation. The test case only included a
proxy service with a send mediator using a fixed endpoint, no routing
decision, no logging/tracing. CPU load on the ESB had been minimal (<
5%).
While checking the esb log file I saw a lot of entries like that:
2008-04-28 11:04:25,255 [-] [Finalizer] WARN TemporaryData Cleaning up
unreleased temporary file work/temp/esb/tmp_43238.dat
2008-04-28 11:04:25,255 [-] [Finalizer] WARN TemporaryData Cleaning up
unreleased temporary file work/temp/esb/tmp_43239.dat
2008-04-28 11:04:25,255 [-] [Finalizer] WARN TemporaryData Cleaning up
unreleased temporary file work/temp/esb/tmp_43240.dat
I think this is related to the way "big" responses are handled. They are
streamed and temporarily written to disc, because they are larger than
some internal buffer. The warning may indicate that the client code does
not properly release the resources (in this case the temp file) and some
utility class does its best to compensate this misbehaviour through
fixing this inside a finalize method and logging the above warning (only
my blind guess).
Could you please check this and fix it, if I'm not wrong with my
uneducated guess! ;-)
Can we increase the log level, meaning only errors would be logged?
Samisa...
a
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
