[
https://wso2.org/jira/browse/MASHUP-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18608#action_18608
]
Channa Gunawardena commented on MASHUP-1063:
--------------------------------------------
There does not appear to be a simple fix or workaround which will resolve this
issue.
Service Monitor's design to be revisited taking recommendations made in
http://msdn.microsoft.com/en-us/library/bb325654.aspx into account, perhaps
separating the monitoring functionality into separate service and UI
components, to enable UI to be activated on startup while retaining the ability
to start and stop the Mashup server service in Vista (and any other environment
with UAC).
Workaround is to use the 'Run as Administrator' option when starting the
'System Tray Monitor' manually, in the MS 'Start' Menu.
> 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.6
>
>
> 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
_______________________________________________
Mashup-dev mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
