jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Should we release a 2.10.1 ?
Date Tue, 26 Nov 2013 16:11:59 GMT
On 26 November 2013 12:37, Philippe Mouawad <philippe.mouawad@gmail.com> wrote:
> Hello,
> It seems there may be some other Use case to double check when installing
> on Windows.
>
> On french forum we have a issue reported by a user who installs jmeter 2.10
> (On Windows 2007 Server), he has this time issues with write access to bin
> folder:
>
> Env Vars :
>
>    - JAVA_HOME = C:\Program Files\Java\jdk1.7.0_45
>    - JMETER_HOME = C:\Program Files\Java\JMeter
>
> Error message:
>
>    - 2013/11/26 10:43:17 ERROR - jmeter.protocol.http.proxy.ProxyControl:
>    Could not initialise key store java.io.IOException: Command :'"keytool"
>    "-genkeypair" "-alias" ":root_ca:" "-dname" "CN=_ DO NOT INSTALL unless
>    this is your certificate (JMeter root CA), OU=Username: JM, C=BE" "-keyalg"
>    "RSA" "-keystore" "proxyserver.jks" "-storepass" "JA9YysNFMEtENUxHAPRz"
>    "-keypass" "JA9YysNFMEtENUxHAPRz" "-validity" "7" "-ext" "bc:c"' failed,
>    code: 1
>    erreur keytool : java.io.FileNotFoundException: proxyserver.jks (Accès
>    refusé)
>
> I don't have a windows Machine to double check it.

The same would happen on other OSes.

> This kind of issue may be faced by users havinf different Home and Install.
>
> So I wonder if it is a good idea to use:
>
>     private static final String CERT_DIRECTORY =
>
>         JMeterUtils.getPropDefault("proxy.cert.directory",
> JMeterUtils.getJMeterBinDir()); // $NON-NLS-1$
>
>
> Should we use this instead:
>
> JMeterUtils.getPropDefault("proxy.cert.directory",
> JMeterUtils.getJMeterHome()); // $NON-NLS-1$

Not sure that would help, as JMeterBin is JMeterHome + "/bin".

If the bin dir is not writable, then home (i.e. its parent dir) is
unlikely to be writable either.

> Regards
> Philippe
>
> On Tue, Nov 12, 2013 at 4:17 PM, Milamber <milamber@apache.org> wrote:
>
>>
>> Le 12/11/2013 09:40, Shmuel Krakower a ecrit :
>>
>>  Hi,
>>> Is there a date or a process started for the 2.10.1 release?
>>>
>>
>> As soon as possible.
>> Still some works with the keytool availability issue. After the release
>> process could be start.
>>
>>
>>
>>
>>> Best,
>>>
>>> Shmuel Krakower.
>>> www.Beatsoo.org - re-use your jmeter scripts for application performance
>>> monitoring from worldwide locations for free.
>>>
>>>
>>> On Wed, Nov 6, 2013 at 12:08 AM, Philippe Mouawad <
>>> philippe.mouawad@gmail.com> wrote:
>>>
>>>  On Tue, Nov 5, 2013 at 1:14 PM, sebb <sebbaz@gmail.com> wrote:
>>>>
>>>>  On 4 November 2013 18:49, Milamber <milamber@apache.org> wrote:
>>>>>
>>>>>> Le 04/11/2013 17:19, Philippe Mouawad a ecrit :
>>>>>>
>>>>>>  Hello,
>>>>>>> You may have missed my previous mail so created a special thread.
>>>>>>>
>>>>>>> Current 2.10 contains 3 issues:
>>>>>>> - NativeCommand timeout issue => Not a problem for me as it's
not a
>>>>>>> regression
>>>>>>> - Bad handling of redirects => This is a regression and could
be a big
>>>>>>> problem for users/
>>>>>>>
>>>>>>>
>>>>>>>  http://stackoverflow.com/questions/19636282/jmeter-
>>>> error-in-redirect-url-for-getviewed
>>>>
>>>>> 65 times
>>>>>>> - HTTPS Recorder => Current implementation introduces issue
for BAD
>>>>>>>
>>>>>> java
>>>>
>>>>> installation. This issue seems to affect some users judging on the
>>>>>>>
>>>>>> number
>>>>>
>>>>>> of views of views It seems to be annoying although I am not sure
we
>>>>>>>
>>>>>> can
>>>>
>>>>> do
>>>>>
>>>>>> something about it as we do not distribute the jks anymore. But maybe
>>>>>>>
>>>>>> give
>>>>>
>>>>>> more details in LOG or UI:
>>>>>>>
>>>>>>>
>>>>>>>  http://stackoverflow.com/questions/19550472/jmeter-2-
>>>> 10-http-recorder-throws-keytool-exception=
>>>>
>>>>>    517 views
>>>>>>>
>>>>>>>
>>>>>>>  http://stackoverflow.com/questions/19592609/jmeter-2-
>>>> 10-proxyserver-jks-error=
>>>>
>>>>> 68 views
>>>>>>>
>>>>>>>
>>>>>>> So I vote for a new 2.10.1
>>>>>>>
>>>>>>
>>>>>> Ok for me too.
>>>>>>
>>>>>>  Agreed.
>>>>>
>>>>>  Ok great
>>>>
>>>>  and propose to add a clear UI message when
>>>>>>> keytool is not available or folder is not writable.
>>>>>>>
>>>>>>
>>>>>> Not already done?
>>>>>>
>>>>> I was working on improving the checks.
>>>>> Have not committed anything yet.
>>>>>
>>>>> The idea is to check what happens when keytool is run on its own - it
>>>>> should generate a help message and exit with success status.
>>>>> If not, then report an error. The check needs to be done early enough
>>>>> to ensure that the correct option is chosen (keytool may still be
>>>>> needed for Java6).
>>>>>
>>>>> BTW I found out why a Java installation can work for JMeter but not
>>>>> keytool - it seems that the instal process can put java[w].exe in the
>>>>> Windows directory. That is sufficient to run Java, but of course not
>>>>> keytool. In this case the java app must be able to find the runtime
>>>>> jar, so it might be possible to look up the class loader for say
>>>>> java.lang.Object and use that to find the keytool path.
>>>>>
>>>>> It might still be sensible to provide a property override for the
>>>>> keytool
>>>>> path.
>>>>>
>>>>>
>>>>> Agree
>>>>>
>>>>>> Regards
>>>>>>> Philippe M.
>>>>>>>
>>>>>>>
>>>>
>>>> --
>>>> Cordialement.
>>>> Philippe Mouawad.
>>>>
>>>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Mime
View raw message