"Communications link failure" Error with JIRA User Management on MySQL
プラットフォームについて: Data Center のみ。 - この記事は、 Data Center プラットフォーム。
この KB は Data Center バージョンの製品用に作成されています。Data Center 固有ではない機能の Data Center KB は、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。 Server* 製品のサポートは 2024 年 2 月 15 日に終了しました。Server 製品を実行している場合は、 アトラシアン Server サポート終了 のお知らせにアクセスして、移行オプションを確認してください。
*Fisheye および Crucible は除く
要約
症状
atlassian-confluence.log に次のエラーが返される。
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
2009-03-17 09:39:46,951 FATAL [http-9080-13] [user.provider.jdbc.JDBCCredentialsProvider] handles Could not see if [<Username>] is handled
com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:
\** BEGIN NESTED EXCEPTION \**
java.net.SocketException
MESSAGE: Broken pipe
STACKTRACE:
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2692)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2621)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1552)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1666)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2994)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:936)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1030)
診断
This applies to the following condition:
Using MySQL database
Using JIRA User management
When logging into Confluence, the users are randomly/intermittently denied entry with an invalid username/password error. The same user can log in successfully into JIRA at the same time
The user can be locked out/denied login intermittently, with the time ranging from a few minutes to up to 2 hours
トラブルシューティング
Checked that the
?autoconnect=trueparameter has been set for both Confluence and Jira connection URL, but the problem persistsThis is not a session timeout problem, as the user should be allowed to log in after the first login for the day
Adding the Validation query parameter, to help survive closed DB connections, does not help
原因
MySQL connections are getting terminated by MySQL before they have been released by the connection pool. Then the next time you try to get a connection from the pool, you'll get a dead connection which will give a "broken pipe" error, as noted in the stack trace above.
ソリューション
ソリューション
Evict the idle session before MySQL does. Retrying the connection will simply create a new connection. The following parameters can be added to the JIRA datasource connection URL in Confluence's server.xml for the same:
minEvictableIdleTimeMillis=21600000 (evict after 6 hours of inactivity, given that MySQL has a default timeout of 8 hours for idle database connections after which it closes the connection)
timeBetweenEvictionRunsMillis=1800000 (run the evicter every 30 minutes)
numTestsPerEviction=-1 (check every connection)
この内容はお役に立ちましたか?