Uncaught Exception Handler

[jamiepb]

Hello,

I am running Bagger 2.7.7 on Windows 7 Enterprise. On a particular bag receive the error "Exception: Java.lang.NoClassDefFoundError thrown from the UncaughtExceptionHandler in thread "Thread-4" The bag validates in the command-line, but not in Bagger. I've attached the log from opening the bag to trying to validate.

Thank you,

Jamie

BaggerUncaughtExceptionLog.txt

[johnscancella]

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?

[jamiepb]

Hi John,

The bag is 695 GB (308284 files), and it is on an external drive.

Jamie

JAMIE PATRICK-BURNS Digital Archivist State Archives of North Carolina

215 N Blount St MSC 4615 Raleigh, NC 27699 919 807 7355 office

[cid:image002.png@01D3B21F.C1077CA0]

Email correspondence to and from this address is subject to the North Carolina Public Records Law and may be disclosed to third parties.

Facebookhttp://www.facebook.com/NorthCarolinaCulture Twitterhttp://www.twitter.com/ncculture Instagramhttp://www.instagram.com/ncculture YouTubehttp://www.youtube.com/ncculture

From: John Scancella [mailto:notifications@github.com] Sent: Friday, March 02, 2018 12:02 PM To: LibraryOfCongress/bagger bagger@noreply.github.com Cc: Patrick-Burns, Jamie A jamie.patrickburns@ncdcr.gov; Author author@noreply.github.com Subject: [External] Re: [LibraryOfCongress/bagger] Uncaught Exception Handler (#51)

CAUTION: External email. Do not click links or open attachments unless verified. Send all suspicious email as an attachment to Report Spam.mailto:report.spam@nc.gov

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?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/LibraryOfCongress/bagger/issues/51#issuecomment-369983550, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AhKazpF2MxfZQ89d0gks9VRxHM-rT21-ks5taXsSgaJpZM4SaMNT.

[johnscancella]

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.

[jamiepb]

Hi John,

Is there anywhere in particular I need to run this file from? I tried it from my desktop and get an error that says “Error occurred during initialization of VM Could not reserve enough space for 3145728KB object heap Press any key to continue . . .” But I’m wondering if that’s an issue with my computer more than anything else.

Thanks for your help.

JAMIE PATRICK-BURNS Digital Archivist State Archives of North Carolina

215 N Blount St MSC 4615 Raleigh, NC 27699 919 807 7355 office

[cid:image002.png@01D3B52B.9A66DCD0]

Email correspondence to and from this address is subject to the North Carolina Public Records Law and may be disclosed to third parties.

Facebookhttp://www.facebook.com/NorthCarolinaCulture Twitterhttp://www.twitter.com/ncculture Instagramhttp://www.instagram.com/ncculture YouTubehttp://www.youtube.com/ncculture

From: John Scancella [mailto:notifications@github.com] Sent: Friday, March 02, 2018 2:53 PM To: LibraryOfCongress/bagger bagger@noreply.github.com Cc: Patrick-Burns, Jamie A jamie.patrickburns@ncdcr.gov; Author author@noreply.github.com Subject: [External] Re: [LibraryOfCongress/bagger] Uncaught Exception Handler (#51)

CAUTION: External email. Do not click links or open attachments unless verified. Send all suspicious email as an attachment to Report Spam.mailto:report.spam@nc.gov

bagger.bat.txthttps://github.com/LibraryOfCongress/bagger/files/1776388/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.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/LibraryOfCongress/bagger/issues/51#issuecomment-370034219, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AhKazntHrUIzvEGv4Nfs8D1yM3YAbD3xks5taaMJgaJpZM4SaMNT.

[johnscancella]

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.

[jamiepb]

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

[johnscancella]

@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.