Dear Tim,
I have seen that in the log directory of tomcat the only file that is
modified is localhost_access_log
66.249.64.8 - - [17/Sep/2019:09:51:44 +0200] "GET
/xmlui/themes/Mirage2/vendor/BookReader/BookReaderJSSimple.js HTTP/1.1" 404
16300
66.249.64.8 - - [17/Sep/2019:09:51:45 +0200] "GET
/xmlui/themes/Mirage2/vendor/BookReader/jquery.ui.ipad.js HTTP/1.1" 404
16288
66.249.64.10 - - [17/Sep/2019:09:51:46 +0200] "GET
/xmlui/themes/Mirage2/vendor/BookReader/dragscrollable.js HTTP/1.1" 404
16288
66.249.64.10 - - [17/Sep/2019:09:51:47 +0200] "GET
/xmlui/themes/Mirage2/vendor/BookReader/jquery-ui-1.8.5.custom.min.js
HTTP/1.1" 404 16244
66.249.64.10 - - [17/Sep/2019:09:51:48 +0200] "GET
/xmlui/themes/Mirage2/vendor/BookReader/BookReader.js HTTP/1.1" 404 16196
66.249.64.10 - - [17/Sep/2019:09:51:49 +0200] "GET
/xmlui/themes/Mirage2/vendor/BookReader/jquery-ui-1.8.5.custom.min.js
HTTP/1.1" 404 16244
127.0.0.1 - - [17/Sep/2019:09:52:11 +0200] "POST
/solr/statistics/update?wt=javabin&version=2 HTTP/1.1" 200 40
127.0.0.1 - - [17/Sep/2019:09:52:13 +0200] "POST /solr/search/select
HTTP/1.1" 200 449
Th cocoon.log is this
2019-09-17 09:47:33,209 WARN cocoon.access -
org.apache.catalina.connector.ClientAbortException: java.io.IOException:
Pipe interrotta
2019-09-17 09:47:33,209 INFO cocoon.access - 'handle/10556/2949'
Processed by Apache Cocoon in 2.0272 minutes.
As if the system goes in timeout the answer is "Service Unavailable" The
server is temporaly unable to service your request due to maintance
downtime or capacity problems. Please try again later.
I have followed even this https://github.com/DSpace/DSpace/pull/2130 but
nothing change.
And if I put log4j.proprieties in "DEBUG" I have this error:
unknown protocol resource.
as in https://jira.duraspace.org/browse/DS-239?src=confmacro
Thanks
Il giorno lunedì 16 settembre 2019 22:31:24 UTC+2, Tim Donohue ha scritto:
>
> 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:* dspac...@googlegroups.com <javascript:> <dspac...@googlegroups.com
> <javascript:>> on behalf of Massimiliano CILURZO <mcil...@unisa.it
> <javascript:>>
> *Sent:* Tuesday, September 10, 2019 6:39 AM
> *To:* DSpace Technical Support <dspac...@googlegroups.com <javascript:>>
> *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:* dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf
> of Massimiliano CILURZO <mcil...@unisa.it>
> *Sent:* Wednesday, September 4, 2019 12:38 PM
> *To:* DSpace Technical Support <dspac...@googlegroups.com>
> *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 dspac...@googlegroups.com.
> 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 dspac...@googlegroups.com <javascript:>.
> 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 dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/6f72be27-e7ec-4023-a021-40bd5ddf0d97%40googlegroups.com.
