| Dart Home | PowerTCP Sockets for .NET | Custom Development | Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
| Author | Forum: PowerTCP Sockets for .NET (Secure and Standard) Topic: Ping component: Excessive duration for receiving the response from ping |
| allueraq From: Barcelona, Spain Posts: 8 Member Since: 07/10/07 |
posted April 7, 2010 9:30 AM Hello, I am wearing the component Sockets For .Net 1.1.1.0 with VS2008 and framework 3,5. We make ping asynchronously in our application software to approximately 6000 pings every 5 minutes. We used the methods for it Begin Send and End Send. Normally we took long between 30 and 60 seconds in finishing each session ( 6000 pings ). The case is than, once in a while, that session takes long more than 5 minutes, even days!! This does not happen always, which is why it is difficult to reproduce it, but it has happened 4 times in the last 3 days!! I did not succeed with the previous version that we had, 1,0,4, this, but we needed the 1.1.1.0 for the precision of the field ResponseTime. Therefore, we believe that it is due to an internal malfunction of the component. It seems like some thread is left waiting for a long time. I hope that they can help us problem to solve this because the fact that we bought the new version of the component and we make your good functioning necessarily does not make much. Best regards, Raquel HP Enterprise Services -- Hola, Estoy usando el componente Sockets For .Net 1.1.1.0 con VS2008 y framework 3.5. En nuestra aplicación hacemos ping asíncronamente a aproximadamente 6000 pings cada 5 minutos. Para ello usamos los métodos "Begin Send" y "End Send". Normalmente tardamos entre 30 y 60 segundos en terminar cada sesión (6000 pings). El caso es que, de vez en cuando, esa sesión tarda más de 5 minutos, incluso días!! esto no pasa siempre, por lo que es difícil reproducirlo, pero en los últimos 3 días ha sucedido 4 veces!! Con la anterior versión que teníamos, la 1.0.4, esto no sucedía, pero necesitamos la 1.1.1.0 para la precisión del campo "ResponseTime". Por tanto, creemos que ello se debe a un mal funcionamiento interno del componente. Parece que algun thread se quede en espera por largo tiempo. Espero que puedan ayudarnos a solucionar éste problema pues hace poco que compramos la nueva versión del componente y creemos necesario su buen funcionamiento. Atentamente, Raquel HP Enterprise Services |
| Jamie Powell (Admin) From: Rome, NY USA Posts: 448 Member Since: 03/13/07 Extra Support Options Custom Application Development |
posted April 8, 2010 10:58 AM Thank you for your post. Please send a small self contained zipped sample to support@dart.com demonstrating the issue. This sample should replicate what you're doing with our control. Thank you. ------ |
| allueraq From: Barcelona, Spain Posts: 8 Member Since: 07/10/07 |
posted April 13, 2010 7:29 AM Hi Jamie, As I said in the previous message, this does not always happen. So it is very difficult to reproduce this bug. The test involves running an application 6000 ping ip address every 5 minutes and control the duration until the error happens. As I explained, the development environment is: Windows7 x64 + VS2008 +. NET Framework 3.5 + Sockets For. NET 1.1.1.0. We are developing a test application to try to capture that bug to show it. Do you have performed tests of this type to the component? Otherwise, you could test your component too. This occurred shortly after buying the new version 1.1.1.0 (February 2010) and 1 month subscription has ended. However, we believe that if the new version has problems multi-thread (and the previous version 1.0.4.0 works well), we should give support and solve this bug. I wait for your response. Best regards, Raquel HP Enterprise Services |
| Jamie Powell (Admin) From: Rome, NY USA Posts: 448 Member Since: 03/13/07 Extra Support Options Custom Application Development |
posted April 14, 2010 4:24 PM Unfortunately we cannot continue to troubleshoot without duplication information. We have performed tests, but are not seeing this issue. Please send in the sample when you are finished. Thank you. ------ |
| allueraq From: Barcelona, Spain Posts: 8 Member Since: 07/10/07 |
posted April 23, 2010 4:42 AM Hello Jamie, I've responded to support@dart.com. Best Regards, Raquel HP Enterprise Services |
| Jamie Powell (Admin) From: Rome, NY USA Posts: 448 Member Since: 03/13/07 Extra Support Options Custom Application Development |
posted April 23, 2010 3:21 PM Thank you. You email has been received and will be reviewed. I will update you as the status changes. |
| allueraq From: Barcelona, Spain Posts: 8 Member Since: 07/10/07 |
posted May 26, 2010 9:45 AM Un mes más tarde la incidencia sigue abierta. La gente de Dart Support aún no ha podido dar con la solución. ¿Alguien más tiene problemas de este tipo con la nueva versión 1.1.1.0 del componente Sockets For .NET? más concretamente con el componente de pings. Necesitamos solucionarlo pronto por lo que sería de ayuda encontrar más usuarios afectados por este problema. Gracias. ----------------------------------------------------- A month later, the incidence is still open. Dart People Support has not been able to find the solution. Does anyone else have such problems with the new version 1.1.1.0 Component Sockets For. NET? more specifically with the component of pings. We need to fix it soon so it would help find more users affected by this problem. Thank you. |
| Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|