1

Topic: inbound connection timed out (ORA-3136)

Good afternoon. The question already 100 times was considered, but who else all the same can that prompts.
There is an application on Java (indirect development), which sometimes falls out at primary start on a time-out (even out of working hours) Especial loading on the server of Oracle is not present during this moment (I look in  and in OS)
Error from application (the server debian 9.6, java version "1.8.0_112")

wrote:

2018-ijul-31 7:03:09 PM: DEBUG main com.zaxxer.hikari.pool. HikariPool - BaseHikariPool.addConnection (line:466) - Connection attempt to database dataSource failed: an input/conclusion Error: Connection reset
java.sql. SQLRecoverableException: an input/conclusion error: Connection reset

Error from basis (other errors are not present, oracle linux,  is not present smile)

wrote:

***********************************************************************
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 12.1.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production
Time: 31-JUL-2018 6:15:10 PM
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS = (PROTOCOL=tcp) (HOST=192.168.166.19) (PORT=36020))
Tue Jul 31 6:15:10 PM 2018
WARNING: inbound connection timed out (ORA-3136)

Not so it would be desirable to put SQLNET.INBOUND_CONNECT_TIMEOUT and INBOUND_CONNECT_TIMEOUT_listener_name in 0 (or other great values) Can at whom were such dancings with a tambourine)
p.s. With a network of problems it has not been noted.

2

Re: inbound connection timed out (ORA-3136)

Well it is similar in this case timeout works from server side.
1. I would look at application on Java that it does at the moment of loading. Especially would look on GC. Probably there brakes read off scale.
2. Whether there can be banal problems with a network?

3

Re: inbound connection timed out (ORA-3136)

Leonid Kudryavtsev;
Yes is not present, with a network all should be good. And here with Garbage Collection it is similar you are right. Errors are...

wrote:

Java HotSpot (TM) Client VM (25.112-b15) for linux-x86 JRE (1.8.0_112-b15), built on Sep 22 2016 7:45:47 PM by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)
Memory: 4k page, physical 4136972k (2977672k free), swap 349180k (349180k free)
CommandLine flags:-XX:InitialHeapSize=16777216-XX:MaxHeapSize=268435456-XX: + PrintGC-XX: + PrintGCDateStamps-XX: + PrintGCDetails-XX: + PrintGCTimeStamps-XX: + UseCMSInitiatingOccupancyOnly-XX: + UseParNewGC
2018-07-31T21:29:23.294+0300: 0,217: [GC (Allocation Failure) 2018-07-31T21:29:23.294+0300: 0,217: [ParNew: 4416K-> 511K (4928K), 0,0024915 secs] 4416K-> 1080K (15872K), 0,0025797 secs] [Times: user=0,00 sys=0,00, real=0,00 secs]
2018-07-31T21:29:23.425+0300: 0,347: [GC (Allocation Failure) 2018-07-31T21:29:23.425+0300: 0,348: [ParNew: 4927K-> 512K (4928K), 0,0032925 secs] 5496K-> 2081K (15872K), 0,0033863 secs] [Times: user=0,00 sys=0,00, real=0,00 secs]
2018-07-31T21:29:23.514+0300: 0,437: [GC (Allocation Failure) 2018-07-31T21:29:23.515+0300: 0,437: [ParNew: 4928K-> 512K (4928K), 0,0032310 secs] 6497K-> 2812K (15872K), 0,0032839 secs] [Times: user=0,01 sys=0,00, real=0,00 secs]
2018-07-31T21:29:23.593+0300: 0,516: [GC (Allocation Failure) 2018-07-31T21:29:23.593+0300: 0,516: [ParNew: 4928K-> 512K (4928K), 0,0030476 secs] 7228K-> 3854K (15872K), 0,0031017 secs] [Times: user=0,00 sys=0,00, real=0,00 secs]
2018-07-31T21:29:23.699+0300: 0,622: [GC (Allocation Failure) 2018-07-31T21:29:23.699+0300: 0,622: [ParNew: 4928K-> 512K (4928K), 0,0022282 secs] 8270K-> 4496K (15872K), 0,0022770 secs] [Times: user=0,00 sys=0,00, real=0,00 secs]
2018-07-31T21:29:23.766+0300: 0,689: [GC (Allocation Failure) 2018-07-31T21:29:23.766+0300: 0,689: [ParNew: 4928K-> 512K (4928K), 0,0027286 secs] 8912K-> 5260K (15872K), 0,0027918 secs] [Times: user=0,00 sys=0,00, real=0,00 secs]
2018-07-31T21:29:23.885+0300: 0,808: [GC (Allocation Failure) 2018-07-31T21:29:23.885+0300: 0,808: [ParNew: 4928K-> 512K (4928K), 0,0029736 secs] 9676K-> 5806K (15872K), 0,0030553 secs] [Times: user=0,01 sys=0,00, real=0,00 secs]
2018-07-31T21:29:24.029+0300: 0,952: [GC (Allocation Failure) 2018-07-31T21:29:24.029+0300: 0,952: [ParNew: 4928K-> 512K (4928K), 0,0035641 secs] 10222K-> 6571K (15872K), 0,0036303 secs] [Times: user=0,00 sys=0,01, real=0,01 secs]
2018-07-31T21:29:24.101+0300: 1,024: [GC (Allocation Failure) 2018-07-31T21:29:24.101+0300: 1,024: [ParNew: 4928K-> 512K (4928K), 0,0038491 secs] 10987K-> 7721K (15872K), 0,0038949 secs] [Times: user=0,01 sys=0,00, real=0,00 secs]
2018-07-31T21:33:40.051+0300: 256,974: [GC (Allocation Failure) 2018-07-31T21:33:40.051+0300: 256,974: [ParNew: 4928K-> 512K (4928K), 0,0042898 secs] 12137K-> 8502K (15872K), 0,0043729 secs] [Times: user=0,01 sys=0,00, real=0,00 secs]
Heap
par new generation total 4928K, used 1819K [0xa4200000, 0xa4750000, 0xa9750000)
eden space 4416K, 29 % used [0xa4200000, 0xa4346f70, 0xa4650000)
from space 512K, 100 % used [0xa4650000, 0xa46d0000, 0xa46d0000)
to space 512K, 0 % used [0xa46d0000, 0xa46d0000, 0xa4750000)
tenured generation total 10944K, used 7990K [0xa9750000, 0xaa200000, 0xb4200000)
the space 10944K, 73 % used [0xa9750000, 0xa9f1da40, 0xa9f1dc00, 0xaa200000)
Metaspace used 10456K, capacity 10610K, committed 10648K, reserved 11568K

