Bug #46637 CommunicationsException has bad message when no packets received by server

• Submitted: 10 Aug 2009 20:56
• Modified: 16 Sep 2009 16:00
• Reporter: Mark Matthews
• Status: Closed
• Category: Connector / J
• Severity: S3 (Non-critical)
• Version: 5.1
• OS: Any
• CPU Architecture: Any

[10 Aug 2009 20:56] Mark Matthews

Description:
When the driver encounters an error condition that causes it to create a CommunicationsException, it tries to build a friendly error message that helps diagnose what is wrong.

However, if there has been no network packets received from the server, the error message contains this bogus text:

"The last packet successfully received from the server was 1,249,932,468,916 milliseconds ago.  The last packet sent successfully to the server was 0 milliseconds ago."

How to repeat:
By inspection.

Suggested fix:
Don't calculate a delta from "now", if no packet(s) have ever been received from the server.

[10 Aug 2009 21:03] Mark Matthews

Fixed for 5.1.9.

[16 Sep 2009 16:00] Tony Bedford

An entry was added to the 5.1.9 changelog:

When Connector/J encountered an error condition that caused it to create a CommunicationsException, it tried to build a friendly error message that helped diagnose what was wrong. However, if there had been no network packets received from the server, the error message contained the following incorrect text:

The last packet successfully received from the server was 1,249,932,468,916 milliseconds
ago.  The last packet sent successfully to the server was 0 milliseconds ago.