[Red5] deleted SO still existing (for a while)
javaguy at freenet.de
javaguy at freenet.de
Tue Jul 1 04:17:14 PDT 2008
Hello,
I've a problem managing my shared objects.
After using a SO for communication with a certain client it should get
destroyed. If this special client returns a SO with the same ID is used
again. In most cases this is no problem, but sometimes a SO does survive
anyhow. It is not accessable but its ID is still listet inside red5 (I
use v0.7).
So here are some snippets how I create and destroy the obejcts
Application.createSharedObject(Application.scope, name, isPersistent);
ISharedObject so = s_oApp.getSharedObject(Application.scope, name);
so.addEventListener(eventListenerDummy);
so.addSharedObjectListener(new MySharedObjectListener(name));
Then I save this ISharedObject object to gat later access to it.
If I want to destroy the object I use
so.removeEventListener(Application.getEventListenerDummy());
so.clear();
so.close();
Now it may happen, that I get the mapped ID-Name for this SO.
Application.getSharedObjectNames(Application.scope);
In this String Set sometimes there are the names of closed SOs.
Sometimes they disappear after some time, sometimes not.
Creating a new SO with an ID of an old SO failes, if the closed SO is
still listed.
If I try to get it I get an ISharedObject! An attempt to place some
Attributes into it or read from it ... does end in a NullpointerException.
Do I have to do anything in a different way?
Why do the RSOs sometimes survive?
Can I kick these RSOs in any way?
If you need more information to help me, please inform me.
Thanks
___________________________________________________________________
Matthias Ullrich
People Zapping
Ambitious Bytes GmbH i.Gr. email: matthias.ullrich at pz-project.com
Washingtonstraße 2 phone: +49 (0) 3643 906245
D-99423 Weimar fax : +49 (0) 3643 506426
Geschäftsführer: Jan Kegelberg
Firmensitz: Weimar
HR-Eintrag: GmbH i.Gr.
More information about the Red5
mailing list