Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Best Approach for long-running Java Oracle Connection

Re: Best Approach for long-running Java Oracle Connection

From: Volker Hetzer <volker.hetzer_at_ieee.org>
Date: Mon, 13 Oct 2003 17:57:48 +0200
Message-ID: <bmei1t$sdb$1@news.fujitsu-siemens.com>

"Keithadler" <keithadler_at_aol.com> schrieb im Newsbeitrag news:20031013113052.22348.00000429_at_mb-m29.aol.com...
> Hello, I'm creating a Java Application that will poll an Oracle database on a
> frequent basis (every minute) to query a table to determine if a pseudo-job
> should be run. What is the best approach for establishing this single
> long-running connection, as well as ensuring that it gracefully deals with
> things such as database downtime for backups, etc.?
>
> I appreciate your assistance.

So, for some reason dbms_job is out of the question?

Ok, if that's true and I had to deal with downtime and stuff and want to make it easy for the dba I'd probably log on every minute and see what's there. Oracle ought to be able to deal with loads of connections always coming and going. If this causes unacceptable load, ISTR that your dba can make a shared server for you that stays up.

So, you try to connect, if it's ok you poll once and then disconnect.

I'd not like to have one permanent connection because "what if everybody does it?". Programs such as yours tend to be forgotten if they work well and if the dba needs to shut down the db he will have to know which sessions to kill and which to wait for.

Lots of Greetings!
Volker Received on Mon Oct 13 2003 - 10:57:48 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US