maybe the problem is just one of MBean registration, but I would have
assumed that error would mean that that subscription is not propagated
through the network so a round trip producer consumer test would fail.
Do you see any other bad symptoms other than this error in the logs?
If you do, I gues
I've created issue #2879 but I could use some help narrowing down what
I need to look for. I don't even know for instance if this is
triggered by a particular topic or queue.
Similarly if I were to open junit I'm not sure what I'd be testing for
at present.
James
On 25 August 2010 14:48, Gary Tu
Hi everyone!
I'm quite new to ActiveMQ and unable to achieve my desired
configuration.
I have two JBoss (4.2.3) instances running in prallel (*not*
clustered) which works quite fine.
Now I want to add a single logical JMS queue to both.
From my research JDBC master/slave seems quite well-suite
http://activemq.apache.org/wildcards.html
On 25 August 2010 15:04, gng wrote:
>
>
> Gary Tully wrote:
>>
>> peek at the schema, there is also a topicPrefetch and
>> durableTopicPrefetch attributes. You need topicPrefetch I guess. then
>> it looks ok.
>>
>
> Thanks - finally, is there a wildcard c
Gary Tully wrote:
>
> peek at the schema, there is also a topicPrefetch and
> durableTopicPrefetch attributes. You need topicPrefetch I guess. then
> it looks ok.
>
Thanks - finally, is there a wildcard character that can be used to indicate
all topics should be affected ? Something like :-
You may need to disable concurrentStoreAndDispatch on the kahaDB
persistence adapter so that the messages pass through the cursors.
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/store/kahadb/KahaDBMessagePriorityTest.java?view=markup
On 25 August 2010
peek at the schema, there is also a topicPrefetch and
durableTopicPrefetch attributes. You need topicPrefetch I guess. then
it looks ok.
On 25 August 2010 14:37, gng wrote:
>
>
> Gary Tully wrote:
>>
>> yea, need to add it there, it is in the schema though:
>> view-source:http://activemq.apache.o
yea, it looks like it warrants an issue. Have a look at the java stomp
tests, that use a trivial java stomp client.
org.apache.activemq.transport.stomp.StompTest in activemq-core for
some inspiration for a junit test.
On 25 August 2010 14:29, James Green wrote:
> Hmm, I'm connecting to both hub
Gary Tully wrote:
>
> yea, need to add it there, it is in the schema though:
> view-source:http://activemq.apache.org/schema/core/activemq-core-5.4.0.xsd
>
> that is always the most up to date reference
>
Thanks Gary - so I'm using v5.3.2 and the queuePrefetch attribute is there.
I want to ch
Hmm, I'm connecting to both hub and spoke using PHP with the PECL
Stomp library (1.0.1).
To the hub I'm sending to /topic/accounts with a header 'persistent' => 'true'.
To the spoke I am subscribing to /topic/accounts with a client-id of
'sutton_accounts'. I use the same 'sutton_accounts' value f
I have the following section in my config file:
and I am using 4 for my default and 9 for my high priority messages which
show up in the queue browser when I look at the messages.
When I connect to the queue, I use the following string:
QUEUENAME?consumer.prefetchSize=1
However, my messages
javax.jms.Message#DEFAULT_PRIORITY = 4
normal priority == javax.jms.Message#DEFAULT_PRIORITY
low priority < javax.jms.Message#DEFAULT_PRIORITY
high priority > javax.jms.Message#DEFAULT_PRIORITY
On 25 August 2010 14:13, Kondro wrote:
>
> If we can set the priority by using setJMSPriority to 0 -
If we can set the priority by using setJMSPriority to 0 - 9 for the
JDBCStore, how do we set the priority to low/normal/high for kahaDB? Are
these constants somewhere?
Gary Tully wrote:
>
> priority support needs to be enabled for a destination with a policy
> entry, prioritizedMessages
> see:
What frames are being used to the create the stomp subscription.
>From the code, there is a subscription name present in the consumer
info so it is attempting to treat it as a durable topic subscription
when in fact it is a queue subscription.
Can you post the relevant stomp frames, and possibly
Both servers are 5.4.0 on Ubuntu.
>From the hub in full:
[ .. ]
java.lang.ClassCastException:
org.apache.activemq.broker.region.QueueSubscription cannot be cast to
org.apache.activemq.broker.region.DurableTopicSubscription
at
org.apache.activemq.broker.jmx.DurableSubscriptionView.(Durable
is there a stack trace? please post if there is.
what version of broker?
On 25 August 2010 12:31, James Green wrote:
> On our hub I see the following:
>
> 2010-08-25 12:09:47,378 | ERROR | Failed to register subscription
> QueueSubscription: consumer=ID:billing-59361-1282733145999-6:14:-1:1,
> de
On our hub I see the following:
2010-08-25 12:09:47,378 | ERROR | Failed to register subscription
QueueSubscription: consumer=ID:billing-59361-1282733145999-6:14:-1:1,
destinations=0, dispatched=0, delivered=0, pending=0 |
org.apache.activemq.broker.jmx.ManagedRegionBroker | ActiveMQ
Transport: tc
A single duplex connector on either end will work. It will create a
forwarding bridge in both directions.
Yes, selectors are JMS message selectors. The only think to note is
that with conduit subscriptions (where multiple consumers for a
destination are considered by the bridge to be a single cons
You should be able to specify the complete URI from the
managementContext, have it create the jmx rmi server rather than using
the management services built into the jvm:
To see where these attributes are used peek at:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/jav
I doubt it, it already are text messages and both the correctly
delivered and empty messages are TextMessage according to the client.
Arjen
On 25-8-2010 7:54, Antony Bowesman wrote:
I vaguely remember seeing something similar, not sure if it was over
XMPP or Stomp, but I was sending BytesMessa
20 matches
Mail list logo
