DSpace/DSpace — pull request #589 by kohts (2014-07-27 21:24:48+00:00)
Title: output bitstream to be processed in verbose mode

This is useful to understand where dspace media-filter fails,
otherwise it is quite tricky to understand where the problem is.

Consider the sample output with the modified code:

SKIPPED: bitstream 7133 (item: 123456789/898) because 'nvf-2116-0171-004.jpg.jpg' already exists
SKIPPED: bitstream 9388 (item: 123456789/886) because 'nvf-2116-0430-001.jpg.jpg' already exists
SKIPPED: bitstream 9389 (item: 123456789/886) because 'nvf-2116-0430-002.jpg.jpg' already exists
SKIPPED: bitstream 9390 (item: 123456789/886) because 'nvf-2116-0430-003.jpg.jpg' already exists
SKIPPED: bitstream 9391 (item: 123456789/886) because 'nvf-2116-0430-004.jpg.jpg' already exists
PROCESSING: bitstream 9495 (item: 123456789/860)
original size: 8892.0,6514.0
x scale factor: 0.008996851
new size: 80.0,58.605488
created thumbnail size: 80.0, 58.605488
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000ea680000, 93847552, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 93847552 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /home/dspace/hs_err_pid15915.log