I solved the problem thanx. This is how context file should be setup.
###########################################
<Context path="/pro_GMS" docBase="C:\Pro_GMS\server" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_pro_GMS_log." suffix=".txt" timestamp="true"/>
<Resource name="jdbc/sqlserver" auth="Container" type="javax.sql.DataSource"
/>
<ResourceParams name="jdbc/pro_GMS">
<parameter>
<name>maxWait</name>
<value>5000</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>4</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:jtds:sqlserver://10.0.3.112:1433;DatabaseName=ProGMS;SelectMetho
d=cursor</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>net.sourceforge.jtds.jdbc.Driver</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>2</value>
</parameter>
<parameter>
<name>username</name>
<value>sa</value>
</parameter>
<parameter>
<name></name>
<value></value>
</parameter>
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
</ResourceParams>
</Context>
#########################################
-----Original Message-----
From: [email protected]
[mailto:[EMAIL PROTECTED] Behalf Of Bruce Stewart
Sent: Friday, November 18, 2005 1:39 PM
To: [email protected]
Subject: [CTJUG Forum] Re: JDBC Sql deadlock Error
Can't help on the factory stuff, but I don't think
"com.microsoft.jdbcx.sqlserver.SQLServerDataSource" should be in your config
if you're using jtds.
Look at http://jtds.sourceforge.net/faq.html#urlFormat
Database name should be part of the url:
jdbc:jtds:sqlserver://10.0.3.112/ProGMS;SendStringParametersAsUnicode=false;
prepareSQL=2;lastUpdateCount=true
-----Original Message-----
From: mogammad noordien [mailto:[EMAIL PROTECTED]
Sent: 18 November 2005 12:23
To: [email protected]
Subject: [CTJUG Forum] Re: JDBC Sql deadlock Error
I have changed the isolationlevel on the query that gives the deadlock
problem.
I just need to test it to see if the problem still comes up, since it
happens intermittently.
I cant seem to get the jdts driver working though. this is wot my database
configuration file looks like :
<Context path="/pro_GMS" docBase="C:\Pro_GMS\server" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_pro_GMS_log." suffix=".txt" timestamp="true"/>
<Resource name="jdbc/pro_GMS" auth="Container"
type="com.microsoft.jdbcx.sqlserver.SQLServerDataSource"/>
<ResourceParams name="jdbc/pro_GMS">
<parameter><name>factory</name>
<value>net.sourceforge.jtds.jdbcx.JtdsObjectFactory</value></parameter>
<parameter><name>driverClassName</name><value>net.sourceforge.jtds.jdbcx.Jtd
sDataSource</value></parameter>
<parameter><name>driverName</name><value>JDTS Driver</value></parameter>
<parameter><name>description</name><value>SQL Server
DataSource</value></parameter>
<parameter><name>serverName</name><value>10.0.3.112</value></parameter>
<parameter><name>portNumber</name><value>1433</value></parameter>
<parameter><name>selectMethod</name><value>cursor</value></parameter>
<parameter><name>databaseName</name><value>ProGMS</value></parameter>
<parameter><name>user</name><value>sa</value></parameter>
<parameter><name>password</name><value></value></parameter>
<parameter><name>loginTimeout</name><value>3000</value></parameter>
</ResourceParams>
</Context>
- i had the database factory parameter specified as
'org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory'
but that gave me a classnotfoundexception.
Do you have any ideas ???
This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to which they are addressed.
If you have received this e-mail in error please notify NSFAS immediately.
Please note that any views or opinions presented in this e-mail are solely
those of the author and do not necessarily represent those of the
organisation.
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.3/174 - Release Date: 11/17/2005
