Bug #45419 | C/J reports incorrect time since last packets | ||
---|---|---|---|
Submitted: | 9 Jun 2009 23:35 | Modified: | 23 Jun 2009 10:25 |
Reporter: | Todd Farmer (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.1-bzr | OS: | Any |
Assigned to: | Todd Farmer | CPU Architecture: | Any |
[9 Jun 2009 23:35]
Todd Farmer
[10 Jun 2009 23:43]
Todd Farmer
Fixed in r819.
[23 Jun 2009 10:25]
Tony Bedford
An entry was added to the 5.1.8 changelog: The reported milliseconds since the last server packets were received/sent was incorrect by a factor of 1000. For example, the following method call: SQLError.createLinkFailureMessageBasedOnHeuristics( (ConnectionImpl) this.conn, System.currentTimeMillis() - 1000, System.currentTimeMillis() - 2000, e, false); returned the following string: The last packet successfully received from the server was 2 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago.