Service JNA bloqué à l’état « starting » après redémarrage du serveur

[yzhi]

Bonjour,

Après avoir installé le Remote Engine sur notre serveur, nous avons constaté que le service JNA reste systématiquement à l’état “starting” après chaque redémarrage du serveur.

Il est nécessaire d’exécuter manuellement la commande bundle:restart afin que le service passe à l’état “active”.

S’agit-il d’un comportement normal ?

Merci d’avance pour votre aide.

Yan

[gouravdubey5]

Hello,

After restarting Talend Cloud, the JNA service may remain stuck in the “starting” state. This is a known behavior in some environments.
Resolution: Manually restart the bundle to force the service to become active.
Action : bundle:restart

If the issue persists after multiple restarts, collect Karaf logs and contact Talend Support.

Supported links :https://karaf.apache.org/manual/latest/#_managing_bundles
This document explains how restarting bundles resolves services stuck in starting state in Karaf-based runtimes.

Thanks,

Gourav

[david_lucas]

Hello 

Did you install the remote engine manually ? Did yo ufollow RE 2.12 or 2.13 documentation ? 

Can you tell us how you did create the service ? 

To solve this issue, stop the RE,  clean up karaf cach by deleting content on RE/data folder, and start the RE