Hi
In my test plan, I have added som Assertions, namely
ResponseAssertion.
However, some of the Assertions only makes sense if some variables in
the test plan has a certain value.
So in some cases the Assertion needs to be checked for a certain HTTP
Request, but in other cases the assertion
Shouldn't a Java or Junit sample not suffice to meter Corba clients? Do
you want a sampler at the protocol level?
This should be difficult, as the protocol contains no context
information. IIOP data without the corresponding IDL is useless.
Robert Spielmann wrote:
Hi all,
in accordance with
Jürgen Weber schrieb:
Shouldn't a Java or Junit sample not suffice to meter Corba clients?
Do you want a sampler at the protocol level?
This should be difficult, as the protocol contains no context
information. IIOP data without the corresponding IDL is useless.
I will presumably need to load
I wasn't clear, I meant of course load-testing the server, but this you
can do by calling your Corba clients by a Java or Junit sampler. Some 64
jmeter Java sampler threads should indeed stress your server.
Robert Spielmann wrote:
Jürgen Weber schrieb:
Shouldn't a Java or Junit sample not
If it's an easy task in Java, presumably the same will work in JMeter.
On 16/03/07, Steffen Oehme [EMAIL PROTECTED] wrote:
Hi,
one of the applications I wanted to check with JMeter requires me to
use SSL instead of TLS. No way to work around that from the
application side, I'm afraid.
Anyways,
On 17/03/07, Alf Høgemark [EMAIL PROTECTED] wrote:
Hi
I am considering doing some work on the HTTP Proxy Server.
Here is what I've thought about so far :
- Make it possible to filter requests by specifying content type to
include and content type to exclude regular expressions
Good idea.
-
Sure, but I really don't want to go down to the code and modify it!
From what I read, the protocol in JSSE is set with the
setEnabledProtocols-Method for an SSLSocket.
The parameters can be:
SSLv2 SSL version 2 protocol
SSLv3 SSL version 3 protocol
TLSv1 TLS version 1 protocol (defined in
sebb wrote:
I think that has already have been done via a property -
jmeter.httpsampler - but it could be turned into a GUI option.
Yes, that setting controls what class the HTTPSamplerFactory will
instantiate.
But by changing it to HTTPSampler2, and trying to use the HTTP Proxy,
you get
Nino Wael wrote:
Could be really great if you could fix the I mentioned in another thread here
recently. It's actually pretty critical.
I'll be happy to provide more extensively information about it.
regards Nino
Hi.
Is your problem really :
Just had another look at the SSL JMeter code, and the JsseSSLManager
class creates the context using:
SSLContext.getInstance(TLS);
A simple (but not very versatille) way to implement other algorithms
would be to use a property, with a default of TLS.
If I generate a new nightly with that as
On 3/14/07, sebb [EMAIL PROTECTED] wrote:
On 14/03/07, robert lazarski [EMAIL PROTECTED] wrote:
On 3/14/07, sebb [EMAIL PROTECTED] wrote:
On 14/03/07, robert lazarski [EMAIL PROTECTED] wrote:
You may need the referer (sic) header.
Cookie: JSESSIONID=8EF794277593CDAE19A765619417894C
Absolutely, just let me know once done.
And for the long-term solution, as I mentioned, a dropdown with values
such as HTTP, HTTPS (SSLv1), ... HTTPS (TLSv1) would be pretty
nice..
sebb schrieb:
Just had another look at the SSL JMeter code, and the JsseSSLManager
class creates the context
On 17/03/07, robert lazarski [EMAIL PROTECTED] wrote:
On 3/14/07, sebb [EMAIL PROTECTED] wrote:
On 14/03/07, robert lazarski [EMAIL PROTECTED] wrote:
On 3/14/07, sebb [EMAIL PROTECTED] wrote:
On 14/03/07, robert lazarski [EMAIL PROTECTED] wrote:
You may need the referer (sic) header.
On 17/03/07, Alf Høgemark [EMAIL PROTECTED] wrote:
sebb wrote:
I think that has already have been done via a property -
jmeter.httpsampler - but it could be turned into a GUI option.
Yes, that setting controls what class the HTTPSamplerFactory will
instantiate.
But by changing it to
This discussion about TLS / SSL seems related to
:http://issues.apache.org/bugzilla/show_bug.cgi?id=39638
If Sebb's fix works, and he can suggest how he wants the GUI changed for
the HTTP Request parameters, I can probably look into making a patch for
allowing the user to specify what https
I've uploaded r519437 if you want to try and break it ;-)
On 17/03/07, Steffen Oehme [EMAIL PROTECTED] wrote:
Absolutely, just let me know once done.
And for the long-term solution, as I mentioned, a dropdown with values
such as HTTP, HTTPS (SSLv1), ... HTTPS (TLSv1) would be pretty
nice..
On 17/03/07, Alf Høgemark [EMAIL PROTECTED] wrote:
This discussion about TLS / SSL seems related to
:http://issues.apache.org/bugzilla/show_bug.cgi?id=39638
Agreed.
If Sebb's fix works, and he can suggest how he wants the GUI changed for
the HTTP Request parameters, I can probably look into
Yes, it might work well to just leave the protocol field as a text field
where the user can enter whatever he wants, as it is today.
So the novice users will continue to enter either http or https.
And people who read the documentation will write http(tls), for
example, I assume it will
On 3/17/07, sebb [EMAIL PROTECTED] wrote:
On 17/03/07, robert lazarski [EMAIL PROTECTED] wrote:
On 3/14/07, sebb [EMAIL PROTECTED] wrote:
On 14/03/07, robert lazarski [EMAIL PROTECTED] wrote:
On 3/14/07, sebb [EMAIL PROTECTED] wrote:
On 14/03/07, robert lazarski [EMAIL PROTECTED]
On 17/03/07, robert lazarski [EMAIL PROTECTED] wrote:
On 3/17/07, sebb [EMAIL PROTECTED] wrote:
On 17/03/07, robert lazarski [EMAIL PROTECTED] wrote:
On 3/14/07, sebb [EMAIL PROTECTED] wrote:
On 14/03/07, robert lazarski [EMAIL PROTECTED] wrote:
On 3/14/07, sebb [EMAIL PROTECTED]
20 matches
Mail list logo
