Hi. We're suddenly seeing this error when we restart tomcat:
Error occurred during initialization of VM
Could not reserve enough space for object heap
I'm mystified, because we have made no server changes recently. Apache
is running, postgresql is running, but tomcat is borked.
Can anyone
Hi Pradip,
(cc’ing to dspace-tech)
I can’t guarantee this is the problem, but I’ve encountered this SQL error
running stat-initial when I’ve had two metadata schemas that both had
element/qualifier combinations that some Dspace queries expect to be unique.
For instance, on one of my
On 17/08/2009, at 5:56 AM, Kim Shepherd wrote:
the subquery run by stat-initial (when it’s getting a count of
non-withdrawn items) looks for metadata with element ‘date’ and
qualifier ‘accessioned’ but ignores schema ID – both results are
returned, and the exception is thrown
I assume this is to do with database schema rather than metadata registry
schema, so it probably isn't relevant.. sorry if I didn't explain what I meant
by 'schema' very well. If you inspect your metadatafieldregistry table, you'll
see the schema ID I'm talking about.
Cheers,
Kim
Hi Chris,
You can manually reset the destination installation environment by
emptying out the [dspace] directory and re-creating the database:
# the first dollar sign is your shell prompt
# in my case I would do for the [dspace] directory where `x=/usr/
local/dspace'
$ x=/usr/local/dspace
$
On 17/08/2009, at 9:46 AM, Kim Shepherd wrote:
I assume this is to do with database schema rather than metadata
registry schema, so it probably isn't relevant.. sorry if I didn't
explain what I meant by 'schema' very well. If you inspect your
metadatafieldregistry table, you'll see
6 matches
Mail list logo