4

Re: inbound connection timed out (ORA-3136)

Deemaas wrote:

[code] Java HotSpot (TM) Client VM (25.112-b15) for linux-x86 JRE (1.8.0_112-b15), \
built on Sep 22 2016 7:45:47 PM by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)
...
CommandLine flags:\
-XX:InitialHeapSize=16777216-XX:MaxHeapSize=268435456\
...
-XX: + UseCMSInitiatingOccupancyOnly-XX: + UseParNewGC [code]]

And here it is all any real problem solves or it is simple  "the most abrupt XX-set"?

5

Re: inbound connection timed out (ORA-3136)

Basil A. Sidorov;
, Application indirect, the Developer such config put) I with JVM unfortunately is not so familiar... What in it not so?

6

Re: inbound connection timed out (ORA-3136)

On the Internet write that if the client  on password entry in a minute of waiting will be here such .
P.S.
Heap which can change from 16 megabytes to a gigabyte quarter - very strange.
Usage "twice a non-standard option" - is stranger.
Garbage-First In Java 8 it is ready to commercial operation though it is not included by default.
32-bit client JRE too it is strange.

7

Re: inbound connection timed out (ORA-3136)

That that, on the Internet write I know) Wrote that I do not want to change standard parameter SQLNET.INBOUND_CONNECT_TIMEOUT of equal 60 seconds. To me it seems to a wave reasonable and I seek a jamb elsewhere a software)

8

Re: inbound connection timed out (ORA-3136)

Concerning the size of a heap if to me does not change storage that it is standard parameters 16/256 if not to specify xmx xms manually

9

Re: inbound connection timed out (ORA-3136)

"Standard" it when is written nothing by playful hands.
In mine, for example, a case it turns out:

 java-XshowSettings:vm-version
VM settings:
Max. Heap Size (Estimated): [u] 1.33G [/u]
Ergonomics Machine Class: client
Using VM: Java HotSpot (TM) 64-Bit Server VM
java version "1.8.0_181"
Java (TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot (TM) 64-Bit Server VM (build 25.181-b13, mixed mode) 

And all it also depends on the version:

 VM settings:
Max. Heap Size (Estimated): [u] 1.50G [/u]
Using VM: Java HotSpot (TM) 64-Bit Server VM
java version "10.0.2" 2018-07-17
Java (TM) SE Runtime Environment 18.3 (build 10.0.2+13)
Java HotSpot (TM) 64-Bit Server VM 18.3 (build 10.0.2+13, mixed mode) 

10

Re: inbound connection timed out (ORA-3136)

Deemaas wrote:

And here with Garbage Collection it is similar you are right. Errors are...

Errors did not see, time delays in 0,0025797 with. Generally
Storage consumption in units of megabytes, generally about what.
p.s. Allocation Fauilure is the reason on which it was launched GC. All is normal, the free storage came to an end, GC and was launched.

11

Re: inbound connection timed out (ORA-3136)

wrote:

# java-XshowSettings:vm-version
VM settings:
Max. Heap Size (Estimated): 247.50M
Ergonomics Machine Class: client
Using VM: Java HotSpot (TM) Client VM
java version "1.8.0_112"
Java (TM) SE Runtime Environment (build 1.8.0_112-b15)
Java HotSpot (TM) Client VM (build 25.112-b15, mixed mode)

Yes is not present, like all it is normal here. 256 this application should suffice. Out of Memory in a broad gull that is not present...

12

Re: inbound connection timed out (ORA-3136)

Deemaas wrote:

To me it seems to a wave reasonable and I seek a jamb elsewhere a software)

