TCP connection/state behavior should not vary depending on your physical connection type (802.3 vs 802.11). Plus I don't think a different driver should matter. A given connection should go into TIME_WAIT and CLOSE immediately following a JDBC connection close(). Are you using a connection pool, or is your data source configured as SIMPLE? Do you see a single connection in ESTABLISHED state (to remote port 1521), or multiple connections. If you're killing the client application and you still see the TCP state as ESTABLISHED, then this is indeed a strange problem. If you're on Windows and you want to find out what thread or application owns a given TCP connection you should check out some of the tools from sysinternals ( http://www.sysinternals.com/).
Specifically:
TCPView
http://www.sysinternals.com/Utilities/TcpView.html
and
Process Explorer
http://www.sysinternals.com/Utilities/ProcessExplorer.html
On 4/28/06, Brent Ryan <[EMAIL PROTECTED]> wrote:
When I'm plugged into the network I don't have this problem. I only
have this problem when I'm on wireless. I don't think this is a iBatis
issue either. I think it has something to do with the oracle driver
because I've run into something similar with straight JDBC calls before.
I thought I read a while back that there was a different JDBC oracle
driver you should use instead of the THIN driver if using wireless...
But maybe I'm just blowing smoke too.. Who knows?
Brent
--------------------
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf
Of Larry Meadors
Sent: Friday, April 28, 2006 9:15 AM
To: [email protected]
Subject: Re: Oracle DB using a wireless connection causes connection
leaks
I did a search for "if(isWireless()) leakConnection();" and didn't find
anythingso if you unplug your toaster, and put the dog out - I bet it
fixes it. ;-)
Just kidding..I do not see any way that this could be iBATIS related -
it is even hard to imagine that a bad jdbc driver would do that. Are you
absolutely positive that it happens when plugged in, too?
Larry
On 4/28/06, Brent Ryan <[EMAIL PROTECTED]> wrote:
>
> I had a project I was developing on using iBatis and Oracle where I
> ran into this issue. The only reason I was using wireless was because
> I was on my laptop and I noticed that when you called
> dao.endTransaction() that my connection stayed in the ESTABLISHED
> state even after killing the program completely.
>
> Has anyone else had these issues with wirelss? And is there a way to
> avoid this? Like a different JDBC oracle driver...
>
> Thanks,
> Brent
>
>
>
> This e-mail is intended only for the personal and confidential use of
> the
> recipient(s) named above.
> It may include Blackboard confidential and proprietary information,
> and is not for redistribution.
>
