[#XCF-2672] Clicking 'Refresh' on conference participants page with stale data results in an exception

sipXconfig

Clicking 'Refresh' on conference participants page with stale data results in an exception

Created: 2008-06-30 12:55 Updated: 2008-08-11 05:22

Component/s:

conference

Affects Version/s:

3.11.3

Fix Version/s:

3.11.5

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Issue Links:

Duplicate

This issue also reported as:
	~~XCF-2691~~ Using the Evict button then refresh i...

Description

« Hide

If a participant leaves a conference while viewing its Participants page by hanging up normally, clicking 'Refresh' causes an exception. The underlying list of participants is stale and somehow this inconsistency with what FreeSWITCH returns is causing an error.

To reproduce:
1) Create a conference.
2) Call the conference from a phone.
3) Go to the participants page.
4) Hang up the phone.
5) Click Refresh.
6) Exception!

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Chris Parfitt - 2008-07-09 02:35

Not just last paticipant but when Refresh is used after evict issue is seen

[ Permlink | « Hide ]

Damian Krzeminski - 2008-07-10 09:03

change title to reflect the fact that the problem can be reproduced be removing any (not just last) participant

[ Permlink | « Hide ]

Joe Attardi - 2008-07-16 14:16

Verified this bug - looking into it now...

[ Permlink | « Hide ]

Joe Attardi - 2008-07-23 12:17

The cause of this particular scenario seems to be a timing problem - sometimes freeswitch is a bit slow in removing the participant from the list, so we get stale data.
However, the real problem here is that sipxconfig blows up when we have stale data.

[ Permlink | « Hide ]

Joe Attardi - 2008-07-25 14:23

Turns out my previous comment was not entirely accurate. After some more digging and debugging, the problem is when the AutoRefreshForm refreshes after a user has hung up from the conference. If the participants page itself is reloaded, it is fine - the participant disappears from the list - but just clicking the Refresh button causes problems.

To reproduce much more easily than evicting and waiting for the timing:
1) Create a conference.
2) Call the conference from a phone.
3) Go to the participants page.
4) Hang up the phone.
5) Click Refresh.
6) Exception!

Now that I have narrowed down what I am 99% sure is the specific cause, I hopefully can attack it and put an end to its misery.

Hopefully.

[ Permlink | « Hide ]

Joe Attardi - 2008-08-01 11:08

Resolved in SVN 13218.

This is not a true fix, unfortunately - try as I might I have been unable to find the root cause. But this is a workaround that should prevent the issue from occurring.

[ Permlink | « Hide ]

Anushree Ganguly - 2008-08-11 05:22

This issue is Resolved.Verified in the following build :
sipxproxy 3.11.5-013228 2008-08-07T14:21:08 oem-centos5
sipxconfig 3.11.5-013228 2008-08-07T14:43:41 oem-centos5

Steps taken to verify this issue :
1.ph1,ph2,ph3 are in conference
2.Disconnect ph1 and click on refresh.
3.Isolate and then Include phone2.Click Refresh.
4.Mute and then un-mute ph3.Click Refresh.
5.Auto Refresh after 10 seconds.
6.Evict the last participant and then click refresh.
Internal exceptions did not occur in either of these test scenarios.