Then - simple search on hikarypool produces, for example, such .

13

Re: inbound connection timed out (ORA-3136)

Deemaas wrote:

Yes is not present, like all it is normal here. 256 this application should suffice. Out of Memory in a broad gull that is not present...

it is normal when for long-playing application put reasonable-Xms/-Xmx with identical values.
Theoretically, there is a scenario when it not so, but "me again is tormented with vague doubts...".

14

Re: inbound connection timed out (ORA-3136)

Basil A. Sidorov wrote:

....
Heap which can change from 16 megabytes to a gigabyte quarter - very strange.
Usage "twice a non-standard option" - is stranger.

IMHO you are not right.
On a broad gull application consumes less than 10 Mb, .. 16 Mb - apparently saved storage. 256 Mb - it is similar just in case, suddenly 16Mb does not suffice.
-XX: + UseParNewGC - quite normal option, rigidly selected algorithm GC. That, in general, correctly. Under what wrote/tested, that and in .
-XX: + UseCMSInitiatingOccupancyOnly - never faced, but time developers recommended, should be at them there were any reasons. Special harm or "not " it is not visible.
IMHO AND AFAIK
In general, except the initial complaint on timeout, personally I of a crime do not see (((

15

Re: inbound connection timed out (ORA-3136)

Leonid Kudryavtsev wrote:

On a broad gull application consumes less than 10 Mb, .. 16 Mb - apparently saved storage. 256 Mb - it is similar just in case, suddenly 16Mb does not suffice.

It testifies exactly to one - about inability (unwillingness) of the developer adequately to estimate work set of the application in the conditions of the customer.
And it, in turn, calls into question adequacy of all remaining choices.

16

Re: inbound connection timed out (ORA-3136)

Application standard for all customers. It is the gateway. At someone it is a lot of files, someone has not enough through it transits. Happens that in peak of activity 16 MB can not suffice, therefore expands to 256 MB.
Here and I do not see while in what a jamb... If all the same I will find I will unsubscribe)

17

Re: inbound connection timed out (ORA-3136)

Here it is difficult that  to advise
1. On the one hand, 7 start minor GC in one second (2018-07-31T21:29:23), it is a lot of.
2. On the other hand, eden by the normal it is cleaned, full GC never worked - i.e. eden' quite suffices, storage is arranged normally
Well it is possible initial size to increase, GC it becomes possible less, it will not be exact worse. But personally I on a broad gull of any crime do not see. Storages like suffice.
Still a question:
How many physical processors on the client computer (where Java works)?
How many copies Java of applications work simultaneously?
P.S.
Saw JVM which it was used for communication through RMI Java with Cobol'. So there like generally 512 Kb heap was)))

18

Re: inbound connection timed out (ORA-3136)

wrote:

Connection reset

In our case the instructions of parameter ENABLE=BROKEN helped with a line of connection since ostensibly without it keep-alive in JDBC not absolutely works:
jdbc:oracle:thin:@ (DESCRIPTION = (ENABLE=BROKEN) (ADDRESS = (PROTOCOL=TCP) (HOST = <host>) (PORT = <port>)) (CONNECT_DATA = (SERVICE_NAME = <service>)))

19

Re: inbound connection timed out (ORA-3136)

Leonid Kudryavtsev;
On the server/virtualke it is selected two kernels of Intel (R) Xeon (R) CPU E5-2630 v3 2.40GHz and 4 Gb of the RAM
Besides this application (it very not gluttonous in my opinion) is 3 more pieces. One gluttonous, for it I registered-Xmx1024M, like suffices also two more small. I.e. only 4 pieces.

20

Re: inbound connection timed out (ORA-3136)

dimacrat wrote:

...

https://docs.oracle.com/cd/E11882_01/ja … JDBC28984?

21

Re: inbound connection timed out (ORA-3136)

Leonid Kudryavtsev;
With  certainly idea good, but the server  and application in one network, this variant here does not approach.

22

Re: inbound connection timed out (ORA-3136)

Deemaas wrote:

Leonid Kudryavtsev;
With  certainly idea good, but the server  and application in one network, this variant here does not approach.

can work and it is local by the machine.