View Issue Details

IDProjectCategoryView StatusLast Update
0006561SymmetricDS ProBugpublic2024-08-28 17:28
Reportergilles.riand Assigned Topmarzullo  
Prioritynone 
Status closedResolutionno change required 
Product Version3.8.0 
Summary0006561: version 3.7.36 / org.eclipse.jetty.io.EofException: Early EOF
DescriptionWith only one Node impossible to push/pull

I've try with
* Change Java
* http / https

2024-08-22 14:58:29,459 WARN [mags-xxx] [DataLoaderService] [mags-xxx-pull-1] Ack was not sent successfully on try number 5. Read timed out
2024-08-22 14:58:29,459 ERROR [mags-xxx] [PullService] [mags-xxx-pull-1] An IO exception happened while attempting to pull data
java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.socketRead(Unknown Source)
    at java.net.SocketInputStream.read(Unknown Source)
    at java.net.SocketInputStream.read(Unknown Source)
    at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
    at sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
    at sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.readApplicationRecord(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.access$300(Unknown Source)
    at sun.security.ssl.SSLSocketImpl$AppInputStream.read(Unknown Source)
    at java.io.BufferedInputStream.fill(Unknown Source)
    at java.io.BufferedInputStream.read1(Unknown Source)
    at java.io.BufferedInputStream.read(Unknown Source)
    at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
    at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
    at java.net.HttpURLConnection.getResponseCode(Unknown Source)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
    at org.jumpmind.symmetric.transport.http.HttpTransportManager.sendMessage(HttpTransportManager.java:122)
    at org.jumpmind.symmetric.transport.http.HttpTransportManager.sendMessage(HttpTransportManager.java:108)
    at org.jumpmind.symmetric.transport.http.HttpTransportManager.sendAcknowledgement(HttpTransportManager.java:96)
    at org.jumpmind.symmetric.service.impl.AbstractService.sendAck(AbstractService.java:261)
    at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromPull(DataLoaderService.java:290)
    at org.jumpmind.symmetric.service.impl.PullService.execute(PullService.java:132)
    at org.jumpmind.symmetric.service.impl.NodeCommunicationService$2.run(NodeCommunicationService.java:396)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
TagsNo tags attached.

Activities

gilles.riand

2024-08-22 14:09

reporter   ~0002491

Ack was not sent successfully on try number 1. Read timed out

gilles.riand

2024-08-22 18:43

reporter   ~0002492

with a reboot everything is ok

elong

2024-08-22 18:52

developer   ~0002493

It does a HTTP GET request to pull data, then it does a HTTP POST to send the acknowledgement. It might be acknowledging several batches at once, including all the statistics for each batch. It's waiting for a HTTP 200 response from the ack, but the response doesn't return fast enough and it times out waiting. It might help to lower the max_batch_to_send for the sym_channel being used. It shouldn't take very long to update sym_outgoing_batch with status and statistics. But you could check if there is heavy load on that database. It could be the network isn't working right. I've seen read timeouts from VPN connections getting into a bad state or MTU settings on one link of the network causing packet fragmentation. See also https://support.jumpmind.com/kb/article/47-Read-Timed-Out-and-Socket-Timeout . In some cases restarting the VPN or restarting the machine gets networking into a working state.

Issue History

Date Modified Username Field Change
2024-08-22 13:16 gilles.riand New Issue
2024-08-22 14:09 gilles.riand Note Added: 0002491
2024-08-22 18:43 gilles.riand Note Added: 0002492
2024-08-22 18:52 elong Note Added: 0002493
2024-08-28 17:28 pmarzullo Assigned To => pmarzullo
2024-08-28 17:28 pmarzullo Status new => closed
2024-08-28 17:28 pmarzullo Resolution open => no change required