[JBoss JIRA] (ISPN-3582) Server does not expose MBean for registering server-side serialization context
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/ISPN-3582?page=com.atlassian.jira.plugin.... ]
Martin Gencur commented on ISPN-3582:
-------------------------------------
It is running now that Will sorted out the dependencies in modules. It was not running before that. You can see the updated branch with Will's fixes and updated test here: https://github.com/mgencur/infinispan-server/commits/ISPN-3582/remote_que...
> Server does not expose MBean for registering server-side serialization context
> ------------------------------------------------------------------------------
>
> Key: ISPN-3582
> URL: https://issues.jboss.org/browse/ISPN-3582
> Project: Infinispan
> Issue Type: Bug
> Components: Querying, Server
> Affects Versions: 6.0.0.Beta2
> Reporter: Martin Gencur
> Assignee: Tristan Tarrant
> Priority: Blocker
> Labels: jdg62blocker
> Fix For: 6.0.0.CR1
>
>
> There should be the following MBean available when starting ISPN server:
> {code}
> jboss.infinispan:type=RemoteQuery,name="{cacheManagerName}",component=ProtobufMetadataManager
> {code}
> However, this MBean is not exposed and so the server-side serialization context cannot be configured.
> More information about the MBean and its usage can be found in HotRodQueryTest . In infinispan itself (non-server) the JMX domain would be different but in the server it should be jboss.infinispan
> I'll attach a test for server-side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (ISPN-3582) Server does not expose MBean for registering server-side serialization context
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-3582?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-3582:
-------------------------------------
[~mgencur] Is the cache manager in question running? Its component registry has to be started before the query related and protobuf metadata mbeans are visible. To ensure it is started just get a cache from it.
> Server does not expose MBean for registering server-side serialization context
> ------------------------------------------------------------------------------
>
> Key: ISPN-3582
> URL: https://issues.jboss.org/browse/ISPN-3582
> Project: Infinispan
> Issue Type: Bug
> Components: Querying, Server
> Affects Versions: 6.0.0.Beta2
> Reporter: Martin Gencur
> Assignee: Tristan Tarrant
> Priority: Blocker
> Labels: jdg62blocker
> Fix For: 6.0.0.CR1
>
>
> There should be the following MBean available when starting ISPN server:
> {code}
> jboss.infinispan:type=RemoteQuery,name="{cacheManagerName}",component=ProtobufMetadataManager
> {code}
> However, this MBean is not exposed and so the server-side serialization context cannot be configured.
> More information about the MBean and its usage can be found in HotRodQueryTest . In infinispan itself (non-server) the JMX domain would be different but in the server it should be jboss.infinispan
> I'll attach a test for server-side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (ISPN-3557) Key set not empty after transactional CACHE_MODE_LOCAL flagged clear
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3557?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-3557:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Key set not empty after transactional CACHE_MODE_LOCAL flagged clear
> ---------------------------------------------------------------------
>
> Key: ISPN-3557
> URL: https://issues.jboss.org/browse/ISPN-3557
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 5.3.0.Final, 6.0.0.Beta1
> Reporter: Galder Zamarreño
> Assignee: William Burns
> Priority: Blocker
> Fix For: 6.0.0.CR1, 6.0.0.Final
>
>
> The following test fails (added to AbstractLocalTest):
> {code}
> public void testKeySetAfterClear() throws Exception {
> cache.put(1, "v1");
> tm().begin();
> try {
> cache.getAdvancedCache().withFlags(Flag.CACHE_MODE_LOCAL).clear();
> assertTrue(cache.keySet().isEmpty());
> } finally {
> tm().commit();
> }
> }
> {code}
> If the flag is removed, it works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (ISPN-3401) The default map/reduce cache configuration should have state transfer enabled
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3401?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-3401:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Fixed with ISPN-3221
> The default map/reduce cache configuration should have state transfer enabled
> -----------------------------------------------------------------------------
>
> Key: ISPN-3401
> URL: https://issues.jboss.org/browse/ISPN-3401
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Execution and Map/Reduce
> Affects Versions: 6.0.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 6.0.0.CR1
>
>
> Map/Reduce uses a CreateCacheCommand to create an intermediate cache for the mapper/combiner results. The default configuration for the intermediate cache has fetchInMemoryState disabled, which is probably not a good idea.
> CreateCacheCommand also seems too tightly linked to M/R, it contains both the default intermediate cache configuration and a mechanism to check that the cache has started that adds random keys to the cache (and so it can't be re-purposed for creating regular caches).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (ISPN-3401) The default map/reduce cache configuration should have state transfer enabled
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3401?page=com.atlassian.jira.plugin.... ]
Dan Berindei reassigned ISPN-3401:
----------------------------------
Assignee: Dan Berindei (was: Mircea Markus)
> The default map/reduce cache configuration should have state transfer enabled
> -----------------------------------------------------------------------------
>
> Key: ISPN-3401
> URL: https://issues.jboss.org/browse/ISPN-3401
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Execution and Map/Reduce
> Affects Versions: 6.0.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 6.0.0.CR1
>
>
> Map/Reduce uses a CreateCacheCommand to create an intermediate cache for the mapper/combiner results. The default configuration for the intermediate cache has fetchInMemoryState disabled, which is probably not a good idea.
> CreateCacheCommand also seems too tightly linked to M/R, it contains both the default intermediate cache configuration and a mechanism to check that the cache has started that adds random keys to the cache (and so it can't be re-purposed for creating regular caches).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months