[
https://issues.jboss.org/browse/ISPN-4171?page=com.atlassian.jira.plugin....
]
Paul Ferraro updated ISPN-4171:
-------------------------------
Description:
Currently, Infinispan assumes full ownership of a provided channel. It registers the up
handler of the CommandAwareDispatcherFactory with the channel. If there is already a
registered up handler, it gets overwritten.
Currently, WildFly shares Infinispan's channel for use by other services - however, it
needs to bend over backwards to make sure infinispan is initialized before attempting to
fork/mux it.
If an Infinispan cache manager is built with a channel that is used by some other service,
it should instead fork that channel using ForkChannel. This let's us do something
like, say, let WF and Infinispan share a channel without requiring infinispan to start
first, or to use the same channel for multiple cache managers.
was:
Currently, Infinispan assumes full ownership of a provided channel. It registers the up
handler of the CommandAwareDispatcherFactory with the channel. If there is already a
registered up handler, it gets overwritten.
Currently, WildFly shares Infinispan's channel for use by other services - however, it
needs to bend over backwards to make sure infinispan is initialized before attempting to
fork/mux it.
If an Infinispan cache manager is built with a channel that is used by some other service,
it should instead fork that channel using ForkChannel. This let's us do something
like, say, let WF and Infinispan share a channel without requiring infinispan to start
first, or use the same channel for multiple cache managers.
Allow Infinispan to properly use a foreign channel
--------------------------------------------------
Key: ISPN-4171
URL:
https://issues.jboss.org/browse/ISPN-4171
Project: Infinispan
Issue Type: Feature Request
Components: Core
Affects Versions: 7.0.0.Alpha2
Reporter: Paul Ferraro
Assignee: Dan Berindei
Currently, Infinispan assumes full ownership of a provided channel. It registers the up
handler of the CommandAwareDispatcherFactory with the channel. If there is already a
registered up handler, it gets overwritten.
Currently, WildFly shares Infinispan's channel for use by other services - however,
it needs to bend over backwards to make sure infinispan is initialized before attempting
to fork/mux it.
If an Infinispan cache manager is built with a channel that is used by some other
service, it should instead fork that channel using ForkChannel. This let's us do
something like, say, let WF and Infinispan share a channel without requiring infinispan to
start first, or to use the same channel for multiple cache managers.
--
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