Envelope-to: omar@ssf.com.mx
Delivery-date: Fri, 18 Sep 2015 19:45:33 -0500
Date: Fri, 18 Sep 2015 19:45:32 -0500
From: Rogelio Delgado <issuessicom@gmail.com>
Reply-To: noreply@108.161.137.201
To: omar@ssf.com.mx
Message-ID: <55fcb02c4425f_96263fbb8a46a6c453062@develop.mail>
References: <merge_request_17@108.161.137.201>
Subject: G4S | Eliminar cliente (#15)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_55fcb02c42770_96263fbb8a46a6c452921";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
 
 Content preview:  New comment for Merge Request 15 http://108.161.137.201:9000/Rogelio/g4s/merge_requests/15#note_20
    Rogelio Delgado [...] 
 
 Content analysis details:   (-0.8 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -0.7 RCVD_IN_DNSWL_LOW      RBL: Sender listed at http://www.dnswl.org/, low
                             trust
                             [209.85.213.180 listed in list.dnswl.org]
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                             (issuessicom[at]gmail.com)
 -0.0 SPF_PASS               SPF: sender matches SPF record
  0.0 WEIRD_PORT             URI: Uses non-standard port number for HTTP
  0.0 NORMAL_HTTP_TO_IP      URI: URI host has a public dotted-decimal IPv4
                             address
  0.0 HTML_MESSAGE           BODY: HTML included in message
 -0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
                             domain
  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
 -0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
  0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                             See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [URIs: 108.161.137.201]
 -0.0 RCVD_IN_MSPIKE_H3      RBL: Good reputation (+3)
                             [209.85.213.180 listed in wl.mailspike.net]
 -0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders
X-Spam-Flag: NO


----==_mimepart_55fcb02c42770_96263fbb8a46a6c452921
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

New comment for Merge Request 15

http://108.161.137.201:9000/Rogelio/g4s/merge_requests/15#note_20


Rogelio Delgado

Esta linea es sumamente peligrosa, podemos caer en una inconsistencia ent=
re bases de datos por que est=C3=A1s enviando mensajes al broker
antes de que se termine de realizar operaciones en la base de datos (se e=
st=C3=A1 enviando comandos al broker dentro del for). Como lo platicamos
si por alguna raz=C3=B3n en la iteraci=C3=B3n, digamos, 3 ocurre un probl=
ema (NullPointerException o algo) la transacci=C3=B3n har=C3=A1 rollback =
y dejar=C3=A1 los
datos en la base de datos sin modificar, pero los mensajes de la iteraci=C3=
=B3n 1 y 2 ya se enviaron y ya afectaron bases de datos de los brokers.

La forma "correcta" es hacer una lista de listas de comandos y al final d=
e todo, incluso del for, enviarla a la cola. =


----==_mimepart_55fcb02c42770_96263fbb8a46a6c452921
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html lang=3D'en'>
<head>
<meta content=3D'text/html; charset=3Dutf-8' http-equiv=3D'Content-Type'>=

<title>
GitLab
</title>
</meta>
</head>
<style>
  p.details {
    font-style:italic;
    color:#777
  }
  .footer p {
    font-size:small;
    color:#777
  }
</style>
<body>
<div class=3D'content'>
<p class=3D'details'>
New comment on diff for
<a href=3D"http://108.161.137.201:9000/Rogelio/g4s/merge_requests/15#note=
_20">SCGasPAR/CatalogsServicesImpl/src/main/java/mx/ssf/sicom/catalogsSer=
vices/apiImpl/CustomerReceptionUnitServiceImpl.java</a>
:
</p>
<div>
<p>Esta linea es sumamente peligrosa, podemos caer en una inconsistencia =
entre bases de datos por que est=C3=A1s enviando mensajes al broker
antes de que se termine de realizar operaciones en la base de datos (se e=
st=C3=A1 enviando comandos al broker dentro del for). Como lo platicamos
si por alguna raz=C3=B3n en la iteraci=C3=B3n, digamos, 3 ocurre un probl=
ema (NullPointerException o algo) la transacci=C3=B3n har=C3=A1 rollback =
y dejar=C3=A1 los
datos en la base de datos sin modificar, pero los mensajes de la iteraci=C3=
=B3n 1 y 2 ya se enviaron y ya afectaron bases de datos de los brokers.</=
p>

<p>La forma &quot;correcta&quot; es hacer una lista de listas de comandos=
 y al final de todo, incluso del for, enviarla a la cola. </p>

</div>


</div>
<div class=3D'footer' style=3D'margin-top: 10px;'>
<p>
=E2=80=94
<br>
You're receiving this notification because you are a member of the Rogeli=
o Delgado / G4S project team.
<a href=3D"http://108.161.137.201:9000/Rogelio/g4s/merge_requests/15#note=
_20">View it on GitLab</a>
</p>
</div>
</body>
</html>

----==_mimepart_55fcb02c42770_96263fbb8a46a6c452921--