-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application unable to read external properties file after upgrading WKO from 3.2.3 to 4.0.0 #4061
Comments
Are you using 4.0.0 or the latest, 4.0.5? |
4.0.0 But I can upgrade to 4.0.5 if you would recommend that. |
None of the fixes in 4.0.1 through 4.0.5 seem immediately relevant to the problem you are facing (https://github.com/oracle/weblogic-kubernetes-operator/releases); however, I'd still recommend upgrading to 4.0.5 for two related reasons: 1) It's possible that 4.0.5 will resolve your problem because your issue was a side-effect of one of the issues that was fixed and so it would be a shame to waste time diagnosing such a problem, and 2) If we do need to fix a bug and release a fix then this would be a 4.0.6 release. We don't have a process for delivering patches similar to how this is done for WebLogic. |
Hi @rjeberhard still having the same issue with 4.0.5. So for now we will not update our wko. And in the meantime I will try to find out at which version after 3.2.3 the issue occurs. |
@jkramplify Please see https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/#wlsdeploycustom. Dropping a random file in a random location in the WDT Archive is not supported (and never has been--even if it was previously working). |
I encountered issues when upgrading from 3.2.3 to 4.0.0. Some of our applications suddenly unable to read an external environment.properties file located at DOMAIN_HOME/wlsdeploy/environment.properties.
The way our applications are reading this file is
<beans:value>file:wlsdeploy/environment.properties</beans:value>
Nothing changed in the application side. The only changes were upgrading WKO to 4.0.0 and using oracle.weblogic/v9 domain schema.
Edit: Updated the initial wko version from 3.0.0 to 3.2.3.
The text was updated successfully, but these errors were encountered: