Ah,
Yes, these parameters only apply to DSpace 1.5 and are not available
in previous versions.
Scott--
On Mar 4, 2008, at 8:51 PM, Thornton, Susan M. (LARC-B702)[NCI
INFORMATION SYSTEMS] wrote:
> Hi again Scott,
> I added both of those to dspace.cfg and it didn't seem to have any
> ef
Hi again Scott,
I added both of those to dspace.cfg and it didn't seem to have any
effect - I got the same error again:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
Are those parameters valid for DSpace 1.4.2?
Thanks again,
Sue
-Original Message-
From: S
Oh, Sorry.
The parameters go into your dspace.cfg. They are both boolean
parameters so just add:
pdffilter.largepdfs = true;
or
pdffilter.skiponmemoryexception = true;
Then re-run your dsrun command and they will take effect.
Scott--
On Mar 4, 2008, at 6:13 PM, Thornton, Susan M. (LARC-B7
Hi Scott,
Thanks for the info, but can you tell me exactly where to put/how
to format the parameters? Do they go on the dsrun command?
Thanks again,
Sue
From: Scott Phillips [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2008 6:51 PM
To: Thornton,
Have you tried using the "pdffilter.largepdfs" and
"pdffilter.skiponmemoryexception" parameters?
Turning on largepdfs will tell pdfbox to use a temporary file while
processing the pdf instead of keeping it all in memory. It will use
the standard java.io.tmpdir directory to store them in.
We have recently been getting the following error in the filter-media
cron:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
I changed -Xmx256m in the java command in dsrun to -Xmx512m
(documentation says that's the max you can set it to) and we're still
getting the
Dear Charlotte,
we are working on the same issue on a DSpace 1.3.2 installation.
Typically, it occurs during the submission process.
When we figure it out, we'll post it here.
When you find a solution, we'd also be interested.
regards,
Bram Luyten
On Tue, Mar 4, 2008 at 9:40 AM, Charlotte Poll
David:
I would do this in SQL. Here is an example of the command I use:
update collection2item set collection_id= where
item_id=;
Then I do the following:
update item set owning_collection= where
item_id=;
OR run index_all after making the changes and it would fix the owning
collections an
If you're using a postgres database, then you can
turn up the logging on the database server.
http://www.postgresql.org/docs/8.3/static/runtime-config-logging.html
Cheers,
Reuben
>>> Charlotte Pollock <[EMAIL PROTECTED]> 3/4/2008 2:40 AM >>>
Hi
I'm getting an the following intermittent er
Dear colleagues,
I want to move items from one collection to another in order to delete the old
collection but still retain the handles on the items. One colleague suggested
the following, but he stressed that he had not tried it before:
"I would try exporting the item ( you'll get the handle )
Hi Charlotte,
if you set your log level to DEBUG, the queries will appear in the
dspace log files.
In order to do so edit
[dspace-source]/config/templates/log4j.properties
change the line
log4j.rootCategory=INFO, A1
to
log4j.rootCategory=DEBUG, A1
then you got to run [dspace]/bin/install-config
On Tue, Mar 04, 2008 at 08:40:32AM +, Charlotte Pollock wrote:
> I'm getting an the following intermittent error
>
> database_error:org.postgresql.util.PSQLException: ERROR: current transaction
> is aborted, commands ignored until end of transaction block
>
> With no clear pattern as to why
>
Hi
I'm getting an the following intermittent error
database_error:org.postgresql.util.PSQLException: ERROR: current transaction
is aborted, commands ignored until end of transaction block
With no clear pattern as to why
What I really would like to do is to see the raw SQL that is causing
postgr
13 matches
Mail list logo