.net sybase 执行非查询异常
我正在使用 Sybase.Data.ASEClient 命名空间从我的 asp.net 应用程序连接到 Sybase DB。在最近发布的应用程序生产版本中，我们在 DatabaseHelper 类中包含了一段代码，该代码仅尝试执行 ExecuteNonQuery()。在生产环境中，command.ExecuteNonQuery() 行抛出异常，显示
“尝试读取或写入受保护的内存。这通常表明其他内存已损坏。”
但这并不持续发生。该应用程序工作正常 4 天，在第五天，我们突然为用户收到此错误，然后在尝试使用涉及数据库访问的功能时，没有其他人能够使用该应用程序。
我还用谷歌搜索并了解到 Sybase.Data.ASEClient 有一些内存泄漏问题。但没有关于它是否已修复的信息。
有人能解释一下吗？您在之前的项目中是否遇到过此类问题？有没有办法通过某种方式解决这个问题？
I am connecting to Sybase DB from my asp.net application using Sybase.Data.ASEClient namespace. With the recent production release of the App, we included a code in the DatabaseHelper class which just tries to do an ExecuteNonQuery(). In production the line that says command.ExecuteNonQuery(), was throwing an exception that says
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
But this does not happen consistently. The application works fine for 4 days and in the fifth day we are suddenly getting this error for a user and then no one else was able to use the application when trying to use the functionality that involved database access.
I also googled and came to know that Sybase.Data.ASEClient has some memory leak issues. But no information on whether it got fixed or not.
Can anyone throw some light on this? have you experienced such issues in your previous projects? And is there a way to figure out the problem by any means?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这听起来确实像是 Sybase 驱动程序中的一个错误。
我会尝试从 Sybase 和/或更新版本的驱动程序获得支持。 Google 对 Sybase 支持的帮助并不大，因为我相信您需要注册才能在 Sybase 网站上访问此类信息。
至于内存泄漏，我记得在过去（2006 年）Sybase 驱动程序 1.1.465.0 存在内存泄漏 - 这在 1.1.516.0 中已修复。这些是 Sybase 12 的驱动程序，从那时起事情当然已经发生了很大的变化。
It certainly sounds like a bug in the Sybase driver.
I would try to get support from Sybase and/or a more recent version of the driver. Google isn't as helpful as it could be for Sybase support, as I believe you need to be registered to access this kind of info on the Sybase website.
As for memory leaks, I remember that in the past (2006) the Sybase driver 1.1.465.0 had memory leaks - this was fixed in 1.1.516.0. These were drivers for Sybase 12 and things have of course evolved a long way since then.