Stephan van Hulst wrote:Can you show us the requests and responses that the network analyzer displays when you send those requests?
Stephan van Hulst wrote:I think what you wrote should work.
How do you know that it doesn't? How are you sending the request? What error message are you getting?
Dave Tolls wrote:The fix options can be got using Alt-Return (at least on mine).
Yes, clicking on the red line on the right-side gutter just takes you to the error.
Jaikiran Pai wrote:It's a natural and common thing with connections. They don't stay alive forever. The DB server terminates the connection that it has leased out after a period of inactivity.
Datasource pools which pool open connections allow configuring a "idle timeout" on connections. The idle timeout setting allows the pool to release back connections from the pool, back to the DB server, when a certain connection hasn't been in use for the specified period of time (i.e. idle timeout). That way, the pool doesn't end up holding on to a terminated/stale connection and subsequently handing it out to the caller applications. You just need to specify an idle timeout on your pool configuration. If you are using the admin console to configure that datasource, I think you'll see the setting there (or else there are other ways to go about configuring this).
Jaikiran Pai wrote:Glad to know that you got it working.
It's interesting that you had to specify the username and password as part of the connection URL (and it indeed is what the documentation states here http://technet.microsoft.com/en-us/library/ms378526%28v=sql.110%29.aspx). To me, that defeats the purpose of having a (masked) password textbox/field on the UI, for this specific driver of course.
Jaikiran Pai wrote:Is there anything that you see in the server.log of the server, if you have access to it?
Jaikiran Pai wrote:How are you issuing that management operation? From some code? What does it look like? Or are you using the CLI to issue it? If so, how are you connecting to the CLI? Either way, the quickest way to test a connection in pool is to use the admin console to issue that request and let it manage what management operation needs to be invoked behind the scenes.