CollectionNode exception during collaboration

[TryingAnotherOn]

My App uses AFCS to let users send messages to other
connected users. I am getting an exception



Error: The node is not synchronized. Make sure you've
subscribed.

at
com.adobe.rtc.sharedModel::CollectionNode/publish_Item()[C:\work\main\connect\cocomo\src\com\adobe\rtc\sharedModel\CollectionNode.as:608]

.......

.......

Note: '_' inserted in publish_Item() as this editor reporting
without '_' ( You have censored word(s) in your text )



I have subclass of CollectionNode that do all the messaging.
This exception happens after sucessfully exchanging some messages.
( so the connection is first established , and then drops after
successfully exchanging some messages ). Any help to handle this
would be appropriated.

Thanks

[Former Community Member]

Hi,



As you are sayig you are already subscribed and you are able
to exchange message first and then the connection drops? We can
look at it at your side and see whats going wrong. But can you
provide us with a small example showing this and are you hitting
this error always. Also, put a breakpoint in SYNCHRONIZATION_CHANGE
event handler in your collectionNode class and see if you hit the
breakpoint just before this error happens.



Thanks

Hironmay Basu

[TryingAnotherOn]

quote:

---

As you are sayig you are already subscribed and you are able
to exchange message first and then the connection drops?

---

Yes.

quote:

---

But can you provide us with a small example showing this and
are you hitting this error always."

---

This error is random. I did not hit this during development,
my testing reported this bug (they have debugger version of flash
player installed on their machine). They tried to narrow it down
but its behavior is totally random.

quote:

---

Also, put a breakpoint in SYNCHRONIZATION_CHANGE event
handler in your collectionNode class and see if you hit the
breakpoint just before this error happens.

---

As the behavior of this error is random, so it might not be
possible to figure it out by debugging. I will put an alert in
SYNCHRONIZATION_CHANGE event, to see this.