Actually Sebastian, I don't think this is your problem because your site configs are ASYNC.

This only appears when a site is configured with SYNC, which is when a response is waited for.

Cheers,

On Mon, Apr 30, 2018 at 5:18 PM Galder Zamarreno <galder@redhat.com> wrote:
Ups, sent too early! So, the NYC site is not up, so I see in the logs:

2018-04-30 16:53:49,411 ERROR [org.infinispan.test.fwk.TEST_RELAY2] (testng-ProtobufMetadataXSiteStateTransferTest[DIST_SYNC, tx=false]:[]) 
ProtobufMetadataXSiteStateTransferTest[DIST_SYNC, tx=false]-NodeA-55452: no route to NYC: dropping message

But the put hangs and never completes [2]. I've traced the code and [3] never gets called, with no events.

I think this might be a JGroups bug because ChannelCallbacks implements UpHandler, but JChannel never deals with a receiver that might implement UpHandler, so it never delivers site unreachable message up the stack.

@Bela?

Cheers,
Galder




On Mon, Apr 30, 2018 at 5:09 PM Galder Zamarreno <galder@redhat.com> wrote:
Hi Sebastian,

Did you mention something about x-site not working on master?

The reason I ask is cos I was trying to create a state transfer test for [1] and there are some odds happening.

In my test, I start LON site configured with NYC but NYC is not up yet.

_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev