Difference: KnownIssues (61 vs. 62)

Revision 622013-10-03 - EricFrizziero

Line: 1 to 1
 
META TOPICPARENT name="GeneralDocumentation"

Known issues

Line: 13 to 13
 This error is reported only by tomcat6 when the server container is being shutting down. Even if the message shows a memory leak this issue doesn't occur when the server is running.
Added:
>
>

Problem in configuring CREAM (ONLY if the YAIM tool isn't used)

If CREAM isn't configured by using YAIM tool, the following query MUST be executed on the cream database:

use creamdb; ALTER TABLE db_info MODIFY creationTime TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP; commit;

This because there is an unwanted auto-updating of the field "creationTime" on the cream database that it causes a problem by submitting jobs via WMS

Submitting jobs via WMS, you could obtain the following wrong message:

=============== glite-wms-job-status Success =============

BOOKKEEPING INFORMATION:

Status info for the Job : ...

Current Status: Aborted <-----------------

Status Reason: CREAM'S database has been scratched and all its jobs have been lost <-----------------

Destination: ...

Submitted: ...

Parent Job: ...

==================================================================

N.B: The CREAM database isn't scratched, but it is so from the WMS point of view because of the above problem.

 

Authorization error from Argus in EMI-2

Argus server does not authorize a user if it is under heavy load.

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback