We have had issues related to system instability.

It's quite stable. Ever since I started using it, for the past year, we only had to restart that product one time.

Coherence was not originally an Oracle product. Oracle bought it and made it more mature. They made it enterprise-wide; and it’s good. They also made it a bit pricier. We were using an EH cache open source, which actually wasn’t performing that well. We had to do a lot of restarting and troubleshooting. But now with Coherence, it's quite stable. Because we are an Oracle vendor, we have a license.

We have encountered the occasional minor bug and very occasional more serious bug.

Intermittent issues with data.

I have not encountered any stability issues.

Mostly, it has been stable other than encountering full GC cycles occasionally.

None.

We have encountered stability issues. We have nodes failing all the time, especially because of timeouts caused by node synchronization, but occasionally there are also memory-related errors.

No, as long as we ensure we have 4x memory capacity than the objects that we want to keep in the cache.

I did not encounter any stability issues.

We found some issues using the incubator libraries for database integration on writing and also using the feature to write cache contents to disk.

It is a stable product. We don't really have any issues. The only thing that we really need to think about is when we need to reload the whole thing, especially if we need to do some patching or maintenance. That really takes about 24 hours. That's the downside. It’s something that we are now living with. So we really take that hit on that. Generally, that's why we really plan our maintenance.

In four years, we haven´t found any issues with stability. We have had some problems but they derived from how clients use this product.

For the most part, we have not encountered stability issues.

There have been issues in the cache configuration file in older versions, and a nodes eviction and timeout error.

I have not really encountered any stability issues. I was pleased with its fault tolerance.

I encountered stability issues sometimes, but that was mainly due to the wrong cache configuration used in implementation. Wrong configuration causes an impact on how objects are serialized or retained, etc.

I have not encountered any stability issues.

No.

No stability issues: A node can fail, but the topology can be designed to be fault-tolerant.

We had one instance when we experienced intermittent network failure. This issue was not reproducible for obvious reasons. Coherence failed to live up to its SLA by not being able to recover but getting into a state where new nodes were created when the old ones were still there but for some reason no longer recognized as being part of the cluster. The Oracle support was not something to write home about, i.e. there was a constant request for more info (logs, timelines, etc. – which were provided) and never a feeling that the problem was understood or at least that there was any serious attempt at investigating or reproducing on Oracle’s side.

We have a stability issue once a year on the average. Most of the time, the cause is a network issue. When a few servers get out of the cluster, we lose data.

Yes, there is a big problem in Coherence cluster. For example, a master, because of connection issues, does not announce its mastery to a slave; slave becomes a master, then two masters appears in cluster, and the whole cluster dies.

We did not encounter any issues with stability.

The product is stable and solid.