|
Home > Archive > WebSphere Site Analyzer > January 2004 > WAS stops prematurely when site analyzer is processing large files.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WAS stops prematurely when site analyzer is processing large files.
|
|
|
| Hi Everyone!
When I am performing the log import process, after some hours, I get
that error:
SASC1411I: WebSphere Site Analyzer: task failed to complete due to
errors. Task
type=Http Log Import Task id=1,107 Display name =Sample2Log. See message
below for details.SAERROR0001I: Multiple messages, each reported below:
SASC1414E: The scheduler has detected that a running task is not
responding.
This is usually because WebSphere Application Server stopped while a
task was
running. Try to run the task again. Task type=207 Task id=1,107. See
below
for any information that the task posted before being stopped.
SADC5026I: Processing log data...
That errors is caused by the WAS stop. But why does this happen? Is
there a simple clue for solving that? Is there any parameter to be set up?
Our environment:
Windows 2000 Server (SP3)
DB2 7.2 (SP8)
WAS 4.0
Site Analyzer 4.1
File being imported 128MB
Best Regards!
| |
| Farhan Thawar 2004-01-19, 3:03 pm |
| Try processing smaller log files and see if the error occurs? You can
set WPS to produce more frequent logs, meaning they will be smaller.
Farhan
On Mon, 17 Mar 2003 16:32:17 -0800, Kevin <kevinuk@bol.com.br> wrote:
quote:
>Hi Everyone!
>
>When I am performing the log import process, after some hours, I get
>that error:
>
>SASC1411I: WebSphere Site Analyzer: task failed to complete due to
>errors. Task
>type=Http Log Import Task id=1,107 Display name =Sample2Log. See message
>below for details.SAERROR0001I: Multiple messages, each reported below:
>SASC1414E: The scheduler has detected that a running task is not
>responding.
>This is usually because WebSphere Application Server stopped while a
>task was
>running. Try to run the task again. Task type=207 Task id=1,107. See
>below
>for any information that the task posted before being stopped.
>SADC5026I: Processing log data...
>
>That errors is caused by the WAS stop. But why does this happen? Is
>there a simple clue for solving that? Is there any parameter to be set up?
>
>Our environment:
>Windows 2000 Server (SP3)
>DB2 7.2 (SP8)
>WAS 4.0
>Site Analyzer 4.1
>File being imported 128MB
>
>Best Regards!
>
|
|
|
|
|