[dspace-tech] Export Person Publications Error
Hi all,
Whenever I Login and click Researchers → Publications → Export
(Publication), I get a "There are no items to export with the selected
configuration" error message when there are clearly items to export.
Not sure what could be causing the issue, can anyone help me out with this?
Thanks
My Environment
dspaceVersion: "DSpace 7.6.1"
crisVersion: "cris-2023.02.03"
Use Docker
Traefik proxy → Angular → Dspace
Traefik proxy middleware setting
## Middlewares HTTP Headers - customHeader
-
"traefik.http.middlewares.customHeader.headers.customFrameOptionsValue=SAMEORIGIN"
- "traefik.http.middlewares.customHeader.headers.contentTypeNosniff=true"
- "traefik.http.middlewares.customHeader.headers.browserxssfilter=true"
-
"traefik.http.middlewares.customHeader.headers.referrerPolicy=strict-origin-when-cross-origin"
- "traefik.http.middlewares.customHeader.headers.stsSeconds=31536000"
- "traefik.http.middlewares.customHeader.headers.stsIncludeSubdomains=true"
- "traefik.http.middlewares.customHeader.headers.stsPreload=true"
- "traefik.http.middlewares.customHeader.headers.forceSTSHeader=true"
-
"traefik.http.middlewares.customHeader.headers.permissionsPolicy=geolocation=(),midi=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()"
-
"traefik.http.middlewares.customHeader.headers.customResponseHeaders.Content-Security-Policy-Report-Only=default-src
'self' https: data: 'unsafe-inline' 'unsafe-hashes' 'unsafe-eval';
object-src 'none';"
## Middlewares HTTP Headers - customRedirectRegex
-
"traefik.http.middlewares.customRedirectRegex.redirectregex.regex=^https://${DSPACE_REST_HOST:-localhost}/cris/rp/(.*)"
-
"traefik.http.middlewares.customRedirectRegex.redirectregex.replacement=https://${DSPACE_REST_HOST:-localhost}/lucky-search?index=legacy-id=$${1};
## Middlewares Prevent DDoS attacks - customInflightreq, customRatelimit
- "traefik.http.middlewares.customInflightreq.inflightreq.amount=100"
- "traefik.http.middlewares.customRatelimit.ratelimit.average=100"
- "traefik.http.middlewares.customRatelimit.ratelimit.burst=200"
discovery.xml setting
...
...
Dspace Log
2024-04-12 08:28:20 2024-04-12 08:28:20,462 INFO
c5a70b65-bc5f-41ac-83e6-37411c6f4666 964c07c2-de87-4186-b69d-436c9abfc6d2
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request
[GET /server/api/discover/search/objects] originated from
/entities/person/test1/publications
2024-04-12 08:28:20 2024-04-12 08:28:20,746 ERROR
c5a70b65-bc5f-41ac-83e6-37411c6f4666 964c07c2-de87-4186-b69d-436c9abfc6d2
org.dspace.discovery.utils.DiscoverQueryBuilder @
ad...@lib.ntu.edu.tw::Error in Discovery while setting up date facet
range:date facet\colon;
org.dspace.discovery.configuration.DiscoverySearchFilterFacet@e985418
2024-04-12 08:28:20 org.dspace.discovery.SearchServiceException: Error from
server at http://dspacesolr:8983/solr/search:
org.apache.solr.search.SyntaxError: Cannot parse 'author_authority:{0} AND
search.resourcetype:Item': Encountered " "}" "} "" at line 1, column 19.
2024-04-12 08:28:20 Was expecting:
2024-04-12 08:28:20 "TO" ...
2024-04-12 08:28:20
2024-04-12 08:28:20 at
org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:792)
~[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
org.dspace.discovery.FacetYearRange.calculateNewRangeBasedOnSearchIndex(FacetYearRange.java:113)
~[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
org.dspace.discovery.FacetYearRange.calculateRange(FacetYearRange.java:58)
~[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
org.dspace.discovery.SolrServiceImpl.getFacetYearRange(SolrServiceImpl.java:1692)
~[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
org.dspace.discovery.utils.DiscoverQueryBuilder.fillFacetIntoQueryArgs(DiscoverQueryBuilder.java:255)
[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
org.dspace.discovery.utils.DiscoverQueryBuilder.addFaceting(DiscoverQueryBuilder.java:442)
[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
org.dspace.discovery.utils.DiscoverQueryBuilder.buildQuery(DiscoverQueryBuilder.java:125)
[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
org.dspace.app.rest.utils.RestDiscoverQueryBuilder.buildQuery(RestDiscoverQueryBuilder.java:96)
[dspace-server-webapp-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
org.dspace.app.rest.repository.DiscoveryRestRepository.getSearchObjects(DiscoveryRestRepository.java:110)
[dspace-server-webapp-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at
[dspace-tech] Error with refresh page
Subject: Refresh webpage problem
Hi, we are having a problem with webpage response when trying to refresh a
page.
On our site when I go through the pages normally by clicking Researchers →
Publications → Filters (Type: book) the webpage response is fine, the URL
shows
"/entities/person/test1/publications?f.itemtype=book,equals=1"
But when I try to refresh the page, I get a 404 error instead.
I tried refresh on the 4Science demo site:
https://dspacecris7.4science.cloud/entities/person/andreabollini/publications?spc.page=1=Dataset,equals
and the webpage response seems to be fine
Not really sure what could be causing the problem, any help is appreciated.
My Environment
dspaceVersion: "DSpace 7.6.1"
crisVersion: "cris-2023.02.03"
Use Docker
Traefik proxy → Angular → Dspace
Traefik proxy middleware setting
## Middlewares HTTP Headers - customHeader
-
"traefik.http.middlewares.customHeader.headers.customFrameOptionsValue=SAMEORIGIN"
- "traefik.http.middlewares.customHeader.headers.contentTypeNosniff=true"
- "traefik.http.middlewares.customHeader.headers.browserxssfilter=true"
-
"traefik.http.middlewares.customHeader.headers.referrerPolicy=strict-origin-when-cross-origin"
- "traefik.http.middlewares.customHeader.headers.stsSeconds=31536000"
- "traefik.http.middlewares.customHeader.headers.stsIncludeSubdomains=true"
- "traefik.http.middlewares.customHeader.headers.stsPreload=true"
- "traefik.http.middlewares.customHeader.headers.forceSTSHeader=true"
-
"traefik.http.middlewares.customHeader.headers.permissionsPolicy=geolocation=(),midi=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()"
-
"traefik.http.middlewares.customHeader.headers.customResponseHeaders.Content-Security-Policy-Report-Only=default-src
'self' https: data: 'unsafe-inline' 'unsafe-hashes' 'unsafe-eval';
object-src 'none';"
## Middlewares HTTP Headers - customRedirectRegex
-
"traefik.http.middlewares.customRedirectRegex.redirectregex.regex=^https://${DSPACE_REST_HOST:-localhost}/cris/rp/(.*)"
-
"traefik.http.middlewares.customRedirectRegex.redirectregex.replacement=https://${DSPACE_REST_HOST:-localhost}/lucky-search?index=legacy-id=$${1};
## Middlewares Prevent DDoS attacks - customInflightreq, customRatelimit
- "traefik.http.middlewares.customInflightreq.inflightreq.amount=100"
- "traefik.http.middlewares.customRatelimit.ratelimit.average=100"
- "traefik.http.middlewares.customRatelimit.ratelimit.burst=200"
Angular Log
2024-04-12 07:54:39 1|dspace-ui | Environment extended with app config
2024-04-12 07:54:39 1|dspace-ui | dspace-angular
2024-04-12 07:54:39 1|dspace-ui | Version: 2023.02.03
2024-04-12 07:54:39 1|dspace-ui | Environment: Production
2024-04-12 07:54:39 1|dspace-ui | [HPM] Proxy created: / ->
https://cris7test/server/sitemaps
2024-04-12 07:54:39 1|dspace-ui | [HPM] Proxy created: / ->
https://cris7test/server
2024-04-12 07:54:39 1|dspace-ui | [07:54:39 GMT+0800 (Taipei Standard
Time)] Listening at http://dspace-angular:4000/
2024-04-12 07:54:46 1|dspace-ui | 7 rules skipped due to selector errors:
2024-04-12 07:54:46 1|dspace-ui |
.custom-file-input:lang(en)~.custom-file-label -> unmatched pseudo-class
:lang
2024-04-12 07:54:46 1|dspace-ui | html:lang(zh) .ntubox>div -> unmatched
pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui | html:lang(en) .ntubox>div -> unmatched
pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui | html:lang(zh) .ntubox>div:nth-child(2)
-> unmatched pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui | html:lang(en) .ntubox>div:nth-child(2)
-> unmatched pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui | html:lang(zh) .ntubox>div:nth-child(3)
-> unmatched pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui | html:lang(en) .ntubox>div:nth-child(3)
-> unmatched pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui | GET
/entities/person/test1?f.itemtype=report,equals=1 404 3140.960 ms
- -
Dspace Log
2024-04-12 08:09:23 2024-04-12 08:09:23,360 INFO unknown
09ee14dd-3697-4b40-8dfb-31580ccbb412
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request
[GET /server/api] originated from /
2024-04-12 08:09:23 2024-04-12 08:09:23,390 INFO
c5a70b65-bc5f-41ac-83e6-37411c6f4666 78aedb62-49d0-4e84-bf0a-9d53f0f44b3a
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request
[GET /server/api/authn/status] originated from /
2024-04-12 08:09:23 2024-04-12 08:09:23,406 INFO
c5a70b65-bc5f-41ac-83e6-37411c6f4666 a0d50ad1-967f-43b9-aaa1-a182465c9f85
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request
[GET /server/api/config/properties/user-agreement.enabled] originated from /
2024-04-12 08:09:23 2024-04-12 08:09:23,584 INFO
c5a70b65-bc5f-41ac-83e6-37411c6f4666 4f1b604b-1a11-4c44-a2f4-86782a951508
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request
[GET /server/api/layout/sections/search/visibleTopBarSections] originated
from /
2024-04-12
[dspace-tech] Re: Dspace index-discovery error
Hi, Thanks for the reply. We are not using any custom codes, and we weren't able to find any additional errors in the log. The DSpace version we are using is: dspaceVersion": "DSpace 7.6.1", "crisVersion": "cris-2023.02.01 Hope that clarifies it a bit. On Saturday, January 27, 2024 at 12:12:51 AM UTC+8 DSpace Technical Support wrote: > Hi, > > The error " could not initialize proxy - no Session" usually implies a > database connection or communication error. (It also can occur if you are > using custom code and the custom code has a bug where it's not contacting > the database properly...but that's less likely for most sites.) > > I'd recommend looking for additional errors just before this regarding > your database connection... or possibly a major error earlier in the logs > which resulted in an invalid database connection. Based on the details of > this error message, it's difficult to say what the cause is. But, I'd > recommend looking closer at your dspace.log and/or Tomcat logs to see if > **additional errors** exist...as they may be causing this error. > > If that doesn't help, then you should share the exact version of DSpace > you are using. It's also possible this is a bug in a specific version of > DSpace, but we'd need more information about your setup to see if someone > else can reproduce the problem. > > Tim > > On Thursday, January 25, 2024 at 9:06:51 PM UTC-6 uno...@gmail.com wrote: > >> Hi all >> >> We are getting an error every time we try to execute "/dspace/bin/dspace >> index-discovery", but not problem when executing "/dspace/bin/dspace >> index-discovery -b" >> Anyone know what the problem might be and how to resolve it? Any help is >> greatly appreciated, thanks! >> Error msg at follows: >> >> javax.persistence.PersistenceException: >> org.hibernate.LazyInitializationException: failed to lazily initialize a >> collection of role: org.dspace.content.DSpaceObject.metadata, could not >> initialize proxy - no Session >> at >> org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:154) >> at >> org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1626) >> at org.hibernate.query.Query.getResultList(Query.java:165) >> at >> org.dspace.authorize.dao.impl.ResourcePolicyDAOImpl.findValidPolicyOwners(ResourcePolicyDAOImpl.java:450) >> at >> org.dspace.authorize.ResourcePolicyServiceImpl.findValidPolicyOwners(ResourcePolicyServiceImpl.java:430) >> at >> org.dspace.authorize.AuthorizeServiceImpl.getValidPolicyOwnersActionFilter(AuthorizeServiceImpl.java:529) >> at >> org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:79) >> at >> org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:70) >> at >> org.dspace.discovery.indexobject.DSpaceObjectIndexFactoryImpl.buildDocument(DSpaceObjectIndexFactoryImpl.java:30) >> at >> org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:144) >> at >> org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:81) >> at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:185) >> at >> org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:175) >> at >> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:365) >> at >> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:352) >> at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:139) >> at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150) >> at >> org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:174) >> at >> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:151) >> at >> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) >> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:100) >> Caused by: org.hibernate.LazyInitializationException: failed to lazily >> initialize a collection of role: org.dspace.content.DSpaceObject.metadata, >> could not initialize proxy - no Session >> at >> org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:614) >> at >> org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:218) >> at >> org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:591) >> at >> org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:787) >> at >> org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:1005) >> at >>
[dspace-tech] Re: SLOR error string field too large
Thanks, we will look into it! On Tuesday, January 23, 2024 at 6:12:57 PM UTC+8 Maruan Sahyoun wrote: > I'm wondering if the content is correct. Looks like you are trying to > index content larger than 32766 but that's coming from the field > bi_2_dis_prefix. Are you sure that the content in that field is correct. > > To handle content larger than 32766 you need to change the field type in > the Solr schema. It looks like you are using a string type to hold the data > but string is limited in length. You can change to 'text' for example which > allows to handle more data. > > BR > Maruan > FileAffairs GmbH > > > Jack OE schrieb am Dienstag, 23. Januar 2024 um 08:09:09 UTC+1: > >> Hi all, >> >> We've been encountering this error with SOLR in the past few days and I >> am wondering if anyone has any a solution for it, any help is greatly >> appreciated! >> >> Remote error message: Exception writing document id >> Item-1739ff68-6dff-46ca-ad71-b8803a2a9137 to the index; possible analysis >> error: Document contains at least one immense term in >> field="bi_2_dis_prefix" (whose UTF8 encoding is longer than the max length >> 32766), all of which were skipped. Please correct the analyzer to not >> produce such terms. The prefix of the first immense term is: '[98, 114, >> 111, 119, 110, 44, 32, 112, 46, 59, 122, 104, 111, 117, 44, 32, 121, 46, >> 59, 116, 97, 110, 44, 32, 97, 46, 45, 99, 46, 59]...', original message: >> bytes can be at most 32766 in length; got 37865. Perhaps the document has >> an indexed string field (solr.StrField) which is too large >> at >> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:681) >> at >> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:266) >> at >> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:248) >> at >> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:214) >> at >> org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:177) >> at >> org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:138) >> at >> org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:156) >> at >> org.dspace.discovery.indexobject.IndexFactoryImpl.writeDocument(IndexFactoryImpl.java:151) >> at >> org.dspace.discovery.indexobject.ItemIndexFactoryImpl.writeDocument(ItemIndexFactoryImpl.java:752) >> at >> org.dspace.discovery.indexobject.ItemIndexFactoryImpl.writeDocument(ItemIndexFactoryImpl.java:81) >> at >> org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:186) >> at >> org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:175) >> at >> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:365) >> at >> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:352) >> at >> org.dspace.discovery.SolrServiceImpl.createIndex(SolrServiceImpl.java:320) >> at >> org.dspace.discovery.IndexClient.internalRun(IndexClient.java:120) >> at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150) >> at >> org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:174) >> at >> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:151) >> at >> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) >> at >> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:100) >> > -- 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/4debc16b-7098-4ae2-921d-1e58bbafdfc4n%40googlegroups.com.
[dspace-tech] Dspace index-discovery error
Hi all We are getting an error every time we try to execute "/dspace/bin/dspace index-discovery", but not problem when executing "/dspace/bin/dspace index-discovery -b" Anyone know what the problem might be and how to resolve it? Any help is greatly appreciated, thanks! Error msg at follows: javax.persistence.PersistenceException: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: org.dspace.content.DSpaceObject.metadata, could not initialize proxy - no Session at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:154) at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1626) at org.hibernate.query.Query.getResultList(Query.java:165) at org.dspace.authorize.dao.impl.ResourcePolicyDAOImpl.findValidPolicyOwners(ResourcePolicyDAOImpl.java:450) at org.dspace.authorize.ResourcePolicyServiceImpl.findValidPolicyOwners(ResourcePolicyServiceImpl.java:430) at org.dspace.authorize.AuthorizeServiceImpl.getValidPolicyOwnersActionFilter(AuthorizeServiceImpl.java:529) at org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:79) at org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:70) at org.dspace.discovery.indexobject.DSpaceObjectIndexFactoryImpl.buildDocument(DSpaceObjectIndexFactoryImpl.java:30) at org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:144) at org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:81) at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:185) at org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:175) at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:365) at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:352) at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:139) at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150) at org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:174) at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:151) at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:100) Caused by: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: org.dspace.content.DSpaceObject.metadata, could not initialize proxy - no Session at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:614) at org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:218) at org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:591) at org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:787) at org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:1005) at org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:991) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:362) at org.hibernate.loader.Loader.doList(Loader.java:2868) at org.hibernate.loader.Loader.doList(Loader.java:2850) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2682) at org.hibernate.loader.Loader.list(Loader.java:2677) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:540) at org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:400) at org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:218) at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1459) at org.hibernate.query.internal.AbstractProducedQuery.doList(AbstractProducedQuery.java:1649) at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1617) -- 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/162e92bc-01f4-4600-b2c1-e2bae0e9c921n%40googlegroups.com.
[dspace-tech] SLOR error string field too large
Hi all, We've been encountering this error with SOLR in the past few days and I am wondering if anyone has any a solution for it, any help is greatly appreciated! Remote error message: Exception writing document id Item-1739ff68-6dff-46ca-ad71-b8803a2a9137 to the index; possible analysis error: Document contains at least one immense term in field="bi_2_dis_prefix" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[98, 114, 111, 119, 110, 44, 32, 112, 46, 59, 122, 104, 111, 117, 44, 32, 121, 46, 59, 116, 97, 110, 44, 32, 97, 46, 45, 99, 46, 59]...', original message: bytes can be at most 32766 in length; got 37865. Perhaps the document has an indexed string field (solr.StrField) which is too large at org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:681) at org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:266) at org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:248) at org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:214) at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:177) at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:138) at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:156) at org.dspace.discovery.indexobject.IndexFactoryImpl.writeDocument(IndexFactoryImpl.java:151) at org.dspace.discovery.indexobject.ItemIndexFactoryImpl.writeDocument(ItemIndexFactoryImpl.java:752) at org.dspace.discovery.indexobject.ItemIndexFactoryImpl.writeDocument(ItemIndexFactoryImpl.java:81) at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:186) at org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:175) at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:365) at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:352) at org.dspace.discovery.SolrServiceImpl.createIndex(SolrServiceImpl.java:320) at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:120) at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150) at org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:174) at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:151) at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:100) -- 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/4790f396-2acc-4dd9-859b-24a8005dce68n%40googlegroups.com.
[dspace-tech] How to set up load balance?
Hi all, I discovered on this page that Shannon Searle mentioned Cambridge has set up load balance for their servers: https://wiki.lyrasis.org/display/cmtygp/DCAT+Meeting+September+2023 "Shannon Searle: Cambridge had some issues with slow connectors - they have a large self-hosted repository. They have a separate Angular interface for staff/students and another for public, a separate solr server and two backend tomcat servers with a round-robin load balance" How did they achieve load balance and how would I go about setting it up? Any help is appreciated Thanks Jack -- 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/40f324d6-520f-4c1e-9968-9f38eafad4e1n%40googlegroups.com.
