Hi
I connect to a derby dbase in my java program and get a message to say the
connection is made
Then, once in a while, I get the following...
SQL Exception---
SQL State: 40XL1
Error Code: 3
Message: A lock could not be obtained within the time requested
Please
Probably, too many simultaneous connections.
2014-03-18 9:06 GMT+01:00 Bob M rgmatth...@orcon.net.nz:
Hi
I connect to a derby dbase in my java program and get a message to say the
connection is made
Then, once in a while, I get the following...
SQL
Hi,
You might have a query that runs for a long time.
You might be able to speed it up by adding indexes, or you can adjust the
timeout properties.
Or you might have multiple connections that fight eachother.
Read the relevant section in the Derby Developer's Guide on Locking,
concurrency, and
On 03/17/2014 08:48 PM, spykee wrote:
Hi Dyre ,
Thank you for your comments.
The JMS Queue ( Topic ) has an API, and it will be called from the stored
procedure. The scope of the queue is to be an entry point of the messages
publishes by the stored procedures, messages which will go to a
I agree, starting 20K threads/sec does not sound like I good idea. But
since I'm not familiar with these other technologies that you use, I
don't understand why you need to fire a thread per message. Why can't
you have a dedicated sender thread that reads everything in your
queue-table and
On 18/03/2014 22:58, spykee wrote:
Using the monitor approach I will have to make *2 steps:*
- throw a notifier message from the db to the monitor thread ( execute a
stored procedure)
- the monitor thread will then have a logic, and then query the table for
the changes and publish them to the
