Published by exdone
Posted on August 11, 2008
If you get the following error message repeatedly when a ColdFusion page connects to a database, deselect the Maintain Connections option for the data source:
[Macromedia][Oracle JDBC Driver]Connection reset by peer: socket write error
If you do not want to deselect the Maintain Connections option for performance reasons, you can lower the Timeout setting for the data source from the default of 20 minutes to 1 or 2 minutes. This way, if your database connections are dropped by a database server event, your ColdFusion MX server will recover in 1 or 2 minutes instead of 20 minutes.
Coldfusion release notes
Connection reset by peer.
A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a restart. On a datastream socket, the connection was reset. This reset could be generated locally by the network system when it detects a connection failure, or it might be received from the remote host (in TCP terms, the remote host sent an RST packet). This error is also possible on a datagram socket; for instance, this error could result if your application sends a UDP datagram to a host, which rejects it by responding with an ICMP Port Unreachable.
Check the following: 1. Ping the remote host you were connected to. If it doesn’t respond, it might be offline or there might be a network problem along the way. If it does respond, this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again). 2. Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step). 3. Ping your local router address. If you are on a serial connection, your local router is the IP address of the host you initially logged on to using SLIP or PPP. 4. Ping a host on the same subnet as the host you were connected to (if you know of one). This will verify that the destination network is functioning. 5. Type tracert at the command prompt to determine the path to the host you were connected to. This won’t reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way.