[JBoss JIRA] (WFLY-5529) Clustering Quickstarts Tracker
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-5529?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-5529:
---------------------------------
Description:
Tracker for clustering quickstarts.
There are bunch of areas that could use a quickstart, see linked issues. Bunch of areas that might be interesting as well with no concrete plans:
* Cross-site replication
* JGroups channel injection (community-only)
* Infinispan cache injection (community-only)
was:
Tracker for clustering quickstarts.
There are bunch of areas that could use a quickstart, see linked issues. Bunch of areas that might be interesting as well with no concrete plans:
* Cross-site replication
* remote-cache/remote-cache-container (HotRod client injection)
* JGroups channel injection (community-only)
* Infinispan cache injection (community-only)
> Clustering Quickstarts Tracker
> ------------------------------
>
> Key: WFLY-5529
> URL: https://issues.jboss.org/browse/WFLY-5529
> Project: WildFly
> Issue Type: Task
> Components: Clustering, mod_cluster, Quickstarts
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: Awaiting Volunteers
>
>
> Tracker for clustering quickstarts.
> There are bunch of areas that could use a quickstart, see linked issues. Bunch of areas that might be interesting as well with no concrete plans:
> * Cross-site replication
> * JGroups channel injection (community-only)
> * Infinispan cache injection (community-only)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11612) Not possible to configure more than 1 passivation-store per deployment
by Daniel Čihák (Jira)
[ https://issues.jboss.org/browse/WFLY-11612?page=com.atlassian.jira.plugin... ]
Daniel Čihák commented on WFLY-11612:
-------------------------------------
PR with the automated test: [#12143|https://github.com/wildfly/wildfly/pull/12143].
> Not possible to configure more than 1 passivation-store per deployment
> ----------------------------------------------------------------------
>
> Key: WFLY-11612
> URL: https://issues.jboss.org/browse/WFLY-11612
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 15.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
> Fix For: 16.0.0.Beta1, 16.0.0.Final
>
>
> In EAP 7.1 and 7.2 per subdeployment, in the EAR, only one passivation store can be used.
> If within one EAR-subdeployment caches "infinispanCache" and "infinispanCache2" per config below are used (referenced via @Cache annotation or <ec:cache-ref> deplyoment desriptor), it results in the error listed below:
> <caches>
> <cache name="simple"/>
> <cache name="infinispanCache" passivation-store-ref="infinispanStore" aliases="passivating"/>
> <cache name="infinispanCache2" passivation-store-ref="infinispanStore2" aliases="longLife"/>
> </caches>
> <passivation-stores>
> <passivation-store name="infinispanStore" cache-container="ejb" bean-cache="passivation" max-size="5"/>
> <passivation-store name="infinispanStore2" cache-container="ejb" bean-cache="passivation" max-size="10"/>
> </passivation-stores>
> using both caches from 1 EAR-subdeployment leads to:
> 2019-01-10 12:14:10,757 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."frameworktest.ear"."framework_ejb.jar".cache-dependencies-installer: org.jboss.msc.service.StartException in service jboss.deployment.subunit."frameworktest.ear"."framework_ejb.jar".cache-dependencies-installer: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
> [...]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache-configuration.ejb.frameworktest.ear/framework_ejb.jar is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:111)
> It should be possible to configure more than 1 passivation-store per subdeployment, in particular when different time-outs are configured this way.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-8549) Create Externalizers, @Immutable and general session replication/failover quickstart
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-8549?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8549:
---------------------------------
Priority: Critical (was: Major)
> Create Externalizers, @Immutable and general session replication/failover quickstart
> ------------------------------------------------------------------------------------
>
> Key: WFLY-8549
> URL: https://issues.jboss.org/browse/WFLY-8549
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Quickstarts
> Affects Versions: 11.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: Awaiting Volunteers
>
>
> Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
> To demonstrate externalizers, we can demonstrate with non-serializable objects
> For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover – set attribute must be used.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-8549) Create Externalizers, @Immutable and general session replication/failover quickstart
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-8549?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8549:
---------------------------------
Description:
Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
To demonstrate externalizers, we can demonstrate with non-serializable objects
For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover – set attribute must be used.
was:
Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
To demonstrate externalizers, we can demonstrate non-serializable objects
For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover – set attribute must be used.
> Create Externalizers, @Immutable and general session replication/failover quickstart
> ------------------------------------------------------------------------------------
>
> Key: WFLY-8549
> URL: https://issues.jboss.org/browse/WFLY-8549
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Quickstarts
> Affects Versions: 11.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: Awaiting Volunteers
>
>
> Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
> To demonstrate externalizers, we can demonstrate with non-serializable objects
> For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover – set attribute must be used.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-8549) Create Externalizers, @Immutable and general session replication/failover quickstart
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-8549?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8549:
---------------------------------
Description:
Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
To demonstrate externalizers, we can demonstrate non-serializable objects
For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover – set attribute must be used.
was:
Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
To demonstrate externalizers, we can demonstrate non-serializable objects
For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover.
> Create Externalizers, @Immutable and general session replication/failover quickstart
> ------------------------------------------------------------------------------------
>
> Key: WFLY-8549
> URL: https://issues.jboss.org/browse/WFLY-8549
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Quickstarts
> Affects Versions: 11.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: Awaiting Volunteers
>
>
> Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
> To demonstrate externalizers, we can demonstrate non-serializable objects
> For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover – set attribute must be used.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-8549) Create Externalizers, @Immutable and general session replication/failover quickstart
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-8549?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8549:
---------------------------------
Description:
Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
To demonstrate externalizers, we can demonstrate non-serializable objects
For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover.
was:Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
> Create Externalizers, @Immutable and general session replication/failover quickstart
> ------------------------------------------------------------------------------------
>
> Key: WFLY-8549
> URL: https://issues.jboss.org/browse/WFLY-8549
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Quickstarts
> Affects Versions: 11.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: Awaiting Volunteers
>
>
> Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication.
> To demonstrate externalizers, we can demonstrate non-serializable objects
> For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months