Allow Configurable File Encoding for hotdeploy PBDs

[Richard S. Green]

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?

[Lynn Williams]

Hi Richard,

While researching your error I found you logged case 01064118 for similar "Syntax Error: Unsupported character" symptoms for hotdeploy file AutoPersist.pbd and had to disable smart instrumentation to resolve it.

During that case research you thought there may be some EBCDIC/ASCII read/write incompatibility going on.

From web research it looks like an  ASCII "%" has the same code point as an EBCDIC "LF" (LineFeed) (IBM Knowledge Center ), so as the error occurred on line 1 of the jndierrorskip.pbd a problem with interpreting the LF sounds like a possibility.

For this problem I would also suggest to create a support case so we can investigate in more detail.

Please also reference this community thread URL when you create the case.

 

Thanks

 

Lynn