Starting the JWSDP 1.3 server fails for jaxr standalone tck run

This issue is duplicated to track the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=541542 .

Using the same information from the bug:

[Anand Francis Joseph] 2018-11-25 23:19:02 EST

As part of JAXR suite, we start the JWSDP 1.3 server, It was working fine earlier in the Jakarta EE TCK CJE environment. Now I suddenly see this error

'[' jaxr == jaxr ']'

'[' -f /opt/jwsdp-1.3/bin/startup.sh ']'

/opt/jwsdp-1.3/bin/startup.sh Error: no client' JVM at/opt/j2sdk1.4.2_41/jre/lib/i386/client/libjvm.so'.

Was there any change in the CJE instance or its configuration recently, that is causing this error ?

The same Docker image runs fine in my environment, So I don't think its an issue with the docker image. If its due to some restrictions in the OpenShift instance, please suggest the required changes to be done in the Docker image.

The jvm.cfg (at /opt/j2sdk1.4.2_41/jre/lib/i386/jvm.cfg) contains the following entries.
-client KNOWN
-server KNOWN
-hotspot ALIASED_TO -client
-classic WARN
-native ERROR
-green ERROR

[Anand Francis Joseph] 2018-11-26 05:26:36 EST

The issue does not happen always. I reran the job and there this issue was not seen and the JWSDP server was started without any issue. https://jenkins.eclipse.org/jakartaee-tck/blue/organizations/jenkins/jakartaee-tck/detail/master/116/pipeline/36/

Solution suggested by Frederic Gurr: [Frederic Gurr] 2018-11-26 12:32:23 EST

This issue seems to be related: => https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623419 Possible fix is provided here: => https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg29226.html Please try the described fix and report back if it worked.

eclipse-ee4j / jaxr-api

Starting the JWSDP 1.3 server fails for jaxr standalone tck run #25