You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need some help understanding why the configuration settings of a service fabric application aren't being overriden by the values defined in the application manifest, as expected. Curently I have some settings defined for my two different environments: the default settings are for the final Azure cluster and I have a custom publish profile for my local dev cluster.
When publishing the application to the local cluster, I can see in the output the log when creating the application and it seems the parameters are ok:
But using the service explorer I can see that errors occurred during the application startup and if I check the event log I can see the following error:
failed to set security settings to { provider=SSL
protection=EncryptAndSign certType = '' store='LocalMachine/My'
findValue='FindByThumbprint:e47c0e4b80e9b83e39e5e1dc35610b6b84a3b764'
remoteCertThumbprints='e47c0e4b80e9b83e39e5e1dc35610b6b84a3b764'
remoteX509Names=('*.thefinaldomain.com',issuer=)
certChainFlags=40000000 isClientRoleInEffect=false
claimBasedClientAuthEnabled=false }: FABRIC_E_CERTIFICATE_NOT_FOUND
Some things I've already tried:
Used Service Fabric explorer and confirmed that the Parameters under the Details tab of the application are correct and match the parameters that have been sent to the deployment script according to the Output window;
Confirmed that the contents of the "Settings.xml" file under "C:\SfDevCluster\Data_App_Node_0\SampleServFabricAppType_App18\SampleServFabricApp.EndpointPkg.Config.1.0.0" are equal to the contents of the "SampleServFabricApp.Endpoint/PackageRoot/Config/Settings.xml";
As you can see it seems that the deployment process assumes the correct overridden values, but the application doesn't work and event viewer shows the default values instead of the ones used during deployment.
The text was updated successfully, but these errors were encountered:
@lusocoding
This is a known issue and has been fixed in next sdk release (3.3) .
For the workaround , you can use below Api's to read these settings from config package and then create FabricTransportSettings programmatically.
var configurationPackage = Context.CodePackageActivationContext.GetConfigurationPackageObject("Config");
var maxMessageSize = configurationPackage.Settings.Sections["TransportConfig"].Parameters["MaxMessageSize"];
Need some help understanding why the configuration settings of a service fabric application aren't being overriden by the values defined in the application manifest, as expected. Curently I have some settings defined for my two different environments: the default settings are for the final Azure cluster and I have a custom publish profile for my local dev cluster.
Below what I have for each file:
SampleServFabricApp/ApplicationPackageRoot/ApplicationManifest.xml
SampleServFabricApp/ApplicationParameters/dev_cluster.xml
SampleServFabricApp.Endpoint/PackageRoot/Config/Settings.xml
When publishing the application to the local cluster, I can see in the output the log when creating the application and it seems the parameters are ok:
But using the service explorer I can see that errors occurred during the application startup and if I check the event log I can see the following error:
Some things I've already tried:
As you can see it seems that the deployment process assumes the correct overridden values, but the application doesn't work and event viewer shows the default values instead of the ones used during deployment.
The text was updated successfully, but these errors were encountered: