[dspace-tech] [DSpace 6.3] ArrayIndexOutOfBoundsException when requesting cocoon:/admin/item/bitstreams

['Alexander Vielhauer' via DSpace Technical Support]

Dear list,

I have some items with 1,000+ bitstreams and when I edit those items as 
admin and change to "Item Bitstreams" to delete or reorder the 
bitstreams, DSpace gives me an ArrayIndexOutOfBoundsException.


The DSpace log doesn't show anything in 'INFO' mode, in 'DEBUG' mode it 
shows a lot of messages from hibernate and some from 
org.dspace.app.xmlui.cocoon.DSpaceI18NTransformer afterwards. It gets 
the texts for the table columns first (e.g. 
xmlui.administrative.item.EditItemBitstreamsForm.column1) before it 
finally gets the xmlui.error.* message texts.


The cocoon log should be more helpful, I attached the relevant snippet.

I tried setting high values for tomcat's maxPostSize and 
maxParameterCount, as I found that solve the symptom for other people 
but I guess it's a different problem here.


I am using DSpace 6.3 with xmlui.

Thanks for any pointers
Alexander

--
Alexander Vielhauer
Philipps-Universität Marburg | UB
Digitale Dienste | Deutschhausstraße 9 | D226
Tel. +49 06421 28-25290

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/bc133033-b26c-f523-a31b-20c49476c5d8%40staff.uni-marburg.de.
2021-11-17 20:08:15,577 INFO  
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor$TreeProcessorRedirector
  - Redirecting to 'cocoon:/admin/item/bitstreams'
2021-11-17 20:08:15,579 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
HIT for 
PK_G-file-file:///home/alexander/DSpace/dspace-instance/webapps/xmlui/aspects/protodocument.xml
2021-11-17 20:08:15,580 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for 
PK_G-aspect-cocoon://DRI/9/admin/item/bitstreams?pipelinehash=5418682656771414144_T-Navigation--1998771133613710815
2021-11-17 20:08:15,580 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for 
PK_G-aspect-cocoon://DRI/8/admin/item/bitstreams?pipelinehash=5975535465194916768_T-Navigation-1626669117201114516_T-HorizontalNavigation-1626669117201114516
2021-11-17 20:08:15,580 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for 
PK_G-aspect-cocoon://DRI/7/admin/item/bitstreams?pipelinehash=6521962834012231305_T-Navigation-1626669117201114516
2021-11-17 20:08:15,581 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for 
PK_G-aspect-cocoon://DRI/6/admin/item/bitstreams?pipelinehash=7883136649745533047_T-SystemwideAlerts-1_T-Navigation--5332861444251892712_T-IncludePageMeta-518716617435405932
2021-11-17 20:08:15,582 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for PK_G-aspect-cocoon://DRI/5/admin/item_T-Navigation-4582598597259495814
2021-11-17 20:08:15,583 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for PK_G-aspect-cocoon://DRI/4/admin/item_T-Navigation-1
2021-11-17 20:08:15,583 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for PK_G-aspect-cocoon://DRI/3/admin/item
2021-11-17 20:08:15,583 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for PK_G-aspect-cocoon://DRI/2/admin/item_T-Navigation--5332861444251892712
2021-11-17 20:08:15,583 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for PK_G-aspect-cocoon://DRI/1/admin/item
2021-11-17 20:08:15,584 INFO  org.apache.cocoon.caching.impl.CacheImpl  - Cache 
MISS for 
PK_G-file-cocoon://DRI/admin/item_T-xslt-file:///home/alexander/DSpace/dspace-instance/webapps/xmlui/themes/Mirage2/xsl/preprocess.xsl_T-IncludePageMeta--2183294294163301955_T-xslt-file:///home/alexander/DSpace/dspace-instance/webapps/xmlui/themes/Mirage2/xsl/theme.xsl_T-i18n-context://i18n/?de___T-strip-namespaces-1_S-html-no-doctype-;encoding=UTF-8;indent=yes
2021-11-17 20:08:31,725 INFO  org.apache.cocoon.i18n.XMLResourceBundle  - 
Bundle 

 not loaded: Source URI not found
2021-11-17 20:08:31,728 INFO  org.apache.cocoon.i18n.XMLResourceBundle  - 
Bundle  not loaded: Source 
URI not found
2021-11-17 20:08:31,729 INFO  org.apache.cocoon.i18n.XMLResourceBundle  - 
Bundle 

 not loaded: Source URI not found
2021-11-17 20:08:31,731 INFO  org.apache.cocoon.i18n.XMLResourceBundle  - 
Bundle  not loaded: Source 
URI not found
2021-11-17 20:08:31,732 INFO  org.apache.cocoon.i18n.XMLResourceBundle  - 
Bundle 

 not loaded: Source URI not found
2021-11-17 20:08:31,734 INFO  org.apache.cocoon.i18n.XMLResourceBundle  - 
Bundle  not loaded: Source 
URI not found
2021-11-17 20:08:31,735 INFO  org.apache.cocoon.i18n.XMLResourceBundle  - 
Bundle 

 not loaded: Source URI not found
