error after upgrading to vocbench 9.1

[cbs bibliotheek]

I have upgraded from vocbench 8.0.1 to 9.1. But when starting it, I get these errors:

java.lang.IllegalStateException

Caused by: java.lang.IllegalStateException: Cannot use 'defaultEncoding', 'fallbackToSystemLocale' and 'cacheSeconds' on the standard ResourceBundleMessageSource when running on Java 5. Consider using ReloadableResourceBundleMessageSource instead

Now there is no project visible anymore. And I get these errors whatever I do.

I have one project in this application which uses Dutch and English language. The old 8.0.1 instance still shows the project, but I cannot access it.

it.uniroma2.art.semanticturkey.exceptions.ProjectUpdateException: java.lang.NullPointerException

I hope somebody can help with this.

Henk Laloli

[Roland Wingerter]

Hi Henk,

go to ANN: VocBench 9.0 released and look for "Migration from a previous version of the system".

I always install the new version in a new directory, and copy the directory “SemanticTurkeyData” there as well. As an example, here is my directory structure:

C:\VocBench3\

C:\VocBench3\vocbench3-8.0.1-full\

C:\VocBench3\vocbench3-8.01-full\semanticturkey-8.0

C:\VocBench3\vocbench3-8.01-full\SemanticTurkeyData

C:\VocBench3\vocbench3-9.1.0-full\

C:\VocBench3\vocbench3-9.1.0-full\semanticturkey-9.1

C:\VocBench3\vocbench3-9.1.0-full\SemanticTurkeyData

If everything works OK directories of older versions can be deleted.

 Hope this helps

Roland

[cbs bibliotheek]

Thank you, Roland. This helps. I have reconstituted the 8.0.1 version. It now works fine. But the 9.1 version still gives the same errors. I have tried it with an empty version, but again with the same errors that I previously reported. So, it appears to be a general error. So, the specific error about the encoding seems relevant.

Henk

Op woensdag 19 mei 2021 om 18:51:39 UTC+2 schreef Roland Wingerter:

[Armando Stellato]

There is also something strange: why is it mentioning Java 5?

Do you know if, for instance, you did setup something for pointing to a specific version of Java (e.g. modifying the batch file used to run Karaf) on your 8.0.1 version and you did not on the 9.1 version?

 

Kind Regards,

 

Armando

 

--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vocbench-user/5e3b7cb1-11cf-43ca-a26d-5972e0483ba1n%40googlegroups.com.

[cbs bibliotheek]

Yes, Armando, you are right. That is strange. I am using java-11-openjdk. I have not changed the startup script or pointed to this old java version. Where can it come from?

My environment setting for more memory seems to be overidden too: it just gives -Xms128M -Xmx512M, while I have added 1G and 3G to /etc/environment.

Henk

Op donderdag 20 mei 2021 om 16:38:56 UTC+2 schreef stel...@uniroma2.it:

[Roland Wingerter]

Henk,

according to the VB3 documentation,  VocBench requires "Java 8 (any build of Java 8 is fine, but it has to be 8, no less no more!)"

Roland

[cbs bibliotheek]

Yes, thanks Roland. Looking at karaf.log it says: Caused by: java.lang.IllegalStateException: Could not find sun.misc.Unsafe. Searching shows that this class was removed in Java 11. So, I better should use an older Java version.

Op donderdag 20 mei 2021 om 22:39:36 UTC+2 schreef Roland Wingerter:

[cbs bibliotheek]

Can I refer to a specific Java version in the start script (I put this in semanticturkey-9.1/bin/karaf) ? I don't want to change my general Java set up in which I have set up Java 11 as JAVA_HOME, because other applications depend on it. I tried to refer to Java 8 in the start script, but it gave only errors. (JAVA_HOME = "/usr/lib/jvm/java-8-openjdk-amd64").

Henk

Op donderdag 20 mei 2021 om 22:47:08 UTC+2 schreef cbs bibliotheek:

[Armando Stellato]

Hi Henk,

 

indeed you can. I don’t know exactly the way you played it into the script, but it should be possible. I suggest to echo the value of the variable on the console within the script, before Java is invoked, so you can check if it is well configured.

 

Kind Regards,

Armando

 

 

 

To view this discussion on the web visit https://groups.google.com/d/msgid/vocbench-user/1fbea465-0e76-4b2e-b59c-720250a0dc2dn%40googlegroups.com.