Thank you Steve and Gordon for your suggestion.
Is this meaning the client tries to reconnect the first time, but gets the
explicit error, then it stops trying to reconnect?
Can you explain how increasing reconnect_interval_min would help if the first
reconnection attempt is supposed to
Hi Rawad,
I assume you are correct... To be honest I personally don't have a lot of
experience with RDBMs that use schemas - all my serious database work was
against Sybase / SQL Server (and it's probably been 10 years since I was
using them).
When the JDBC store was initially written I fired up
On 05/12/16 19:41, Bee wrote:
Hello, I'm quite new here. Hopefully, I can get some help for qpid-0.20 I'm
using at work.
A few times now, I get this error:
[Protocol] error Execution exception: resource-locked: Cannot grant exclusive
access to queue (qpid/broker/SessionAdapter.cpp:324)
Try increasing your reconnect_interval_min to 1.0
> -Original Message-
> From: Bee [mailto:nbe...@hotmail.com]
> Sent: Monday, December 05, 2016 2:42 PM
> To: users@qpid.apache.org
> Subject: qpid-0.20 Execution exception: resource-locked
>
> Hello, I'm quite new here. Hopefully, I can
Hello, I'm quite new here. Hopefully, I can get some help for qpid-0.20 I'm
using at work.
A few times now, I get this error:
[Protocol] error Execution exception: resource-locked: Cannot grant exclusive
access to queue (qpid/broker/SessionAdapter.cpp:324)
Please correct me, but my
Hello,
While checking the implementation of the JDBC Message Store I noticed that
the implementation starts by checking if the tables exist (as
per AbstractJDBCMessageStore#upgrade).
However, the check for table existence in JdbcUtils doesn't filter on a
specific schema:
ResultSet rs =
