Bug 919423 - Carmart quickstart has low max-entries for eviction
Summary: Carmart quickstart has low max-entries for eviction
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: unspecified
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER2
: 6.3.1
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-08 12:27 UTC by Jakub Markos
Modified: 2015-01-26 14:03 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-01-26 14:03:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jakub Markos 2013-03-08 12:27:21 UTC
Carmart quickstart for EAP in client-server mode (other modes are OK because they use cache store) has eviction max-entries set to 4, which causes confusing behaviour (cars are being evicted, but are still listed on the main page).

Comment 1 Martin Gencur 2013-03-08 13:20:31 UTC
The workaround here is not to use eviction - i.e. remove the eviction configuration from a readme file which suggests using it. If we stil want to use eviction, we would need to add some logic to the application, like a cache listener which listens for events related to eviction and changes the list of stored cars (stored under a special key as an array list). IMO we could just remove the eviction configuration.

Comment 5 Misha H. Ali 2013-05-07 03:40:41 UTC
Set flag to nominate bug for 6.2 release notes.

Comment 6 Misha H. Ali 2013-06-18 04:19:11 UTC
Changed doc type to known issue since it looks like this bug is open.

Comment 12 gsheldon 2014-01-09 06:43:48 UTC
removing requires_doc_text flag as this bug is not to be included in release notes.

Comment 13 Martin Gencur 2014-07-31 13:28:43 UTC
Removed the eviction configuration in my pull request.

Comment 14 Adrian Nistor 2014-08-11 17:26:49 UTC
PR integrated in master: https://github.com/jboss-developer/jboss-jdg-quickstarts/pull/49


Note You need to log in before you can comment on or make changes to this bug.