Maarten Dirkse-2 wrote:
>
> Hi,
> I've spent quite a bit of time trying to find a solution to this problem,
> but nothing that I've come across in the documentation or the mailing list
> seems to help, so here goes:
>
> I've got ActiveMQ set up to provide messaging between a chain of four
> co
I seem to be having the same issue. Is it a requirement to sign the Apache
Contributor License Agreement now?
--
View this message in context:
http://www.nabble.com/How-can-i-contribute-to-the-AMQ-documentation--tp12250045s2354p16827989.html
Sent from the ActiveMQ - User mailing list archive at
Only the Destination, Connection, and ConnectionFactory objects support
concurrent usage per the JMS 1.1 spec. If you want to share a Sessions
across multiple threads then you should create an object to manage
synchronous access to any JMS objects which do not support this (i.e.
Session).
-Trevor
Have a look at this thread to resolve your issue.
http://www.nabble.com/forum/ViewPost.jtp?post=15748971&framed=y&skin=2354
If you wish to update the ActiveMQ documentation you can create a login for
confluence just click on the edit page link at the very bottom of the page
you wish to edit, the
I'm not familiar with what you are trying to achieve in your example. Is
there some documentation on the Sun implementation that you are trying to
model? The broker LDAP configuration is used to provide management of large
broker topologies remotely.
--
View this message in context:
http://www.n
i've dynamicOnly with true and false...the same results
i've also tried decreaseNetworkConsumerPriority for true and false...same
results
i've tried permutations of the above and encounter the same
--
View this message in context:
http://www.nabble.com/Unexpected-duplex-connection-behavior-tp15
In our test environment we are seeing unexpected behavior with the duplex
network connection in the following configuration. broker2 establishes a
duplex connection to broker1.
[broker1] <> [broker2]
broker1
---
producer writing to "queue/A"
broker2
---
producer writing to "queue/A"
I've created a JIRA issue and a patch at the following link for the
networkTTL problem. This problem actually affects more than just the
networkTTL parameter as mentioned in the ticket. See that for more info.
see: https://issues.apache.org/activemq/browse/AMQ-1542
-Trevor
--
View this messag
Upon further investigation it seems that the networkTTL is not being
forwarded as I expected due the BrokerInfo object on the connection not
containing the networkTTL parameter. After looking in the
broker/TransportConnection.java file i can see that a new
NetworkBridgeConfiguration object is bei
Hi Rob,
This patch in AMQ-1521 doesn't seem to fix the issue I was seeing in my
previous post.
[producer]-->[broker 1]-->[broker 2]<-->[broker 3]<--[consumer]
The messages are successfully dispatched from broker 2 to 3 if there is a
producer on broker 2. The messages are not successfully dispat
t;>
>> And it now works. It seems duplex=true is the fly-in-the-ointment.
>>
>> I have networkTTL=2 set for brokers 1 and 2. Broker 3 is just
>> listening.
>>
>> Joe
>>
>>
>>
>>
>>
>> tpounds wrote:
>>>
>
Is this configuration used on all 3 machines?
ttmdev wrote:
>
> Here's an example that works for me w/a similar 3 broker topology.
>
>
> name="twowaybridge"
> uri="static:(tcp://remotehost:61616)"
> networkTTL="2"
>
What is the correct configuration for networkTTL and duplex? I cannot seem
to get this to work as expected. The network topology I am trying to use is
shown below.
[BROKER 1] -> [BROKER 2] <- [BROKER 3]
Broker 1 establishes a network connection (Non Duplex) to Broker 2.
Broker 3 establ
Are you using the correct namespaces/schemas for spring and activemq? Are you
using the spring ClassPathXmlApplicationContext directly or the xbean
version? The version provided by xbean doesn't require the spring
namespaces/schemas to be defined...If you look through the bundled activemq
XML fil
no problem I hope it works out for you
-Trevor
Roger Hoover wrote:
>
> Interesting idea. Thanks, Trevor.
>
> On 11/1/07, tpounds <[EMAIL PROTECTED]> wrote:
>>
>> If your broker is forwarding to another broker similar to a network of
>> brokers conf
If your broker is forwarding to another broker similar to a network of
brokers configuration you could stop the network connector between them
temporarily via JMX. The configuration could be similar to the following:
Before Connector Stop:
(Producer) -> (Broker 1) -> (Broker 2) -> (Consumer)
A
I've found a suitable workaround via system properties and command line. For
anyone else interested this may be useful.
activemq.xml:
http://"; brokerName="${system.hostname}
dataDirectory="${activemq.base}/data">
It can be run on *nix systems as follows. I suspect there is a way to do
thi
I found the root cause for this error...I found it burried in another thread
and seems to be the result of all the brokers having the same default name
set to "localhost".
see:
http://www.nabble.com/forum/ViewPost.jtp?post=4426623&framed=y&skin=2354
It may be beneficial to generate unique broker
I'm seeing a weird problem when using static network connectors in the latest
5.0 snapshots. If i specify the following in my activemq.xml. The following
happens when my local broker is running activemq 5.0 and the upstream
servers are using 4.1.1 or 5.0-SNAPSHOT. I also see the issue when using
A possible fix for this below
http://www.nabble.com/FanoutTransport-Patches-tf4562939s2354.html
-Trevor
--
View this message in context:
http://www.nabble.com/FanoutTransport---how-to-specify-value-for-minAckCount---tf4126265s2354.html#a13023053
Sent from the ActiveMQ - User mailing list archi
20 matches
Mail list logo
