Uncaught Exception Handler about bagger HOT 7 CLOSED

Hi Jamie,

How large is this Bag? I think the NoClassDefFoundError is a red herring because I see in the log there is java.lang.OutOfMemoryError: Java heap space which means that Bagger ran out of memory.
Is this bag on local disk, on a external drive, or somewhere else?

from bagger.

from bagger.

bagger.bat.txt
rename this to bagger.bat and try running it again. This startup script allocates 3GB worth of memory for Bagger.

It should be noted that we don't really support external drives due to the added complexity and IO errors that can occur.

from bagger.

from bagger.

You want to put that file in the same location as the other bagger.bat file. But the error you are seeing is that it can't reserve the 3 GB of ram. Not being at your computer I can't 100% confirm, but it sounds like your computer needs more ram in order to verify the bag using bagger.

from bagger.

Hello,

I am running into another uncaught exception error with another large bag, and I wonder if it is the same problem. I've attached the log file. The bag is 101 GB with 94699 files. Thank you for your help.
Bagger_error_log_04032018.txt

from bagger.

@jamiepb you will notice it says in the log java.lang.OutOfMemoryError: Java heap space. The heap space is what java uses to do work. To put it simply you haven't given Bagger enough ram. From my earlier comments it seems that your computer simply doesn't have the ram needed to run Bagger for that large of a bag. I would recommend using https://github.com/LibraryOfCongress/bagit-python command line tool to validate it instead.

from bagger.