Hi.
We are experiencing still this problem when trying to deploy ActiveMQ into a
clustered Tomcat 6.0.14 environment with MySQL for presistence, but the
issue you created shows this problem as solved.
Was the applied solution specific for JBoss and the problem still exists
when using Tomcat?
Ma
Looks like we should start the embedded broker async to avoid hanging
the Jboss startup.
I created issue: https://issues.apache.org/activemq/browse/AMQ-1519
to track.
On Nov 12, 2007 12:07 PM, James Strachan <[EMAIL PROTECTED]> wrote:
> On 11/11/2007, ikbenben <[EMAIL PROTECTED]> wrote:
> >
> > h
bump :)
ikbenben wrote:
>
> Hey James,
>
> thanks for the feedback. i had read the docs.
>
> just to be sure i am understanding correctly, suppose we have 2 jboss
> nodes in a cluster, both with activemq-ra.rar and jbossweb-tomcat55.sar
> deployed. then, when the 1st node is started, both
Hey James,
thanks for the feedback. i had read the docs.
just to be sure i am understanding correctly, suppose we have 2 jboss nodes
in a cluster, both with activemq-ra.rar and jbossweb-tomcat55.sar deployed.
then, when the 1st node is started, both the activemq and tomcat modules
will compl
On 11/11/2007, ikbenben <[EMAIL PROTECTED]> wrote:
>
> hey all,
>
> i've got a question regarding the behaviour of using the
> jdbcPersistenceAdaptor. i have deployed ActiveMQ into a clustered JBoss
> 4.0.5 environment. I basically have 2 JBoss servers, each of which has the
> ActiveMQ RAR deploy
