[Ds-java-dev] [jira] Resolved: (DS-114) Mercury module disengages when server is restarted

[Amila Suriarachchi (JIRA)]

     [ https://wso2.org/jira/browse/DS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Suriarachchi resolved DS-114.
-----------------------------------

    Resolution: Fixed

fixed the issue

> Mercury module disengages when server is restarted
> --------------------------------------------------
>
>                 Key: DS-114
>                 URL: https://wso2.org/jira/browse/DS-114
>             Project: WSO2 Data Services
>          Issue Type: Bug
>          Components: core
>         Environment: winxp, jdk15
>            Reporter: Charitha Kankanamge
>            Assignee: Amila Suriarachchi
>            Priority: Blocker
>
> RM settings does not seem to persist when restarting server. 
> Steps to reproduce
> --------------------------
> 1. Engage Mercury to a data service
> 2. Invoke service with RM
> 3. Restart ds server
> 4. Run mercury enabled client again. You will get "The [action] cannot be processed at the receiver" fault

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