We recently changed our ASA 8.0 server startup params to
bind to
specific addresses:

dbsrv8 -gk all -n ittdb.1.1.8.0.0 -ud -x
tcpip(MyIP=10.0.64.32:2638,10.0.64.64:2638;DoBroad =no)"
.....

When it starts everything is fine. Then when our apps start
connecting
to it and executing queries, they all work fine. However,
the server
keeps consuming 10% CPU while there is no activity, several
open JDBC
connections, but no queries being processed.

Looking at the sockets, I noticed that the server keeps
binding (port
number keeps going up):


PID USERNAME THR PR NCE SIZE RES STATE TIME FLTS
CPU COMMAND
6329 root 25 59 0 37.1M 14.3M sleep 21:14 0
8.60% dbsrv8
6484 root 88 29 10 133M 89.7M run 7:20 0
1.89% java
6562 root 17 29 10 74.0M 27.0M sleep 1:59 0
1.00% java
6502 root 45 29 10 120M 58.8M sleep 4:49 0
0.76% java
687 root 26 59 0 48.9M 14.4M sleep 7:06 0
0.38% java
6384 root 36 29 10 73.5M 17.8M sleep 0:34 0
0.32% java
6609 root 18 29 10 72.8M 24.0M run 0:57 0
0.24% java


dbsrv8 6329 root 19u IPv4 0x3008b550368 0t0
TCP master-management:2638->master-management:63216
(BOUND)
dbsrv8 6329 root 20u IPv4 0x3008b54e370 0t0
TCP master-management:2638->master-management:35372
(ESTABLISHED)
dbsrv8 6329 root 21u IPv4 0x30001cdf9e0 0t0
TCP master-management:2638->master-management:35249
(ESTABLISHED)
dbsrv8 6329 root 22u IPv4 0x3001a97af50 0t0
TCP master-management:2638->master-management:35259
(ESTABLISHED)
dbsrv8 6329 root 23u IPv4 0x3008b551268 0t0
TCP master-management:2638->master-management:35248
(ESTABLISHED)
dbsrv8 6329 root 24u IPv4 0x30005524ac0 0t0
TCP master-management:2638->master-management:35256
(ESTABLISHED)
dbsrv8 6329 root 25u IPv4 0x3008b55ede0 0t0
TCP master-management:2638->master-management:63215
(BOUND)
dbsrv8 6329 root 26u IPv4 0x30003e047b0 0t0
TCP master-management:2638->master-management:35279
(ESTABLISHED)
dbsrv8 6329 root 28u IPv4 0x300042bc4a8 0t0
TCP master-management:2638->master-management:35371
(ESTABLISHED)
dbsrv8 6329 root 30u IPv4 0x3008b54c4a8 0t0
TCP master-management:2638->master-management:35415
(ESTABLISHED)
dbsrv8 6329 root 31u IPv4 0x3008b54c1a8 0t0
TCP master-management:2638->master-management:35422
(ESTABLISHED)
dbsrv8 6329 root 33u IPv4 0x300364b5e30 0t0
TCP master-management:2638->master-management:35420
(ESTABLISHED)
dbsrv8 6329 root 34u IPv4 0x3008b54cf28 0t0
TCP master-management:2638->master-management:35455
(ESTABLISHED)

When I look at the BOUND state socket, its port number keeps
increasing, which I interpret as rebinding over and over
again:

dbsrv8 6329 root 25u IPv4 0x3008b550368 0t0
TCP master-management:2638->master-management:63299
(BOUND)
.... and few seconds later:
dbsrv8 6329 root 25u IPv4 0x300055ec348 0t0
TCP master-management:2638->master-management:63416
(BOUND)


The question is why is the server consuming so much of CPU
util?
Why is it binding so often? Thanks


P.S.:

Here is the list of interfaces:
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
cgtp0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4>
mtu 1500 index 2
inet 10.1.3.32 netmask ffffff00 broadcast 10.1.3.255
cgtp0:1:
flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRE CATED,IPv4>
mtu 1500 index 2
inet 10.1.3.1 netmask ffffff00 broadcast 10.1.3.255
eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 3
inet 10.1.1.32 netmask ffffff00 broadcast 10.1.1.255
eri0:1:
flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRE CATED,IPv4>
mtu 1500 index 3
inet 10.1.1.1 netmask ffffff00 broadcast 10.1.1.255
eri1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 4
inet 10.0.32.64 netmask ffffff00 broadcast
10.0.32.255
eri1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4>
mtu 1500 index 4
inet 10.0.32.32 netmask ffffff00 broadcast
10.0.32.255
eri1:2: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 4
inet 10.0.32.33 netmask ffffff00 broadcast
10.0.32.255
qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 5
inet 10.1.2.32 netmask ffffff00 broadcast 10.1.2.255
qfe0:1:
flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRE CATED,IPv4>
mtu 1500 index 5
inet 10.1.2.1 netmask ffffff00 broadcast 10.1.2.255
qfe1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 6
inet 10.0.32.66 netmask ffffff00 broadcast
10.0.32.255
qfe1:1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 6
inet 10.0.32.32 netmask ffffff00 broadcast
10.0.32.255
qfe1:2: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 6
inet 10.0.32.33 netmask ffffff00 broadcast
10.0.32.255
qfe2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 7
inet 10.0.64.64 netmask ffffff00 broadcast
10.0.64.255
qfe2:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4>
mtu 1500 index 7
inet 10.0.64.32 netmask ffffff00 broadcast
10.0.64.255
qfe2:2: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu
1500 index 7
inet 10.0.64.33 netmask ffffff00 broadcast
10.0.64.255

First, Please always state the platform that you are using.
I am guessing that you are using some flavour of Linux ?

The only reason that I can think of that the server would
continue to bind to new ports is that the client app is
dropping the connection and then reconnecting.

If you turn on the -z option on the server, you should see
some additional diagnostic messages, including connects/disconnects.
--
Mark Culp
ASA Research and Development
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------
* <<<<< Please always include the ASA version and build number >>>>> *
* <<<<< _and_ the operating system version that you are using >>>>> *
-------------------------------------------------------------------------

Bob wrote:

Damn I am dumb, sorry about that.
Solaris 9, SunFire V100/120, Netra V120

Good idea. I'll try that. thanks