Questions & Answers

[anhphamtuan83]

Hi everyone,

I am update to fs_2022.9 and switch to isolated mode (currently running in legacy mode)

What I did:

After copy fs-isolated-server.jar and wrapper.jar to /server/lib-isolated

And edit /bin.fs5.mode -> isolated

Copy fs-wrapper.isolated.conf   ~fs/conf/ fs-wrapper.isolated.conf

Server still in Legacy mode.

As I checked in system information:

ava.class.path

shared/lib-isolated/com.sap.security.api.jar shared/lib-isolated/com.sap.security.core.jar shared/lib-isolated/iaik_jce.jar server/classes server/lib/fs-server.jar > I think it should be server/lib-isolated/fs-isolated-server.jar server/lib/wrapper.jar

Please help to fix this issue for me. Any advice are appreciated. 

Thank you very much!

[hoebbel]

Dear anhphamtuan83,

Have you updated the backend (unpacking the fs-update-3.0.1.tar.gz via the FirstSpirit installation directory)?
If so, did you then start the FirstSpirit server via the fs-server start script?

Hints:
The fs5 start script is outdated and cannot be used with 2022.9.
A start as a service configured with the old version could also cause the effect.
Have a look at the fs-wrapper.log - maybe you will find a hint there.

If these hints do not help, please contact our Tech Support so that the problem can be analysed.

Best regards
Holger

[anhphamtuan83]

Good morning Holger,

Have you updated the backend (unpacking the fs-update-3.0.1.tar.gz via the FirstSpirit installation directory)?
If so, did you then start the FirstSpirit server via the fs-server start script?

Yes, I did.

The fs5 start script is outdated and cannot be used with 2022.9.
A start as a service configured with the old version could also cause the effect.
Have a look at the fs-wrapper.log - maybe you will find a hint there.

->  Yes I tried fs5 start. fs-warapper.log show like this:

INFO | jvm 1 | 2022/09/12 08:49:49 | [0.214s][info][class,load] java.text.MessageFormat$Field source: jrt:/java.base
INFO | jvm 1 | 2022/09/12 08:49:49 | Error: Could not find or load main class de.espirit.firstspirit.server.CMSServer
INFO | jvm 1 | 2022/09/12 08:49:49 | Caused by: java.lang.ClassNotFoundException: de.espirit.firstspirit.server.CMSServer
INFO | jvm 1 | 2022/09/12 08:49:49 | [0.214s][info][class,load] java.lang.Shutdown source: jrt:/java.base
INFO | jvm 1 | 2022/09/12 08:49:49 | [0.214s][info][class,load] java.lang.Shutdown$Lock source: jrt:/java.base
DEBUG | wrapper | 2022/09/12 08:49:49 | Preparing to restart with mode 2.
DEBUG | wrapper | 2022/09/12 08:49:49 | JVM was only running for 0 seconds leading to a failed restart count of 1.
DEBUG | wrapper | 2022/09/12 08:49:49 | Enqueue Event 'jvm_failed_invocation'
FATAL | wrapper | 2022/09/12 08:49:49 | There were 1 failed launches in a row, each lasting less than 35 seconds. Giving up.
FATAL | wrapper | 2022/09/12 08:49:49 | There may be a configuration problem: please check the logs.
DEBUG | wrapper | 2022/09/12 08:49:49 | Enqueue Event 'jvm_max_failed_invocations'
DEBUG | wrapper | 2022/09/12 08:49:49 | Enqueue Event 'wrapper_stop'
DEBUG | wrapperp | 2022/09/12 08:49:50 | closing backend server.

If these hints do not help, please contact our Tech Support so that the problem can be analysed.

-> Yes please send an technical to support. Thank you

Regards,

Tuan Anh

[hoebbel]

Hello Tuan,

have you also tried "fs-server start"?

The exception sounds to me like an attempt to start a legacy server from an fs-isolated-server.jar. The start class does not exist, which is why the ClassNotFound exception occurs.

This could be because the outdated fs5 is used instead of the current start script fs-server.

Further pitfalls when updating very old FirstSpirit versions could be:
* Java version must now be at least 11
* The projects must have been migrated to Berkeley DB 7

Best regards
Holger