AnsweredAssumed Answered

Allow Configurable File Encoding for hotdeploy PBDs

Question asked by richardgreen_SSA on Jun 6, 2018
Latest reply on Jun 6, 2018 by Lynn_Williams

Moderately sized Enterprise WebSphere deployment on z/OS with multiple agents sharing a common hotdeploy folder.

 

It appears Agent is attempting to read an auto-generated PBD file in hotdeploy folder using an assumed default encoding. Failure to read the auto-generated PBD results complete abort of AutoProbe.

 

Log snippet:

[ERROR] [IntroscopeAgent.Agent] Introscope AutoProbe will not run because the provided directives files are not valid: (.../hotdeploy/jndierrorskip.pbd:1) Syntax Error: Unsupported character "%".

[ERROR] [IntroscopeAgent.Agent] Failed to load extensions bundles PBDs

[ERROR] [IntroscopeAgent.Agent] Unable to instantiate class com.wily.introscope.autoprobe.AutoProbeTransformer

 

Is there any configuration property that allows the Agent to be configured to use a specific file encoding to read auto-generated PBD?

 

Is this a bug in the Agent code?
Should the Agent be "suspicious" of hotdeploy by default and use try-catch-finally to avoid AutoProbe failure due to hotdeploy PBD?

Outcomes