I did take a look at the activemq logs on both the brokers, i only have
information such as below in the primary broker. There is not much i can
infer from this.
2013-07-24 15:06:21,916 | DEBUG | bridging (localhost -> localhost)
5a2c1e2a-9df2-45a8-aebc-861c3ab271e0:1:1:161, consumer:
ID:global-de
Well, you have to make sure messages are getting bridged properly (take a
close look at the bridge logging output) and are not bouncing back and
forth for some reason.
On Tue, Jul 23, 2013 at 12:27 AM, Praveen Bysani wrote:
> Hi Christian,
>
> Thank you for the clarification. What are the factor
Hi Christian,
Thank you for the clarification. What are the factors in activemq that
could effect this, other than time to live that is set in the publisher ? I
have a time to live of 2 minutes currently, how can i ensure that most
messages are delivered before expiry ?
On 15 July 2013 20:04, Chr
Yes, that's what it means.
On Sunday, July 14, 2013, Praveen Bysani wrote:
> Hi,
>
> I observed a lot of following messages in my log,
>
> 2013-07-15 03:48:22,399 | DEBUG | Message expired ActiveMQBytesMessage
> {commandId = 1498, responseRequired = false, messageId =
> d7dfc864-e46a-44b0-a0ec-b5
Hi,
I observed a lot of following messages in my log,
2013-07-15 03:48:22,399 | DEBUG | Message expired ActiveMQBytesMessage
{commandId = 1498, responseRequired = false, messageId =
d7dfc864-e46a-44b0-a0ec-b5d9e3a07127:1:1:253, originalDestination = null,
originalTransactionId = null, producerId
Hi,
Thanks i added the log4j for all components under org.apache.activemq.
Hopefully i can see something useful.
On 12 July 2013 00:21, Christian Posta wrote:
> Add logging configuration to turn on logging for the bridge.
>
> e.g.,
>
> to your log4j.properties, add
>
>
> log4j.logger.org.apache.
Add logging configuration to turn on logging for the bridge.
e.g.,
to your log4j.properties, add
log4j.logger.org.apache.activemq.network.DemandForwardingBridgeSupport=DEBUG
On Thu, Jul 11, 2013 at 3:38 AM, Praveen Bysani wrote:
> Hi,
>
> I found the following lines in the subscriber log
>
>
Hi,
I found the following lines in the subscriber log
| org.apache.activemq.transport.InactivityMonitor | DEBUG | 2013-07-11
07:34:44,384 | 3 ms elapsed since last read check.
| org.apache.activemq.transport.InactivityMonitor | DEBUG | 2013-07-11
07:34:44,384 | org.apache.activemq.transport.I
Hi Christian,
Thanks for your input. But i have little idea of what those terms mean.
Could you elaborate please.
On 10 July 2013 21:06, Christian Posta wrote:
> Your best bet would be to set logging to debug on the network bridge
> (DemandForwardingBridgeSupport) and possibly the RegionBroker
Your best bet would be to set logging to debug on the network bridge
(DemandForwardingBridgeSupport) and possibly the RegionBroker to see what
is happening.
On Wednesday, July 10, 2013, Praveen Bysani wrote:
> Hi,
> I have the following setup in my project,
>
>1. multiple producers (p1,p2,p3)
Hi,
I have the following setup in my project,
1. multiple producers (p1,p2,p3) in Hongkong region sending variable
size non-persistent messages to a topic t1 on the broker (b1) in
Phillippines region
2. p1,p2 and p3 send messages frequently (~1 second)
3. each message has a time to
11 matches
Mail list logo
