Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server connection status notification to the application. #23

Closed
GoogleCodeExporter opened this issue Apr 7, 2016 · 3 comments
Closed

Comments

@GoogleCodeExporter
Copy link
Contributor

I am using 2.0.2 client on RHEL and have one issue.

We have two TOMCAT servers in production and will have memcached running on
both. 
case 1. when one servers goes down client uses the other active one.(works
fine)
case 2. when both the servers goes down then we are disabling cache and
fetching data from database.(works fine)
case 3. When atleast one of the servers comes back is there any way for the
client to get notified about it. So that we can enable caching.

I could not find any solution for the above problem in case 3. so changed
the client implementation to have a broadcaster and added two more classes
as listeners. Applications who requires a notification should subscribe to
the events and hence will get the notifications.
I am not sure how to do this with the current implementation.
If there is a better way then let me know other wise I would like to
contribute to this.

Regards,
Paul.

Original issue reported on code.google.com by bishwaje...@gmail.com on 5 May 2008 at 7:12

@GoogleCodeExporter
Copy link
Contributor Author

Interesting.  I just added the ability for you to poll status in what will be 
2.1. 
It makes a lot of sense to be actively told when we lose servers, though.  I 
mean,
it's not like I don't know.

I've been doing a ton of work for 3.0, it might fit in there very well if not 
sooner.

Original comment by dsalli...@gmail.com on 5 May 2008 at 7:31

  • Changed state: Accepted
  • Added labels: Milestone-Release3.0, Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Contributor Author

This has been sitting around for a while.  I finally did something good here in 
what
will be 2.3.  It's only for observers, but I've been able to do things like 
block for
failures/bringups on latches and what-not.

Original comment by dsalli...@gmail.com on 3 Feb 2009 at 5:21

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Contributor Author

Thanks for fixing it.

Original comment by bishwaje...@gmail.com on 3 Feb 2009 at 8:06

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant