Creating 2 streams with one socket

it helps some times You might want to read The ultimate SO_LINGER page, or: why is my tcp not reliable, which I think applies to your situation.
Edit:

wish help you to fix your issue See CipherOutputStream.flush():

Cipher cipher = Cipher.getInstance("AES/CTR/PKCS5Padding");

it helps some times
If any IO streams or reader/writers is created from socket's input or output stream, is it necessary to close them before or after socket is closed?

like below fixes the issue I think streamqueue is what you're looking for:

var streamqueue = require('streamqueue');

gulp.task('dist', function() {
  return streamqueue({ objectMode: true },
    gulp.src(['**/[^_]*.js', '!**/_*/**'], { cwd: 'js' }),
    gulp.src(['**/[^_]*.html', '!**/_*/**'], { cwd: 'views' })
      .pipe(compile_views())
  )
  .pipe(concat('output.js'))
  .pipe(gulp.dest('dist'));
});

it should still fix some issue You can either use a library like Boost.Asio or the C function poll() (or select() which does basically the same thing) to wait on multiple sockets at once. Either way, you want to "multiplex" the sockets, meaning you block until any of them has data available, then you read from that one. This is how many network applications are built, and is usually more efficient, more scalable, and less error-prone than having a thread or process for each connection.