> > -----Original Message-----
> > From: Alan Conway [mailto:[email protected]]
> >
> > There is another issue that turned up with the same symptom
> > https://issues.apache.org/jira/browse/QPID-225. Fixed in r888874. Let
> > me know if
> > that resolves your problem, if not I want to look into it more.
>
> Thanks Alan.
>
> I don't think that's the issue, because this system should only be
> receiving connections from clients who are using AUTO_ACKNOWLEDGE, but
> I'm happy to try it.
>
> I will let you know how it goes.
I made a new build of the java client from trunk today, and used that to spam a
cluster of two brokers running qpidd-0.5.752581-34 and rhm-0.5.3206-27 and saw
the error again:
2009-dec-15 12:10:34 trace 10.59.174.211:19320(READY) DLVR 27677: Frame[BEbe;
channel=0; {SessionCompletedBody: commands={ [0,203] }; }] data
10.59.174.186:24880-40
2009-dec-15 12:10:34 debug [email protected]:
sender marked completed: { [0,203] }
2009-dec-15 12:10:34 debug Exception constructed:
[email protected]: confirmed < (204+0) but only
sent < (203+0) (qpid/SessionState.cpp:163)
2009-dec-15 12:10:34 error Execution exception: invalid-argument:
[email protected]: confirmed < (204+0) but only
sent < (203+0) (qpid/SessionState.cpp:163)
2009-dec-15 12:10:34 error 10.59.174.211:19320(READY/error) channel error 27677
on 10.59.174.186:24880-40(shadow): invalid-argument:
[email protected]: confirmed < (204+0) but only
sent < (203+0) (qpid/SessionState.cpp:163) (unresolved: 10.59.174.186:24880
10.59.174.211:19320 )
2009-dec-15 12:10:34 trace MCAST 10.59.174.211:19320-0: {ClusterErrorCheckBody:
type=1; frame-seq=27677; }
OS is an up to date installation of RHEL 5.4 32 bit running on VMWare.
Qpidd.conf is:
no-module-dir=true
load-module=/usr/lib/qpid/daemon/cluster.so
load-module=/usr/lib/qpid/daemon/msgstore.so
cluster-mechanism=PLAIN
cluster-username="***"
cluster-password="***"
cluster-name="na1m-dev1"
log-to-file=/var/lib/qpidd/qpidd.log
trace=1
auth=yes
wait=60
JNDI connection string:
connectionfactory.qpidConnectionFactory =
amqp://***:*...@test/?brokerlist='tcp://***.com:443?ssl='true',connectdelay='1000',connecttimeout='5000'',failover='roundrobin?cyclecount='999'',sync_publish='all'
The SSL is terminated at the load balancer.
I'd love to hear the community's ideas on where to look next. I recently
tested out a build of the 0.6beta1 release, and found that the bug (or at least
the same symptoms) occurred there as well. I don't have a good fast way to
reproduce the problem. This particular crash occurred after I spammed the
cluster for about 7 minutes, during which time the spammer sent about 20k
messages of between 1-1000 KB in size through the cluster, whilst periodically
closing and reopening sending and receiving connections.
Thanks!
Sandy
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
