[MXS-3122] Tmeout 600 seconds for Java application while connecting via MaxScale Created: 2020-08-21  Updated: 2021-08-20  Resolved: 2021-08-20

Status: Closed
Project: MariaDB MaxScale
Component/s: galeramon, readwritesplit
Affects Version/s: 2.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Valerii Kravchuk Assignee: markus makela
Resolution: Cannot Reproduce Votes: 0
Labels: None


 Description   

Application gets the following timeouts after 600 seconds while working via readwritesplit with 3 nodes Galera cluster back end:

2020 Jun 28 08:55:10:094 GMT +0200 BW.BusinessConnect-Interior_Server-1 Error [bw.logger] BW-EXT-LOG-100000  com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
 
The last packet successfully received from the server was 600 027 milliseconds ago.  The last packet sent successfully to the server was 600 028 milliseconds ago.
        at sun.reflect.GeneratedConstructorAccessor130.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
        at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
        at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:983)
        at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3644)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2452)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2550)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
        at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962)
        at com.tibco.ax.fw.util.cfgix.jasper.JasperFlattenBlobs.getCSStructuredStatus(JasperFlattenBlobs.java:679)
        at com.tibco.ax.fw.util.cfgix.jasper.JasperFlattenBlobs.jasperPoller(JasperFlattenBlobs.java:994)
        at com.tibco.ax.fw.runtime.poller.jasper.JasperPoller.onPollEvent(JasperPoller.java:61)
        at com.tibco.ax.fw.runtime.poller.Poller.pollEvent(Poller.java:86)
        at sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.tibco.plugin.gateway.PollerServiceActivity.invokeOp(PollerServiceActivity.java:198)
        at com.tibco.plugin.gateway.PollerServiceActivity.access$000(PollerServiceActivity.java:41)
        at com.tibco.plugin.gateway.PollerServiceActivity$PollerThread.execute(PollerServiceActivity.java:363)
        at com.tibco.plugin.gateway.PollerServiceActivity$PollerThread.execute(PollerServiceActivity.java:357)
        at com.tibco.ax.fw.util.ThreadPool$ManagedThread.run(ThreadPool.java:270)
Caused by: java.net.SocketException: Connection reset
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:115)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3626)
        ... 17 more

None of the explicitly defined timeouts is set to 600 seconds, neither at MaxScale nor at MariaDB level. Why these errors happen?



 Comments   
Comment by markus makela [ 2021-08-20 ]

Closing as Cannot Reproduce. Testing whether this happens with 2.4 or 2.5 would help identify if this was already fixed in a newer release.

Generated at Thu Feb 08 04:19:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.