You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "SebastianWagner (JIRA)" <ji...@apache.org> on 2012/05/25 18:54:23 UTC
[jira] [Commented] (OPENMEETINGS-270) MemoryLeak / Dead-Lock in
FlvRecorderConverter
[ https://issues.apache.org/jira/browse/OPENMEETINGS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283595#comment-13283595 ]
SebastianWagner commented on OPENMEETINGS-270:
----------------------------------------------
I was able to find the Exception why it does not stop.
However I am not sure yet about the reason as I cannot reproduce it.
We will need to update the demo server with my latest changes and see if the problem persists
> 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 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: SebastianWagner
> Priority: Critical
> Fix For: 2.0 Apache Incubator Release
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira