Databases
StackOverflow2013
Postsdbo
POc# exception not caught
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POc# exception not caught
    primarykey
    data
    text
    <p>I have a method that is a listener for a TCP client which looks like this:</p> <pre><code> private static void ProcessClient( Object obj) { ISession session = (ISession)obj; NetworkStream networkStream = null; try { DebugUtility.SetThreadName("Worker: {0}", session.Name); networkStream = session.TcpClient.GetStream(); networkStream.ReadTimeout = Config.ReadTimeout; // Loop received packets (blocks untill next packet) Int32 packetSize; Byte[] buffer = new Byte[session.PacketSize]; while ((packetSize = networkStream.Read(buffer, 0, buffer.Length)) != 0) { // Get String from packet bytes String packet = Encoding.UTF8.GetString(buffer, 0, packetSize); // Check if packet has data if (String.IsNullOrEmpty(packet)) continue; // Log biggest received package DebugUtility.CheckMaxPacketSize(session.Name, packet.Length); // Handle packet (in new thread) Logger.DebugLog("Received: {0}", packet); ThreadPool.QueueUserWorkItem(session.HandlePacket, packet); } } catch (ObjectDisposedException) { } catch (NotSupportedException) { } catch (TimeoutException) { } catch (SocketException) { } catch (IOException) { } catch (Exception ex) { Logger.LogException(ex); } finally { if (networkStream != null) networkStream.Close(); if (session != null) session.Disconnect(); } } </code></pre> <p>This is for a game service but when I check my logs, I occasionally see this error:</p> <pre><code>System.Int32 Read(Byte[], Int32, Int32): The stream does not support reading. at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at BusinessLayer.Listener.ListenerWorker.ProcessClient(Object obj) in C:\path\ListenerWorker.cs:line 141 Line: 0 </code></pre> <p>That is the above described file and line 141 is </p> <pre><code> while ((packetSize = networkStream.Read(buffer,.... </code></pre> <p>Now I have found that NotSupportedException is throwing this error, but why does it go through? Why is it not ignored but does it fall through the normal Exception ex handler?</p> <p>Edit: Does anyone know how I can invoke this exception? When does it occur? I only see it coming back in my logs to other users, but I don't know when it happens.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USYesMan85
    1. USYesMan85
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POc# exception not caught
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POc# exception not caught
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POc# exception not caught
      1. This table or related slice is empty.
      1. VTUpMod
    1. COFirst thing I would fix in this code is to stop swallowing a big chunk of your exceptions. Since you have a logger system, why are you actively swallowing the most relevant exceptions without any trace at all?
      singulars
      1. POc# exception not caught
      1. USØyvind Bråthen
    2. COCan't agree more! Why on earth are you doing this to all your lovely exceptions - they're there to help you!
      singulars
      1. POc# exception not caught
      1. USm.edmondson
 

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