----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Hello,
I have Apache/1.3.11 (Unix) ApacheJServ/1.1 PHP/4.0b3 on Linux (RH 6.2) with
JDK 1.1.7 v3 from Blackdown.org.
Problem:
Some JDBC calls (executeQuery() in java.sql.Statement class) take extra long
to return when run under JServ.
I can execute the same code from a different driver class (as opposed to
servlet) that I can run from the command line and everything executes
quickly.
The same code under JServ takes a loooong time to execute and results in the
following exception (from the log file):
Tue May 16 12:34:44 EDT 2000: SQL: SELECT COUNT(H.harvest_id) FROM
nm_harvest H WHERE H.user_id=21 AND H.deleted='N' AND H.harvest_type='foo'
Tue May 16 12:35:04 EDT 2000: Caught current thread not owner
java.lang.IllegalMonitorStateException: current thread not owner
at
oracle.jdbc.oci8.OCIDBAccess.parseExecuteDescribe(OCIDBAccess.java)
at
oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java)
at
oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
)
at
oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java)
at com.neomeo.DBL.DBCore.executeNonModQuery(DBCore.java:141)
at com.neomeo.DBL.DBCore.getCount(DBCore.java:263)
at com.neomeo.DBL.DBHarvest.getHarvestCount(DBHarvest.java:144)
at
com.neomeo.BL.HarvestService.getHarvestCount(HarvestService.java:119)
at NMHarvest.getHarvest(NMHarvest.java:291)
at NMHarvest.harvestView(NMHarvest.java:208)
at NMHarvest.handle(NMHarvest.java:107)
at org.webmacro.servlet.WMServlet.doRequest(WMServlet.java:251)
at org.webmacro.servlet.WMServlet.doGet(WMServlet.java:212)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:499)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at
org.apache.jserv.JServConnection.processRequest(JServConnection.java:314)
at org.apache.jserv.JServConnection.run(JServConnection.java:188)
at java.lang.Thread.run(Thread.java)
Could there be something in JServ that triggers this exception....and makes
the execution of some JDBC methods super slow?
I have noticed that the time between the start of the execution and the
exception is always around 10 seconds (10-13 secs on average). I've tried
looking in jserv config files to see if there is any mention of '10 seconds'
there and I did find this:
# The amount of time to give to the JVM to start up as well
# as the amount of time to wait to ping the JVM to see if it
# is alive. Slow or heavily loaded machines might want to
# increase this value.
# Default: 10 seconds
ApJServVMTimeout 60
I set it to 60 to see if that will cause the exception to be thrown after 60
seconds, but that didn't change anything.
Any help would be appreciated.
Thanks,
Otis
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
