It seems to have something to do with the broker, because I purged the queue and added the same messages to the queue several times w/o any additional failures (this was with the same broker snapshot). In addition, I picked up the snapshot that you suggested and I'll use this from now on. However, the abort is still disturbing and the AMQ-CPP should guard against invalid data. Perhaps if I get the same happening again is it possible to send the data store? I only have a few messages so it should be small.
-- Fred Fred Crable wrote: > > I'll try this version and see if I have any better luck. I'm using 5.0 > because we had issues with memory and large messages using 4.x version of > broker. > -- Fred > > tabish121 wrote: >> >> FYI - there is no AMQ CPP v4.1.1, do you mean 2.1? >> >> I don't really recommend using AMQ-CPP with AMQ v5.0 right now as I'm >> seeing different behavior from the broker on each snapshot. The OCT >> 10th snapshot works the best so far for me, but not perfectly. >> (apache-activemq-5.0-20071010.200250-21) >> >> Regards >> Tim. >> >> On Mon, 2007-10-15 at 07:02 -0700, Fred Crable wrote: >>> Hi Nate, >>> >>> The version of MQ-CPP is 4.1.1 and the broker is taken from >>> apache-activemq-5.0-20071008.215641-19.tar.gz. As far as a sample, the >>> most >>> basic consumer which only created a broker, session, etc exhibits the >>> behaviour. I think the only way to recreate it is to have the actual >>> message queued that was causing the issue but I'm not sure how to >>> "extract" >>> the message as this problem aborts. I suppose I could send a screen >>> shot or >>> copy the properties out of the jms console? BTW -- this consumer was >>> using >>> the recv method on the consumer and did not do an onMessage(). As you >>> can >>> see in the backtrace, the issue was occuring in the thread of the >>> consumer >>> and not in the recv or onMessage function itself. >>> >>> Let me know how you would like to "view" the message and I'll try to >>> cook up >>> another. >>> >>> -- Fred >>> >>> >>> nmittler wrote: >>> > >>> > Hi Fred, >>> > Could you provide us with the following? >>> > >>> > - verion of ActiveMQ-CPP you're using >>> > - version of the ActiveMQ Broker >>> > - sample code snippet that demonstrates the problem. >>> > >>> > Thanks, >>> > Nate >>> > >>> >> >> > > >-(>-(:confused::confused::confused::confused::confused::confused::confused: -- View this message in context: http://www.nabble.com/C%2B%2B-OpenwireStringSupport%3A%3AreadString-aborts-on-empty-property-tf4623108s2354.html#a13214334 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
