Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » myLogParser sample fails to import (hangs 4ever)

Help

Home

Home » Archived » Test and Performance Tools Platform (TPTP) » myLogParser sample fails to import (hangs 4ever)

Show: Today's Messages :: Show Polls :: Message Navigator

myLogParser sample fails to import (hangs 4ever) [message #35135]

Thu, 13 October 2005 14:42

Norbert PlÃ¶tt

Messages: 233
Registered: July 2009

Senior Member

Hello,

I am trying out the sample log parser from the tutorial

http://www.eclipse.org/tptp/home/documents/tutorials/gla/GLA _CreatingLogParser/GLA_CreatingLogParser.viewlet/GLA_Creatin gLogParser_viewlet_swf.html

When I try import the sample log file the progress quickly goes to 98%, then
seems to hang indefinitely (for minutes, at least). When I cancel I get an
error message

IWAT0027E Error importing the specified log file(s)

The details have around 18.000 entries, so many that the output is garbled
up, but I can copy-paste to a text editor. The output looks like this:

==========snip===========
IWAT0027E Error importing the specified log file(s).
IWAT0412E Errors occurred parsing the log file d:\Temp\sample.log.
IWAT0398I Sensor will read file sample.log from directory d:\Temp using
the converter command null.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 1 items.
IWAT0425I Component OS File Sensor is returning 0 items.
IWAT0425I Component OS File Sensor is returning 0 items.
IWAT0425I Component OS File Sensor is returning 0 items.
==========snap===========

then repeat the last line "to infinity". Eclipse seems to be missing the
fact that the file is at it's end.
Can anybody help? More info required?

This is the configuration:

WinXP
eclipse 3.1.1
EMF 2.1.0
TPTP 4.0.0
RAServer 4.0.0.0

Thanks,

Norbert Ploett

Report message to a moderator

Re: myLogParser sample fails to import (hangs 4ever) [message #35227 is a reply to message #35135]

Fri, 14 October 2005 06:03

No real name

Messages: 11
Registered: July 2009

Junior Member

I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=112590 for the
problem to be tracked down. I have also added your email address to the CC
list of the defect.

In the meanwhile you may find the following help topic available under Help
> Help Contents useful:
Monitoring and analyzing performance > Determining problems in distributed
applications > Creting a log parser > Creating a rules-based adapter.

Thanks.

"Norbert Ploett" <norbert.ploett@siemens.com> wrote in message
news:1129214531.900626@baruth.khe.siemens.de...
> Hello,
>
> I am trying out the sample log parser from the tutorial
>
>
http://www.eclipse.org/tptp/home/documents/tutorials/gla/GLA _CreatingLogParser/GLA_CreatingLogParser.viewlet/GLA_Creatin gLogParser_viewlet_swf.html
>
> When I try import the sample log file the progress quickly goes to 98%,
then
> seems to hang indefinitely (for minutes, at least). When I cancel I get an
> error message
>
> IWAT0027E Error importing the specified log file(s)
>
> The details have around 18.000 entries, so many that the output is garbled
> up, but I can copy-paste to a text editor. The output looks like this:
>
> ==========snip===========
> IWAT0027E Error importing the specified log file(s).
> IWAT0412E Errors occurred parsing the log file d:\Temp\sample.log.
> IWAT0398I Sensor will read file sample.log from directory d:\Temp using
> the converter command null.
> IWAT0425I Component OS File Sensor is returning 5 items.
> IWAT0425I Component OS File Sensor is returning 5 items.
> IWAT0425I Component OS File Sensor is returning 5 items.
> IWAT0425I Component OS File Sensor is returning 5 items.
> IWAT0425I Component OS File Sensor is returning 5 items.
> IWAT0425I Component OS File Sensor is returning 5 items.
> IWAT0425I Component OS File Sensor is returning 5 items.
> IWAT0425I Component OS File Sensor is returning 1 items.
> IWAT0425I Component OS File Sensor is returning 0 items.
> IWAT0425I Component OS File Sensor is returning 0 items.
> IWAT0425I Component OS File Sensor is returning 0 items.
> ==========snap===========
>
> then repeat the last line "to infinity". Eclipse seems to be missing the
> fact that the file is at it's end.
> Can anybody help? More info required?
>
> This is the configuration:
>
> WinXP
> eclipse 3.1.1
> EMF 2.1.0
> TPTP 4.0.0
> RAServer 4.0.0.0
>
> Thanks,
>
>
> Norbert Ploett
>
>

Report message to a moderator

Re: myLogParser sample fails to import (hangs 4ever) [message #35241 is a reply to message #35227]

Fri, 14 October 2005 06:04

Norbert PlÃ¶tt

Messages: 233
Registered: July 2009

Senior Member

Thanks Ali,

now I tried the exact configuration that is described in
http://eclipse.org/tptp/home/downloads/drops/TPTP-4.0.0.html :

WinXP
eclipse 3.1.0
EMF 2.1.0
TPTP 4.0.0
RAServer 4.0.0.0

but exactly the same behaviour.

Where do I go now!

Norbert

Report message to a moderator

Re: myLogParser sample fails to import (hangs 4ever) [message #35256 is a reply to message #35227]

Fri, 14 October 2005 07:42

Norbert PlÃ¶tt

Messages: 233
Registered: July 2009

Senior Member

More findings after some drilling into the code:

- The "hanging" behaviour is due to the fact that I had the "Continuous
Operation" setting for the context instance set. This does not make sense
for importing a static log file.
- The amount of messages can be reduced when I set the Pause Interval for
the context instance to a higher value.

After these changes the import ends with an error message box "IWAT0027E
Error importing the specified log file(s)."

Copy-pasting the details yields:

=========snip==========
IWAT0027E Error importing the specified log file(s).
IWAT0412E Errors occurred parsing the log file d:\Temp\sample.log.
IWAT0398I Sensor will read file sample.log from directory d:\Temp using
the converter command null.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 5 items.
IWAT0425I Component OS File Sensor is returning 1 items.
IWAT0425I Component OS File Sensor is returning 0 items.
IWAT0425I Component OS File Sensor is returning 0 items.
IWAT0425I Component OS File Sensor is returning 0 items.

=========snip==========

The log view is opened but says that it has no filter, and that 0 of 0
records matched the filter.
I'll try to find out about the parsing errors now.

Can anybody help?

Norbert

Report message to a moderator

Re: myLogParser sample fails to import (hangs 4ever) [message #35270 is a reply to message #35256]

Fri, 14 October 2005 08:56

Norbert PlÃ¶tt

Messages: 233
Registered: July 2009

Senior Member

Even more drilling:

In the component definition for the OS File Sensor the logging level is set
to 0. --> Even the most minor information message is logged to the adapter's
internal log. ParserWrapper.parse() will throw it's LogParserException
because it only sees that the message count is >0, without distinction what
kind of message was processed.

I can increase the logging level (to > 10) to suppress the info messages and
there is no more error popup dialog now.

Still not happy because the log view which is opened does not contain any
entries, as described before.
I looked into all components with the debugger and they all had 36 messages
processed, so where does the output go?

Tnx for any further pointers

Norbert

Report message to a moderator

Re: myLogParser sample fails to import (hangs 4ever) [message #35306 is a reply to message #35270]

Fri, 14 October 2005 09:34

Norbert PlÃ¶tt

Messages: 233
Registered: July 2009

Senior Member

The question "Where does my output go"? led me to the solution. It can also
be found in the documentation (at least partially):

Help book Monitoring and analyzing ... --> Determining problems ...-->
Creating a log parser --> Creating a rules-based adapter --> Configuring the
outputter component

says:

"4. ... Update the Name, Description and Executable Class for the Outputter.
Refer to the Configuration file structure reference to obtain the correct
name of outputter classes to use. In the example below, the outputter has
been changed to use the LogImportOutputter which receives Common Base Event
instances and writes the externalized records to the Log Import loader of
the Log and Trace Analyzer."

In the demo the outputter type is preset to LoggingAgentOutputter, and
consequently the output goes nowhere and nothing is shown in the Log View.

BTW when I follow the link to the Configuration file structure then the
LogImportOutputter is not listed there so the list does not seem to be
up-to-date. The LogImportOutputter can of course be found with the java
search, but that is not the way it is supposed to be.

OK, so now I have answered all my own questions, maybe others can learn
something from it. (I sure learned a lot)

I hope that it was not all my fault by making some blunder, but I think
somebody should look through the demo example and documentations.

Bye,

Norbert

Report message to a moderator

Previous Topic:	Get Started Profiling Applications in Eclipse
Next Topic:	View imported logs as UML Sequence diagrams

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 23:06:04 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter