aspose file tools*
The moose likes JDBC and the fly likes any known jtds jdbc driver problems? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC
Bookmark "any known jtds jdbc driver problems?" Watch "any known jtds jdbc driver problems?" New topic
Author

any known jtds jdbc driver problems?

graham king
Ranch Hand

Joined: Dec 30, 2004
Posts: 133
Hi,

I was wondering if anyone has come across any problems using the jtds jdbc driver classes?

i liked the idea of finally updating to a higher level of jdbc code by using jtds. but, i don't like not knowing its performance capabilities nor it's overall behavior. on my dev machine's it seems fine, but, in production there appears to be a problem; one application server is locking up we don't have the slightest clue as to why.

by locking up i mean that the application server looses the ability to talk to the database.

being the newest developer within the bunch, they like to joke and say it's gotta be something that i've done. they only thing i could think of is the switch to the jtds driver classes?

are there known methods on how to trace memory usage?

could someone give me suggestions on ways to debug such a situation.

Thanks,

graham


write, revise, re-write, revise, again...<br />write, revise, re-write, revise, again...
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 42264
    
  64
by locking up i mean that the application server looses the ability to talk to the database.

Tell us a little more about what that means. Are you using a connection pool? Connections can go stale (i.e., become unusable), so they should be cycled (closed and reopened) every so often, maybe after 5 minutes of being idle.


Ping & DNS - my free Android networking tools app
graham king
Ranch Hand

Joined: Dec 30, 2004
Posts: 133
Ulf,

We're using SilverStream and connecting to a SQLServer. SilverStream, supports Connection pooling. So, basically we ask for a Connection from the pool and return it back by saying Connection.close();...

That aspect of production is only accessible via SS right now. The problem existed before, but, through basic controls, i.e. restarting the server each week, we've been able to maintain a dependable environment.

We're in the process of moving away from SS and onto JBoss . I develop a maintenance piece. This is on JBoss and connecting to the same SQLServer. I had just recently switched to Jtds about a month ago; basically I liked the convience of some of their methods. Today, I came in and went to check if JBoss was still connecting and did find that one of the cached resources had been closed.

I gotta connection reset by peer. Since I look up the resources myself I can usually detect when a cached connection has been reset and then recache a new one, but, reading the server.log I found that wasn't the case with Jtds.

So, just outta paranoia I have to believe that maybe these classes are causing some new problem. I've removed the net.sourceforge.jtds.jdbcx.JtdsDataSource classes and reverted back to the com.microsoft.jdbc.sqlserver.SQLServerDriver classes just to see if there might possibly be a link.

Graham
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: any known jtds jdbc driver problems?