[infinispan-issues] [JBoss JIRA] (ISPN-3582) Server does not expose MBean for registering server-side serialization context

[Martin Gencur (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809369#comment-12809369 ] 

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_query_mbean
                
> 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