Bug #26326 Driver ignores socketFactory property

Submitted:	13 Feb 2007 15:32	Modified:	22 Feb 2007 11:36
Reporter:	Drew Donaho	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / J	Severity:	S3 (Non-critical)
Version:	5.0.4	OS:	Windows (Microsoft XP)
Assigned to:	Mark Matthews	CPU Architecture:	Any

Description:
I'm trying to use Named Pipes as described in the Connector/J documentation. I set the "socketFactory" property to "com.mysql.jdbc.NamedPipeSocketFactory" in my Sun Java Application Server JDBC connection pool. Connector/J still uses the "com.mysql.jdbc.StandardSocketFactory". This works for the 3.x Connector/J versions. This bug was introduced in Connector/J 5.x.

How to repeat:
Instead of setting the "socketFactory", set "socketFactoryClassName" to "com.mysql.jdbc.NamedPipeSocketFactory". This works!

Suggested fix:
Either correct the Connector/J documentation to reflect the "socketFactoryClassName" property or change the declared field name in ConnectionProperties.java to "socketFactory".

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/19777

Hi Drew and thanks for your report. As you can see, it has already been fixed :)

A note has been added to the 5.0.5 changelog.

Page generated in 0.051 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.