To reproduce the issue the following configuration options have to be set:
vc.adobe.createMeetingImmediately=false (not the default)
The following steps lead to the issue:
1. Create a Virtual Classroom Coursenode
2. Create two Meetings without configuring / opening them.
3. Open the second meeting to create the AdobeConnect Room
4. Open the first meeting to create (another!) Room
The 4th Step should not result in a new room, but it does as currently the first db entry is used not taking into account, that it does not have an sco id associated yet. The patch tries to fix this issue in the singleMeetingMode and in the permanentRoom scenario (where this could also occur).