Sidekick showing in Publish instance - where to look beyond runmodes?

[CordThomas]

We recently made a copy of our production publish instance to create a new development instance.  As per http://forums.adobe.com/message/5387365, the publish instance is showing the sidekick and edit features.  

We are still at CQ 5.4

We have verified that the:

• Sling Settings run mode is publish
• If we programmatically ask for run modes, we get isAuthor is false and isPublish is true (based on code we wrote to look at the SlingSettingsService.getRunModes()
• our jar is named cq-publish-4503.jar, for additional assurance we set the sling.properties values and added the -Dsling.run.modes startup parameter.

Anywhere else to look for why it might be misbehaving like this?

[smacdonald2008]

Did you look at this AEM community blog?

http://blog.kristianwright.com/2013/05/19/cq5-tip-confirming-the-runmode/

[CordThomas]

Thank you for the reply

Yes, that is what we did first - checking the Sling Settings in the OSGI Console.  It claims to be running as publish instance as do several other indicators.

Hoping there is some other explanation for why a publish runmode server would show the sidekick.

Also just verified in server/startup.log - see that it is starting as a publish server.

[smacdonald2008 · Accepted solution]

Just checked with AEM Adobe staff - here is their response on this subject:

This behaviour is not a bug. Once run mode changed for what ever reason can't revert it back. Some tips I gave are at:  

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...