Ah, I see what you're saying, and I think you should submit a bug in JIRA
for it. Ideally, provide a minimal configuration that'll reproduce the
problem when you do, if you can create one...
Tim
On Sat, Jul 25, 2015 at 10:06 AM, James A. Robinson
wrote:
> Well, I'm pretty sure zookeeper won't
Well, I'm pretty sure zookeeper won't let the client specify a value
outside its own minSessionTimeout and maxSessionTimeout, so I think the
real question is how close to minSessionTimeout I can get without seeing
problems. It's really just masking the underlying problem though, right?
The client o
James,
You've tested two of the three cases; would it be possible to test the
third one?
- ActiveMQ timeout < ZooKeeper timeout: fails
- ActiveMQ timeout = ZooKeeper timeout: succeeds
- ActiveMQ timeout > ZooKeeper timeout: ???
If we can zero in on exactly what the recommendation is, I
So about 40 hours after fixing the settings so that both activemq and
zookeeper agreed on what the session timeout is, I haven't seen any new
instances of the errors I was seeing before. Previously it'd typically be
no more than 4 hours between complaints about needing to re-establish
zookeeper co
Hrm... I'm wondering if this is due to the zookeeper server having a
default session timeout of 40 seconds vs. a lower one I set for the
activemq node...
