Spacewalk: A Large Numbers of Established Connections of java Process Continue to Grow While Using a IDLE_TIME value in Oracle DB (Doc ID 2540018.1)

Last updated on APRIL 28, 2020

Applies to:

Symptoms

On the Spacewalk server a large numbers of established connections of a java process continue to grow while using a IDLE_TIME of 30 minutes in Oracle DB. That leads process limit on the server.

tcp 0 0 <IP Address>:47023 <IP Address>:61911 ESTABLISHED
tcp 0 0 <IP Address>:55129 <IP Address>:61911 ESTABLISHED
tcp 0 0 <IP Address>:39860 <IP Address>:61911 ESTABLISHED
tcp 0 0 <IP Address>:45298 <IP Address>:61911 ESTABLISHED


# ss -tp | grep java | wc -l
963

(After few hours)

# ss -tp | grep java | wc -l
1002

#ss -tp | grep java
State Recv-Q Send-Q Local Address:Port Peer Address:Port
ESTAB 0 0 <IP Address>:33231 <IP Address>:61911 users:(("java",10643,1360))
ESTAB 0 0 <IP Address>:50192 <IP Address>:61911 users:(("java",10643,82))
ESTAB 0 0 <IP Address>:43014 <IP Address>:61911 users:(("java",10643,697))

 
SQL> select a.username,b.profile,b.RESOURCE_NAME,b.LIMIT from dba_users a, dba_profiles b where b.resource_name in ('IDLE_TIME','CONNECT_TIME') AND a.profile=b.profile and a.username='SPACEWALK';

USERNAME             PROFILE              RESOURCE_NAME                    LIMIT
-------------------- -------------------- -------------------------------- ------------------------------
SPACEWALK            SCHEMA_PROF          IDLE_TIME                        30                                 >>
SPACEWALK            SCHEMA_PROF          CONNECT_TIME                 DEFAULT

2 rows selected.

A spacewalk service restart clears the processes.

Changes

A IDLE_TIME of 30 minutes has been configured in Oracle DB.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.