stephan.lux wrote: > > > gnodet wrote: >> >> Can you track where these objects are allocated from ? >> > Yes, Jprofiler is realy a fine tool :-) > The most of the instances are created by the microsoft mssql driver. As > you can see in the allocation reports, a lot of objects were not destroyed > that are created by the groovy component. Maybe a hint that here is the > root of the memory leak? The database access via the mssql jdbc driver is > done there... > > I have also added two reports, that are showing how many objects are left > after processing some jobs. Sometimes - as written before - some of the > jobs are not processed successfully without returning an error (I have > also checked the debug log). In this case some mb are left in memory. The > report 'Recorded_Objects_400_jobs_17_failed.html' shows these classes. > > I don't know where and why the messages are disapearing, but I still keep > on profiling and searching... > > http://www.nabble.com/file/5289/JProfiler_Results.zip > JProfiler_Results.zip > > Stephan >
-- View this message in context: http://www.nabble.com/Severe-issues-while-load-testing-tf2845236s12049.html#a8158869 Sent from the ServiceMix - User mailing list archive at Nabble.com.
