Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>If a message is bad, write error message (6 bytes), flush it, close the socket and do not read any unread messages in the socket. Otherwise continue reading messages.</p> </blockquote> <p>That will cause a connection reset, which will be seen by the client as a broken pipe in Unix, Linux etc.</p> <blockquote> <p>After writing N good messages, write one bad message and continue writing M good messages.</p> </blockquote> <p>That will encounter the broken pipe error just mentioned.</p> <blockquote> <p>This process happens in a separate thread.</p> </blockquote> <p>Why? The whole point of NIO and therefore Netty is that you don't need extra threads.</p> <blockquote> <p>I've found that server is closing connection after writing the error message.</p> </blockquote> <p>Well that's what you said it does, so it does it.</p> <blockquote> <p>Client began seeing broken pipe errors when writing good messages after the bad message.</p> </blockquote> <p>As I said.</p> <blockquote> <p>This is because server detected bad message and responded with error message and closed socket.</p> </blockquote> <p>Correct.</p> <blockquote> <p>Client is not reading error message from server always.</p> </blockquote> <p>Due to the connection reset. The delivery of pending data ceases after a reset.</p> <blockquote> <p>Does netty trigger channel read if the write fails due to broken pipe?</p> </blockquote> <p>No, it triggers read when data or EOS arrives</p> <p>However your bizarre system design/protocol is making that unpredictable if not impossible. You're writing a bad message that will cause a reset, followed by good messages that you already know won't get through, and trying to read a response that may have been thrown away. It doesn't make any sense to me whatsoever. What are you trying to prove here?</p> <p>Try a request-response protocol like everybody else.</p>
    singulars
    1. This table or related slice is empty.
    1. PONetty failing to read bytes from server when write fails due to socket close by server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USuser207421
    1. USuser207421
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COUnfortunately its not my design to change. I'm trying to implement a client and mock apple push notification service. See updated details in the question. In real world, client doesn't know if its a bad message or not.
      singulars
      1. PO
      1. USSrikanth
    2. COcopying specific phrases from APNS docs - "If you send a notification that is malformed or otherwise unintelligible, APNs returns an error-response packet and closes the connection. Any notifications that you sent after the malformed notification using the same connection are discarded, and must be resent."
      singulars
      1. PO
      1. USSrikanth
    3. COThat means you have to close the connection on any error or EOS, reconnect, and resume sending from the message after the failed one; which also implies an internal message queue. It also implies that you should wait for a response for a short period after sending each message to see if there is a failure response, before sending the next message. Otherwise there is a genuine risk of losing outbound messages completely. I personally wouldn't use NIO (and therefore Netty) for this, I would use blocking I/O with a read timeout. I don't really believe in NIO in clients.
      singulars
      1. PO
      1. USuser207421
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload