That's an awful lot of processes. Quite possibly a problem with the
driver you are using ... It's not very well rated.
If you want some advice, try using a non-DBCP pool (C3P0)
sourceforge.net/projects/c3p0, and also the best SQL Server driver out
there which is at jtds.sourceforge.net.
Add both c3p0 and jtds jars to your common/lib and redefine your
Resource as follows;
<Resource
name="jdbc/dbase"
auth="Container"
driverClass="net.sourceforge.jtds.jdbc.Driver"
minPoolSize="25" maxPoolSize="50"
acquireIncrement="1"
user="sa" password="Abuja5^"
factory="org.apache.naming.factory.BeanFactory"
type="com.mchange.v2.c3p0.ComboPooledDataSource"
jdbcUrl="jdbc:jtds:sqlserver://localhost:1433/dbase"
/>
Restart SQL Server and Tomcat and see how you get on.
Allistair.
-----Original Message-----
From: Kamalmeet Singh [mailto:[EMAIL PROTECTED]
Sent: 28 November 2005 12:12
To: Tomcat Users List
Subject: Tomcat stops responding
Hi,
I am facing a problem with tomcat 5.5. After working smoothly for
sometime(3-4 days), the server stopped working and resumed only after a
Tomcat restart. It stopped connecting to database. The same behavior was
observed twice.
The exception thrown was:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at
com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at
com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown
Source)
at
com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown
Source)
at
org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(Dri
verConnectionFactory.java:37)
at
org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(Poolabl
eConnectionFactory.java:290)
at
org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.borrowObject(GenericO
bjectPool.java:771)
at
org.apache.tomcat.dbcp.dbcp.AbandonedObjectPool.borrowObject(AbandonedOb
jectPool.java:74)
at
org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataS
ource.java:95)
I am using settings in my ROOT.xml
<Resource name="jdbc/dbase" auth="Container" type="javax.sql.DataSource"
username="user" password="pass"
driverClassName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
url="jdbc:microsoft:sqlserver://localhost:1433;databaseName=dbase"
maxActive="5000" maxIdle="10000" maxWait="100" removeAbandoned="true"
removeAbandonedTimeout="2"/>
Additional info: In both cases the common thing was, that in SQL server
under management/process info I could see more than 3500 processes
connected to the database from tomcat, but in sleeping mode. (not sure
this has anything to do with problem).
also, I am using Tomcat as Apache module using mod_jk
I cannot make out anything of this, why suddenly server stops connecting
to database. Any ideas about the problem?
Regards
Kamal
<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE>
-------------------------------------------------------
QAS Ltd.
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT> <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLACK>
Disclaimer: The information contained within this e-mail is confidential and
may be privileged. This email is intended solely for the named recipient only;
if you are not authorised you must not disclose, copy, distribute, or retain
this message or any part of it. If you have received this message in error
please contact the sender at once so that we may take the appropriate action
and avoid troubling you further. Any views expressed in this message are those
of the individual sender. QAS Limited has the right lawfully to record,
monitor and inspect messages between its employees and any third party. Your
messages shall be subject to such lawful supervision as QAS Limited deems to be
necessary in order to protect its information, its interests and its
reputation.
Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS
Limited cannot guarantee that attachments are virus free or compatible with
your systems and does not accept any liability in respect of viruses or
computer problems experienced.
</FONT>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
