On Fri, Aug 23, 2013 at 5:51 PM, Javier Távara <email@example.com> wrote:
> I use DSpace 3.1 and XMLUI, all was going right until we released to publicNo solution yet, but here's something for starters. This describes how
> (only changing DNS).
to read this type of error: .
> # V [libjvm.so+0x679cf3] JVM_RaiseSignal+0xdd033
> # V [libjvm.so+0x69732d] MachNode::in_RegMask(unsigned int) const+0x3dSo according to  it seems the crash is in a a library that's part
of JRE (libjvm.so). Nevertheless, I'm suspicious of the fact that two
different flavours of JRE are crashing in the same library - I
wouldn't rule out error in application yet.
I'd start with obvious stuff
* Did you give Tomcat enough memory? Insufficient memory could cause
crashes. See .
* You said this occurred after you changed DNS record to point to DSpace:
a) did you change dspace.hostname, dspace.baseUrl and dspace.url to
the new domain name and restart Tomcat?
b) otherwise the crash might have been caused by a spike in traffic
when actual live requests started hitting your new DSpace
Compulsory reading: DSpace Mailing List Etiquette