[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35888
]
james strachan commented on AMQ-643:
We could always raise another feature request JIRA for the subscription
dropping; also for nondurable messaging we have the option to drop
[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35889
]
Kevin Yaussy commented on AMQ-643:
--
I'm very happy with the eviction policy features. We will make *extensive* use
of that (btw, we may want to implement an eviction policy at
[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35890
]
Kevin Yaussy commented on AMQ-643:
--
Doh! Yes, issue resolved!
maxInactivityDuration does not seem to work properly
[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35861
]
Kevin Yaussy commented on AMQ-643:
--
However, that sounds like both sides would still have to explicitly make the
setting, right?
maxInactivityDuration does not seem to work
[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35864
]
Hiram Chirino commented on AMQ-643:
---
The change has been commited.
You now configure the maxInactivityDuration on the wireFormat. So on tcp
connection, it would look like:
[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35845
]
Hiram Chirino commented on AMQ-643:
---
Hi Kevin,
The maxInactivityDuration setting has to match on both sides of the connection.
If they do then there is no need to make
[ http://jira.activemq.org/jira//browse/AMQ-643?page=comments#action_35852
]
Hiram Chirino commented on AMQ-643:
---
Hi Kevin,
Yeah, I agree, making sure everybody is using the same setting is a bit of a
problem. I working on a change right now that will
