[JBoss JIRA] (ISPN-11469) Upgrade Tutorials - default cache
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11469?page=com.atlassian.jira.plugi... ]
Katia Aresti resolved ISPN-11469.
---------------------------------
Resolution: Done
> Upgrade Tutorials - default cache
> ---------------------------------
>
> Key: ISPN-11469
> URL: https://issues.redhat.com/browse/ISPN-11469
> Project: Infinispan
> Issue Type: Task
> Components: Demos and Tutorials
> Affects Versions: 10.1.4.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Critical
> Labels: tutorials
>
> The tutorials using getCache() method.
> Embedded tutorials need the default cache name to be configured in the global configuration and we won't want to do this anymore
> The new server has not a default cache, so all the tutorials are broken
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (ISPN-11574) Automatic server authentication configuration
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11574?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11574:
-------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Automatic server authentication configuration
> ---------------------------------------------
>
> Key: ISPN-11574
> URL: https://issues.redhat.com/browse/ISPN-11574
> Project: Infinispan
> Issue Type: Enhancement
> Components: Security, Server
> Affects Versions: 11.0.0.Dev03
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> if the <endpoint> is configured with a security realm, authentication should be enabled automatically based on the security realm stores.
> Default mechs for Hot Rod:
> * SCRAM-SHA-512 SCRAM-SHA-384 SCRAM-SHA-256 SCRAM-SHA-1 DIGEST-SHA-512 DIGEST-SHA-384 DIGEST-SHA-256 DIGEST-SHA DIGEST-MD5
> Default mechs for HTTP:
> * DIGEST
> *PLAIN/BASIC will only be enabled if TLS is also enabled
> * EXTERNAL/CLIENT_CERT will only be enabled if TLS is enabled and require-ssl-client-auth="true"
> * GSSAPI/GS2-KRB5/SPNEGO will only be enabled if a kerberos realm is present
> * OAUTHBEARER/BEARER_TOKEN will only be enabled if a token realm is present
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (ISPN-10428) Docs: Configuring paths for single file cache stores
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-10428?page=com.atlassian.jira.plugi... ]
Ryan Emerson resolved ISPN-10428.
---------------------------------
Resolution: Done
> Docs: Configuring paths for single file cache stores
> ----------------------------------------------------
>
> Key: ISPN-10428
> URL: https://issues.redhat.com/browse/ISPN-10428
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Environment: XSD
> jboss-infinispan-core*.xsd
> infinispan-config*.xsd
> Reporter: Wolf-Dieter Fink
> Assignee: Donald Naro
> Priority: Minor
> Fix For: 9.4.19.Final
>
>
> Embedded and server mode are using a different configuration for file-store
> embedded : infinispan-config*
> {code}
> </xs:attribute>
> <xs:attribute name="relative-to" type="xs:string">
> <xs:annotation><xs:documentation>Unused XML attribute</xs:documentation></xs:annotation>
> </xs:attribute>
> <xs:attribute name="path" type="xs:string">
> <xs:annotation>
> <xs:documentation>
> The path within "relative-to" in which to store the cache state.
> If undefined, the path defaults to the cache container name.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> </xs:extension>
> </xs:complexContent>
> </xs:complexType>
> {code}
> Here the relative-to is not used but referenced for path.
> But path is used relative to PWD if it is not an absolute one, also if defaults to 'Infinispan-SingleFileStore' if not set.
> For the server configuration it is
> {code}
> <xs:attribute name="relative-to" type="xs:string" default="jboss.server.data.dir">
> <xs:annotation>
> <xs:documentation>The base directory in which to store the cache state.</xs:documentation>
> </xs:annotation>
> </xs:attribute>
> <xs:attribute name="path" type="xs:string">
> <xs:annotation>
> <xs:documentation>
> The path within "relative-to" in which to store the cache state.
> If undefined, the path defaults to the cache container name.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> {code}
> But relative-to is a reference to a path declaration like this
> {code}
> <paths>
> <path name="my.dir" path="/MyCacheStore"/>
> </paths>
> ...
> <distributed-cache name="wolf">
> <persistence>
> <file-store shared="false" fetch-state="true" relative-to="my.dir"/>
> </persistence>
> </distributed-cache>
> {code}
> If relative-to is set to a real path or env variable the server start will fail with
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.wolf.config: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.wolf.config: Failed to start service
> ...
> Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/MyCacheStore'
> at org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:110)
> at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:765)
> at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:760)
> at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:58)
> at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1517)
> at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1503)
> at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:55)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1699)
> ... 6 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (ISPN-11673) RemoteStore should allow ClientIntellegience configuration
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11673?page=com.atlassian.jira.plugi... ]
Ryan Emerson closed ISPN-11673.
-------------------------------
Resolution: Won't Do
Closing as it's possible to configure additional hotrod properties using the store `<property/>` element like so:
{code:xml}
<persistence>
<remote-store xmlns="urn:infinispan:config:store:remote:10.1" shared="true" segmented="false" cache="example">
<remote-server host="<some-host>" port="11222" />
<property name="infinispan.client.hotrod.client_intelligence">BASIC</property>
</remote-store>
</persistence>
{code}
> RemoteStore should allow ClientIntellegience configuration
> ----------------------------------------------------------
>
> Key: ISPN-11673
> URL: https://issues.redhat.com/browse/ISPN-11673
> Project: Infinispan
> Issue Type: Feature Request
> Components: Hot Rod, Loaders and Stores
> Affects Versions: 11.0.0.Dev04, 10.1.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.1.7.Final, 11.0.0.Dev05
>
>
> In Kubernetes environments, it's not always possible to utilise the default intelligence HASH_DISTRIBUTION_AWARE, therefore it should be possible to configure this.
> Similarly, long term it would probably be more maintainable to allow the remote-store to utilise a `hotrod-client.properties` file.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (ISPN-11674) Clean up RemoteCache method overrides
by Will Burns (Jira)
Will Burns created ISPN-11674:
---------------------------------
Summary: Clean up RemoteCache method overrides
Key: ISPN-11674
URL: https://issues.redhat.com/browse/ISPN-11674
Project: Infinispan
Issue Type: Enhancement
Components: Hot Rod
Reporter: Will Burns
Fix For: 11.0.0.Dev05
There are a lot of various method overrides in the RemoteCache. This is because of async, versions and expiration overrides bloating almost all methods by eight times. We should consolidate these so they are simpler to handle and harder to mess up.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months