|
All
this allocating more memory and allowing more instances to be created wont solve
any problem. Only delay it. If the server crashes at 6000 instances of 90.000,
how much more memory would that require? A lot. I don't know what's current on
the orion ejbPassivate issue, but you should still consider having a refactoring
go at the code first. Maybee you keep references to all the imported articles in
a Collection of some sort or something like that. If not, then I dont'
know what could be causing the problem.
regards,
Patrik
Andersson
|
- EJB Passivation problem James Donnelly
- Re: EJB Passivation problem Hani Suleiman
- Re: EJB Passivation problem Mikko Kurki-Suonio
- Re: EJB Passivation problem Rafael Alvarez
- EJB Passivation problem James Donnelly
- Re: EJB Passivation problem KirkYarina
- Re: EJB Passivation problem James Donnelly
- UserTransaction lookup from client Patrik Andersson
- UserTransaction lookup from client Tim Burns
