All:
I think I have a relatively simple - and typical - environment but am having
trouble getting failover to work the way I expect it to. Here is my
environment:
ActiveMQ 5.3.1 running on linux (CentOS 5.2) - two nodes; primary & failover
Shared Database (jdbcPersistenceAdapter)
Multiple JBoss
Maybe the 5.3.1 version should be repacked with the osgi and spring-osgi jar
file moved from optional to lib
BTJ
On Thu, 15 Apr 2010 16:59:39 +0200
Dejan Bosanac wrote:
> Hi Bjorn,
>
> we will make it optional in the following release -
> https://issues.apache.org/activemq/browse/AMQ-25
keith doyle wrote:
>
> For senders and listeners this works fine but you don't see the any
> details being listed in the admin web console which I would do if i
> changed the broker to tcp://127.0.0.1:61616
>
Hi Keith, keep in mind that when using vm transport if the broker is not
found a
Hi Dejan,
Thank you so much for taking time out to reply, I'm not really sure how to
do this (excuse my stupidity) but in my activemq.conf I have a broker
"localhost"
http://activemq.apache.org/schema/core";
brokerName="localhost" dataDirectory="${activemq.base}/data">
:
:
I
So I finally got around to doing this. I've made changes on a per
destination basis only for now and have attached the patch to the JIRA.
Also, can you please comment on
https://issues.apache.org/activemq/browse/AMQ-2659 AMQ-2659 ? I've proposed
a small code change for that. Should be a quick
Hi Keith,
that's because your web console is probably in other VM. You'd need to embed
into the application where the embedded broker is used, and then you should
be able to monitor it.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ
Using spring and activemq I can create a queue like so:
For senders and listeners this works fine but you don't see the any details
being listed in the admin web console which I would do if i changed the
broker to tcp://127.0.0.1:61616
Is there any reason for this? or to put it another wa
Hi Bjorn,
we will make it optional in the following release -
https://issues.apache.org/activemq/browse/AMQ-2574
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.ne
Thanks! Perfixing with 'transport.' worked.
It would be helpful if we were allowed to configure the TCP_KEEPIDLE,
TCP_KEEPCNT, and TCP_KEEPINTERVL on the underlying socket as well.
Otherwise one would need to rely on reasonable sysctl settings.
Thanks for the hlep.
Cheers,
-Josh
On 04/15/2
All the answers provided help.
--
View this message in context:
http://old.nabble.com/Topic-Inheritance-tp28245081p28255890.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
AMQ 5.3.0, Tomcat 6.0.20
I have and embedded client and server broker running within a single Tomcat
instance for testing. With
message compression enabled we get the following error. Any ideas what we
can do to mitigate this, or at least debug it further?
2010-04-15 11:46:16,378 INFO [Active
Josh, thanks for completing the loop with your reply.
I think the keepAlive option needs to be prefixed with transport. to make it
work for the accepted socket.
stomp://mmq1:61613??transport.keepAlive=true
There is a bit too much going on in the transport configuration with
TcpTransport option
When it's clearly required?
Regards,
BTJ
--
---
Bjørn T Johansen
b...@havleik.no
---
Someone wrote:
"I unders
Is there a direct way to connect to activeMq without the tcp overhead.
since the consumer and jmsbroker will reside on the same server there is
really no need for a wire protocol in between.
I am using the activemq-cpp-library-3.1.2 and activemq 5.3.1
one possibility might maybe using the vm tran
Hi Josh,
that config should be
can you try it out and see if it works for you?
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Wed, Apr 14, 2010 at 11
Hi,
I try to set some message expiration strategy on my durable subscriptions. I
tried to set the expireMessagesPeriod, but it is working with queues only.
Then I tried the constantPendingMessageLimitStrategy, but the pending queue
is growing endlessly even if I set this prop.
Is it supposed to
On Thu, Apr 15, 2010 at 12:55 AM, go canal wrote:
> thanks for the examples.
>
> just wanted to make sure if my understanding is correct:
> * is to match any name, including empty name;
> > is to match any name (not for empty?) and hierarchy.
>
> So
>
> a.* means 'a.' followed by one or zero hi
17 matches
Mail list logo