You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by swclhard <cl...@gmx.de> on 2018/03/12 14:37:55 UTC
JDBC persistence is silently falling back to KahaDB, if an error
occurs
We are using ActiveMQ 5.15.3 with Wildfly 10. Integration was done as
instructed here:
http://www.mastertheboss.com/jboss-server/jboss-jms/integrate-activemq-with-wildfly
In general it is working fine, but we have found an issue with JDBC
persistence.
If the password of our db user is wrong, wildfly logs that error, but
deployment of active.rar succeed and afterwards it is using KahaDB. So
nobody will recognize, that messages gets persisted to file system instead
of database.
Any idea what could be wrong?
Wildfly log:
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: JDBC persistence is silently falling back to KahaDB, if an error occurs
Posted by Tim Bain <tb...@alumni.duke.edu>.
That's great, thank you for doing that.
Tim
On Tue, Mar 13, 2018 at 12:45 AM, swclhard <cl...@gmx.de> wrote:
> JIRA issue was created:
>
> https://issues.apache.org/jira/browse/AMQ-6926
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: JDBC persistence is silently falling back to KahaDB, if an
error occurs
Posted by swclhard <cl...@gmx.de>.
JIRA issue was created:
https://issues.apache.org/jira/browse/AMQ-6926
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: JDBC persistence is silently falling back to KahaDB, if an error occurs
Posted by Tim Bain <tb...@alumni.duke.edu>.
Would you be willing to submit a bug in JIRA for this issue?
Tim
On Mar 12, 2018 10:39 AM, "swclhard" <cl...@gmx.de> wrote:
> Looks like an issue with vm connector.
>
> Now we are working around by using the tcp connector. In case that password
> is wrong, no broker is available and incoming requests are refused.
>
> We will use a startup Singleton bean to check, if broker is available, so
> that startup fails, if there is something wrong.
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>
Re: JDBC persistence is silently falling back to KahaDB, if an
error occurs
Posted by swclhard <cl...@gmx.de>.
Looks like an issue with vm connector.
Now we are working around by using the tcp connector. In case that password
is wrong, no broker is available and incoming requests are refused.
We will use a startup Singleton bean to check, if broker is available, so
that startup fails, if there is something wrong.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html