Hi Bob,
It sounds like you need a better inter-process communication technique
than relying on Derby's database lock file (db.lck). Maybe someone on
this list can recommend a good resource for you to consult.
Glad to hear that your applications are playing nicely now.
-Rick
On 7/24/19 10:16 PM, Bob M wrote:
Hi Rick
Today I employed a delay in programs 2, 3,4, & 5 on both PCs [5 sec, 10sec,
15sec, & 20sec]
So Program 1 on both machines which uses currency-pair EURCAD start
immediately on the hour and hopefully finishes before 5 secs is up
Then Program 2 on both machines kicks off etc.
So far, I have had no errors involving missing drivers etc.
In addition, I get a new record added to each database each hour
My problem was a timing issue involving instances of derby opening while
another instance was already opened
I don't know how to better my 'work-around'
Bob M
--
Sent from:
http://apache-database.10148.n7.nabble.com/Apache-Derby-Users-f95095.html
