[infinispan-issues] [JBoss JIRA] Commented: (ISPN-833) Revisit cache name predefinition limitation for cache servers

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-833:
---------------------------------------

If for whatever reason this does not make it into 5.0.0, consider RemoteCacheManager.getCache() returning null rather than throwing an exception for 5.x branch.

> Revisit cache name predefinition limitation for cache servers
> -------------------------------------------------------------
>
>                 Key: ISPN-833
>                 URL: https://issues.jboss.org/browse/ISPN-833
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Cache Server
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 5.0.0.BETA1, 5.0.0.Final
>
>
> There're are two primary reasons why Infinispan servers require predefined caches to be started up on startup, and do not allow invocations to undefined caches:
> 1. Concurrent cache startups were resulting in NPEs (ISPN-635) - This is already solved since the 4.2.x days. 
> 2. Infinispan has issues dealing with asymmetric clusters (ISPN-658).
> Once these two issues have been resolved, revisit the limitation. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira