[Mashup-dev] [jira] Commented: (MASHUP-1063) desk tray icon glitches

[Channa Gunawardena (JIRA)]

    [ https://wso2.org/jira/browse/MASHUP-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18529#action_18529 ] 

Channa Gunawardena commented on MASHUP-1063:
--------------------------------------------

1) The service does start up automatically when the Vista instance is started in our test setup, but the system tray icon does not start and needs to be started using the 'start menu' option.
2) The desk tray icon, started by simply clicking on the menu, is not able to start the service. The problem is with how Vista grants privileges; a logged in user, even one with admin privileges, does not actually grant them to a program launched from the 'Start' menu or from a command line. You are in fact 'acting as a user' in vista, by default. You need to right-click on the 'Start System Tray' icon and chose the 'Run as administrator' option. The tray icon started in this manner has privileges to start and stop the server.
3) If the service is started and the tray icon connects successfully, as was observed in testing, it is able to stop the server as this is a JMS request sent to the server to shut itself down, and does not require admin rights.

Next step - is it possible to grant these privileges when installing, so that the tray icon starts up automatically and with admin privileges?

> desk tray icon glitches
> -----------------------
>
>                 Key: MASHUP-1063
>                 URL: https://wso2.org/jira/browse/MASHUP-1063
>             Project: WSO2 Mashup Server
>          Issue Type: Bug
>            Reporter: Jonathan Marsh
>            Assignee: Channa Gunawardena
>             Fix For: 1.5.1
>
>
> Lately I've encountered a number of issues with the mashup server installed as an NT service on Vista:
> 1) The Mashup Server doesn't automatically start up.  I have to open the Services panel to do so.
> 2) The desk tray Start option doesn't seem to work in the above case.
> 3) While Shut Down appears to work, checking Services shows that the Mashup Server was in fact not shut down.
> Has anyone else experienced glitches like these?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira