[
https://issues.apache.org/jira/browse/SYNCOPE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900213#comment-13900213
]
Francesco Chicchiriccò commented on SYNCOPE-481:
------------------------------------------------
Hi [[email protected]],
to solve your immediate need, you just need to reduce the trace level from ALL
(default) to at least ERROR (see the
[wiki|https://cwiki.apache.org/confluence/display/SYNCOPE/External+resources]
for some more details) for each external resource you have.
Anyway, the out of memory error returned by admin console is not acceptable:
could give an idea of the size of TaskExec table when this condition is
reached? Also, could you also provide some information about the type of such
executions (how many from PropagationTasks? how many from SyncTask?) and so on.
Thanks.
> Limit the number of results stored for Task Exectutions
> -------------------------------------------------------
>
> Key: SYNCOPE-481
> URL: https://issues.apache.org/jira/browse/SYNCOPE-481
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.1.5
> Environment: Syncope 1.1.5 mysql backend
> Reporter: bryan staley
>
> We currently have a sychronization task that runs every 5 minutes. Over the
> course of a couple of weeks, the TaskExec table continues to grow and
> attempts to open the Task Executions pane within console result in an out of
> memory. Clearing this table buys us some more time but it would be nice if
> we could specify how much of a history to maintain (or atleast display via
> the Task Execution pane.)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
