|
Home > Archive > WebSphere Commerce suite > June 2004 > MassLoad trace
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]
|
|
| Carlos Beltrán 2004-06-07, 8:43 am |
| Hi,
We have a problem with MassLoad and we want to know if there is a way to
tell
MassLoad to generate a better trace.
We have been working with WCALoggerConfig.xml but even setting the
messageType
to INFO, WARN, ERROR, FATAL, PUBLIC, PRIVATE, ... we can't get a trace at
whitch we can trace more accurately the process execution.
We want to know if the INSERT/UPDATE statement is really executed, if it
hangs before or
after the statement execution, ...
By the moment we just have a "useless" trace at whitch we can see that the
process is
executing a INSERT/UPDATE statement ( but we can see the real parameters
used or
other usefull information ).
Thank you in advance.
--
Carlos Beltrán Vázquez
Departamento e-business
Tel: 93 419 63 46
Fax: 93 419 65 61
cbeltran@mss.es
| |
| Robert Brown 2004-06-07, 11:51 pm |
| You can enable a database trace if you want the SQL statements that are
being executed. Why not do that?
R
Carlos Beltrán wrote:
> Hi,
>
>
> We have a problem with MassLoad and we want to know if there is a way to
> tell
> MassLoad to generate a better trace.
>
> We have been working with WCALoggerConfig.xml but even setting the
> messageType
> to INFO, WARN, ERROR, FATAL, PUBLIC, PRIVATE, ... we can't get a trace at
> whitch we can trace more accurately the process execution.
>
> We want to know if the INSERT/UPDATE statement is really executed, if it
> hangs before or
> after the statement execution, ...
>
> By the moment we just have a "useless" trace at whitch we can see that the
> process is
> executing a INSERT/UPDATE statement ( but we can see the real parameters
> used or
> other usefull information ).
>
>
> Thank you in advance.
>
> --
> Carlos Beltrán Vázquez
> Departamento e-business
> Tel: 93 419 63 46
> Fax: 93 419 65 61
> cbeltran@mss.es
>
>
|
|
|
|
|