"Alias folder SecureMode does not exist at path /SecurityConfiguration" error when discovering domain in WLS 12.1.3 version #1467
Comments
|
@anatoliatanasov Can you please provide the complete log file? |
|
I believe that this is all related to #1466. The SecureMode folder is already filtered out in versions prior to 12.2.1 so clearly, the version is not being set properly during tool initialization. This is just a side effect of the previous problem. |
Please, find the log file attached. |
From the analysis and debugging I did yesterday it seems that the version verification for the SecureMode model folder / mbean the version check says that it should not be processed, but the actual processing occurs, i.e. the VersionUtils functions work OK, but the result is not properly treated. The problematic part is in the discover.py's |
|
If interested I managed to work that problem around with this piece of code in discover.py's secure_mode_location.append_location(model_constants.SECURE_MODE)
secure_mode_path = aliases.get_wlst_list_path(secure_mode_location)
secure_mode_token = helper.get_singleton_name(secure_mode_path)with # Patched by [email protected]
# For domains of WLS version 12.1.3 and earlier there is no SecureModeMBean/SecureModeEnabled causing
# runtime errors using the discoverDomain.
# The SecureModeMBean/SecureModeEnabled attribute is examined and if missing, error is suppressed.
try:
# Tries to get value of SecureModeMBean.isSecureModeEnabled() method
helper.get(model_constants.SECURE_MODE_ENABLED)
secure_mode_location.append_location(model_constants.SECURE_MODE)
secure_mode_path = aliases.get_wlst_list_path(secure_mode_location)
secure_mode_token = helper.get_singleton_name(secure_mode_path)
except DiscoverException, ex:
e = ex
while True:
if(not e.getCause() and isinstance(e, java.lang.NoSuchMethodException)):
__logger.warning('#################### PATCHed logic by [email protected] START ####################', class_name='discover-py', method_name=_method_name)
__logger.warning(str(e.getMessage()), class_name='discover-py', method_name=_method_name)
__logger.warning('#################### PATCHed logic by [email protected] END ####################', class_name='discover-py', method_name=_method_name)
secure_mode_token = None
break
e = e.getCause()With this modification the discoverDomain.sh tool completes with a few warnings, but I don't think this is a sustainable solution. |
|
Yeah, that's not the right way to fix this but thanks for your effort. We will get both issues fixed as soon as possible and will cut a 3.2.1 release that resolves both issues. |
Check if secure mode location is valid before getting value See merge request weblogic-cloud/weblogic-deploy-tooling!1471
|
Fixed in release 3.2.1 |
Uh oh!
There was an error while loading. Please reload this page.
Trying to discover WLS 12.1.3 domain of which SOA Studio 12.1.3 integrated WebLogic Server is part of with the command:
raises the following error:
The command is run against WLDT vanilla installation where the
${WLDT_HOME}/lib/typedefs/WLS.jsonis changed to:{ "copyright": "Copyright (c) 2017, 2019, Oracle Corporation and/or its affiliates. All rights reserved.", "license": "Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl", "name": "WLS", "description": "WLS type domain definitions", "versions": { "10.3.6": "WLS_11G", "12.1.1": "WLS_11G", "12.1.2": "WLS_12CR1", "12.1.3": "WLS_12CR1", "12.2.1": "WLS_12CR2", "12.2.1.3": "WLS_12CR2", "12.2.1.4": "WLS_12CR2", "14.1": "WLS_14" }, "definitions": { "WLS_11G": { "baseTemplate": "@@WL_HOME@@/common/templates/domains/wls.jar", "extensionTemplates": [ ], "customExtensionTemplates": [ ], "serverGroupsToTarget": [ ], "rcuSchemas": [ ] }, "WLS_12CR1": { "baseTemplate": "Basic WebLogic Server Domain", "extensionTemplates": [ ], "customExtensionTemplates": [ ], "serverGroupsToTarget": [ ], "rcuSchemas": [ ] }, "WLS_12CR2": { "baseTemplate": "Basic WebLogic Server Domain", "extensionTemplates": [ ], "customExtensionTemplates": [ ], "serverGroupsToTarget": [ ], "rcuSchemas": [ ] }, "WLS_14": { "baseTemplate": "Basic WebLogic Server Domain", "extensionTemplates": [ ], "customExtensionTemplates": [ ], "serverGroupsToTarget": [ ], "rcuSchemas": [ ] } } }I suppose the SecureModeMBean appears in newer version, but I cannot find a way to enforce older version of the config mbeans hierarchy.
The text was updated successfully, but these errors were encountered: