You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2014/06/19 06:32:24 UTC
[jira] [Resolved] (OPENMEETINGS-270) MemoryLeak / Dead-Lock in
FlvRecorderConverter
[ https://issues.apache.org/jira/browse/OPENMEETINGS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik resolved OPENMEETINGS-270.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.3
Assignee: Maxim Solodovnik (was: SebastianWagner)
Should be fixed
latest commit: Committed revision 1603707.
> MemoryLeak / Dead-Lock in FlvRecorderConverter
> ----------------------------------------------
>
> Key: OPENMEETINGS-270
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-270
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Priority: Critical
> Fix For: 3.0.3, 3.1.0
>
>
> DEBUG 05-15 16:08:19.955 FlvRecorderConverter.java 113480470 96 org.openmeetings.app.data.flvrecord.converter.FlvRecorderConverter [taskExecutor-4] - ### Stream not yet written Thread Sleep -
> => The Thread does sleep endlessly. We need to find out what causes that error and how we can prevent it.
> First of all a more detailed trace is needed to identify those recording_Ids that are broken to try to find out what happened and how long the Converter hands in the loop.
> It can be criticial if it turns out that there is a general issue with the recording there.
--
This message was sent by Atlassian JIRA
(v6.2#6252)