Bug 1089842 – [GSS] (6.3.0) listMessagesAsJSON method fails to list messages if the filter property contians \n character.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1089842 - [GSS] (6.3.0) listMessagesAsJSON method fails to list messages if the filter property contians \n character.

Summary:	[GSS] (6.3.0) listMessagesAsJSON method fails to list messages if the filter ...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	HornetQ (Show other bugs)
Sub Component:
Version:	6.2.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR2
Target Release:	EAP 6.3.0
Assigned To:	Clebert Suconic
QA Contact:	Miroslav Novak
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1064596 1084639 1088602
	Show dependency tree / graph

Reported:	2014-04-22 00:40 EDT by Jimmy Wilson
Modified:	2014-08-06 10:37 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	In previous versions of JBoss EAP 6, filter parsing failed to parse messages correctly if the message contained a new line character (`\n`) inside a string or any other property. The root cause of this issue was faulty logic in the `listMessagesAsJSON` method, which failed to account for a newline character. This issue has been resolved in this release.
Story Points:	---
Clone Of:	1088602
Environment:
Last Closed:	2014-08-06 10:37:51 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jimmy Wilson 2014-04-22 00:40:14 EDT

+++ This bug was initially created as a clone of Bug #1088602 +++

listMessagesAsJSON fails to list messages if filter property coanitns '\n' character.

For example filter '%1234%' will list messages containing 'hello1234' but it will not list the same message if the string is 'hello1234\n'.

Comment 1 Russell Dickenson 2014-05-13 23:42:38 EDT

'Known Issue' text added for the Beta release. The following text can be used for the final release.

"Filter parsing failed to parse messages correctly if the they contained a new line character (`\n`) inside a string or any other property. The root cause of this issue was faulty logic in the `listMessagesAsJSON` method, which failed to account for a newline character. This issue has now been resolved by improving the handling of messages in method `listMessagesAsJSON`. As a result, messages are correctly parsed, even when containing one or more new line characters."

Comment 2 Kabir Khan 2014-07-01 10:27:10 EDT

Should be fixed by upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1064596 for DR2

Comment 3 Miroslav Novak 2014-07-02 04:17:58 EDT

Verified using FilterTest in EAP 6.3.0.ER7. Thanks

Note You need to log in before you can comment on or make changes to this bug.