In a large library (about 17,000 files), the search stopped working in the latest build.

[NeymanDmitry]

JabRef version

Latest development branch build (please note build date below)

Operating system

GNU / Linux

Details on version and operating system

Ubuntu 24.04.3

Checked with the latest development build (copy version output from About dialog)

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. ...
2. ...
3. ...

Appendix

...

Log File

Paste an excerpt of your log file here

[NeymanDmitry]

JabRef 6.0-alpha2.809--2025-09-27--32a9a68
Linux 6.14.0-32-generic amd64
Java 24.0.2
JavaFX 25+29

Indexing of bibliographic fields is not completed when the library starts. It reaches approximately 20 percent and then abruptly ends, as if it had been completed completely.

Naturally, the program finds nothing when searching for most entries.

When attempting to search for unindexed files, the operating system sometimes terminates abnormally.

I've previously reported problems with searching in Jabref when using full-text search #13048, but now even regular search stops working.

[koppor]

@NeymanDmitry Could you maybe run with --debug?`(See https://docs.jabref.org/advanced/commandline#debug-mode-debug). Maybe, we have some logs saying why something went wrong.

I assume that some exception is going on during inserting into the SQL database - and then the search thread stops. We need to find out, which thing it is.

[NeymanDmitry]

log_2025-09-30_20-48-53.txt

[Siedlerchr]

2025-09-30 20:49:10 [JavaFX Application Thread] org.jabref.gui.util.UiTaskExecutor.convertToException()
WARN: Converting throwable to Exception: java.time.DateTimeException: Invalid value for MonthOfYear (valid values 1 - 12): 2017
	at java.base/java.time.temporal.TemporalAccessor.get(TemporalAccessor.java:224)
	at org.jabref.jablib/org.jabref.model.entry.Date.get(Date.java:360)
	at org.jabref.jablib/org.jabref.model.entry.Date.getMonth(Date.java:367)
	at org.jabref.jablib/org.jabref.model.entry.BibEntry.genericGetFieldOrAlias(BibEntry.java:554)
	at org.jabref.jablib/org.jabref.model.entry.BibEntry.getFieldOrAlias(BibEntry.java:592)
	at org.jabref.jablib/org.jabref.model.entry.BibEntry.genericGetResolvedFieldOrAlias(BibEntry.java:344)
	at org.jabref.jablib/org.jabref.model.entry.BibEntry.getResolvedFieldOrAlias(BibEntry.java:328)
	at org.jabref.jablib/org.jabref.logic.search.indexing.BibFieldsIndexer.addToIndex(BibFieldsIndexer.java:255)
	at org.jabref.jablib/org.jabref.logic.search.indexing.BibFieldsIndexer.addToIndex(BibFieldsIndexer.java:182)
	at org.jabref.jablib/org.jabref.logic.search.indexing.BibFieldsIndexer.updateOnStart(BibFieldsIndexer.java:165)
	at org.jabref.jablib/org.jabref.logic.search.IndexManager$2.call(IndexManager.java:99)
	at org.jabref/org.jabref.gui.util.UiTaskExecutor$1.call(UiTaskExecutor.java:188)
	at javafx.graphics@25/javafx.concurrent.Task$TaskCallable.call(Task.java:1407)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:328)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:545)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:328)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1095)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run

[ThiloteE]

Were you able to solve this issue? We could close it, if so.

If I were to interpret the exception, it would mean that you have a year instead of a month in the month field. You should search for month = 2017 or month = {2017}, in the library file. If JabRef cannot do it, then an external text editor would be able to do the job.

[ThiloteE]

Maybe if an exception happens during the indexing, a warning should pop up? Edit: Popups are antipatterns and annoying. Better not!

[koppor]

Were you able to solve this issue? We could close it, if so.

We should have a regression test in JabRefs code base.

If we just close the issue, we will not be sure if the bug is re-appearing in a future version.

[ThiloteE]

Maybe is also something for the integrity check.