Prev: JDO and metadata annotations
Next: access HTTP request parameters?
From: stc on 14 Jul 2008 18:16
I have developed a simple job using Java 5 and Quartz Enterprise Job
Scheduler API (1.6.0). All it does is transfer data from one Oracle database
(10g) to another. The logic is quite simple but it results in about 70k rows
inserted/updated in the target database. Job is run once a day on Oracle
Application Server 10g R3.

The problem is that the job simply stops executing with around 1k "rows" of
data before the end. It doesn't stop always at the same line and there is
absolutely nothing in the logs, no errors, no exceptions, even in the
application server's logs. What is happening, where to look? What kind of
errors would cause such a behavior? Maximum heap size is set to 1024M so
that shouldn't be a problem.

Thanks in advance for the help...


From: Daniele Futtorovic on 14 Jul 2008 19:18
On 2008-07-15 00:16 +0100, stc allegedly wrote:
> I have developed a simple job using Java 5 and Quartz Enterprise Job
> Scheduler API (1.6.0). All it does is transfer data from one Oracle database
> (10g) to another. The logic is quite simple but it results in about 70k rows
> inserted/updated in the target database. Job is run once a day on Oracle
> Application Server 10g R3.
>
> The problem is that the job simply stops executing with around 1k "rows" of
> data before the end. It doesn't stop always at the same line and there is
> absolutely nothing in the logs, no errors, no exceptions, even in the
> application server's logs. What is happening, where to look? What kind of
> errors would cause such a behavior? Maximum heap size is set to 1024M so
> that shouldn't be a problem.

Does the Job Scheduler report success? If yes, this might be a bug (that
being said without any knowledge whatsoever of the API mentioned).
Otherwise, this smells a lot like an OutOfMemoryException. You might
want to monitor the system while the job is being executed. Yet better,
if you can afford it, you might try to reduce the heap size and see if
that makes it "break" sooner than "1k 'rows' of data before the end".

--
DF.
to reply privately, change the top-level domain
in the FROM address from "invalid" to "net"
 | 
Pages: 1
Prev: JDO and metadata annotations
Next: access HTTP request parameters?