I wonder if this is related to the bug in the HTTP Proxy; when you
click the Stop button, it will wait for one more connection because of the
way it is coded. There is a port bind call, that will block until there is
a connection, and the check to see if stop has been pressed is located
after this. It really needs to be in it's own thread, so that the bind can
be interrupted.
"Stover, Michael"
<Michael.Stover@usa. To: "'JMeter Users List'"
<[EMAIL PROTECTED]>
xerox.com> cc:
Subject: RE: New Bug(s)
02/26/02 03:16 PM
Please respond to
"JMeter Users List"
yeah, I think I can see why that would happen. This deserves to be
submitted as real bug so I don't forget about it. :-)
-Mike
> -----Original Message-----
> From: Paone, Frank J [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 26, 2002 3:10 PM
> To: '[EMAIL PROTECTED]'
> Subject: New Bug(s)
>
>
> I think I noticed a new bug or bugs..
>
> I am utilizing the jdbc function of jMeter. When I start a
> thread, it kicks
> off ok, but when I stop it, it appears that jMeter continues
> to put a load
> on the data server, and the connections to the data base
> don't go away until
> I kill jMeter.
> And once jMeter produces a considerable load on the data server, the
> charting seem to degrade.
>
>
>
>
>
>
> Frank Paone
> DBA Engineering Team
> phone: 201 524-4661 two-way: [EMAIL PROTECTED]
>
>
>
> --------------------------------------------------------------
> ----------------
> This message is intended only for the personal and
> confidential use of the designated recipient(s) named above.
> If you are not the intended recipient of this message you are
> hereby notified that any review, dissemination, distribution
> or copying of this message is strictly prohibited. This
> communication is for information purposes only and should not
> be regarded as an offer to sell or as a solicitation of an
> offer to buy any financial product, an official confirmation
> of any transaction, or as an official statement of Lehman
> Brothers. Email transmission cannot be guaranteed to be
> secure or error-free. Therefore, we do not represent that
> this information is complete or accurate and it should not be
> relied upon as such. All information is subject to change
> without notice.
>
>
--
To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>