Service dead when an error occurs in the middle of beginUpdate() and endUpdate()

[GoogleCodeExporter]

This issue refence form Issue No.505

What steps will reproduce the problem?
1.write some error code line between beginUpdate() and endUpdate()of 
SharedObject 
2.nest them all in try{ }catch statement.
3.do not solve exception just log them.
4.form client side call this method.
such....

public testMethod(){
try{
  so.beginUpdate() 
  {{{{error code}}}}
  so.endUpdate()
}catch(exception e){
  // logging statement
}

What is the expected output? What do you see instead?
-this app will can't be connected.  all client connect will be rejected after 
error lines done (including new connection they all dead since appConnect() 
method).  It's seem this problem cause by some code inside of so.beginUpdate() 
freezing app's main proceed. and this can solve by call so.endUpdate() in 
catch(){} nest.  app will not stuck and works fine after an error appears.

What version of the product are you using? On what operating system?
-red5 1.0
-windows 7

Please provide any additional information below.
-tell me if these issue solved in later version of red5  and how to install 
1.0.2 in windows 64 host.

Original issue reported on code.google.com by sun...@hotmail.com on 15 Jun 2014 at 7:27