Details
-
Bug
-
Resolution: Fixed
-
Critical
-
0.17.0
-
None
-
Couchbase Docker image on MacOS and Couchbase Docker image on Openshift platform
-
1
Description
We are using Couchbase Docker image both to develop on laptop and on our DEV and QA environment.
We are developing on Mac OS and our DEV and QA environment work with OpenShift v3.7.1 (Kubernetes v1.7.6).
On preproduction and production environment, Couchbase is deployed on VM.
- When using Java DCP client 0.17.0 or older version hosted in Docker, Java DCP client always failed to reconnect to Couchbase container once we restart the container.
- When using Java DCP client 0.17.0 or older version hosted on a VM (or directly on laptop), Java DCP client always reconnect to Couchbase container once we restart Couchbase.
Step to reproduce
This issue occur both with Couchbase 4.6.5 and Couchbase 5.1.0 (and probably all others versions)
- Run Couchbase in Docker container as described in configuration (https://developer.couchbase.com/documentation/server/current/install/getting-started-docker.html)
- Init the Couchbase server and install the sample bucket "travel-sample"
- Run the exemple described in the Readme on GitHub https://github.com/couchbase/java-dcp-client after increasing the sleep timeout to several minutes (see Main.java in attachement)
- Make a mutation on a document in "travel-sample" bucket though the Couchbase administrator interface
- The mutation is printed by the java program
- Stop your Couchbase Docker container
- Start your Couchbase Docker container few second later
- Make a mutation on a document in travel-sample bucket though the Couchbase administrator interface
- The mutation is not printed by the java program
When doing the same test without Couchbase on Docker container, step 9 print the mutation.
Thanks,
Attachments
Issue Links
- blocks
-
KAFKAC-127 SOURCE: can't reconnect to Couchbase hosted on Docker Container
- Resolved
- is cloned by
-
JDCP-215 Java DCP client could not reconnect to Couchbase host
- Closed
- relates to
-
JVMCBC-371 Safeguard Endpoint connect when callback does not return.
- Resolved