Datacite Connection timed out

[Maylein, Leonhard]

Dear Dataverse-Community,

Recently, we have increasingly observed that the publish process is being canceled for new datasets. The reason is always a connection timeout in the connection to Datacite. Is this only happening to us?

Leonhard Maylein

[2024-07-18T12:37:01.029+0200] [Payara 6.2023.8] [WARNING] [] [edu.harvard.iq.dataverse.pidproviders.doi.datacite.DataCiteDOIProvider] [tid: _ThreadID=227 _ThreadName=__ejb-thread-pool10] [timeMillis: 1721299021029] [levelValue: 900] [[
  modifyMetadata failed: Connection timed out
java.net.SocketException: Connection timed out
        at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:330)
        at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:355)
        at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:808)
        at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966)
        at java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:484)
        at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:478)
        at java.base/sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:70)
        at java.base/sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1461)
        at java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:1065)
        at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137)
        at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153)
        at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:280)
        at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138)
        at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
        at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
        at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
        at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:157)
        at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
        at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272)
        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)

...

[2024-07-18T12:37:01.030+0200] [Payara 6.2023.8] [WARNING] [] [edu.harvard.iq.dataverse.engine.command.impl.FinalizeDatasetPublicationCommand] [tid: _ThreadID=227 _ThreadName=__ejb-thread-pool10] [timeMillis: 1721299021030] [levelValue: 900] [[
  Failed to register the identifier doi:10.11588/data/RFGMKY, or to register a file in the dataset; notifying the user(s), unlocking the dataset]]

[Philip Durbin]

Good question. I'm not sure. If it helps, https://status.datacite.org is showing "all systems operational" with the last incident three days ago.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/17fc8ffeb8bb4f01aeb3a37627e65d8f%40ub.uni-heidelberg.de.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Maylein, Leonhard]

Hi Phil,

Thank you. I know this site. But in the past, when we had problems with other services with DOI registrations taking a long time, it also didn't show any errors. I suspect long runtimes are not recognized or tracked there.

Leo

---

Von: dataverse...@googlegroups.com <dataverse...@googlegroups.com> im Auftrag von Philip Durbin <philip...@harvard.edu>
Gesendet: Donnerstag, 18. Juli 2024 17:51
An: dataverse...@googlegroups.com
Betreff: Re: [Dataverse-Users] Datacite Connection timed out

 

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8GFTheMk1R%2BaLDy1-EW0brCrTv4nXSfJhbmjHby16UO3A%40mail.gmail.com.

[Philipp Conzett]

We've had similar issues when trying to publish datasets with many files in DataverseNO, where we use DOIs at file-level. That's why we recommend not to have more than about 300 files in one dataset.

Best, Philipp