I have not seen this happen again with the 10/10 version of ActiveMQ broker. The producer too is the simpilest form of a broker publishing a TextMessage with some properties filled in. I had however inadverntly read in my properties without values and put them into the message this way. If I find a reproducible test case I'll surely post some example code. -- Fred
tabish121 wrote: > > So the question is what does the message that you are sending look like? > If you have some sample Java code (or C++) that sends a message that > mimics the one that you are sending we can try and reproduce it. > > Its hard for us not know what exactly you are sending to reproduce the > problem. I've looked at the code but nothing jumps out at me, so having > something to make the error happen so I can debug it would help. > > Also it would be helpful if you opened a Jira issue and documented what > you are experiencing that way we can target a fix for the next release. > > Regards > Tim. > > On Mon, 2007-10-15 at 07:36 -0700, Fred Crable wrote: >> Sorry, I am using 2.1 ActiveMQ-CPP. I modified the example main.cpp and >> used >> my queue named Combo_in instead of the default topic TEST.FOO and the >> result >> is the same. Here is the diff of the main.cpp versus what is in the 2.1 >> release. I simply commented out the producer because the messages are >> already queued. >> >> 213c213 >> < destination = session->createTopic( "TEST.FOO" ); >> --- >> > destination = session->createTopic( "Combo_in" ); >> 215c215 >> < destination = session->createQueue( "TEST.FOO" ); >> --- >> > destination = session->createQueue( "Combo_in" ); >> 344c344 >> < bool useTopics = true; >> --- >> > bool useTopics = false; >> 349c349 >> < HelloWorldProducer producer( brokerURI, numMessages, useTopics ); >> --- >> > //HelloWorldProducer producer( brokerURI, numMessages, useTopics ); >> 357c357 >> < consumer.waitUnitlReady(); >> --- >> > //consumer.waitUnitlReady(); >> 359a360 >> > /* >> 364a366 >> > */ >> >> >> >> Mittler, Nathan wrote: >> > >> > Really what I'm looking for is a simple main that has a producer and a >> > consumer talking over a topic/queue. I want to see your usage of the >> > client so that we can replicate it exactly. >> > >> > Also, ActiveMQ-CPP is only up to version 2.1 >> > (http://activemq.apache.org/cms/) - is that what you're using? >> > >> > Thanks, >> > Nate >> > >> >> -----Original Message----- >> >> From: Fred Crable [mailto:[EMAIL PROTECTED] >> >> Sent: Monday, October 15, 2007 10:03 AM >> >> To: [email protected] >> >> Subject: Re: C++ OpenwireStringSupport::readString aborts on >> >> empty property >> >> >> >> >> >> 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 >> >> > >> >> >> >> -- >> >> View this message in context: >> >> http://www.nabble.com/C%2B%2B-OpenwireStringSupport%3A%3AreadS >> >> tring-aborts-on-empty-property-tf4623108s2354.html#a13213445 >> >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > > -- View this message in context: http://www.nabble.com/C%2B%2B-OpenwireStringSupport%3A%3AreadString-aborts-on-empty-property-tf4623108s2354.html#a13233469 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
