Bug #50288 NPE in invalidateCurrentConnection()

Submitted: 12 Jan 2010 19:57 Modified: 15 Jan 2010 10:20
Reporter: Todd Farmer (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / J Severity:S2 (Serious)
Version:5.1.10 OS:Any
Assigned to: Todd Farmer CPU Architecture:Any

[12 Jan 2010 19:57] Todd Farmer
Description:
NPE stack trace:

Mon Jan 11 21:44:14,550 GMT+00:00 2010 [cds.Root,45] SEVERE <0472> Exception

java.lang.NullPointerException: (no message provided)

at
com.mysql.jdbc.LoadBalancingConnectionProxy.invalidateCurrentConnection(LoadBalancingConnectionProxy.java:289)

at
com.mysql.jdbc.LoadBalancingConnectionProxy.dealWithInvocationException(LoadBalancingConnectionProxy.java:257)

at
com.mysql.jdbc.LoadBalancingConnectionProxy.invoke(LoadBalancingConnectionProxy.java:372)

How to repeat:
Review code

Suggested fix:
Check for null on return from maps.
[12 Jan 2010 20:34] Todd Farmer
Patch

Attachment: patch.txt (text/plain), 1.55 KiB.

[12 Jan 2010 22:54] Todd Farmer
Patch reviewed with Mark, pushed in r887.
[15 Jan 2010 10:20] Tony Bedford
An entry has been added to the 5.1.11 changelog:

NullPointerException sometimes occurred in invalidateCurrentConnection() for load-balanced connections.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.