Details
-
Bug
-
Resolution: Fixed
-
Critical
-
13.4.7
-
Unknown
-
N/A
-
N/A
-
Description
This happens on XWki 13.4.7 and solrsecurity 1.0.2, on a debian system (dunno the exact version). The exception in the logs is the following:
2022-03-25 00:43:14,795 [Job status serializer] WARN o.x.j.i.DefaultJobStatusStore - Failed to save job status [org.xwiki.job.DefaultJobStatus@57d57751]
java.nio.file.FileSystemException: /usr/local/tomcat/temp/status.xml11528274451048441444.tmp -> /usr/local/xwiki-workdir/jobs/status/solrsecurity/entity/stsubwiki/TestQA/T%C3%A9%C2%A3+st%CE%A6%C3%A9d+-+There+are+5+French+accents%3A+the+c%C3%A9dille+%C3%87%2C+the+accent+aigu+%C3%A9%2C+the+accent+circonflexe+%C3%A2%2C+%C3%AA%2C+%C3%AE%2C+%C3%B4%2C+%C3%BB%2C+the+accent+grave+%C3%A0%2C+%C3%A8%2C+%C3%B9+and+the+accent+tr%C3%A9ma+%C3%AB%2C+%C3%AF%2C+%C3%BC.+The+umlaut+%28%C3%A4%2C+%C3%AB%2C+%C3%AF%2C+%C3%B6%2C+%C3%BC%29/WebPreferences/status.xml: File name too long
at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:100)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:478)
at java.base/sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:267)
at java.base/java.nio.file.Files.move(Files.java:1422)
at org.xwiki.job.internal.JobStatusSerializer.write(JobStatusSerializer.java:80)
at org.xwiki.job.internal.DefaultJobStatusStore.saveJobStatus(DefaultJobStatusStore.java:363)
at org.xwiki.job.internal.DefaultJobStatusStore.access$000(DefaultJobStatusStore.java:69)
at org.xwiki.job.internal.DefaultJobStatusStore$JobStatusSerializerRunnable.run(DefaultJobStatusStore.java:151)
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)
It's not clear to me what's the importance of this issue, how this is impacting the rest of the indexation or whether it's just about a job status not being saved on disk (job status that is not used as data, as far as I know).