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

Bug 203598

Summary:

Import Server Log option failing

Product:

z_Archived

Reporter:

Joef Huang <joefh>

Component:

TPTP.monitoring

Assignee:

Yasuhisa Gotoh <gotohy>

Status:

CLOSED INVALID

QA Contact:

Severity:

major

Priority:

CC:

apnan, ewchan, jkubasta

Version:

unspecified

Keywords:

plan

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

closed460

Attachments:

Description	Flags
monitor	none
wps	none

Description Joef Huang

2007-09-17 10:40:20 EDT

There is a new option in WID called "Import Server Log..."



When using this, there does not seem to be WebSphere Process Server option, so I use WebSphere Application Server systemout.log option and then point to the WPS SystemOut.log file.

I get the errors below.  Would Valentina know what is causing this and what needs to be done so that I can use this new import option on WPS logs.  BTW, the logs do exist in the location below.

!ENTRY org.eclipse.tptp.monitoring.logui 4 0 2007-09-14 23:36:52.156
!MESSAGE An error occurred while attempting to import the log file D:\wid61\pf\wps\logs\server1\SystemOut.log;.
!STACK 0
org.eclipse.hyades.logging.parsers.LogParserException: IWAT0075E The log parser's initialization parameters are not set properly.
IWAT0243E The log file D:\wid61\pf\wps\logs\server1\SystemOut.log; does not exist.
	at org.eclipse.hyades.logging.parsers.importer.ParserWrapper.parse(Unknown Source)
	at org.eclipse.hyades.logging.parsers.internal.importer.LocalLogImportLoader.startParsing(Unknown Source)
	at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard$LocalLogImportJob.runOnLocalHost(Unknown Source)
	at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard$LocalLogImportJob.run(Unknown Source)
	at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Embedded exception follows:
org.eclipse.hyades.logging.adapter.AdapterException: IWAT0075E The log parser's initialization parameters are not set properly.
IWAT0243E The log file D:\wid61\pf\wps\logs\server1\SystemOut.log; does not exist.
	at org.eclipse.hyades.logging.adapter.internal.util.Controller.prepareAdapter(Unknown Source)
	at org.eclipse.hyades.logging.adapter.Adapter.start(Unknown Source)
	at org.eclipse.hyades.logging.parsers.importer.ParserWrapper.parse(Unknown Source)
	at org.eclipse.hyades.logging.parsers.internal.importer.LocalLogImportLoader.startParsing(Unknown Source)
	at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard$LocalLogImportJob.runOnLocalHost(Unknown Source)
	at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard$LocalLogImportJob.run(Unknown Source)
	at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
!SUBENTRY 1 org.eclipse.tptp.monitoring.logui 4 0 2007-09-14 23:36:52.156
!MESSAGE

Comment 1 Joef Huang

2007-09-17 10:41:05 EDT

Created attachment 78550 [details]
monitor

Comment 2 Joef Huang

2007-09-17 10:41:28 EDT

Created attachment 78551 [details]
wps

Comment 3 Eugene Chan

2007-09-17 10:47:50 EDT

Marking this as major, user can workaround the problem now with the 'File>Import>Log' alternative.

Comment 4 Denis Roy

2007-09-17 13:30:30 EDT

The content of attachment 78551 [details] has been deleted by
    Denis Roy <denis.roy@eclipse.org>
who provided the following reason:

Requested by attachment creator, via webmaster inbox

The token used to delete this attachment was generated at 2007-09-17 13:30:14 -0400.

Comment 5 Denis Roy

2007-09-17 13:30:55 EDT

The content of attachment 78550 [details] has been deleted by
    Denis Roy <denis.roy@eclipse.org>
who provided the following reason:

Requested by attachment creator, via webmaster inbox

The token used to delete this attachment was generated at 2007-09-17 13:30:48 -0400.

Comment 6 Eugene Chan

2008-03-19 15:39:17 EDT

Alex, could you please take a look? It could be the source path not being passed to the import wizard correctly.

Comment 7 Alex Nan

2008-03-19 15:45:35 EDT

This is not containable in i6. Will have to move to i7.

Comment 8 Alex Nan

2008-04-01 10:28:23 EDT

Reassigning...

Comment 9 Alex Nan

2008-04-04 20:53:38 EDT

Reassigning to Gotoh-san. Please take a look.

Comment 10 Alex Nan

2008-04-21 15:38:52 EDT

Gotoh-san please get a resolution on this defect ASAP. If this is a problem in the proprietary code, i.e. Websphere parser, please open a defect against the IBM log parsers on the proprietary side and return this defect.

Comment 11 Alex Nan

2008-04-30 16:17:10 EDT

This is not a TPTP defect. In TPTP we open the import log wizard in the Import Server Log... option as part of the org.eclipse.tptp.monitoring.profile.server extension to the Server view. All the parsers in TPTP are working correctly if the correct input is provided so I conclude that this is not a TPTP defect.
Please open a defect against the Autonomic Computing Log and Trace Analyzer or pehaps a defect against Rational Application Developer.

Comment 12 Paul Slauenwhite

2009-06-30 13:17:33 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.