Skip to content
This repository has been archived by the owner on Nov 28, 2022. It is now read-only.

Jmeter 4.0 and 5.0 servers fail to start due to rmi_keystore error #9

Open
christiannews opened this issue Aug 14, 2020 · 2 comments
Open

Comments

@christiannews
Copy link

Attempting to build the docker image with apache jmeter 5.0 leads to the following error:

rmi_keystore.jks (No such file or directory)

The local_master container would come up but the server wouldn't start.

I was able to fix this issue by updating user.properties within the master container with the following line:
server.rmi.ssl.disable=true

(I also needed to add an extra line in the dockerfile for installing unzip in order for the build to succeed).

After making these changes I was able to build the dockerfile (but set the jmeter version to 5.3 in the build args in order to use a recent version of jmeter) and then docker-compose up my local image successfully, providing me with a master and server container. I was then able to successfully run my jmx tests from within the master docker container. Perhaps adding these changes to 4.0 and 5.0 will allow the servers to start for those that want to use a newer version of jmeter?

@subanithak
Copy link

You can use PodPreset concept by following steps

  • Define user.properties
jmeter.save.saveservice.default_delimiter=\t
jmeter.save.saveservice.print_field_names=true
server.rmi.ssl.disable=true
  • Create a configmap for user.properties.
$ kubectl create configmap user.properties --from-file=user.properties
  • Create PodPreset as below
apiVersion: settings.k8s.io/v1alpha1
kind: PodPreset
metadata:
  name: jmeter-podpreset
spec:
  selector:
    matchLabels:
      app.kubernetes.io/name: distributed-jmeter
   
  volumes: 
    - configMap:
          defaultMode: 420
          name: user.properties
      name: user-properties-vol

  volumeMounts:
    - mountPath: /jmeter/apache-jmeter-5.0/bin/user.properties
      name: user-properties-vol
      subPath: user.properties
  • Apply PodPreset
$ kubectl apply -f jmeter-podpreset.yaml

@jayachandralingam
Copy link

@christiannews If you are using helm, simply add a line to "distributed-jmeter-docker/config/user.properties" file with "server.rmi.ssl.disable=true"... I hope this will work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants