Skip to main content
A
Anonymous
June 27, 2006
Question

Coldfusion Error Really Bugging Me

  • June 27, 2006
  • 1 reply
  • 885 views
I am hosted by HOSTMYSITE and the other day i found out that they were using the old built in JDBC driver for connecting to MySql5 and as we know it doesnt work that well. So i told them and after alot of messages they created a new DSN using this new driver and every now and then i get this error. Now when i call querys and etc i gte this error. Its kind of driving me mad!!

DataSource gunixcom
Detail Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: Broken pipe STACKTRACE: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2689) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2618) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1551) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1665) at com.mysql.jdbc.Connection.execSQL(Connection.java:2978) at com.mysql.jdbc.Connection.execSQL(Connection.java:2902) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:930) at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:770) at coldfusion.server.j2ee.sql.JRunPreparedStatemen...
    This topic has been closed for replies.

    1 reply

    Q
    qtpattuti
    Participant
    July 18, 2006
    I recently had a batch of broken pipe errors as well, and here is what I found and how the issue was resolved. A broken pipe error means that the socket is being closed by the network before the handshake to the database is completed and/or re-established (if you're using a jdbc pool). On our network, the cause was a bad path to the database in the hosts file on the webservers. The only reason any connections made it through at all initially was because the database had a routing to the network where the webservers were searching for the database.

    If you're working with a hosting service, you may have a hard time getting this type of issue resolved, but I thought I'd pass along my findings. Good luck.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices