Troubles with Shenandoah

Simone Bordet simone.bordet at gmail.com
Sun Apr 7 15:19:48 UTC 2019


Hi,

On Sun, Apr 7, 2019 at 4:54 PM Roman Kennke <rkennke at redhat.com> wrote:
>
> Oh apparently it has trobles to print anything to the terminal. I can
> get it to start by blindly pressing enter a few times ;-) Duh.

This is an issue in a library used by Maven
Go to $MAVEN/lib/ and delete or rename jansi-<version>.jar to
jansi-<version>.jar.dontuse

> I am getting an exception like this on the server side, do you also see
> it?
>
> https://paste.fedoraproject.org/paste/uTRDekos5uPbU7bojMK45g

Ah yes, this is due to the fact that the monitoring we use was not
aware of the JMX names of Shenandoah.

You will have a better luck using the latest code:

$ git clone https://github.com/cometd/cometd.git
$ cd cometd
$ mvn clean install -DskipTests

You're good to go.

I can setup a Google Meet/Hangout if you want.

I'm running now with heuristics=passive, and the problem seems gone.
I'll post when the run is finished, in about 15-20 minutes.

-- 
Simone Bordet
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz


More information about the shenandoah-dev mailing list