[GLASSFISH-17097] Certain message strings set in action reporter prevent asadmin from correctly handling the return action report Created: 25/Jul/11  Updated: 02/Dec/11

Status: Open
Project: glassfish
Component/s: admin
Affects Version/s: 3.1.1, 4.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Tim Quinn Assignee: Byron Nevins
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1_1-exclude, 3_1_1-scrubbed

 Description   

Please also see the related issue.

asadmin asks the DAS to use the PropsFileActionReporter to report the command status. PropsFileActionReporter does not correctly handle certain strings when passed to setMessage if parts of the string are formatted in the same way as a manifest attribute: new line, attr-name: attr-value

The related issue shows an example in which the apparent attribute name is invalid, so asadmin's attempt to interpret the entire action report as a manifest fails.

PropsFileActionReporter should be changed so it can handle such strings and/or asadmin should use some other type of action reporter implementation that can handle such strings.



 Comments   
Comment by Tom Mueller [ 25/Jul/11 ]

Byron, is this related to the email discussion that you and Tim were already having?

Comment by Byron Nevins [ 24/Oct/11 ]

-> P4

Generated at Mon Aug 29 19:24:18 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.