Bug 82678 - Change the way GLA handles long messages
Summary: Change the way GLA handles long messages
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP.monitoring (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Dave Smith CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation
Depends on:
Blocks: 90765
  Show dependency tree
 
Reported: 2005-01-12 11:14 EST by Dave Smith CLA
Modified: 2010-06-03 15:10 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Smith CLA 2005-01-12 11:14:13 EST
Currently if the value for the Common Base Event msg field is longer than 1024, 
the GLA CBEFormatter class sets the msg value to be the first 1024 characters 
of the value and then creates two or more ExtendedDataElements to contain the 
full message value, each one being 1024 characters or less.

However, since an ExtenedDataElement can contain an array of strings for its 
values value, it makes more sense to create one ExtendedDataElement for the 
full message with a string array value to contain the whole message split into 
1024 chunks.
Comment 1 Dave Smith CLA 2005-01-12 11:16:00 EST
Targetting this change to 4.0 as it can break existing users of GLA that expect 
multiple ExtendedDataElements for the complete message.
Comment 2 Dave Smith CLA 2005-01-12 12:21:33 EST
Note, some existing static parser classes like 
org.eclipse.hyades.logging.parsers.AbstractAccessLogParser process long 
messages as one ExtendedDataElement.
Comment 3 Dave Smith CLA 2005-03-18 14:26:12 EST
This new behaviour should be documented, even though the old behaviour was not 
documented.
Comment 4 Dave Smith CLA 2005-04-08 02:26:45 EDT
Committed change to CBEFormatter class to TPTP Head CVS
Comment 5 Dave Smith CLA 2007-08-02 12:28:12 EDT
Verified this with TPTP 4.4.0 GA driver.