[opencms-dev] XSD's
Schliemann, Kai
K.Schliemann at comundus.com
Wed Jan 17 17:59:03 CET 2024
Hello Atle,
difficult issue.
Your MySQL version is quite old, but I doubt, that this is a problem. So if it is easy for you to replace it with an newer version, give it a try.
One more thing you could check is the SAX parser config in OpenCms as described here:
https://documentation.opencms.org/opencms-documentation/server-administration/tomcat-configuration/index.html#improving-xml-unmarshalling-performance-22cb94f4
We never use this option, so if it is set to true, change it back to false and restart Tomcat.
If all this does not help you could try one more thing.
Create a new content type and add the fields from your old / "broken" schema files to the new schema file. Make all the necessary steps to make it available to the content editor and try to add a new content item of this new type.
Doing this I would suggest to start very simple.
So create the new schema with just one field.
Add field by field.
Leave out nested schemas and configurations in the first place.
Between each step, try to place new content type to the page and see if everything works.
If you are lucky, the error never appears with the new content type.
But if it does, you should be able to find the field or the config, which is responsible for the problem.
You might need to dig into a nested schema. Maybe the problem is there.
Last hint:
If you have the possibility for debugging this could help you finding the problem as well.
Good luck.
Best regards
Kai
-----Ursprüngliche Nachricht-----
Von: Atle Enersen <atle.enersen at gmail.com>
Gesendet: Mittwoch, 17. Januar 2024 16:04
An: Schliemann, Kai <K.Schliemann at comundus.com>
Cc: opencms-dev at opencms.org
Betreff: SV: [opencms-dev] XSD's
Hello Kai, and thanks for taking time to explore this strange behaviour.
1. It seems it only triggers the exception on content I add. I could add, modify and remove content in the Mercury template without any errors.
2. MySQL: Server version: 5.7.42-0ubuntu0.18.04.1 (Ubuntu)
3. Tomcat 9.0.33.
4. No, well, yes. The standard apps that ship with Tomcat.
5. No.
6. root at s160-153-244-17:/home/nesrene# java -version openjdk version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
Vennlig hilsen Atle Enersen
--
Tel.: +47 48063171
Bluesky/X-Twitter: @nesrene
-----Opprinnelig melding-----
Fra: Schliemann, Kai <K.Schliemann at comundus.com>
Sendt: onsdag 17. januar 2024 10:41
Til: The OpenCms mailing list <opencms-dev at opencms.org>
Kopi: Atle Enersen <atle.enersen at gmail.com>
Emne: AW: [opencms-dev] XSD's
Hello Atle,
this sounds really strange.
I don't know if these questions have been asked:
1. Do the unmarshalling errors occur only on "your" content items? Can you place new demo content from the mercury demo?
2. What database engine and version do you use?
3. what tomcat version do you use?
4. are there any other webapps in the same tomcat instance?
5. are there any additional libs in tomcat common libs folder?
6. which java version do you use?
Maybe we can find the problem by checking on those questions.
Best regards
Kai
-----Ursprüngliche Nachricht-----
Von: opencms-dev <opencms-dev-bounces at opencms.org> Im Auftrag von Atle Enersen via opencms-dev
Gesendet: Mittwoch, 17. Januar 2024 08:17
An: opencms-dev at opencms.org
Cc: Atle Enersen <atle.enersen at gmail.com>
Betreff: Re: [opencms-dev] XSD's
Hello.
In search of the unmarshalling-error reason I have now done fresh installs of both v15 an v16, with and without the mercury template. No luck. There are no errors until I try to drag in new content via the wand. The the unmarshalling-error pops up. It does so on all attempts to add new content.
One major problem here is that nowhere I can see which file that triggers the exception.
All both browser and system caches are cleared, all databases flushed.
Best regards Atle Enersen
--
Bluesky/X-Twitter: @nesrene
Today's Topics:
1. Re: XSD's (Atle Enersen)
----------------------------------------------------------------------
More information about the opencms-dev
mailing list