Hi everyone.
I found the following error in the SystemOut logs:
ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service CWSRV0014E: Uncaught service() exception root cause /themes/html/Default.jsp: com.ibm.websphere.servlet.error.ServletErrorReport: com.ibm.wps.resolver.data.exceptions.URIProcessingIOException: EJCBD0021E: No se han podido procesar el URI [dav:fs-type1/themes/Theme/theme.html] ni los parámetros [['mime-type'=['text/html'], 'themeURI'=['dav:fs-type1/themes/Theme/theme.html']]]: [EJCBD0021E: No se han podido procesar el URI [dav:fs-type1/themes/Theme/nls/theme_es.html] ni los parámetros [['mime-type'=['text/html'], 'themeURI'=['dav:fs-type1/themes/Theme/theme.html']]]: [Unable to resolve navigation node.]]
I made this configuration in the web.xml file but the error
CWSRV0014E EJCBD0021E (some theme resource) "could not be be found" (hcltechsw.com)
I would be very grateful if you can help me!
Do you see the whitelist / blacklist error message that is mentioned in the article? Also, which web.xml file did you update?
Is this a new theme you deployed to the environment? Do you have it working on another environment?
Can you check if the theme files exist using a WebDAV client to connect on the fs-type1 entry point? For example, the error is looking for this file:
fs-type1/themes/Theme/theme.html
Hi David, for example this error:
[5/23/22 14:44:41:318 COT] 000063cc ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service CWSRV0014E: Uncaught service() exception root cause /themes/html/Default.jsp: com.ibm.
websphere.servlet.error.ServletErrorReport: com.ibm.wps.resolver.data.exceptions.URIProcessingIOException: EJCBD0021E: No se han podido procesar el URI [dav:fs-type1/themes/VotreThemeCOL/theme.
html] ni los parámetros [['mime-type'=['text/html'], 'themeURI'=['dav:fs-type1/themes/VotreThemeCOL/theme.html']]]: [EJCBD0021E: No se han podido procesar el UR
I [dav:fs-type1/themes/VotreThemeCOL/nls/theme_es.html] ni los parámetros [['mime-type'=['text/html'], 'themeURI'=['dav:fs-type1/themes/VotreThemeCOL/theme.html'
;]]]: [Unable to resolve navigation node.]]
The file dav:fs-type1/themes/VotreThemeCOL/theme.html exists:
And fs-type1/themes/VotreThemeCOL/nls/theme_es.html exists too
I saw the whitelist / blacklist error message and I update the web.xml inside the war.
This war contains the resources called in that theme and they are called from theme.html and theme_es.html files, both ones exist in the path:
fs-type1/themes/Theme/nls/theme_es.html
fs-type1/themes/Theme/theme.html
Can you try restarting the Portal JVM? Sometimes clearing the cache can help these types of errors.
Hello Heady,
how did you update the war file? Did you done the changes on the fly or did you uninstalled the war, modified the web.xml and then redeployed it? Do you also see the problem, when you do the following steps:
1) undeploy the war-file and sync all your nodes
2) stop all Portal instances
3) clean the /temp and /wstemp folder
4) run osgiCfgInit.sh script on all profiles
5) run clearClassCache.sh script
6) restart the portal server
7) install the new modified war-version and sync the nodes
8) test, again
Thanks for the clarification. If you still struggle feel free to open a support case with us.
with best regards
Thorsten
Hello Thorsten, the theme has deployed through webdav and doesn't have a war file.
Hello Heady,
thanks for your update. Independent if you deployed it via webdav or as an ear-file I think you can try to use my managed steps above to ensure that the problem is not caused because of any caching issues. Did you already tried it?
Thanks, Thorsten
