[JBoss JIRA] (ISPN-11974) Remove GenericJbossMarshaller automatic configuration
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-11974:
-----------------------------------
Summary: Remove GenericJbossMarshaller automatic configuration
Key: ISPN-11974
URL: https://issues.redhat.com/browse/ISPN-11974
Project: Infinispan
Issue Type: Task
Components: Configuration, Hot Rod
Affects Versions: 11.0.0.CR1
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 12.0.0.Final
Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan 12 we should no automatically configure this marshaller if the module is present.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11945) JGroups Kubernetes stack should set `port_range="0"`
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11945?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11945:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> JGroups Kubernetes stack should set `port_range="0"`
> ----------------------------------------------------
>
> Key: ISPN-11945
> URL: https://issues.redhat.com/browse/ISPN-11945
> Project: Infinispan
> Issue Type: Enhancement
> Components: Cloud, Configuration
> Affects Versions: 11.0.0.CR1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> Currently the provided jgroups kubernetes stack does not set {{port_range="0"}}. This doesn't make sense in Kubernetes deployments as ports are tightly controlled, so we want the sockets to always just use the configured {{bind_port}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months