Hi, the freezing was fixed last week in trunk, it pretty much failed all weekend 2 weeks ago, wish i knew about that jstack command. Along with the freeze fix, there is no more outofmemory errors. Getting JMX exceptions now though.
Luke Hubbard wrote: > Hi All, > > There have been reports of red5 freezing from different people on the > list. We have been working to fix these issues are making progress and > improving performance at the same time. Some people are telling us the > problem is fixed others that its still happening. Most likely there > are a few places this can happen and we have not fixed them all yet. > > So if you get server deadlock here if what you can do to help us fix > the problem. > > 1. Ensure you are running trunk. This is so we can be sure the problem > has not already been fixed. > > 2. Make sure you start the server using red5.sh or red5.bat. This will > ensure the server is running under its own pid. > > 3. When the server freezes run the jstack command. You can find the > process id using ps -ef (linux) ps -aux (osx) or task manager (win). > > jstack <pid> > > 4. Create a jira ticket, attach the output from jstack, and describe > your environment and application. Include details of your thread > settings etc if you have changed from the defaults. If doesnt do any > harm to fire off an email to the dev list too. > > Ideally with your help we can fix these issues before the next release. > > Luke > > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
