Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 cwiklik@us.ibm.com does not designate 216.139.250.139 as permitted sender)
Date: Fri, 7 Feb 2014 07:49:33 -0800 (PST)
From: Jerry Cwiklik <cwiklik@us.ibm.com>
To: users@activemq.apache.org
Message-ID: <1391788173267-4677624.post@n4.nabble.com>
Subject: Wire format negotiation timeout - auto retry
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Under a  heavy network load we occasionally are getting the dreaded "Wire
format negotiation timeout..." exception when opening broker's connection in
the client. We attempted to solve the problem with
wireFormat.maxInactivityDurationInitalDelay=60000 url param, but even with
that extended timeout the exception still happens. Our best guess is that
the wire format frame gets lost somehow. We have no concrete evidence of
that other than the timeout. 60 secs seems like a pretty long time though.

Is there any chance to add a new wireFormat configuration parameter that
would control a number of retries on "Wire format negotiation timeout" with
default = 1? I know its a long shot, but I want to float the idea for
consideration.

We can build the retry in the application, but I think the framework support
would be a better fix.

Comments?

Jerry C


--
View this message in context: http://activemq.2283324.n4.nabble.com/Wire-format-negotiation-timeout-auto-retry-tp4677624.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.