[ http://wso2.org/jira/browse/WSAS-625?page=all ]
Afkham Azeez reassigned WSAS-625:
---------------------------------
Assignee: sumedha rubasinghe (was: Afkham Azeez)
Here is how this should be fixed.
The dataservice deployer detects that the DB connection is unavailable.
Now it registers a TimerTask which periodically tries to connect to the DB
If successful, it removes the service from the faulty list, redeploys the
service
Similarly, even if the service was successfully deployed, the DB connection can
fail later. In this case, when a DB failure is detected, the service should be
classified as a faulty services, and a TimerTask should try to re-establish the
connection.
> data service hotupdate does not handle re-established db connections
> ---------------------------------------------------------------------
>
> Key: WSAS-625
> URL: http://wso2.org/jira/browse/WSAS-625
> Project: WSO2 WSAS
> Issue Type: Bug
> Components: data-services
> Affects Versions: 2.1
> Environment: winxp, mysql5, jdk15
> Reporter: Charitha Kankanamge
> Assigned To: sumedha rubasinghe
> Priority: Critical
>
> Please go through the following steps to reproduce this issue.
> Make sure to enable hotupdate in axis2.xml
> 1. Create a data service (suppose it uses a mysql data source)
> 2. Shutdown mysql
> 3. restart WSAS
> 4. The data service will be deployed as faulty due to the unavailable db
> connection
> 5. Now, restart MySQL
> The faulty status of the data service will not be changed until you restart
> WSAS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
