Our website is using the sybase database and we use the ASE ado.net
provider
to connect to the sybase DB. Sometime the website hang and we finally
found
that one thread is locked on the method of open connection for sybase
DB.
The windbg clr call stack shows that the thread is waiting on the
Sybase.Data.AseClient.Unmanaged.OpenConnection() method which call
the
sybdrvado11.dll ( which is a unmanaged dll ) to open the connection.
Does anyone know why this issue happen? Or any tool could help me to
check
what is going on and which is the thread waiting for?
Wei Lu
sybdrvado11.dll - version here, on what windows env, 2000 or 32 bit
Is this windows box and ASE box in same data center?
Show tracert, in the end, could be an ASE bug, who knows?
Which version of ASE ADO.NET Provider?
-Paul
"Wei Lu" <huofo...@gmail.com> wrote in message
news:ce0fa19e-656a-48c7...@q30g2000prq.googlegroups.com...
And the .net application and ASE database are not in the same box.
The network is connected without any error.
On Mar 7, 2:18 am, "Paul Vero [Sybase]" <pv...@nospam.com> wrote:
> Hi Wie,
>
> Which version of ASE ADO.NET Provider?
>
> -Paul
>
> "WeiLu" <huofolu...@gmail.com> wrote in message
> >WeiLu- Hide quoted text -
>
> - Show quoted text -
Could you try the latest version of the provider, SDK 12.5.1 ESD#25?
This doesn't sound like correct behavior at all. Where do you store
the DLLs?
-Paul
"Wei Lu" <huofo...@gmail.com> wrote in message
news:d140224d-5b4d-40c7...@z6g2000pre.googlegroups.com...
1c9fe830 7c9585ec [NDirectMethodFrameSlim: 1c9fe830]
Sybase.Data.AseClient.Unmanaged.OpenConnection(IntPtr, System.String
[], System.String[], Int32)
1c9fe848 1cb16f85 Sybase.Data.AseClient.AseConnectionImpl.Open()
1c9fe88c 1cb16124 Sybase.Data.AseClient.AseConnectionPool.GetConnection
(Sybase.Data.AseClient.AseConnection)
1c9fe8c4 1cb1564f Sybase.Data.AseClient.AseConnection.Open()
1c9fe8fc 1dd71717 WebSite.Common.DB.getConnection()
The thread is locked which makes other threads could not get the
openconnection.
On Mar 11, 4:00 am, "Paul Vero [Sybase]" <pv...@nospam.com> wrote:
> Hi
>
> Could you try the latest version of the provider, SDK 12.5.1 ESD#25?
> This doesn't sound like correct behavior at all. Where do you store
> the DLLs?
>
> -Paul
>
> "Wei Lu" <huofolu...@gmail.com> wrote in message
> >> - Show quoted text -- Hide quoted text -
Build 457 must be included in an ASE PC Client, probably released around May
2005.
If the Provider DLL and the un-managed DLL (Provider is
Sybase.Data.AseClient.dll,
and the un-managed is sybdrvado11.dll) are both together, versions must be
the same -
I'm certain they are since you're not getting TypeInitializer Exception.
However, it sounds to me
the pooling is unstable for some reason - are you able to get the SDK
(Software Developers Kit)
12.5.1 ESD#25? This is the latest version of the provider. Install on that
machine and copy
both DLLs to your application folder to see if the hanging goes away. I've
not heard of any
such problems now.
What application and API? What versions? And what operating system?
Thank you,
-Paul
"Wei Lu" <huofo...@gmail.com> wrote in message
news:2ccf61d4-f7ba-4edd...@v18g2000pro.googlegroups.com...