Cache.stop() should not remove the cache from the cache manager.
But AFAIK the ComponentRegistry that holds all the cache-scoped components
is destroyed, and recreated by Cache.start(). In the constructor it should
register Query's CommandInitializer again, so LifecycleManager should find
it and
NPE is thrown at diff place; see #125 line in LM class.
No initializer is found, hence NPE on initializer::initialize(Cache).
Sent from my iPad
On Aug 28, 2012, at 9:25, Dan Berindei dan.berin...@gmail.com wrote:
Cache.stop() should not remove the cache from the cache manager.
But AFAIK
On Aug 27, 2012, at 10:51 PM, Ales Justin wrote:
OK, let me try this workaround.
But should Cache::stop also remove it or not?
I'm not sure whether it should remove it or not.
I remember working on the cache restart procedure and I have the feeling I
might have avoided it to be removed
That's the NPE I was talking about, the CommandInitializer *should* be
registered again by the ComponentRegistry constructor so the initializer
variable shouldn't be null...
I can't say why that doesn't happen, though. Could you try with an
Infinispan-only test?
On Tue, Aug 28, 2012 at 11:10
+1 This is how it's also done for AS7 project.
Rado
On 28/08/12 15:29, Sanne Grinovero wrote:
Hi all,
I see that on github there are many pull requests for Infinispan, but
a good amount of them is not to be merged, needing more feedback or
pending for other reasons.
Rather than keeping
All I can contribute is that you cannot really avoid buffering in the
marshaller, because for user data it uses constructs of the form:
length content
You generally cannot know length without some form of buffering.
There may be some optimizations which are possible that I haven't done
Hi all,
since Marko Lukša is again submitting nice patches to Infinispan
Query, I've changed JIRA permissions to add him to the team.
Thanks Marko for all the help! Now you can send more and assign issues
to yourself :P
Cheers,
Sanne
___
Rado, is the AS7 process documented anywhere?
Sanne, I'm not sure I understood what you mean by tracking these in JIRA...
do you mean I should add a link to the branch on GitHub instead of a pull
request (if my code is not quite ready), and feedback should go in JIRA
comments as well?
Dan
On
