Results 1 to 6 of 6

Thread: Memory usage of ConfigurationInjectorBeanPostProcessor

Threaded View

  1. #1
    Join Date
    Oct 2012
    Posts
    4

    Default [SOLVED] Memory usage of ConfigurationInjectorBeanPostProcessor

    Hi dear all, i am new to this forum, so please be gentle... :-D

    I have created an app which reads ids from a queue, and processes records from a database with those ids. To do that i created a taskExecutor object which uses a thread pool.

    To make sure that there will be no "interferences", i use prototype-scoped processing beans.

    I run a "burn-in" test the day before Yesterday, and everything went fine, except the memory usage... It seemed that there was a memory leak. Using my favourite memory analyzer, it turned out, that the ConfigurationInjectorBeanPostProcessor holds references to all already configured beans (List<Object> alreadyConfiguredBeans), and i end up with ~70k objects which i don't want to have any more (no other references to them)...

    So is there a way to instruct this class not to save all references, or clean them up after the processing is complete? Or should i write my own PostProcessor?

    Using 3.1.0.RELEASE

    Thanks for any suggestions!
    Last edited by ltuska; Oct 10th, 2012 at 06:37 AM. Reason: adding thanks

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •