Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates
 209.85.217.181 as permitted sender)
MIME-Version: 1.0
Sender: chirino@gmail.com
In-Reply-To: 
 <CAAarEAJsv09CNtGCALGR=wz8LqQQhjGAL3MLb5ii0kOHN5rH-w@mail.gmail.com>
References: 
 <CAAarEA+No5=A3Ux=KLZOB+MDxiK-gi1VnxyXQ+EgpevmDqjNwg@mail.gmail.com>
	<CAGZ-RDLTh+575mBLiQQOKSEwE7H3EnXc30rkQ7CuEbuiRRT-7Q@mail.gmail.com>
	<CAAarEAKsdHdfWZgN11+nG6TSz69gwaLaqH_ZA49d+v4xWzQaaA@mail.gmail.com>
	<CAGZ-RD+u1TbZbh=H_bfUczNuSEK7fTR2thf66zcj7K5GinAJvQ@mail.gmail.com>
	<CAAarEAL0toXesFFhEN9XjMfSKR3sFvYi9eghd41rqo8=fBNY8g@mail.gmail.com>
	<CAAarEA+2mMRnfEhdHr7P8A0vyLBs_EfUkTAHOp3FC-_F+FmZCw@mail.gmail.com>
	<CAGZ-RDL4sGqaDTHkY=heQZEt+17g_Fnk5T98+ognHZ4RBq06Cg@mail.gmail.com>
	<CAAarEAKjT1YKdg6eir8JUGZvNg74K2pPGsRy5MSkcw0cwCC7Ww@mail.gmail.com>
	<CAAarEAJsv09CNtGCALGR=wz8LqQQhjGAL3MLb5ii0kOHN5rH-w@mail.gmail.com>
Date: Fri, 25 Jan 2013 08:10:06 -0500
Message-ID: 
 <CAGZ-RDKpzq5cPy00G-6TNFNr-C7x=4vCiLELx4bABUQa7Tqryg@mail.gmail.com>
Subject: Re: AMQP connector warning
From: Hiram Chirino <hiram@hiramchirino.com>
To: ActiveMQ-Developers <dev@activemq.apache.org>
Content-Type: multipart/alternative; boundary=e89a8f2348a974335104d41ca5b6

--e89a8f2348a974335104d41ca5b6
Content-Type: text/plain; charset=ISO-8859-1

Hi Zhigang,

Do you have the a script that can reproduce that error?


On Thu, Jan 24, 2013 at 4:18 PM, Zhigang Wang <w1z2g3@gmail.com> wrote:

> It seem worse now for today's snapshot:
>
> INFO   | jvm 1    | 2013/01/24 16:14:13 |
> org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process
> AMQP commands
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
> java.lang.Thread.run(Unknown Source)
> INFO   | jvm 1    | 2013/01/24 16:14:13 | Caused by:
> java.lang.NullPointerException
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.command.ActiveMQDestination.createDestination(ActiveMQDestination.java:93)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.createDestination(AmqpProtocolConverter.java:636)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onReceiverOpen(AmqpProtocolConverter.java:601)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onLinkOpen(AmqpProtocolConverter.java:380)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       at
>
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:207)
> INFO   | jvm 1    | 2013/01/24 16:14:13 |       ... 6 more
>
> Please have a look.
>
> Thanks,
>
> Zhigang
>
>
> On Wed, Jan 23, 2013 at 12:40 PM, Zhigang Wang <w1z2g3@gmail.com> wrote:
>
> > Thank you for your quick fix. I will test it later.
> >
> > Zhigang
> >
> >
> > On Wed, Jan 23, 2013 at 11:38 AM, Hiram Chirino <hiram@hiramchirino.com
> >wrote:
> >
> >> Yep. your script looks good.  I found a problem /w how the AMQP impl was
> >> handling the socket disconnect.  I've now committed a fix for that.  If
> >> you
> >> try a fresh build those messages should go away.  Thanks for the report!
> >>
> >>
> >> On Wed, Jan 23, 2013 at 9:21 AM, Zhigang Wang <w1z2g3@gmail.com> wrote:
> >>
> >> > Here it is:
> >> >
> >> > #!/usr/bin/env python
> >> >
> >> >
> >> --
> >>
> >> **
> >>
> >> *Hiram Chirino*
> >>
> >> *Engineering | Red Hat, Inc.*
> >>
> >> *hchirino@redhat.com <hchirino@redhat.com> | fusesource.com |
> redhat.com*
> >>
> >> *skype: hiramchirino | twitter: @hiramchirino<
> >> http://twitter.com/hiramchirino>
> >> *
> >>
> >> *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
> >>
> >
> >
>


-- 

**

*Hiram Chirino*

*Engineering | Red Hat, Inc.*

*hchirino@redhat.com <hchirino@redhat.com> | fusesource.com | redhat.com*

*skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino>
*

*blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*

--e89a8f2348a974335104d41ca5b6--