Sent from my iPhone
On Jun 21, 2011, at 11:39 PM, "Jorge Infante Osorio" <[email protected]> wrote: > Hi folks. I continue with the feedbacks. > > > > When I active the service discovery functionality in AS and the Greg are > online all work fine, but when Greg in down for every service in AS I see an > error like this in the console during the startup. > > > > [2011-06-22 02:24:32,984] ERROR > {org.wso2.carbon.discovery.TargetServiceObserver} - Cannot send the hello > message > > org.wso2.carbon.discovery.DiscoveryException: Error while sending the > WS-Discovery notification for the service wso2carbon-sts > > > > If I have a few services for test this is not a problem, but if I have 100 > services or more the delay in the server startup is noted. > > > > I think that if Greg is down during the AS startup this must be capture, and > in this case none hello message must be send. > No. Right solution would be to male the notification logic run asynchronously. Otherwise we have to make two network calls for each notification. Please raise a jira for this. Will fix for a future release. > > > In this same scenario, what happen If I startup the Greg after the AS? > GReg will have the last updated service states which could be different from actual service states. If the services are redeployed states will be updated in the registry correctly. > > > Saludos, > > Ing. Jorge Infante Osorio. > > J´Dpto Soluciones SOA. > > CDAE. > > Fac. 5. > > UCI. > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
