Re: message stuck inside Activemq queue
we'll need some more information about the setup, number of consumers etc - and a junit test case always makes resolution of issues quicker cheers, Rob On 23 Dec 2006, at 07:34, bluedolphin wrote: I m using activemq 4.1 and wonder y sometimes the message that pass inside the dedicated queue can't be read out by my other application? Most of the times the application can read the message from the queue but just sometimes the message won't be read out. Is there any configuration needed for the activemq? Thanks -- View this message in context: http://www.nabble.com/message-stuck- inside-Activemq-queue-tf2873800.html#a8032192 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Created: (AMQCPP-32) Stomp messages don't preserve property types: please document this behaviour
Stomp messages don't preserve property types: please document this behaviour Key: AMQCPP-32 URL: https://issues.apache.org/activemq/browse/AMQCPP-32 Project: ActiveMQ C++ Client Issue Type: Wish Components: Stomp Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler I am producing messages from Java and C++ using ActiveMQ and AMQCPP, respectively. Messages I produce have an int property set on them which I want to select on, again in Java or C++. As far as I can tell from the [Stomp Protocol specification|http://stomp.codehaus.org/Protocol] there is no way to specify the types of message headers. As a result, all the messages end up with String properties as can be be seen in the unmarshal method of [org.apache.activemq.transport.stomp|http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/stomp/StompWireFormat.java?revision=470398view=markup]. I can work around this problem by selecting on id=123||id='123' in both Java and C++, but it seems a bit suboptimal. At least, this issue should be documented somewhere in activemq::connector::stomp::commands::StompMessage to help other people who can't figure out why their selectors don't work. We could consider adding a function that allows the user to specify that Stomp message properties should be sent in a type safe manner, and then prepend some kind of string to the property name to indicate the type. StompWireFormat on the Java side could check for this case and set the typed properties accordingly. This is probably too much of a hack -- people who want typed properties to work right can use Openwire in the (hopefully) near future. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Message Groups Stomp
I am using the php stomp client to produce and consume messages. Please, can somebody clarify whether my understanding of message group implementation is correct. (1) All that is needed to CREATE a message group is to add the jmsxgroupid to the producer stomp header of the first message and the broker will create the message group? (2) To keep sending messages to the message group, add the jmsxgroupid to the producer stomp header for each message intended for the message group? (3) The broker will automatically assign the message group to the first avaliable stomp consumer? Thus I do not have to assign consumers to message groups because the broker does this? Thanks -- View this message in context: http://www.nabble.com/Message-Groups---Stomp-tf2874706.html#a8034700 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Updated: (AMQCPP-32) Stomp messages don't preserve property types: please document this behaviour
[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=all ] Timothy Bish updated AMQCPP-32: --- Priority: Trivial (was: Major) Stomp messages don't preserve property types: please document this behaviour Key: AMQCPP-32 URL: https://issues.apache.org/activemq/browse/AMQCPP-32 Project: ActiveMQ C++ Client Issue Type: Wish Components: Stomp Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler Priority: Trivial I am producing messages from Java and C++ using ActiveMQ and AMQCPP, respectively. Messages I produce have an int property set on them which I want to select on, again in Java or C++. As far as I can tell from the [Stomp Protocol specification|http://stomp.codehaus.org/Protocol] there is no way to specify the types of message headers. As a result, all the messages end up with String properties as can be be seen in the unmarshal method of [org.apache.activemq.transport.stomp|http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/stomp/StompWireFormat.java?revision=470398view=markup]. I can work around this problem by selecting on id=123||id='123' in both Java and C++, but it seems a bit suboptimal. At least, this issue should be documented somewhere in activemq::connector::stomp::commands::StompMessage to help other people who can't figure out why their selectors don't work. We could consider adding a function that allows the user to specify that Stomp message properties should be sent in a type safe manner, and then prepend some kind of string to the property name to indicate the type. StompWireFormat on the Java side could check for this case and set the typed properties accordingly. This is probably too much of a hack -- people who want typed properties to work right can use Openwire in the (hopefully) near future. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQCPP-32) Stomp messages don't preserve property types: please document this behaviour
[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=comments#action_37761 ] Albert Strasheim commented on AMQCPP-32: I think I'll make a documentation patch. Thanks. Stomp messages don't preserve property types: please document this behaviour Key: AMQCPP-32 URL: https://issues.apache.org/activemq/browse/AMQCPP-32 Project: ActiveMQ C++ Client Issue Type: Wish Components: Stomp Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler Priority: Trivial I am producing messages from Java and C++ using ActiveMQ and AMQCPP, respectively. Messages I produce have an int property set on them which I want to select on, again in Java or C++. As far as I can tell from the [Stomp Protocol specification|http://stomp.codehaus.org/Protocol] there is no way to specify the types of message headers. As a result, all the messages end up with String properties as can be be seen in the unmarshal method of [org.apache.activemq.transport.stomp|http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/stomp/StompWireFormat.java?revision=470398view=markup]. I can work around this problem by selecting on id=123||id='123' in both Java and C++, but it seems a bit suboptimal. At least, this issue should be documented somewhere in activemq::connector::stomp::commands::StompMessage to help other people who can't figure out why their selectors don't work. We could consider adding a function that allows the user to specify that Stomp message properties should be sent in a type safe manner, and then prepend some kind of string to the property name to indicate the type. StompWireFormat on the Java side could check for this case and set the typed properties accordingly. This is probably too much of a hack -- people who want typed properties to work right can use Openwire in the (hopefully) near future. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-33) Integration tests crash if broker isn't running
[ https://issues.apache.org/activemq/browse/AMQCPP-33?page=all ] Timothy Bish updated AMQCPP-33: --- Issue Type: Improvement (was: Bug) Priority: Trivial (was: Major) Integration tests crash if broker isn't running --- Key: AMQCPP-33 URL: https://issues.apache.org/activemq/browse/AMQCPP-33 Project: ActiveMQ C++ Client Issue Type: Improvement Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler Priority: Trivial The AMQCPP integration tests crash on my Windows system if a broker isn't running. I'm guessing it's an uncaught exception from the connection attempt that's causing problems. It should probably be caught and do some kind of CPPUNIT_ASSERT(false). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQCPP-33) Integration tests crash if broker isn't running
[ https://issues.apache.org/activemq/browse/AMQCPP-33?page=all ] Timothy Bish reassigned AMQCPP-33: -- Assignee: Timothy Bish (was: Nathan Mittler) Integration tests crash if broker isn't running --- Key: AMQCPP-33 URL: https://issues.apache.org/activemq/browse/AMQCPP-33 Project: ActiveMQ C++ Client Issue Type: Improvement Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Timothy Bish Priority: Trivial Fix For: 1.1 The AMQCPP integration tests crash on my Windows system if a broker isn't running. I'm guessing it's an uncaught exception from the connection attempt that's causing problems. It should probably be caught and do some kind of CPPUNIT_ASSERT(false). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
