JabRef unable to fetch from DOI

Help
1

Starting a day or two ago JabRef suddenly stopped working with DOI.

ISBN appears to work fine. DOI produces “Connection Error” for any new entry.

If I go to any existing entry and Get bibliographic data from ISBN, this works fine.

If I go to any existing entry and Get bibliographic data from DOI, I get Unhandled Exception Occurred,
and show details reveals:

org.jabref.logic.importer.FetcherException: Connection error
at org.jabref@5.3.60000/org.jabref.logic.importer.fetcher.DoiFetcher.performSearchById(Unknown Source)
at org.jabref@5.3.60000/org.jabref.gui.mergeentries.FetchAndMergeEntry.lambda$fetchAndMerge$0(Unknown Source)
at org.jabref@5.3.60000/org.jabref.gui.util.BackgroundTask$1.call(Unknown Source)
at org.jabref@5.3.60000/org.jabref.gui.util.DefaultTaskExecutor$1.call(Unknown Source)
at org.jabref.merged.module@5.3.60000/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Server returned HTTP response code: 504 for URL: https://api.crossref.org/v1/works/10.1039%2Fc2ee90018a/transform
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
at org.jabref@5.3.60000/org.jabref.logic.net.URLDownload.asString(Unknown Source)
at org.jabref@5.3.60000/org.jabref.logic.net.URLDownload.asString(Unknown Source)
… 11 more
Caused by: java.io.IOException: Server returned HTTP response code: 504 for URL: https://api.crossref.org/v1/works/10.1039%2Fc2ee90018a/transform
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.base/java.net.HttpURLConnection.getResponseCode(Unknown Source)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
at org.jabref@5.3.60000/org.jabref.logic.net.URLDownload.openConnection(Unknown Source)
… 13 more

Please can somebody help. I am working on Windows 11. I have installed JDK 17, followed by JabRef 3.5. I have manually allowed JabRef through Windows firewall. I am totally at a loss.
Thank you.

2

Crossref seems to have outages:

https://status.crossref.org/

Not sure if Jabref can help in solving this.

DOI’s are registered with certain providers. Jabref queries doi.org that then redirects to the provider the DOI is registered at. Seems like the DOI you entered was registered with Crossref and Crossref is having an outage.

3

Maybe this is also relevant:

“Scheduled - On 2021 October 13 (Crossref Status - Content negotiation switchover to REST API - Wednesday, 13 October), we made backend changes to our content negotiation (Content negotiation - Crossref) service to route all valid requests to our REST API. On Wednesday, 2021 December 1, we will be shutting down the decommissioned content negotiation service. Requests made according to the specification (DOI Content Negotiation) should be unaffected.”

1 Like
4

Ahhh, that probably explains it. Many thanks for a knowledgeable reply which eased my mind no end. I shall keep monitoring status.crossref.org and being patient.

1 Like
5

Seems like they were also affected by the global AWS outage…

1 Like
6

JabRef all working again now :raised_hands: :grinning:. Clearly my problems were due to problems at Crossref (latterly AWS related), which their status page says are now resolved. Many thanks for all your helpful and insightful replies, it has been a privilege. This place rocks.

2 Likes