Details
-
Bug
-
Resolution: Solved By
-
Major
-
None
-
Unknown
-
N/A
-
N/A
-
Description
I just obtained the following error when trying to access notifications on xwiki.org:
org.xwiki.rendering.RenderingException: Error while retrieving the event status at org.xwiki.notifications.notifiers.internal.DefaultAsyncNotificationRenderer.render(DefaultAsyncNotificationRenderer.java:143) at org.xwiki.rendering.async.internal.AsyncRendererJob.runInternal(AsyncRendererJob.java:101) at org.xwiki.job.AbstractJob.runInContext(AbstractJob.java:246) at org.xwiki.job.AbstractJob.run(AbstractJob.java:223) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: org.xwiki.eventstream.EventStreamException: Failed to execute Solr query at org.xwiki.eventstream.store.solr.internal.SolrEventStore.getEventStatuses(SolrEventStore.java:428) at org.xwiki.eventstream.internal.DefaultEventStore.getEventStatuses(DefaultEventStore.java:439) at org.xwiki.notifications.internal.DefaultCompositeEventStatusManager.getEventStatuses(DefaultCompositeEventStatusManager.java:82) at org.xwiki.notifications.internal.DefaultCompositeEventStatusManager.getCompositeEventStatuses(DefaultCompositeEventStatusManager.java:69) at org.xwiki.notifications.notifiers.internal.DefaultAsyncNotificationRenderer.render(DefaultAsyncNotificationRenderer.java:138) ... 6 more Caused by: org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://92.222.135.242/solr/xwiki_events: Expected mime type application/octet-stream but got text/html. <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>414 Request-URI Too Long</title> </head><body> <h1>Request-URI Too Long</h1> <p>The requested URL's length exceeds the capacity limit for this server.<br /> </p> <hr> <address>Apache/2.4.56 (Debian) Server at xwikiorg-search.xwikisas.com Port 80</address> </body></html>
I suspect a problem because of the number of events for which to retrieve a status. So it's probably a bug to fix in the product...
Attachments
Issue Links
- is caused by
-
-
- Closed
-