[infinispan-issues] [JBoss JIRA] (ISPN-3582) Server does not expose MBean for registering server-side serialization context
Martin Gencur (JIRA)
jira-events at lists.jboss.org
Thu Oct 3 12:51:02 EDT 2013
[ https://issues.jboss.org/browse/ISPN-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Gencur updated ISPN-3582:
--------------------------------
Description:
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.
was:
There should be the following MBean available when starting ISPN server: jboss.infinispan:type=RemoteQuery,name="{cacheManagerName}",component=ProtobufMetadataManager
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.
> 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: Critical
> 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
More information about the infinispan-issues
mailing list