ojdbc

While sending ARRAY to the stord proc we are getting java level dead locks. I am attaching the thread dump. Found one Java-level deadlock: ============================= "http-bio-8080-exec-11": waiting to lock monitor 0x00000000406fb2d8 (object 0x00000000fea1b130, a oracle.jdbc.driver.T4CConnection), which is held by "http-bio-8080-exec-4" "http-bio-8080-exec-4": waiting to lock monitor 0x00000000407d6038 (object 0x00000000fe78b680, a oracle.jdbc.driver.T4CConnection), which is held by "http-bio-8080-exec-11" Java stack information for the threads listed above: ================================

I'm running web-apps on a Tomcat7 server and having trouble undeploying them. It seems that windows keeps a lock on a particular JAR file in the application folder. I've found that there is a context attribute called "antiJARLocking" that i can set to 'true' (defined here: http://tomcat.apache.org/tomcat-6.0-doc/config/context.html#Standard_Implementation ) that may solve the problem. The fact is, i've seen a couple of people stating that i should NOT set this attribute to true in a production environment; but i can't find what are the reasons for that. I know that setting this attribute to

For inexplicable reasons however, this morning the performance increased for two of my Queries that used to be slow. I have no idea why. I have no authority over the server, maybe someone changed something. The problem is no more . In a nutshell: s.executeQuery(sql) runs extremely slowly within a tomcat servlet on server Same query runs fine without servlet (simple java program) on the same machine Not all queries are slow within the servlet. Only a few bigger ones do Same servlet runs fast on another machine UPDATES Please read the updates below the text ! I have a servlet that executes SQL

I am getting the "Protocol Violation". I have an application running on RedHat Linux.The database and the application are co-resident on the machine. Oracle version used: Oracle 11g R2 (11.2.0.3.0) JDBC Driver used: 12.1.0.1 Java used: jdk1.7.0.65 32-bit I have come across many forums where this error has been pointed out to be a driver issue but in all those forums the oracle version used was higher and the driver version were older and changing the driver resolved the issue.But in my case the Oracle version is lower but driver version is higher.So , in this case will the higher version of