Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ClasspathServletSecureModeEnabled parameter doesn't work for OSB domain

See original GitHub issue

I configured OSB domain using WDT providing:

ClasspathServletSecureModeEnabled: false

This doesn’t work, which I tested both by reproducing issue described in Doc Id 2777539.1 and by logging into AdminServer, connecting using WLST to verify that:

wls:/my_domain/serverConfig/> cd ('Servers/AdminServer')
wls:/my_domain/serverConfig/Servers/AdminServer> ls()
(...)
-r--   ClasspathServletDisabled                     false
-r--   ClasspathServletSecureModeEnabled            true
(...)

I can confirm that Weblogic properly reacts on modification of ClasspathServletDisabled property - this should stay as “false”, but for testing purpose I was modifying it just to see if it changes.

I am using WDT 2.1.1 version and OSB 12.2.1.4.0

Issue Analytics

State:
Created a year ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

robertpatrickcommented, Apr 15, 2022

@pwninja OK, this has nothing to do with any final.py change and is easily reproduced with a WebLogic Server only domain.

It appears to be an issue that the Oracle PSU team created by changing the default value of the attribute in “online” mode but not in “WLST offline” mode. Because WLST offline thinks the default is still false, it will not add the attribute to config.xml unless the value is set to true. If we use WLST offline to change the value to false after the domain is created (and since WLST offline believes that the attribute’s default value is false), the attribute is removed from config.xml. I am not sure that there is anything WDT can reasonably do to work around this WLST bug created by the incomplete PSU change.

My advice is to file a bug on WLS for making this change, which makes it impossible to disable this attribute without either hand-editing config.xml or running an online config change step after domain creation. @mriccell @ddsharpe FYI

0reactions

robertpatrickcommented, Apr 15, 2022

@pwninja If you need this to work, you should file a Bug against WLST offline with Oracle Support.