Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 82678

Summary: Change the way GLA handles long messages
Product: z_Archived Reporter: Dave Smith <smith>
Component: TPTP.monitoringAssignee: Dave Smith <smith>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P2 Keywords: Documentation
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:
Bug Depends on:    
Bug Blocks: 90765    

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.