1 message in com.mysql.lists.javaMySQL 4.1.1 crashes with named pipe
FromSent OnAttachments
Peter Schäfer25 Jan 2004 02:39 
Subject:MySQL 4.1.1 crashes with named pipe
From:Peter Schäfer (pete@ecosx.de)
Date:01/25/2004 02:39:34 AM
List:com.mysql.lists.java

Using MySQL 4.1.1-alpha for Windows, Connector/J 3.1 nightly,

The server is started with “--enable-named-pipe”, connection is attempted with “socketFactory=com.mysql.jdbc.NamedPipeSocketFactory”.

Any connection attempt will crash the server process. Connector/J reports:

com.mysql.jdbc.CommunicationsException: The last communications with the server was 1075026536 seconds ago, which may or may not be greater than the server-side timeout (the driver was unable to determine the value of either the 'wait_timeout' or 'interactive_timeout' configuration values from the server.. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. at com.mysql.jdbc.Connection.createNewIO(Connection.java:1462) at com.mysql.jdbc.Connection.<init>(Connection.java:348) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:21 8) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:140) I guess that this is a bug in the server.

By the way, can I use “shared memory” with Connector/J ? It’s mentioned in the 4.1.1 docs, but I’ve no idea how to set it up

Regards, Peter