I am working on a java application that uses sybase. It employs an in-
house database connection pool which uses the Connection.isClosed
method for checking to see if a connection is valid still.
Occasionally this call hangs on a blocking socket read. I am trying to
find out why.
I see from sp_configure that a maximum of 2000 concurrent sessions are
allowed. Over the course of a day the number of sessions taken by this
app gets close to 1000. Can anyone think of specific reasons why this
might be a problem?
Some on our project has said there will be no problem until that limit
is reached then the client will get an error when trying to get a new
connection. The attempt would be rejected, presumably with an error
along the lines of maximum number of connections reached.
Someone else on the project said they had heard that sybase can have
problems when the connection limit is large and reaches half its
configured value, which is the situation I have.
Regards,
Andrew Marlow
