-
1. Re: Is AsyncStore a reliable way to save data?
manik Dec 18, 2009 9:06 AM (in response to kosiakk)Good point, you should create a feature request for this on JIRA. -
2. Re: Is AsyncStore a reliable way to save data?
kosiakk Dec 18, 2009 9:20 AM (in response to manik)Thanks for your quick response!
Well, I think this is a bug, not feature actually.
At least, is 'state' were protected we could override AsyncProcessor with bug-free implementation.
I'll try to contribute a patch for this problem and report it to Jira.
-
3. Re: Is AsyncStore a reliable way to save data?
imbng Jan 4, 2010 7:52 PM (in response to kosiakk)Did this get logged into Jira? I looked and couldn't find it.
We too are interested in an AsyncStore that support retries or at least an extensible version of AsyncStore so we can write our own retry logic.
Bryan
-
4. Re: Is AsyncStore a reliable way to save data?
manik Jan 6, 2010 6:32 AM (in response to imbng)I haven't seen one. Alex, have you created one? -
5. Re: Is AsyncStore a reliable way to save data?
imbng Jan 11, 2010 7:36 PM (in response to manik)I looked again in JIRA and didn't see anything so I opened https://jira.jboss.org/jira/browse/ISPN-327 for this.
Bryan
-
6. Re: Is AsyncStore a reliable way to save data?
manik Jan 12, 2010 9:18 AM (in response to imbng)imbng wrote:
I looked again in JIRA and didn't see anything so I opened https://jira.jboss.org/jira/browse/ISPN-327 for this.
Bryan
Thanks!
-
8. Re: Is AsyncStore a reliable way to save data?
hakansu Nov 21, 2012 7:13 AM (in response to manik)Alexander Kosenkov wrote:
Use case:
- Create async store over JdbcStringBasedCacheStore
- Shut down the database
- Try to save something
- Save operation fails (of course)
- Save queue gets lost on next object put into async save!
This problem still remains afaics. AsyncStore tries to apply the modification three times and then fails with a debug message. In the new (5.2.0) implementation of AsyncStore all fields and relevant methods are private, so any attempts to subclass is futile. Is there any other way to handle this besides writing a new async store ourselves?