Modification of the ace:tabSet selectedIndex via server side does not trigger tab change on the client. Click on refresh button in the browser is required in order to force tab change.

To reproduce:

1. Create a test case from attached source code.
2. Launch application and click on change tab command link
Notice:
- Server log will display messages:
         Action Event begin
         Old Index value: 0
         New index value: 1
         Action Event end
- Tab1 will switch to Tab2 in the browser and display its content

3. Click on change tab for the second time.
Notice:
- Server log will display messages:
        Action Event begin
        Old Index value: 1
        New index value: 2
        Action Event end
- The content of tab 2 will disappear and it will remain selected in the browser.

4. Hit refresh button in the browser
Notice:
- Tab 2 will switch to Tab3 in the browser and display its content.

5. Click on change tab link. Behavior of steps 2-4 will be repeated.

Other notes:
Tried sample code with different parameters of the cache attribute for tabs without any success.
No errors were present in the JavaScript console or server log during the test.