{
Context ctx = null;
Connection con = null;
DataSource ds = null;
try
{
ctx = new InitialContext();
con = ds.getConnection();
}
catch(NamingException ne)
{
System.out.println(ne.getMessage());
System.out.println(ne.getExplanation());
ne.printStackTrace();
throw new EJBException(ne);
}
catch(SQLException se)
{
System.out.println(se.getMessage());
se.printStackTrace();
throw new EJBException(se);
}
-----Original Message-----
From: Cook, Thomas [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 17, 2001 6:24 PM
To: 'jBoss'
Subject: RE: [jBoss-User] Finder Methods are slower when nothing is return edPossible a database thing? If nothing is returned, maybe it is doing a sequential search?
Tom
--
Tom Cook
Systems Development
Australian Submarine Corporation
Mersey Road
Outer Harbour+61 8 8348 7645
"From the instant I picked your book up, until the moment I put it down, I was convulsed with laughter. I fully intend to read it one day."
- Groucho Marx
-----Original Message-----
From: Bolt, Dave [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 5:01 AM
To: [EMAIL PROTECTED]
Subject: [jBoss-User] Finder Methods are slower when nothing is returnedI'm trying to write some code to use BMP Entity beans to update an Oracle 8i database.
I have a session bean that is doing the data loading from an XML file. I want to use the Entity
bean to see if the data exists (via a Finder method) and then either create or update the
record depending on the status.I am seeing that performance is very fast if the record already exists, whereas it is very slow if no
records can be found. Has anyone else noticed a difference in performance in the Finder's thanksDave Bolt
There is always bandwidth, just none for you.
