Red5.getConnectionLocal(). > > getClient().getId() is a red5 API call, it does not so much have todo with OpenMeetings. OpenMeetings never writes that ID. So if the ID/streamId is not correct then either: a) the client is already gone and its a problem of reading the variable at a not appropriate time b) there is an error in the red5 API
Sebastian 2011/1/19 lyric <[email protected]> > Red5.getConnectionLocal().getClient().getId() returns '0' instead of > '1' for the following cenario: > > First Alice enters the room. Then Bob enters. Then Bob closes his > browser. Bob's image > becomes black but is not removed from the room. > > > > On 19 Jan., 13:49, "[email protected]" <[email protected]> > wrote: > > and what does: > > Red5.getConnectionLocal(). > > getClient() > > > > return? > > > > If I remember correctly the problem was that the object/client was > already > > gone when > > Red5.getConnectionLocal(). > > getClient() > > was called, so there was a NullPointer exception at that point. > > > > Sebastian > > > > 2011/1/19 lyric <[email protected]> > > > > > > > > > Hello Sebastian, > > > > > here the main commits which I found that could be realated to the > > > issue: > > > -r1795 Fixes: Null-Pointer Exception in Room-Leave Method > > > -r1867 This seems to workaround the NullPointer Exception in the > > > roomLeaveByScope > > > Method. > > > -r1894 Fixes: Update to fit into RED5-0.8RC3 > > > -r2023 Fixes error that may prevent a User to get cleared correctly > > > when leaving a > > > Room. > > > -r2036 issue 723 fix, syncronizing the ScopeApplicationAdapter > > > methods > > > > > If I understand right, Red5.getConnectionLocal().getClient().getId() > > > called in 'roomLeave'- and 'streamBroadcastClose' should return the > > > streamid of the client whose browser was closed. But in my upgrade it > > > doesn't. Unfortunatly I have no idea why. > > > > > Thanks, > > > Cyril > > > > > On 19 Jan., 09:29, "[email protected]" <[email protected]> > > > wrote: > > > > Hallo Cyril, > > > > > > are there any source code commits linked to the Issue that was fixed? > > > > I can hardly remember those commits anymore as it is such long time > ago. > > > > > > Otherwise I would suggest you need to debug down the problem, if you > have > > > > questions about certain variables or methods let us know. > > > > > > Sebastian > > > > > > 2011/1/19 lyric <[email protected]> > > > > > > > Hello, > > > > > > > currently I am trying to upgrade a customized openmeetings- > > > > > application. I started by upgrading to release 2036 (I know it is > > > > > still a quite old one but I am quite slow with merging ;-) > > > > > > > That release is said to fix a "room leave"-anomaly (issue 723). > > > > > Unfortunately not for me. > > > > > For example having two users Alice and Bob. First Alice enters the > > > > > room. Then Bob enters. Then Bob closes his browser. Bob's image > > > > > becomes black but is not removed from the room. > > > > > > > After some investigation I found that in the 'roomLeave'- and > > > > > 'streamBroadcastClose'-handlers > > > > > Red5.getConnectionLocal().getClient().getId() does not seem to > return > > > > > the correct streamid. In the above example '0' instead of '1'. > > > > > > > Does anybody know what may be wrong? Please tell me if you have any > > > > > idea. I cannot find the reason, although I am already desperately > > > > > searching for more than three weeks. > > > > > > > Thanks for reading, > > > > > Cyril > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > Groups > > > > > "OpenMeetings developers" group. > > > > > To post to this group, send email to > [email protected] > > > . > > > > > To unsubscribe from this group, send email to > > > > > [email protected]<openmeetings-dev%[email protected]> > <openmeetings-dev%[email protected]<openmeetings-dev%[email protected]> > > > > > <openmeetings-dev%[email protected]<openmeetings-dev%[email protected]> > <openmeetings-dev%[email protected]<openmeetings-dev%[email protected]> > > > > > > > > > . > > > > > For more options, visit this group at > > > > >http://groups.google.com/group/openmeetings-dev?hl=en. > > > > > > -- > > > > Sebastian > > > > Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp:// > > >www.wagner-sebastian.com > > > > [email protected] > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "OpenMeetings developers" group. > > > To post to this group, send email to [email protected] > . > > > To unsubscribe from this group, send email to > > > [email protected]<openmeetings-dev%[email protected]> > <openmeetings-dev%[email protected]<openmeetings-dev%[email protected]> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/openmeetings-dev?hl=en. > > > > -- > > Sebastian > Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp:// > www.wagner-sebastian.com > > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "OpenMeetings developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<openmeetings-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/openmeetings-dev?hl=en. > > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.wagner-sebastian.com [email protected] -- You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en.
