W3C home > Mailing lists > Public > public-interledger@w3.org > November 2016

Re: Doubt about Websocket / Rest Messages sequence in ILP transaction

From: Evan Schwartz <evan@ripple.com>
Date: Tue, 15 Nov 2016 18:23:54 +0100
Message-ID: <CAONA2jXiHnMqvMfi0JdonYUUG11q-GxzQi35NdeJndNjJo4J4g@mail.gmail.com>
To: Enrique Arizon Benito <enrique.arizon.benito@everis.com>
Cc: Interledger Community Group <public-interledger@w3.org>
Hi Enrique,

Try running the ILP module script and the connector with DEBUG=*.

The things I would look for in the ILP module log output would be some
error message when the client tries to submit the fulfillment or an error
in the connector logs saying something about why it might not be forwarding
the payment.

The general message sequence is:

   1. Sending client submits transfer to sending ledger
   2. Sending ledger sends notifications of transfer being prepared to
   sender and connector
   3. Connector submits transfer to destination ledger
   4. Destination ledger sends notifications to connector and receiver
   5. Receiver submits fulfillment to destination ledger
   6. Destination ledger sends notifications to receiver and connector
   (with the fulfillment attached)
   7. Connector submits fulfillment to sending ledger
   8. Sending ledger executes transfer and sends notifications to connector
   and sender

Let me know if that helps. We can definitely talk about this on the CG call
tomorrow if you have more questions.


On Tue, Nov 15, 2016 at 4:16 PM, Enrique Arizon Benito <
enrique.arizon.benito@everis.com> wrote:

> I created a test lab demo with 2 five-bells-ledgers, a java ledger and the
> ilp-connector. Now I try to tests transaction between the different ledgers
> using the Combined-Example at https://github.com/interledgerjs/ilp. It
> works fine using 2 five-bells-ledger (as expected). When I try to make a
> trans. from java ledger to five-bells-ledgers it fails with a timeout
> (transaction expired). I can see the ws messages sending the notification
> about a new prepared transaction.
> For some reason that I ignore the fulfillment is never "triggered", due (I
> suppose) to a missing web socket message or PUT request, but even using
> tcpdump to compare the network traces I can NOT find the problem.
>  The real problem is that I'm not 100% sure about the expected message
> sequence between the "wallet" (ilp Combined-Example), the ledger/s and the
> ILP so I'm not sure how/where to start debugging the problem.
>  Is there any documentation detailing this sequence of Websocket / Rest
> messages for a full transaction?
> Regards,
> Enrique Arizon Benito
> Software Architect,
> Tel: +34 976 482 080, ext 117064
> http://www.everis.com
> ________________________________
> Este correo y la información contenida o adjunta al mismo es privada y
> confidencial y va dirigida exclusivamente a su destinatario. everis informa
> a quien pueda haber recibido este correo por error que contiene información
> confidencial cuyo uso, copia, reproducción o distribución está expresamente
> prohibida. Si no es Vd. el destinatario del mismo y recibe este correo por
> error, le rogamos lo ponga en conocimiento del emisor y proceda a su
> eliminación sin copiarlo, imprimirlo o utilizarlo de ningún modo.
> This message and the information contained in or attached to it are
> private and confidential and intended exclusively for the addressee. everis
> informs to whom it may receive it in error that it contains privileged
> information and its use, copy, reproduction or distribution is prohibited.
> If you are not an intended recipient of this E-mail, please notify the
> sender, delete it and do not read, act upon, print, disclose, copy, retain
> or redistribute any portion of this E-mail.

Evan Schwartz
Software Engineer
Managing Director of Ripple Luxembourg
Received on Tuesday, 15 November 2016 17:24:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 15 November 2016 17:24:48 UTC