Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com
 designates 209.85.216.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=n8a0TCDydoyOkxnqmyi0yVDosSAWYKBeQ/KuFBM2kHSx982iMBACSCh+KKMwMbjc9m
         5YsKpg2KmgdY0IoE997wWK9dnJ4Cqxibcjx1QJE9yhwWXlI1tMqpy8w/OYrFS8KGre51
         IqJ/Mz5gJTZbYL4jppdR76Go5q/5fQ7+Py6WI=
MIME-Version: 1.0
In-Reply-To: <1305989285267-3540710.post@n4.nabble.com>
References: <1305989285267-3540710.post@n4.nabble.com>
Date: Mon, 23 May 2011 10:53:14 +0100
Message-ID: <BANLkTi=ExaD378n=YwpRh+dd3bN48C_s+g@mail.gmail.com>
Subject: Re: Problem with NIO protocol
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It looks correct, only change would be to just change the port on the
client broker url, so use

  tcp://ec2-x-x-x-x.us-west-1.compute.amazonaws.com:61618

There is nothing particular to nio on the client, by default it picks
up the tcp impl, but there may be an issue here.

On 21 May 2011 15:48, hodgesz <hodgesz@gmail.com> wrote:
> Hi,
>
> We are currently using ActiveMQ 5.4.2 with Spring/Tomcat clients. =A0We h=
ave
> this configured as standalone two node JDBC master/slave. =A0Right now we=
 are
> only testing with one Spring/Tomcat client and the master ActiveMQ node.
> When changing my broker URL on the clients to use the NIO protocol instea=
d
> of TCP we are seeing the following exceptiom in the ActiveMQ logs.
>
>
> 2011-05-18 21:50:44,950 | INFO =A0| Transport failed: java.io.IOException=
:
> Wire format negotiation timeout: peer did not send his wire format. |
> org.apache.activemq.broker.TransportConnection.Transport | Async Exceptio=
n
> Handler
>
>
> It is very likely I don't have something configured right since I am fail=
y
> new to ActiveMQ. =A0That said I have tried to follow examples from the
> ActiveMQ in Action book I just purchased.
>
> The following is my transportConnectors element in the activemq.xml
>
>
> <transportConnectors>
> =A0 <transportConnector name=3D"tcp" uri=3D"tcp://x.x.x.x:61616"/>
> =A0 <transportConnector name=3D"nio" uri=3D"nio://x.x.x.x:61618"/>
> </transportConnectors>
>
>
> On the client when my broker URL is
> tcp://ec2-x-x-x-x.us-west-1.compute.amazonaws.com:61616 it loads fine
> without any errors. =A0If I change the broker URL to
> nio://ec2-x-x-x-x.us-west-1.compute.amazonaws.com:61618 I see the errors.
>
> A quick search on the web I came across a few JIRAs and the FAQ URL
> http://activemq.apache.org/javaxjmsjmsexception-wire-format-negociation-t=
imeout-peer-did-not-send-his-wire-format.html
>
> The FAQ says this error is one of following three things.
>
> 1. You're connecting to the port not used by ActiveMQ TCP transport
> =A0Make sure to check that you're connecting to the appropriate host:port
>
> 2. You're using log4j JMS appender and doesn't filter out ActiveMQ log
> messages
> =A0Be sure to read How do I use log4j JMS appender with ActiveMQ and more
> importantly to never send ActiveMQ log messages to JMS appender
>
> 3. Your broker is probably under heavy load (or network connection is
> unreliable), so connection setup cannot be completed in a reasonable time
>
>
> As far as I can tell my case doesn't fall in either of those three
> categories. =A0I am pretty sure I have configured the host and port corre=
ctly
> in that the TCP protocol works fine. =A0It's just when using NIO that I s=
ee
> the issue. =A0I am not using the log4j JMS appender, there is no load
> currently and the network connection is fine since I can telnet to both
> ports from the client.
>
> The only thing I can think of is I configured NIO incorrectly on the serv=
er
> or client but from all the examples I have seen it looks consistent.
>
> Any help on this would be greatly appreciated.
>
> Thanks,
>
> Jonathan
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Probl=
em-with-NIO-protocol-tp3540710p3540710.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


--=20
http://fusesource.com
http://blog.garytully.com