Hello Massimiliano,

As noted previously, you should look at the Tomcat Logs whenever the errors 
displayed are coming from Tomcat (and not DSpace).  It's still possible that 
DSpace is causing the error, but Tomcat's logs will contain the detailed error 
message (as it is where the failure occurred).

Depending on your operating system, the Tomcat logs may be under 
"/var/log/tomcat" or "/var/lib/tomcat/logs" or simply in a "logs" folder 
wherever you have installed Tomcat.

Tim
________________________________
From: [email protected] <[email protected]> on behalf of 
Massimiliano CILURZO <[email protected]>
Sent: Tuesday, September 10, 2019 6:39 AM
To: DSpace Technical Support <[email protected]>
Subject: Re: [dspace-tech] Re: dspace 6.3 problem loading items on mirage 2 
theme

Dear Tim,
    Which logs in particular I have to watch?
The problem happen only for mirage 2, in jspui we haven't this problem.
For the memory we have 10 GB of RAM on that machine.
It seems very strange this error because for dspace 5.6 we hadn't this problem.
If we use the original mirage 2 of dspace 6.3 we have this problem with some 
collection. if we put the mirage2 theme used on dspace 5.6 we have even some 
community that goes in error.
Thanks
Best regards
Massimiliano


Il giorno mercoledì 4 settembre 2019 22:06:48 UTC+2, Tim Donohue ha scritto:
Hello Massimiliano,

If the site is crashing on large collections, it's most likely some form of 
"out of memory error" being thrown by Tomcat (you'd want to check the Tomcat 
logs, as this level of error may not appear in the DSpace logs).  My best guess 
is you might want to consider giving your site more memory, see 
https://wiki.duraspace.org/display/DSDOC6x/Performance+Tuning+DSpace

That said, this is only a guess, as you didn't provide any information about 
how much memory you are currently allocating to Tomcat.  Additionally, as Mark 
noted, you should look closely at your log files.  Both of the messages you 
sent to this list are being reported by *Tomcat* (not DSpace).  When Tomcat 
crashes like this, you will almost always see errors reported in the Tomcat 
logs which provide better clues around what the problem may be.

Tim
________________________________
From: [email protected] <[email protected]> on behalf of 
Massimiliano CILURZO <[email protected]>
Sent: Wednesday, September 4, 2019 12:38 PM
To: DSpace Technical Support <[email protected]>
Subject: [dspace-tech] Re: dspace 6.3 problem loading items on mirage 2 theme

Someone have some suggestion for this problem?
We had deleted some collection and rebuilt it.
But some collections are too large and appears as inaccessible with xmlui 
mirage2.
With Jspui there are no problem.
Thanks
Best regards
Massimiliano

Il giorno venerdì 26 luglio 2019 15:45:34 UTC+2, Massimiliano CILURZO ha 
scritto:
Dear All,
    We have a Dspace 6.3 server. We hava upgraded the system from 5.6.
We are using mirage 2 as theme.
Now we have a problem when we try to load items only on some collection.
Especially collections with large pdf (100 MB or more) and a lot of image (400 
or more).
The system give us this error:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to 
complete your request.

Please contact the server administrator at root@localhost to inform them of the 
time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.


It seems as the system goes in time out.

Do you have some suggestions?

We have modified our dspace.cfg putting

xmlui.theme.mirage.item-list.emphasis = file

webui.browse.thumbnail.show = false

webui.preview.enabled = false

xmlui.community-list.render.full = false

Thanks

Best regards

Massimiliano

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/56c90acf-79c3-4bf1-aaf9-55d7ae95e461%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/56c90acf-79c3-4bf1-aaf9-55d7ae95e461%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/668a60e1-792a-4c76-8b71-68289c0c5443%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/668a60e1-792a-4c76-8b71-68289c0c5443%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/DM5PR22MB05728CD339B5BA12F76F628FED8C0%40DM5PR22MB0572.namprd22.prod.outlook.com.

Reply via email to