Queries running under JBoss Not Working

Question

I'm using Kodo 2.3.2 running under JBoss.
It seems like if I attempt to run the same JDOQL query within a single
transaction under JBoss the second time I run the query I see that Kodo
appears to be querying the entire extent of my class instead of performing
my JDOQL query.
For example,
I have a simple JDOQL function like:
runQuery()
Extent e = aPM.getExtent (Persname.class, true);
String aFilter, anOID;
aFilter = "pers.objid == aObjId";
// Create a new query for the specified class and filter
Query query = aPM.newQuery (e, aFilter);
query.declareParameters("double aObjId");
// execute the query
Collection aColl = (Collection) query.execute (aPersOID);
if ( aColl == null )
this.setResults("ERROR: NULL collection returned from query");
return false;
} // end if
// iterate the results and close the query
If I call this method twice in my session bean I see this the first time
(which is correct SQL):
SELECT t0.ObjId, t0.PersObjId, t0.StpDate, t0.StrDate, t0.TypeCd FROM Pers
t1, PersName t0 WHERE (t1.ObjId = '44946832753163' AND t0.PersObjId =
t1.ObjId)
Then on the second call to the method I see this:
SELECT t0.ObjId, t0.PersObjId, t0.StpDate, t0.StrDate, t0.TypeCd FROM
PersName t0
connect:
jdbc:microsoft:sqlserver://ML1JXT0C:1339;DatabaseName=SMSTHtndIT6DJDO;Select
Method=cursor (sa): 1
then Kodo seems to iterate the entire table using all the primary keys.
Has anyone seen anything like this?
Also, when I run more than one query, the second query performs
significantly slower (5 - 6 seconds).

Answer 1

Fred,
That was the problem, once I configured IgnoreCache=true I didn't see that
behavior anymore. Thanks..
"Fred Lucas" <[email protected]> wrote in message
news:[email protected]...
What is the javax.jdo.option.IgnoreCache property set to? If this is
set to 'false' and you run a query after modifying an object in the
transaction, then we perform the entire query in-memory, for transactional
consistency reasons.
-Fred
In article <[email protected]>, TJanusz wrote:
I'm using Kodo 2.3.2 running under JBoss.
It seems like if I attempt to run the same JDOQL query within a single
transaction under JBoss the second time I run the query I see that Kodo
appears to be querying the entire extent of my class instead of
performing
my JDOQL query.
For example,
I have a simple JDOQL function like:
runQuery()
Extent e = aPM.getExtent (Persname.class, true);
String aFilter, anOID;
aFilter = "pers.objid == aObjId";
// Create a new query for the specified class and filter
Query query = aPM.newQuery (e, aFilter);
query.declareParameters("double aObjId");
// execute the query
Collection aColl = (Collection) query.execute (aPersOID);
if ( aColl == null )
this.setResults("ERROR: NULL collection returned from query");
return false;
} // end if
// iterate the results and close the query
If I call this method twice in my session bean I see this the first time
(which is correct SQL):
SELECT t0.ObjId, t0.PersObjId, t0.StpDate, t0.StrDate, t0.TypeCd FROMPers
t1, PersName t0 WHERE (t1.ObjId = '44946832753163' AND t0.PersObjId =
t1.ObjId)
Then on the second call to the method I see this:
SELECT t0.ObjId, t0.PersObjId, t0.StpDate, t0.StrDate, t0.TypeCd FROM
PersName t0
connect:
jdbc:microsoft:sqlserver://ML1JXT0C:1339;DatabaseName=SMSTHtndIT6DJDO;Select
Method=cursor (sa): 1
then Kodo seems to iterate the entire table using all the primary keys.
Has anyone seen anything like this?
Also, when I run more than one query, the second query performs
significantly slower (5 - 6 seconds).
Fred Lucas
SolarMetric Inc.
202-595-2064 x1122
http://www.solarmetric.com