Hi all,

we are using some Aries modules inside our application (deployed as 150 bundles at runtime) :

- Aries JTA/JPA

- Aries Async

- Aries Subsystems


At runtime we encounter OutOfMemoryException and the dumps show a strange context:

 * 88000 instances of Classloaders
 * 88000 instances of PermissionDomain (ok for the 1 -1 cardinality)
 * 896 instances of java.lang.Package[] (I expected 88000 approximately)
 * a huge number of Async instances

I would like to know if this context could be explained by some kind of bug inside Aries .

I just can imagine one scenario like this:

 * trying to load a bundle
 * error
 * retry (several times)

Logging on our application is horrible so I just get useless traces..


We have seen sometimes erratic behaviour with bundle resolution very long (40 minutes before succeeding). I suspect some problems with bundle wiring but don't have many clues.


Did you ever seen such things happen ? Is it a known issue with previous Aries versions (our bundles are not so old , may be 2 or 3 months old).

Kind regards

jerome

PS:

excuse me I can't be really accurate because of the logging and because of legal aspects...

Reply via email to