Hi This requirement first appeared when testing an application that generates a JMS message to a queue as the result of an action (not necessarily a JMS request).
The problem is the different semantics of queues and topics as stated. While with topics the consumer can stay alive till the end of the test and not interfere with other tests, with queues they have to be closed because they will not enable the other consumers to receive the messages... My use case would require that several consumers can be instantiated by their samplers and their life cycle to be well managed so they stop receiving after they receive the specified number of messages. Best regards João Ferreira > -----Original Message----- > From: sebb [mailto:[email protected]] > Sent: quarta-feira, 23 de Junho de 2010 13:14 > To: JMeter Users List > Subject: JMS help wanted: need use cases for queue subscriptions > > JMeter 2.3.4 supports JMS Topics for Publish and Subscribe. > > Most of the code will also work with Queues, however a message sent to > a queue can only be read once (unlike topics, which can be read by > many users). > > So JMeter likely needs to behave differently when receiving messages > from queues. > > In order to implement suitable behaviour, it would be very useful to > have some typical use-cases. > > So if you would like to be able to test your JMS system with JMeter, > please share brief details. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
