[MXS-285] When use maxscale-1.0.5, the java connection will not disconnect when set MaxAge. Created: 2015-07-24 Updated: 2016-01-21 Resolved: 2016-01-21 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbclient |
| Affects Version/s: | 1.0.5 |
| Fix Version/s: | 1.0.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | cai sunny | Assignee: | markus makela |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | galera | ||
| Environment: |
Linux 2.6.32-504.23.4.el6.x86_64 #1 SMP Tue Jun 9 20:57:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux |
||
| Description |
|
When use maxscale-1.0.5, the java connection will not automatically disconnect when set MaxAge. In tomcat connection pool , we set MaxAge=1200, when directly connect to DB, the connection will automatically be disconnected every 20 minutes. But use MaxScale to connect DB, the connection will always connect. |
| Comments |
| Comment by markus makela [ 2015-08-03 ] |
|
Does tomcat explicitly close the connections when MaxAge is exceeded? If the connections are not closed, adding the connection_timeout=<time> parameter should close connections once the time is exceeded. This parameter is supported starting from version 1.1. If the connections are closed by closing the socket or sending a COM_QUIT packet, this does seem to be a valid bug. |
| Comment by markus makela [ 2015-08-27 ] |
|
caisunny Could retest this with the 1.2 version of MaxScale? |
| Comment by Johan Wikman [ 2016-01-21 ] |
|
Reported for a very old version and as we have not received more information it is closed as incomplete. |