You should not be getting 2 separate instances of JDBC Repository. I think
that is the key.
My impression(don't fully remember the code) is that the logic is
wait-notify so 2 repositories would be bad. (the wait-notify could be bad,
because it assumes same process)
You could try making the JDBC Repository a singleton and see if that fixes
the problem.
Harmeet
----- Original Message -----
From: "Serge Knystautas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 20, 2001 9:04 PM
Subject: Am I doing something wrong?
> I'm having trouble with my spool repository getting instantiated multiple
> times. I've got my (JDBC) repository defined as db://EML_spool/spool, and
> this gets defined in 2 places in config.xml... in James' spoolRepository's
> repository's destinationURL... and one in the spoolManager's
> spoolRepository's repository's destinationURL. The notes in the XML says
> these should match, so this seems right.
>
> However, I'm getting 2 separate instances of the JDBC repository, so when
a
> message arrives, it can't notify the threads waiting for a message (since
> they're waiting on a different instance). It doesn't seem to do this with
> the Avalon repository.
>
> Any ideas on what I'm doing wrong? Do I need to put some extra methods on
> the JDBCSpoolRepository?
>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
