Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gaurav.cs.sharma@gmail.com
 designates 209.85.210.46 as permitted sender)
Subject: Re: Slow starting activemq connection
References: <1357756279656-4661562.post@n4.nabble.com>
From: Gaurav Sharma <gaurav.cs.sharma@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <1357756279656-4661562.post@n4.nabble.com>
Message-Id: <D771FF30-DE80-43BD-9914-9E82AB4E568D@gmail.com>
Date: Wed, 9 Jan 2013 11:20:01 -0800
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

It could be a number of things. But first, a couple questions:=20

1. how does your network look like - 2/3 level switches in the DC, flat or s=
omething else? Where are the producers deployed relative to the broker clust=
ers? Do you have tcp keep-alive turned on, spl routing, firewalls, etc?

2. any reason for not using the pooled connection factory?

I would immediately write a long running producer->broker test and deploy on=
 a couple machines in the 'same' network going against the 'same' broker nod=
es, let it run continuously overnight, capture packets via wireshark, etc an=
d analyze the drops. Loop in your network engg. to help sample-trace the rou=
tes during your tests.

Hope this helps or maybe you already did these analyses and didn't find anyt=
hing? Let us know either way.

On Jan 9, 2013, at 10:31, KaZso <zsomboro@gmail.com> wrote:

> Hi,
>=20
> I am facing a strange performance issue with an activemq broker (v. 5.4.0)=
.=20
> The setup is very simple:
> - 1 broker instance
> - no persistence provider
> - about 200 consumers and producers using non-persistent messages. The
> message size can be anything up to 1-2MB but is usually smaller.
> - dedicated task runner has been disabled
> - producer flow control enabled
>=20
> Most message producers open and close their connections for every message
> sent but the number of messages can vary from 5-10 per day to 20-30 every
> minute, meaning that we do have thousands of connections being opened and
> closed every day.=20
>=20
> This is working well enough with delivery times of up to a few hundred
> milliseconds, but every know and then there is a "hiccup". Starting the jm=
s
> connection slows down to tens of seconds for no apparent reason, then
> immediately picks up again. Message delivery of already established
> connections are not affected, and the slowdowns seem totally random. Numbe=
r
> of threads is mostly constant, and the memory levels seem fine as well, wi=
th
> the total garbage collection time being lower than one single slowdown.
>=20
> No exceptions or warnings can be found in the logs, and the slow connectio=
ns
> do eventually start. The message delivery on them is fast and not
> problematic at all.
>=20
> Could anyone help me in finding the root cause of this issue? Could the
> producer flow control delay the start of a new connection but not the flow=

> of messages?
>=20
> Thank you,
> Zsombor
>=20
>=20
>=20
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Slow-s=
tarting-activemq-connection-tp4661562.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.