Winsock application issue: NEED HELP!!!
Actually, I understood excatly what you're talking about.
So the wrapped up MTS/COM portion of the code is behaving badly. Either
there's an object that isn't marshalling correctly or not cleaning up
properly and this is what needs to be fixed.
Well, two things come to mind. Your doing XML and the older version of
it --2.6 -- is having an issue marshalling across boundrys. Install 3.0 and
reference it.
You're using Oracle 8I and when you close a connection and ODBC calls
cleanup and the Oracle driver isn't responde. Again, a known issue. Try
downloading their patch.
Beyond these to intuative leaps, I'm dead in the water.
HTH
Quote:
> The error that is occuring is an unhandled error, before
> we create an error trap for that specific error we really
> would like to figure out what the error is?
> Also the error is not occuring in the data arrival event
> of the winsock application. It is occuring in the MTS
> component's business logic, and since the MTS component
> does not know how to handle the error it returns to the
> error to the winsock application as a run-time error.
> Clear as mud, right....
> >-----Original Message-----
> >Chris:
> >Get rid of the message box. It will behave as though its
> blocking the
> >socket. In effect, it hangs the buffer. Flag the error
> inside the data
> >arrival, but make the messagebox show after you're out of
> the data arrival
> >routine.
> >HTH
> >> I am a MCSD working on contract with a team of
> >> analyst/programmers at a
> >> midwestern life insurance company. We are experiencing
> a
> >> production
> >> problem that we are unable to resolve.
> >> Our environment is an N-Tier architecture, with a data-
> >> entry client application
> >> that is used all over the country. The client
> application
> >> uses HTTP and the
> >> MS Winsock control to get the data back to the central
> SQL
> >> Server. The application was built using VB 6.0
> >> We are using a Winsock server application that
> interfaces
> >> to MTS for the data layer. Essentially, the
> configuration
> >> is as follows:
> >> Client ---> Winsock ---> MTS ---> SQL Server 2000.
> >> All of theses components are on separate Windows 2000
> >> Server machines, with the exception of the client's
> >> machine.
> >> The problem occurs on the Winsock application. It is an
> >> error that is returned from the MTS component (Run-Time
> >> error 3021: BOF or EOF has occurred). We understand the
> >> nature of this error and its causes. The error, which
> is
> >> not occurring in a consistent manner causes the Winsock
> >> application to hang until a user clicks through the
> error
> >> message and then restarts the server app.
> >> We have determined to some extent where in the code the
> >> problem is happening, but no pattern has yet been
> >> established. We also noted that the client that causes
> >> the Winsock app to fail, could turn right around and
> send
> >> the same data with no problems what so ever.
> >> This error has been occurring on average of once per
> week
> >> over the lifetime of the application, which is roughly
> 18
> >> months. Recently we needed to upgrade our firewall
> >> software to Symantec's Raptor 7.0. Previously, we used
> >> version 6.0. This upgrade caused the error to occur
> >> almost every half-hour. In addition, the previous
> >> firewall (6.0) software was on a NT 4.0 environment. We
> >> installed Symantec's 7.0 version on a Windows 2000
> Server.
> >> Unfortunately, we are unable to duplicate the problem
> in a
> >> testing environment,
> >> and we cannot replicate the amount of load that is
> coming
> >> in from our clients
> >> over the internet, as we have limited resources to
> create
> >> such a load.
> >> If anyone has any insight to this particular scenario,
> >> your help would be greatly appreciated.
> >> Chris
> >.
