Ales recently ran into the same issue. The quickfix for now is to add FORK to the WF configuration for the cache you'll use. Apparently, adding FORK dynamically doesn't currently work.
Paul is looking into this specific issue.
Could you please attach the code which deploys the app and modifies the channel. It seems that the problem might be with the stack processing that is done when presenting the channel run-time metrics (channel=*).
I'll try to reproduce locally and have a look at it.
OK - I see the problem. WF8 uses a custom management resource that interrogates the installed channel services to allow management of channels. Consequently, it expects that the protocol stack of the running service match that of the protocol stack as defined in the domain model. This all stems from the fact that, in WF8, the jgroups subsystem only defines protocol stacks, while the infinispan subsystem is responsible for creating the actual channels.
In WF9, I plan to have all manageable channels explicitly enumerated in the jgroups subsystem - which will not only allow you to share channels across infinispan cache containers, but will also make this custom resource obsolete.