Hi,
I investigated the bug report and the logfile.
The timeout is set to 2000 (milliseconds). This is the (undocumented ;-( ) default when there is no timeout.
2005/05/18 14:00:12 DEBUG - jmeter.protocol.jms.sampler.JMSSampler: Timeout = 2000]
This is the flow of the first and the last message.
FIRST MESSAGE ID
2005/05/18 14:00:17 DEBUG - jmeter.protocol.jms.sampler.MessageAdmin: put request id ID:414d512051756575654d616e61676572632d8b4220000601
2005/05/18 14:00:19 DEBUG - jmeter.protocol.jms.sampler.MessageAdmin: get reply for ID:414d512051756575654d616e61676572632d8b4220000601 for [EMAIL PROTECTED]
2005/05/18 14:00:19 DEBUG - jmeter.protocol.jms.sampler.MessageAdmin: Message ID:414d512051756575654d616e61676572632d8b4220000601 not found.
2005/05/18 14:00:29 DEBUG - jmeter.protocol.jms.sampler.Receiver: CorrId:ID:414d512051756575654d616e61676572632d8b4220000601
2005/05/18 14:00:29 DEBUG - jmeter.protocol.jms.sampler.MessageAdmin: put reply id ID:414d512051756575654d616e61676572632d8b4220000601 for holder null
LAST MESSAGE ID
2005/05/18 14:00:17 DEBUG - jmeter.protocol.jms.sampler.MessageAdmin: put request id ID:414d512051756575654d616e61676572632d8b4220001401
2005/05/18 14:00:19 DEBUG - jmeter.protocol.jms.sampler.MessageAdmin: get reply for ID:414d512051756575654d616e61676572632d8b4220001401 for [EMAIL PROTECTED]
2005/05/18 14:00:19 DEBUG - jmeter.protocol.jms.sampler.MessageAdmin: Message ID:414d512051756575654d616e61676572632d8b4220001401 not found.
2005/05/18 14:00:30 DEBUG - jmeter.protocol.jms.sampler.Receiver: CorrId:ID:414d512051756575654d616e61676572632d8b4220001401
2005/05/18 14:00:30 DEBUG - jmeter.protocol.jms.sampler.MessageAdmin: put reply id ID:414d512051756575654d616e61676572632d8b4220001401 for holder null
The first line indicates that the message has been send.
2 seconds later
The second indicates that a notify (arrival of message) or a timeout has occurred.
The third line indicates that it is a timeout has occurred (no message in message administration)
13 seconds later
The fourth line indicates that a message has been received
The fifth line administers this message in the message administration
Try to set the timeout to a higher level. With this information it seems ok that the testcases fail, because an (implicit) timeout of 2 seconds is used.
Hope this helps.
Greetings,
Martijn
P.S. I will update the bugzilla report as soon as I have my account for Bugzilla.
[EMAIL PROTECTED] wrote:
The bug is filed in bugzilla as
Bug #34953 <http://issues.apache.org/bugzilla/show_bug.cgi?id=34953>
Greetings Filip
Please can you file a Bugzilla report, and attach the jmeter.log file to it, plus a copy of a sample test plan that shows the error (remember to remove any passwords etc first). Remember to provide versions of OS, JVM, etc.
Can't make any guarantees as to when it will be fixed, but at least once there is a Bugzilla report it will be easier to keep track of the problem.
S.
On 5/18/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi all,
I am currently using the latest CVS version of Jmeter and it has JMS
support. There is however one big error in the implementation, if I send
JMS messages using multiple threads it occurs as soon as approximately
100messages using 3 threads that JMeter stops the test and reports that
it cannot find the given correlationID. So in fact a multi threaded test
using JMS in JMeter is not possible yet, will this be solved in the
future and if so can you inform me when?
Thanks Filip
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- 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]
