> I have an simple app that pulls UDP socket packets off a network,
> places
> that packet data in a structure, and places the structure into a
> vb.net
> Queue (use enqueue. and dequeue).  Writes queue to SQL server
> In the form I have  global decl.
> PUBLIC DataQueue as NEW QUEUE
> PUBLIC STRUCTURE myDataStruct (add some elements)
> In my ONRECEIVEI place the buffer data into myDataStruct and
> DataQueue.Enqueue(myDataStruct).
>
> I also have a 100ms timer that does this:
> dim tmpStruct as NEW myDataStruct
> tmpStruct = DataQueue.Dequeue()
> write tmpStruct to SQL
> I've got a bool flag in the timer routine to keep it from running
> again
> until it finishes everthing
> Is there any kind of conflict that can occur here?
> If  OnReceive fires and enqueues while timer is dequeueing?
> Some sort of deadlock???
> I debug.writeline when enqueueing to assure what goes in the queue,
> but
> sometimes when I dequeue the data it has a value from another packet
> (scrambled), though the enqueue showed fine. Happens rarely but does
> happen.
> I don't quite understand how the OS executes the code, reading and
> writing
> at what 'I guess' is the same time to that queue sometimes.
> Is the scenerio above OK to use or is there a better solution (more
> stable)
> than what I am doing?
> Thanks
> BUC

"Buc" wrote:

> I have an simple app that pulls UDP socket packets off a network, places
> that packet data in a structure, and places the structure into a vb.net
> Queue (use enqueue. and dequeue).  Writes queue to SQL server
> In the form I have  global decl.
>  PUBLIC DataQueue as NEW QUEUE
>  PUBLIC STRUCTURE myDataStruct (add some elements)
>
> In my ONRECEIVEI place the buffer data into myDataStruct and
> DataQueue.Enqueue(myDataStruct).
>
> I also have a 100ms timer that does this:
> dim tmpStruct as NEW myDataStruct
> tmpStruct = DataQueue.Dequeue()
> write tmpStruct to SQL
> I've got a bool flag in the timer routine to keep it from running again
> until it finishes everthing
>
> Is there any kind of conflict that can occur here?
> If  OnReceive fires and enqueues while timer is dequeueing?
> Some sort of deadlock???
> I debug.writeline when enqueueing to assure what goes in the queue, but
> sometimes when I dequeue the data it has a value from another packet
> (scrambled), though the enqueue showed fine. Happens rarely but does happen.
> I don't quite understand how the OS executes the code, reading and writing
> at what 'I guess' is the same time to that queue sometimes.
> Is the scenerio above OK to use or is there a better solution (more stable)
> than what I am doing?
> Thanks
> BUC
> 
>
>
>

<Buc> wrote in message news:%23WWM30KwGHA.4384@TK2MSFTNGP04.phx.gbl...
>I have an simple app that pulls UDP socket packets off a network, places
>that packet data in a structure, and places the structure into a vb.net
>Queue (use enqueue. and dequeue).  Writes queue to SQL server
> In the form I have  global decl.
> PUBLIC DataQueue as NEW QUEUE
> PUBLIC STRUCTURE myDataStruct (add some elements)
>
> In my ONRECEIVEI place the buffer data into myDataStruct and
> DataQueue.Enqueue(myDataStruct).
>
> I also have a 100ms timer that does this:
> dim tmpStruct as NEW myDataStruct
> tmpStruct = DataQueue.Dequeue()
> write tmpStruct to SQL
> I've got a bool flag in the timer routine to keep it from running again
> until it finishes everthing
>
> Is there any kind of conflict that can occur here?
> If  OnReceive fires and enqueues while timer is dequeueing?
> Some sort of deadlock???
> I debug.writeline when enqueueing to assure what goes in the queue, but
> sometimes when I dequeue the data it has a value from another packet
> (scrambled), though the enqueue showed fine. Happens rarely but does
> happen.
> I don't quite understand how the OS executes the code, reading and writing
> at what 'I guess' is the same time to that queue sometimes.
> Is the scenerio above OK to use or is there a better solution (more
> stable) than what I am doing?
> Thanks
> BUC
>
>
>