JBoss to Clustered MS SQL Server

[prandolph]

Folks-

I'm noticing something in our production environment, and I'm not sure whether it's JBoss or the MS JDBC driver or the database cluster itself. There's one JBoss machine, talking to a Compaq Win2k SQL Server cluster. When I reboot the Cluster machine that owns SQL Server, the SQL Server fails over to the other node seamlessly. But JBoss craps out, reporting (via the JDBC drivers) that there are "broken pipes". I assume that this means the JDBC driver can't figure out that it should drop it's open connections, and reconnect.

Am I missing a configuration parameter for the Pool? Does my JDBC driver suck? Other thoughts?

Thanks,
Peter

[davidjencks]

Just guessing, but I think it might be the jdbc driver. Does it claim to work with the db clustered? Does it get new connections from the failover machine successfully?

I'd write a little test and see...

I wouldn't claim it to be a solution, but it might help slightly to set a short idle timeout in the pool.

[prandolph]

I've seen the i-net software JDBC driver for SQL Server supports clustered databases. I'm going to test that today.

W/r/t your comments - is there a reference for all the different parameters that can be set in the Pool mbean?

Regards,
Peter