[JBoss JIRA] (ISPN-9811) Implement single response publisher methods
by William Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-9811?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9811:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6533
> Implement single response publisher methods
> -------------------------------------------
>
> Key: ISPN-9811
> URL: https://issues.jboss.org/browse/ISPN-9811
> Project: Infinispan
> Issue Type: Sub-task
> Components: Publisher
> Reporter: William Burns
> Assignee: William Burns
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We need to implement the backend for a method like
> {code}
> <R> CompletionStage<R> compose(Function<? super Publisher<T>, ? extends CompletionStage<R>> transformer,
> Function<? super Publisher<R>, ? extends CompletionStage<R>> finalizer);
> {code}
> This would allow for all methods that don't require streaming results to be done very easily.
> For example a count method can then just be implemented by doing:
> {code}
> java.util.function.Function<Publisher<?>, CompletionStage<Long>> transformer = cp ->
> Flowable.fromPublisher(cp)
> .count()
> .to(RxJavaInterop.singleToCompletionStage());
> java.util.function.Function<Publisher<Long>, CompletionStage<Long>> finalizer = results ->
> Flowable.fromPublisher(results)
> .reduce((long) 0, Long::sum)
> .to(RxJavaInterop.singleToCompletionStage());
> return infinispanPublisher.compose(transformer, finalizer);
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9819) Improve Spring-Session events handling in remote and embedded
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-9819?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9819:
-------------------------------
Description:
Embedded listeners should be clustered, otherwise only entry owners will be notified
Remote listeners should use the eager converter to retrieve the value on client side
> Improve Spring-Session events handling in remote and embedded
> -------------------------------------------------------------
>
> Key: ISPN-9819
> URL: https://issues.jboss.org/browse/ISPN-9819
> Project: Infinispan
> Issue Type: Bug
> Components: Spring Integration
> Affects Versions: 10.0.0.Alpha2, 9.4.4.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.5.Final
>
>
> Embedded listeners should be clustered, otherwise only entry owners will be notified
> Remote listeners should use the eager converter to retrieve the value on client side
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9810) RemoteApplicationPublishedBridgeTest.testEventBridge random failures
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9810?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9810:
-------------------------------
Summary: RemoteApplicationPublishedBridgeTest.testEventBridge random failures (was: InfinispanApplicationPublishedBridgeTCK.testEventBridge random failures)
> RemoteApplicationPublishedBridgeTest.testEventBridge random failures
> --------------------------------------------------------------------
>
> Key: ISPN-9810
> URL: https://issues.jboss.org/browse/ISPN-9810
> Project: Infinispan
> Issue Type: Task
> Components: Spring Integration
> Affects Versions: 10.0.0.Alpha2, 9.4.4.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.5.Final
>
>
> InfinispanApplicationPublishedBridgeTCK.testEventBridge
> Fails in remote randomly.
> {noformat}
> java.lang.AssertionError: Expected 2 events of a class SessionCreatedEvent but found 1
> at org.infinispan.spring.common.session.util.EventsWaiter.assertNumberOfEvents(EventsWaiter.java:28)
> at org.infinispan.spring.common.session.InfinispanApplicationPublishedBridgeTCK.testEventBridge(InfinispanApplicationPublishedBridgeTCK.java:59)
> at org.infinispan.spring.remote.session.RemoteApplicationPublishedBridgeTest.testEventBridge(RemoteApplicationPublishedBridgeTest.java:78)
> {noformat}
> This failure is related to the fact that spring session API's have changed. Now to send an event to spring context we need to send the session object instead of the ID.
> In the case of this test, we safe two sessions and remove 1.
> After a while, we will verify if 2 creation events and 1 deletion event has been fired.
> If the creation and removal happens faster than the listener getting notified and retrieving the session object to send the notification to spring, the creation event won't be fired ( (remote get will be null in this case), so we will have 1 event instead of two.
> The test must be changed to meet this case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9810) InfinispanApplicationPublishedBridgeTCK.testEventBridge random failures
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9810?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9810:
-------------------------------
Summary: InfinispanApplicationPublishedBridgeTCK.testEventBridge random failures (was: Fix testEventBridge test)
> InfinispanApplicationPublishedBridgeTCK.testEventBridge random failures
> -----------------------------------------------------------------------
>
> Key: ISPN-9810
> URL: https://issues.jboss.org/browse/ISPN-9810
> Project: Infinispan
> Issue Type: Task
> Components: Spring Integration
> Affects Versions: 10.0.0.Alpha2, 9.4.4.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.5.Final
>
>
> InfinispanApplicationPublishedBridgeTCK.testEventBridge
> Fails in remote randomly.
> This failure is related to the fact that spring session API's have changed. Now to send an event to spring context we need to send the session object instead of the ID.
> In the case of this test, we safe two sessions and remove 1.
> After a while, we will verify if 2 creation events and 1 deletion event has been fired.
> If the creation and removal happens faster than the listener getting notified and retrieving the session object to send the notification to spring, the creation event won't be fired ( (remote get will be null in this case), so we will have 1 event instead of two.
> The test must be changed to meet this case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9810) InfinispanApplicationPublishedBridgeTCK.testEventBridge random failures
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9810?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9810:
-------------------------------
Description:
InfinispanApplicationPublishedBridgeTCK.testEventBridge
Fails in remote randomly.
{noformat}
java.lang.AssertionError: Expected 2 events of a class SessionCreatedEvent but found 1
at org.infinispan.spring.common.session.util.EventsWaiter.assertNumberOfEvents(EventsWaiter.java:28)
at org.infinispan.spring.common.session.InfinispanApplicationPublishedBridgeTCK.testEventBridge(InfinispanApplicationPublishedBridgeTCK.java:59)
at org.infinispan.spring.remote.session.RemoteApplicationPublishedBridgeTest.testEventBridge(RemoteApplicationPublishedBridgeTest.java:78)
{noformat}
This failure is related to the fact that spring session API's have changed. Now to send an event to spring context we need to send the session object instead of the ID.
In the case of this test, we safe two sessions and remove 1.
After a while, we will verify if 2 creation events and 1 deletion event has been fired.
If the creation and removal happens faster than the listener getting notified and retrieving the session object to send the notification to spring, the creation event won't be fired ( (remote get will be null in this case), so we will have 1 event instead of two.
The test must be changed to meet this case.
was:
InfinispanApplicationPublishedBridgeTCK.testEventBridge
Fails in remote randomly.
This failure is related to the fact that spring session API's have changed. Now to send an event to spring context we need to send the session object instead of the ID.
In the case of this test, we safe two sessions and remove 1.
After a while, we will verify if 2 creation events and 1 deletion event has been fired.
If the creation and removal happens faster than the listener getting notified and retrieving the session object to send the notification to spring, the creation event won't be fired ( (remote get will be null in this case), so we will have 1 event instead of two.
The test must be changed to meet this case.
> InfinispanApplicationPublishedBridgeTCK.testEventBridge random failures
> -----------------------------------------------------------------------
>
> Key: ISPN-9810
> URL: https://issues.jboss.org/browse/ISPN-9810
> Project: Infinispan
> Issue Type: Task
> Components: Spring Integration
> Affects Versions: 10.0.0.Alpha2, 9.4.4.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.5.Final
>
>
> InfinispanApplicationPublishedBridgeTCK.testEventBridge
> Fails in remote randomly.
> {noformat}
> java.lang.AssertionError: Expected 2 events of a class SessionCreatedEvent but found 1
> at org.infinispan.spring.common.session.util.EventsWaiter.assertNumberOfEvents(EventsWaiter.java:28)
> at org.infinispan.spring.common.session.InfinispanApplicationPublishedBridgeTCK.testEventBridge(InfinispanApplicationPublishedBridgeTCK.java:59)
> at org.infinispan.spring.remote.session.RemoteApplicationPublishedBridgeTest.testEventBridge(RemoteApplicationPublishedBridgeTest.java:78)
> {noformat}
> This failure is related to the fact that spring session API's have changed. Now to send an event to spring context we need to send the session object instead of the ID.
> In the case of this test, we safe two sessions and remove 1.
> After a while, we will verify if 2 creation events and 1 deletion event has been fired.
> If the creation and removal happens faster than the listener getting notified and retrieving the session object to send the notification to spring, the creation event won't be fired ( (remote get will be null in this case), so we will have 1 event instead of two.
> The test must be changed to meet this case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months