[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)
3 years, 11 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)
3 years, 11 months
[JBoss JIRA] (ISPN-11972) Property expansion in CLI batch
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-11972:
--------------------------------------
Summary: Property expansion in CLI batch
Key: ISPN-11972
URL: https://issues.redhat.com/browse/ISPN-11972
Project: Infinispan
Issue Type: Enhancement
Components: CLI
Affects Versions: 11.0.0.CR1
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
We should support system property expansion in CLI batch files so that they can be easily parameterized
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (ISPN-11948) server/tests HotRod clients should utilise the ProtoStreamMarshaller
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11948?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-11948:
--------------------------------
Description: The {{server-runtime}} modules has a dependency on {{infinispan-jboss-marshalling}} in order for the server to provide transcoding and jbmar on the server-side. However, the {{infinispan-server-testdriver-core}} does not exclude this dependency, resulting in all client tests automatically configuring the {{GenericJBossMarshaller}} . The default for tests should be the {{ProtoStreamMarshaller}}, however it should also be possible to configure other marshallers if required. (was: The {{server-runtime}} modules has a dependency on {{infinispan-jboss-marshalling}} in order for the server to provide transcoding and jbmar on the server-side. However, the {{infinispan-server-testdriver-core}} does not exclude this dependency, resulting in all client tests automatically configuring the {{GenericJBossMarshaller}} .)
> server/tests HotRod clients should utilise the ProtoStreamMarshaller
> --------------------------------------------------------------------
>
> Key: ISPN-11948
> URL: https://issues.redhat.com/browse/ISPN-11948
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 11.0.0.CR1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> The {{server-runtime}} modules has a dependency on {{infinispan-jboss-marshalling}} in order for the server to provide transcoding and jbmar on the server-side. However, the {{infinispan-server-testdriver-core}} does not exclude this dependency, resulting in all client tests automatically configuring the {{GenericJBossMarshaller}} . The default for tests should be the {{ProtoStreamMarshaller}}, however it should also be possible to configure other marshallers if required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months