SQL Server2000 Connection Pool

[pvashisht]

Hi all,
I am using SQL Server 2000. All my EJB's are stateless. When I try to insert a record I am getting the following exception
"[Microsoft][SQLServer 2000 Driver for JDBC]Can't start a cloned connection while in manual transaction mode."
But I am able to modify and delete.
Before inserting I am generating the primary key by querying a table. I am using transaction attribute required. Is this anything to do with the connection pool configuration?
If so please let me know the exact configuration as soon as possible.

Thanks in advance,
Prasanna

[innovatis]

Hello

I've got the same error. Did you find out what happened in the meantime?

Regards,
Carlo

[pbur]

Try this on the end of your URL:

;selectMethod=cursor

I think Microsoft's SQL Server driver is based off of Merant's DataDirect product and I got this exact error until I used the above fix.

Hope that helps,
Patrick

[deepoo]

Hi all,
I am migrating from jboss2.2.x to jboss3.0.x, using MS SQL SERVER2000 with jdbc-odbc bridge.But since from past one week I am stuck up with the following exception, when I try to deploy my application. Can anybody give me some help on this.The exception what I receive on the console is as follows. Your help in this regard will be very invaluable for me.
Awaiting your response in this regard.
Thanks and regards,
Pradeep
....

11:42:28,484 WARN [ServiceController] jboss.jca:service=LocalTxDS,name=SQLServerPool does not implement any Service methods
....
The mssql-service.xml reads as follows


<!-- ======================================================================-->
<!-- New ConnectionManager setup for Microsoft SQL Server 2000 driver -->
<!-- You may download the latest Microsoft JDBC driver from *Microsoft* -->
<!-- http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/MSDN-FILES/027/001/779/msdncompositedoc.xml&frame=true -->
<!-- Build jmx-api (build/build.sh all) and view for config documentation -->
<!-- ===================================================================== -->



<!-- Include a login module configuration named MSSQLDbRealm.
Update your login-conf.xml, here is an example for a
ConfiguredIdentityLoginModule:

<application-policy name = "MSSQLDbRealm">

<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
<module-option name = "principal">yourprincipal</module-option>
<module-option name = "userName">yourusername</module-option>
<module-option name = "password">yourpassword</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=SQLServerPool</module-option>
</login-module>

</application-policy>

NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
module-option name = "managedConnectionFactoryName"
must match the object name of the ConnectionManager you are configuring here.
-->
<!--uncomment out this line if you are using the MSSQLDbRealm above
MSSQLDbRealm
-->

<depends optional-attribute-name="ManagedConnectionFactoryName">
<!--embedded mbean-->


SQLServerPool



<config-property name="ConnectionURL" type="java.lang.String">jdbc:odbc:TFADB</config-property>
<config-property name="DriverClass" type="java.lang.String">sun.jdbc.odbc.JdbcOdbcDriver</config-property>
<!--set these only if you want only default logins, not through JAAS-->
<config-property name="UserName" type="java.lang.String">sa</config-property>
<config-property name="Password" type="java.lang.String"></config-property>



<!--Below here are advanced properties -->