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

Bug 176653

Summary:	Error message is lost
Product:	z_Archived	Reporter:	Jane Fang <janefang>
Component:	TPTP.monitoring	Assignee:	Rohit Shetty <rohit.shetty>
Status:	CLOSED INVALID	QA Contact:
Severity:	major
Priority:	P1	CC:	apnan, jkubasta, jx_china, labadie, rohit.shetty, sleeloy
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	closed460

Description Jane Fang

2007-03-07 17:36:11 EST

1. import several logs.
2. an exception is logged in the eclipse log, but no detailed error message is displayed

The exception is thrown when the error message count is greater than 0, however the client doesnot get any error message.

The error intermittedly occurs when using IBM launch in context service to import mulitple logs.


!ENTRY org.eclipse.ui 4 4 2007-03-07 10:38:59.203
!MESSAGE Plug-in 'org.eclipse.ui.editors' contributed an invalid Menu Extension (Path: 'file/converstLineDelimitersTo' is invalid): org.eclipse.ui.edit.text.delimiter.windows

!ENTRY org.eclipse.ui 4 4 2007-03-07 10:38:59.218
!MESSAGE Plug-in 'org.eclipse.platform' contributed an invalid Menu Extension (Path: 'help' is invalid): org.eclipse.ui.cheatsheets.actions.CheatSheetHelpMenuAction

!ENTRY com.ibm.etools.ac.common.launchincontext 4 4 2007-03-07 10:39:03.265
!MESSAGE An error occurred while attempting to import the log file ///e:/tmp/Apache_error.log.
!STACK 0
org.eclipse.hyades.logging.parsers.LogParserException: IWAT0412E Errors occurred parsing the log file ///e:/tmp/Apache_error.log.
	at org.eclipse.hyades.logging.parsers.importer.ParserWrapper.parse(ParserWrapper.java:144)
	at org.eclipse.hyades.logging.parsers.internal.importer.LocalLogImportLoader.startParsing(LocalLogImportLoader.java:95)
	at org.eclipse.tptp.monitoring.log.internal.core.LocalImportHandler.importLog(LocalImportHandler.java:105)
	at com.ibm.etools.ac.common.services.LogImportAdapter.importLog(LogImportAdapter.java:195)
	at com.ibm.etools.ac.common.launchincontext.internal.util.LogImportJob.run(LogImportJob.java:148)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

Comment 1 Dave Smith

2007-03-10 17:27:40 EST

Since this is intermittent, I am deferring it to iteration 3 for further investigation.  Further investigation/debugging is required to determine if the problem is occurring in the GLA or the log import service when it processes the GLA logged messages.

Comment 2 Dave Smith

2007-05-23 05:13:36 EDT

Could not be contained in iteration 3. Will try to investigate further in iteration 4.

Comment 3 Dave Smith

2007-05-30 05:07:35 EDT

Cannot contain this in TPTP 4.4.  Deferring to future.

Comment 4 Eric Labadie

2007-08-08 16:11:40 EDT

This is required from AC perspective.

Comment 5 Dave Smith

2007-08-31 17:44:49 EDT

Add a sizing.

Comment 6 Alex Nan

2007-10-30 19:46:26 EDT

Targetting 4.5 i2.

Comment 7 Alex Nan

2007-11-05 18:50:35 EST

Targetting to 4.5 i4.

Comment 8 Rohit Shetty

2007-11-26 05:56:21 EST

I tried the described scenario with IBM launch in context service (With the latest driver) and i am not able to recreate it at all.

In my scenario i was importing 20 logs - Apache Access and Apache error. 
1) All valid logs and log records - Import worked fine. No errors in logs or on screen
2) Some invalid logs - Errors on screen.
3) Added a few parsing problems - Errors on screen.

It looked as if things were perfect.

We have tried this on multiple systems, for multiple times on each machine. and No failures.

I think we need some more details.

Comment 9 Jane Fang

2007-11-28 17:57:46 EST

Hi Rohit,

I don't see this happen in lic either.

Could you please write up some multithreaded code to call TPTP common APIs to import several big logs simultaneously? 

You can find an example on the APIs in the following junit code:
org.eclipse.tptp.monitoring.tests > src > org.eclipse.tptp.monitoring.log.tests > ImportAPITests.java > testImportAPI

If you still don't see the error, please close this as not reproducible.

Thanks

Comment 10 Rohit Shetty

2007-11-29 03:04:45 EST

Could not recreate the problem. Rejecting the defect as INVALID.

Jane,
Please reopen this defect if the problem surfaces again.

Comment 11 Paul Slauenwhite

2009-06-30 12:18:32 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.