Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 189485 - CBE XML log can not be imported. java.lang.NullPointerException get thrown.
Summary: CBE XML log can not be imported. java.lang.NullPointerException get thrown.
Status: CLOSED DUPLICATE of bug 157905
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Alex Nan CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-28 14:35 EDT by Praful Rajawat CLA
Modified: 2016-05-05 10:48 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Praful Rajawat CLA 2007-05-28 14:35:18 EDT
Build ID: tptp.sdk-TPTP-4.4.0-200705080100C

Steps To Reproduce:
1.Starr the RCP log analyzer
2.Import any cbe xml log
3.Following null pointer get thrown.


More information:
!ENTRY org.eclipse.tptp.platform.common.cbe 4 0 2007-05-28 13:26:18.125
!MESSAGE An error occurred while attempting to import the log file D:\logs\perf\XML20K.xml.
!STACK 0
org.eclipse.hyades.logging.parsers.LogParserException: IWAT0412E Errors occurred parsing the log file D:\logs\perf\XML20K.xml.
	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:90)
	at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard$LocalLogImportJob.run(ImportLogWizard.java:994)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 org.eclipse.tptp.platform.common.cbe 4 0 2007-05-28 13:26:18.125
!MESSAGE java.lang.NullPointerException
Comment 1 Praful Rajawat CLA 2007-05-28 14:39:17 EDT
This is been tested in large log mode.
Comment 2 Hari H Krishna CLA 2007-05-29 08:25:36 EDT
Praful, Can you please try to use the same set-up and import small log, without large log mode and update me with the test results?
Comment 3 Rohit Shetty CLA 2007-05-29 08:44:32 EDT
Praful,
Can you attach the hgla.log generated for when this problem was encountered? The hgla.log would have more information related to the problem.
Comment 4 Praful Rajawat CLA 2007-05-29 09:07:59 EDT
This works in xmi (In memory) mode.
Comment 5 Praful Rajawat CLA 2007-05-29 09:11:16 EDT
What is hgla.log? Where can I find this log?
Comment 6 Rohit Shetty CLA 2007-05-29 09:15:46 EDT
The hgla.log is generated by the GLA when it finds some problems. I think it would be generated in the temp location on your (machine on which the test was conducted) system.
Comment 7 Praful Rajawat CLA 2007-05-29 09:41:57 EDT
Sorry, I can't find this hgla.log anymore. But at the same time run this test case and you should be able to get info what you looking for.
Comment 8 Marius Slavescu CLA 2007-05-29 17:13:10 EDT

*** This bug has been marked as a duplicate of bug 157905 ***
Comment 9 Praful Rajawat CLA 2007-11-27 10:21:19 EST
Dups