2021-11-17 20:08:31,736 INFO  org.apache.cocoon.i18n.XMLResourceBundle  - 
Bundle  not loaded: Source URI 
not found
2021-11-17 20:08:31,737 INFO  

Re: [dspace-tech] DSpace index discovery not completed on DSpace 7.1

['Tim Donohue' via DSpace Technical Support]

Hi Lewatle,

I googled the error you received in your Solr log file, and found this question 
on StackOverflow:
https://stackoverflow.com/questions/68773301/solr-tomcat-integration-solrrequestparsers-couldnt-get-multipart-parts-in-o

According to that person at least, they hit the same issue with Solr 8.9. But 
after downgrading, the error disappeared.  So, it's possible there's an odd 
issue in Solr 8.9 which you are hitting.  You could try to install a different 
8.x version and see if that fixes the issue.  (Obviously you'd need to copy 
over the DSpace Solr core configs, see step 10 in the upgrade process at 
https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace)

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Lewatle Johannes Phaladi 
Sent: Wednesday, November 17, 2021 7:05 AM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] DSpace index discovery not completed on DSpace 7.1

Dear Tim and DSpace Team,

Currently we are struggling to remove solrcore initialization failure, all 
other previous upgrade known errors have been resolved. Please note that solr 
error came from out of box installation, and if anyone has ever cleared this 
error please share the suggestion, we are only waiting to re-index the site and 
complete this upgrade, please attached screenshots.

Regards,
Lewatle


--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/4cd65737-d302-4d11-9107-a23aa27f40aan%40googlegroups.com.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/DM5PR2201MB114816B52D07B5E6AB1FCF3FED9A9%40DM5PR2201MB1148.namprd22.prod.outlook.com.

Re: [dspace-tech] assetstore too large for dev instance

[paulw...@gmail.com]

Thanks very much, Sean!  Great suggestion.  I will check with my boss about 
what is possible.

Best regards,
paul

On Monday, November 15, 2021 at 4:58:50 PM UTC+1 sean.k...@umanitoba.ca 
wrote:

> Hi Paul,
>
>  
>
> Are you able to mount the production assetstore on your dev instance via 
> NFS in read-only mode? Or, if not that, use SSHFS instead?
>
>  
>
> If you can mount the remote filesystem read-only, you can adjust the 
> bitstore.xml configuration on the dev instance to have two storage 
> locations: one for the original production read-only data, and then a new 
> writeable one for dev to be used for testing. Then make sure the “incoming” 
> storage location is set to the writeable dev filesystem.
>
>  
>
> --
>
> Sean
>
>  
>
> *From: *dspac...@googlegroups.com  on behalf 
> of paulw...@gmail.com 
> *Date: *Monday, November 15, 2021 at 2:27 AM
> *To: *DSpace Technical Support 
> *Subject: *[dspace-tech] assetstore too large for dev instance
>
> *Caution:* This message was sent from outside the University of Manitoba.
>
> Hi,
>
>  
>
> We are running a DSpace instance with a very large assetstore (over 1.2 
> TB), and this is now too large for our dev instance.  We do not have enough 
> disk space.  Is there a way to strip the assetstore of content, use dummy 
> files, or otherwise empty the assetstore for the dev instance?  We sync the 
> database to the dev instance.  We are considering running the dev instance 
> on the same machine, in which case, could we use the same assetstore for 
> the dev instance?  How would we set that up?
>
>  
>
> We are using DSpace 6.3 on SUSE Linux Enterprise Server with PostgreSQL.
>
>  
>
> Thanks for any suggestions,
>
> Paul  
>
> -- 
> All messages to this mailing list should adhere to the Code of Conduct: 
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> --- 
> 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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/3808102f-27e4-4dd6-b24e-d7b38e441255n%40googlegroups.com
>  
> 
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/c0625ebf-a395-4e11-85e1-0df81cb8f197n%40googlegroups.com.

[dspace-tech] Creating Re-authentication

[akun gembell]

hello everyone, hope you are doing well

I'm using DSpace 6.3 xmlui on Windows 10
User convenience aside, I want to add re-authentication when a user wants 
to access a particular community or collection. Has anyone ever made 
something like that before, or is it possible to do? can you give me advice 
on what I should do? Any help would be very valuable for me

Thank you very much.
Best Regards

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/db27e92a-57ad-4e47-b1a4-34bc05b96610n%40googlegroups.com.

[dspace-tech] Discovery Date Range Queries (DSpace 6)

[kpet]

 Hello,

I have a DSpace 6.3 installed on a linux machine, using tomcat 9, jre 1.8, 
ant 1.10 and maven 3.3.9.

I want to be able to perform a search query via the Discovery interface on 
a date field (e.g. dc.date.available) but for a date range, for example 
objects returned should have dc.date.available between March and May of 
2021, i.e. dc.date.available >= 2021-03-01 && dc.date.available <= 
2021-05-31

I have read the documentation of Discovery on how to add custom search 
filters but the problem is I also want to add a custom relational operator, 
as in "greater than". Currently, I only see Contains, Equals, ID, Not 
Contains, Not Equals, Not ID.

Any help would be greatly appreciated.

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/6d8c8661-d9e1-4e19-a6e6-93e17277e73fn%40googlegroups.com.