[Mashup-dev] [jira] Commented: (MASHUP-1067) Once the sys date is changed and reset before a service is created and saved, it do not deploy till the server is restarted

[Channa Gunawardena (JIRA)]

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

Channa Gunawardena commented on MASHUP-1067:
--------------------------------------------

The Axis2 deployer's polling mechanism will need to be examined to see why this occurs. I don't believe this needs to be fixed urgently as it's an edge case with an easy workaround, so am scheduling it for 1.6.

> Once the sys date is changed and reset before a service is created and saved, it do not deploy till the server is restarted
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MASHUP-1067
>                 URL: https://wso2.org/jira/browse/MASHUP-1067
>             Project: WSO2 Mashup Server
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: Nightly
>            Reporter: Anushka Dayananda
>            Assignee: Channa Gunawardena
>             Fix For: 1.6
>
>
> Steps to recreate
> ---------------------
> 1. Start the mashup server
> 2. Change the system date
> 3. Reset the system date to the current date
> 4. Create a new mashup(when the system date is the current date)
> Issue
> ------
> Though the service was created and saved in the correct date, the service do not get deployed till the server get restarted.

-- 
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