User f698d0529d
12-05-2005 17:13:24
Hi - I have a problem with Jchem cartridge. I am only using the cartridge and plain tables.
Red Hat Enterprise Linux AS release 3 (Taroon)
Kernel 2.4.21-4.ELsmp on an i686
Oracle version 10.1.0
Apache Tomcat/4.1.30
JChem version: 3.0.11
JChem Streams version: 3.0.11
I have a problem. I shut down the database using shutdown abort (I will explain why in a minute). Then I shutdown tomcat. Then I restart the db and then I restart tomcat.
On a toy table (1 row, indexed), a jchem query takes 11 seconds to run the first time and then 100ms thereafter. No problem.
But on a real table, a query which yesterday was taking 10s to run is now not returning at all. I wait for an hour - nothing. Plus, I have no idea during this time of what Jchem is doing, if anything.
The query is as follows, but other queries are showing the same behaviour.
select par.Parent_ID from Parent par where (jc_contains (par.ISOSMILES, 'N[C;r6]c1ccccc1') = 1 ) and
par.MOLECULAR_WEIGHT >= 500 and
par.MOLECULAR_WEIGHT <= 600 and rownum < 5001 order by par.molecular_weight;
The table has about 260K rows, and is indexed. Not only that, but I cannot cancel the query (TOAD has a cancel function which normally works) and I cannot use SYSTEM to kill the session either (TOAD hangs - this feature normally works). TOAD continues to list the session as active.
So I have no choice now but to do shutdown abort, and then we start all over again.
The tomcat java memory parameter is set to 360m.
I don’t see anything interesting in catalina.out.
I can send you catalina.sh and catalina.out if you wish.
Actually, I have just noticed that if I shutdown tomcat while the offending query is running, jchem eventually complains with “Please, check if Tomcat is running”
Can you help?
Thanks
Mark
Red Hat Enterprise Linux AS release 3 (Taroon)
Kernel 2.4.21-4.ELsmp on an i686
Oracle version 10.1.0
Apache Tomcat/4.1.30
JChem version: 3.0.11
JChem Streams version: 3.0.11
I have a problem. I shut down the database using shutdown abort (I will explain why in a minute). Then I shutdown tomcat. Then I restart the db and then I restart tomcat.
On a toy table (1 row, indexed), a jchem query takes 11 seconds to run the first time and then 100ms thereafter. No problem.
But on a real table, a query which yesterday was taking 10s to run is now not returning at all. I wait for an hour - nothing. Plus, I have no idea during this time of what Jchem is doing, if anything.
The query is as follows, but other queries are showing the same behaviour.
select par.Parent_ID from Parent par where (jc_contains (par.ISOSMILES, 'N[C;r6]c1ccccc1') = 1 ) and
par.MOLECULAR_WEIGHT >= 500 and
par.MOLECULAR_WEIGHT <= 600 and rownum < 5001 order by par.molecular_weight;
The table has about 260K rows, and is indexed. Not only that, but I cannot cancel the query (TOAD has a cancel function which normally works) and I cannot use SYSTEM to kill the session either (TOAD hangs - this feature normally works). TOAD continues to list the session as active.
So I have no choice now but to do shutdown abort, and then we start all over again.
The tomcat java memory parameter is set to 360m.
I don’t see anything interesting in catalina.out.
I can send you catalina.sh and catalina.out if you wish.
Actually, I have just noticed that if I shutdown tomcat while the offending query is running, jchem eventually complains with “Please, check if Tomcat is running”
Can you help?
Thanks
Mark