[JBoss JIRA] (ISPN-9481) Implement toString in EncoderCache.EntryWrapper
by Katia Aresti (JIRA)
[ https://issues.jboss.org/browse/ISPN-9481?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9481:
-------------------------------
Description:
When we call
{code}
logger.info("Entries from Cache: {}", cache.entrySet());
{code}
Displays:
bq. Entries from Cache: [org.infinispan.cache.impl.EncoderCache$EntryWrapper@5580d62f]
was:
When we call
{code}
logger.info("Entries from Cache: {}", cache.entrySet());
{code}
bq. Displays: Entries from Cache: [org.infinispan.cache.impl.EncoderCache$EntryWrapper@5580d62f]
> Implement toString in EncoderCache.EntryWrapper
> -----------------------------------------------
>
> Key: ISPN-9481
> URL: https://issues.jboss.org/browse/ISPN-9481
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Katia Aresti
> Assignee: Katia Aresti
>
> When we call
> {code}
> logger.info("Entries from Cache: {}", cache.entrySet());
> {code}
> Displays:
> bq. Entries from Cache: [org.infinispan.cache.impl.EncoderCache$EntryWrapper@5580d62f]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9481) Implement toString in EncoderCache.EntryWrapper
by Katia Aresti (JIRA)
[ https://issues.jboss.org/browse/ISPN-9481?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9481:
-------------------------------
Description:
When we call
{code}
logger.info("Entries from Cache: {}", cache.entrySet());
{code}
bq. Displays: Entries from Cache: [org.infinispan.cache.impl.EncoderCache$EntryWrapper@5580d62f]
was:
When we call
{{
logger.info("Entries from Cache: {}", cache.entrySet());
}}
We get : Entries from Cache: [org.infinispan.cache.impl.EncoderCache$EntryWrapper@5580d62f]
> Implement toString in EncoderCache.EntryWrapper
> -----------------------------------------------
>
> Key: ISPN-9481
> URL: https://issues.jboss.org/browse/ISPN-9481
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Katia Aresti
> Assignee: Katia Aresti
>
> When we call
> {code}
> logger.info("Entries from Cache: {}", cache.entrySet());
> {code}
> bq. Displays: Entries from Cache: [org.infinispan.cache.impl.EncoderCache$EntryWrapper@5580d62f]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9481) Implement toString in EncoderCache.EntryWrapper
by Katia Aresti (JIRA)
Katia Aresti created ISPN-9481:
----------------------------------
Summary: Implement toString in EncoderCache.EntryWrapper
Key: ISPN-9481
URL: https://issues.jboss.org/browse/ISPN-9481
Project: Infinispan
Issue Type: Enhancement
Reporter: Katia Aresti
Assignee: Katia Aresti
When we call
{{
logger.info("Entries from Cache: {}", cache.entrySet());
}}
We get : Entries from Cache: [org.infinispan.cache.impl.EncoderCache$EntryWrapper@5580d62f]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9480) misleading client side WARN message
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/ISPN-9480?page=com.atlassian.jira.plugin.... ]
Wolf-Dieter Fink updated ISPN-9480:
-----------------------------------
Security: (was: Red Hat Internal)
> misleading client side WARN message
> -----------------------------------
>
> Key: ISPN-9480
> URL: https://issues.jboss.org/browse/ISPN-9480
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Reporter: Wolf-Dieter Fink
> Assignee: Adrian Nistor
>
> The client will log warn messages for @Indexed annotations
> WARN o.i.p.impl.AnnotatedDescriptorImpl : Encountered and ignored and unknown annotation "Indexed" on <some proto field>
> At client side there is no knowledge about indexing annotations. This is normal.
> The warning should not issued.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9366) Cache.size optimizations
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9366?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9366:
----------------------------------
Sprint: Sprint 9.4.0.CR1, Sprint 9.4.0.Final (was: Sprint 9.4.0.CR1)
> Cache.size optimizations
> ------------------------
>
> Key: ISPN-9366
> URL: https://issues.jboss.org/browse/ISPN-9366
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.4.0.Final
>
>
> Now that we have a segmented data container and segmented store we can add optimizations for the Cache.size operation in various configurations.
> If a store is configured, passivation must be disabled for any of these optimizations related to stores to work
> # Shared store can just invoke Store.size
> # No store & no expired entries can invoke DataContainer.sizeIncludingExpired(IntSet)
> # Non shared store can invoke Store.size(IntSet)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9127) Remote commands can access components before they are started
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9127?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9127:
----------------------------------
Sprint: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.Final (was: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1)
> Remote commands can access components before they are started
> -------------------------------------------------------------
>
> Key: ISPN-9127
> URL: https://issues.jboss.org/browse/ISPN-9127
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.2.2.Final, 9.3.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
>
> {{PerCacheInboundInvocationHandler.handle()}} may be called before the component was started, because {{GlobalInboundInvocationHandler}} fetches it from the component registry without any checks. {{CommandsFactoryImpl.initializeReplicableCommand()}} doesn't wait for the components that it injects into remote commands to be started, either.
> This started causing random test failures in {{ConcurrentStartForkChannelTest}} after ISPN-8515, which moved most initialization work from {{init()}} methods to {{start()}} methods. Because {{StateProviderImpl}} starts after {{StateTransferManagerImpl}}, it's possible for a node to receive a {{StateRequestCommand}} before {{StateProviderImpl}} has initialized:
> {noformat}
> 16:15:09,549 TRACE (remote-thread-Test-NodeB-p51957-t2:[org.infinispan.CONFIG]) [StateProviderImpl] Starting outbound transfer to node Test-NodeA for cache null, topology id 2, segments {0-255}
> 16:15:09,551 WARN (remote-thread-Test-NodeB-p51957-t2:[]) [NonTotalOrderPerCacheInboundInvocationHandler] ISPN000071: Caught exception when handling command StateRequestCommand{cache=org.infinispan.CONFIG, origin=Test-NodeA, type=START_STATE_TRANSFER, topologyId=2, segments={0-255}}
> java.lang.IllegalArgumentException: chunkSize must be greater than 0
> at org.infinispan.statetransfer.OutboundTransferTask.<init>(OutboundTransferTask.java:114) ~[classes/:?]
> at org.infinispan.statetransfer.StateProviderImpl.startOutboundTransfer(StateProviderImpl.java:273) ~[classes/:?]
> at org.infinispan.statetransfer.StateRequestCommand.invokeAsync(StateRequestCommand.java:101) ~[classes/:?]
> at org.infinispan.remoting.inboundhandler.BasePerCacheInboundInvocationHandler.invokeCommand(BasePerCacheInboundInvocationHandler.java:94) ~[classes/:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months