When executing a stored procedure or any query, for that matter the response from the SQL Server is serialized in the same order it is executed in: Sometimes is during ResultSet iteration, other times during query execution. In our oppinion this is better than having a benchmark of our own, which could be designed in such a way as to give jTDS the edge. In case you are wondering if this is right, this is a quote from the CallableStatement API documentation: Once I changed the NIC settings and got it right, the problem went away entirely. I have posted this at StackOverflow and the Liferay forum with no responses thus far:
|Date Added:||28 April 2006|
|File Size:||56.33 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
During Glassfish setup, with create a connection pool with asadmin create-jdbc-connection-pool and asadmin create-jdbc-resource.
I’m running Windows 7 Ultimate bit. I have posted this at StackOverflow and the Liferay forum with no responses thus far: This is what happens with SQL Server-returned errors and warnings and is consistent with how other drivers handle exceptions.
In case you are wondering if this is right, this is glaassfish quote from the CallableStatement API documentation: As a conclusion the only safe multithreading scenarios are these: Batch processing using executeBatch hangs or is unreliable on Sybase.
I still can’t use the JNDI name; the deployment freezes at: I appear to have resolved the problem. I spoke too soon. This is caused by triggers; replication is also implemented through triggers, so you will encounter this issue on replicated databases too.
To Install and Configure Microsoft SQL (Sun GlassFish Web Space Server Installation Guide)
Am I misunderstanding how the pooling works? I set up a command window with a ping command from one of the worker machines pinging the database server and could see the packet loss periodically. In the server log I see an SQL error:.
Here are the results of the i-net test: The datasource is stored on a static variable. When executing a stored procedure or any query, for that matter the gassfish from jgds SQL Server is serialized in the same order it is executed in: Sign up or log in Sign up using Google. Until telnet doesn’t connect, jTDS won’t either. So for procedures returning ResultSet s you will have to loop, consuming all results before reading the output parameters i.
In very rare cases 7 times during an hour we get this exception: If you are getting this in an application, start your application with.
This Managed Connection is not valid as the phyiscal connection is not usable at com. CallableStatement output parameter getter throws java.
Cannot allocate more connections. There are several articles about on the internet that discuss this problem.
However, you can run any of the benchmarks yourself, the effort is minimal. Memory usage keeps increasing when using generated PreparedStatements.
Glassfish example source code file (microsoft_jtds_datasource.xml)
All of my machines were brand new servers and all the network cards were set to auto-sense the network speed. Can jTDS be used in a multi threaded application? Because of the nature fo my final configuration, it is necessary for me to install GlassFish and then deploy Liferay. For queries that return multiple results the JDBC spec requires execute to be used.
This means among other things that it cannot access platform-specific features, such as determining the currently logged user and his credentials. Glawsfish should I do?