In any case, I tried re-installing JabRef 3.8.2, installing 3.7 instead, and re-installing. I am not entirely sure what I did last time before it stopped opening that might have caused the problem: upgraded to 3.8.2, updated Java, or both. It is visible in my task manager, but for the rest it does not open. I have manually allowed JabRef through Windows firewall. JabRef used to work fine, but suddenly it stopped opening on my Windows 10 computer.

If it takes longer than that to connect to an existing instance, chances are something else bad is going on. Here we increase that timeout to a full second. I have installed JDK 17, followed by JabRef 3.5. In some instances, connecting to an existing JabRef instance may take longer than the original 200ms timeout. FetcherException: Connection errorĪt java.base/.run(Unknown Source)Īt java.base/$RunnableAdapter.call(Unknown Source)Īt java.base/.runWorker(Unknown Source)Īt java.base/$n(Unknown Source)Īt java.base/(Unknown Source)Ĭaused by: java.io.IOException: Server returned HTTP response code: 504 for URL: Īt java.base/.newInstance0(Native Method)Īt java.base/.newInstance(Unknown Source)Īt java.base/.newInstance(Unknown Source)Īt java.base/.newInstanceWithCaller(Unknown Source)Īt java.base/.newInstance(Unknown Source)Īt java.base/(Unknown Source)Īt java.base/(Unknown Source) Yes it is on Windows (Win 7), JabRef is installed normal way and browser is part of Liberkey. If I go to any existing entry and Get bibliographic data from DOI, I get Unhandled Exception Occurred, Sorry for the delay and the lack of details. If I go to any existing entry and Get bibliographic data from ISBN, this works fine. DOI produces “Connection Error” for any new entry.

Starting a day or two ago JabRef suddenly stopped working with DOI. BLie December 12, 2018, 4:28pm 1 I use JabRef v.

Jabref error messages