Re: JMS issue

2005-05-19 Thread Peter Lin
setting it in the sampler is definitely the best solution. peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: JMS issue

2005-05-19 Thread sebb
On 5/19/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > sebb wrote: > > >If you set it very high, it might overflow and become negative? > > > >Try enabling debug for > > > >jmeter.protocol.jms.sampler.JMSSampler > > > >and this should show the value actually used. > > > >S. > >On 5/19/05, [EMA

Re: JMS issue

2005-05-19 Thread Filip . L_Ecluse
sebb wrote: If you set it very high, it might overflow and become negative? Try enabling debug for jmeter.protocol.jms.sampler.JMSSampler and this should show the value actually used. S. On 5/19/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: sebb wrote: On 5/18/05, Martijn Blankestijn <

Re: JMS issue

2005-05-19 Thread m . blankestijn
I thought the timeout could be set in the userinterface of the sampler. Not as a JMS property, but as a regular property. Please check the screen, because in the version that I want to commit tonight the timeout version attribute is on the JMS Sampler page (including the milliseconds remark)

Re: JMS issue

2005-05-19 Thread sebb
If you set it very high, it might overflow and become negative? Try enabling debug for jmeter.protocol.jms.sampler.JMSSampler and this should show the value actually used. S. On 5/19/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > sebb wrote: > > >On 5/18/05, Martijn Blankestijn <[EMAIL PR

Re: JMS issue

2005-05-19 Thread sebb
Not sure that's necessary - just need to change it so the code calls resource.wait(timeout) or resource.wait() as appropriate. If it is considered desirable to provide a default, this could be used to set the Timeout field on the Gui if not already set. I guess the default value could be a prop

Re: JMS issue

2005-05-19 Thread Filip . L_Ecluse
sebb wrote: On 5/18/05, Martijn Blankestijn <[EMAIL PROTECTED]> wrote: Hi, I investigated the bug report and the logfile. Thanks! The timeout is set to 2000 (milliseconds). This is the (undocumented ;-( ) default when there is no timeout. Might be more intuitive if no timeout meant

Re: JMS issue

2005-05-18 Thread Peter Lin
I'll take a look at the sampler and see if I can change it to read from jmeter.properties peter On 5/18/05, sebb <[EMAIL PROTECTED]> wrote: > On 5/18/05, Martijn Blankestijn <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I investigated the bug report and the logfile. > > Thanks! > > > The timeout

Re: JMS issue

2005-05-18 Thread sebb
On 5/18/05, Martijn Blankestijn <[EMAIL PROTECTED]> wrote: > Hi, > > I investigated the bug report and the logfile. Thanks! > The timeout is set to 2000 (milliseconds). This is the (undocumented ;-( > ) default when there is no timeout. > Might be more intuitive if no timeout meant just that -

Re: JMS issue

2005-05-18 Thread Martijn Blankestijn
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 l

Re: JMS issue

2005-05-18 Thread Filip . L_Ecluse
The bug is filed in bugzilla as Bug #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). R

Re: JMS issue

2005-05-18 Thread Peter Lin
you're using the queue sampler right? the topic sampler should work correctly. I've tested it for 100K, 200K, 300K, 400K, 500K and 1million messages. peter lin On 5/18/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi all, > > I am currently using the latest CVS version of Jmeter and it ha

Re: JMS issue

2005-05-18 Thread sebb
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 t

JMS issue

2005-05-18 Thread Filip . L_Ecluse
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