You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Mikael Kurula (JIRA)" <ji...@apache.org> on 2012/12/03 13:33:59 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=13508692#comment-13508692 ]
Mikael Kurula commented on OPENMEETINGS-270:
--------------------------------------------
Hi!
I just came across this problem on my server, and it is a definitive showstopper for my application of OpenMeetings. How can I help to debug the problem? (I'm new to OpenMeetings but know how to dig in logs etc.)
Friendly greetings,
Mikael
> 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.1 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
For more information on JIRA, see: http://www.atlassian.com/software/jira