Hi,

We have few WebLogic instances running on Solaris 10 servers (around
10 of them) for a few years now. All of a sudden we are receiving
numerous sessions in IDLE state and all of these are coming from the
WebLogic java processes. With numerous I mean thousands - they grow to
around 15,000 and then roll back to zero and then start climbing
again. Now, nothing has changed either in WebLogic or Solaris or the
code. I performed a Solaris snoop but could not find anything. Since
the connections are in IDLE state, the source/destinations show up as
"*.*" so I cannot really tell what is causing it. I requested the
network gurus to take a look at it, but they could not find anything
either !

Any suggestions ?

-Kevin.

In article 
<a862d40d-f139-48ab-9291-bc2ae917018c@q24g2000prf.googlegroups.com>,
 Kevin <kejoseph@hotmail.com> wrote:

> Hi,
> 
> We have few WebLogic instances running on Solaris 10 servers (around
> 10 of them) for a few years now. All of a sudden we are receiving
> numerous sessions in IDLE state and all of these are coming from the
> WebLogic java processes. With numerous I mean thousands - they grow to
> around 15,000 and then roll back to zero and then start climbing
> again. Now, nothing has changed either in WebLogic or Solaris or the
> code. I performed a Solaris snoop but could not find anything. Since
> the connections are in IDLE state, the source/destinations show up as
> "*.*" so I cannot really tell what is causing it. I requested the
> network gurus to take a look at it, but they could not find anything
> either !
> 
> Any suggestions ?
> 
> -Kevin.

When did this start?  Or more precisely, what was the last thing that 
changed on the machine before you observed this new behavior?  It may be 
a Java patch or perhaps someone changed something (and didn't tell you) 
in the java enviroment that keeps open sessions around.

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...
[I filter all Goggle Groups posts, so any reply may be automatically by ignored]

Thanks for the reply. No change has occurred since this is prod
environment and things do not change would passing through tons of
processes - but even if it did, there should be a way to find out
whats causing it.

My question is - how would I find what is causing high number of IDLE
connections ? There should be some way to tell.

Thanks,
-Kevin.

On Jun 22, 5:28=A0am, Kevin <kejos...@hotmail.com> wrote:
> Thanks for the reply. No change has occurred since this is prod
> environment and things do not change would passing through tons of
> processes - but even if it did, there should be a way to find out
> whats causing it.
>
> My question is - how would I find what is causing high number of IDLE
> connections ? There should be some way to tell.
>
> Thanks,
> -Kevin.

Have you tried using lsof?

Yes, using lsof I know which instances are exhibiting high number of
IDLE connections - but not what is the cause of it. I did a snoop and
tried to analyze it ; not much help.

-Kevin.

Hi Guys, I`m also facing the same problem in my Prod environment. Did any one find any solution for this..?

On 04/29/11 10:40 PM, Anudep wrote:
> Hi Guys, I`m also facing the same problem in my Prod environment. Did any one find any solution for this..?

Solution for what?

-- 
Ian Collins