Hi everyone, We are encountering OutOfMemoryError when checking in about 5000 nodes in a same transaction. Obviously, the workaround is to allocate more heap space when starting JVM (-XmX option). But, we would like to handle this exception properly in any case (to display a proper message in our software). We noticed in ObservationDispatcher.226 (jackrabbit.core) that any Throwable is caught but never thrown. That's why we cannot catch any issue on our side although everything is frozen due to the java heap space.
Does anyone has encounter such issue? Is there any solution to handle this. Regards, Adrien Information in this e-mail and any attachments is confidential, and may not be copied or used by anyone other than the addressee, nor disclosed to any third party without our permission. There is no intention to create any legally binding contract or other binding commitment through the use of this electronic communication unless it is issued in accordance with the Experian Limited standard terms and conditions of purchase or other express written agreement between Experian Limited and the recipient. Although Experian has taken reasonable steps to ensure that this communication and any attachments are free from computer viruses, you are advised to take your own steps to ensure that they are actually virus free. Experian Ltd is authorised and regulated by the Financial Conduct Authority. Companies Act information: Registered name: Experian Limited. Registered office: The Sir John Peace Building, Experian Way, NG2 Business Park, Nottingham, NG80 1ZZ, United Kingdom. Place of registration: England and Wales. Registered number: 653331.
