On Sun, Feb 16, 2025 at 12:04 AM Усманов Азат Анварович <usma...@ieml.ru> wrote:
> Jdbc config from server<Resource name="jdbc/IEML_DB" auth="Container" > type="javax.sql.DataSou > rce" > maxActive="200" maxIdle="200" maxWait="50000" > username="educ_pres" password="*****" > driverClassName="oracle.jdbc.driver.OracleDriver" > url="jdbc:oracle:thin:@//192.168.1.8:1521/moon.ieml.ru" > > Jdbc config from server 2 > > <Resource auth="Container" driverClassName="oracle.jdbc.driver.OracleD > river" > maxActive="1000" maxIdle="1000" maxWait="50000" name="jdb > c/IEML_DB" password="*****" type="javax.sql.DataSource" url="jdbc:oracl > e:thin:@//192.168.1.8:1521/moonutf8.ieml.ru" username="educ" > validationQuery="select 1 from dual" testWhileIdle="true" > testOnReturn="true" accessToUnderlyingConnectionAllowed="true" > removeAbandoned="true" removeAbandonedTimeout="3600" > logAbandoned="true" factory="org.apache.tomcat.jdbc.pool.DataSo > urceFactory"/> > ________________________________ > От: Усманов Азат Анварович <usma...@ieml.ru> > Отправлено: 16 февраля 2025 г. 0:36 > Кому: users@tomcat.apache.org <users@tomcat.apache.org> > Тема: tomcat and linux oom-killer > > Hi everyone! I'm not sure if this is an appropriate place to ask, but here > is my Problem > I have an old oracle 10g server with 2 schemas/sid, moon and moonutf8. > tomcat is also installed as a webserver on the same physical server . > 1-st schema moon - has oldjava app and old tomcat 7.092 with practically > 1-2 people using it. > 2nd schema is a production schema of the much more modern version of the > same app . Modern version of the app is hosted on different ip address > with different tomcat 9.064 > so the only java processes on that old server are related to old tomcat > on the server with old oracle( with ipaddress 192.168.1.8) I received the > following message in the logs > java invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 > Feb 15 11:49:20 moon kernel: java cpuset=/ mems_allowed=0 > Feb 15 11:49:20 moon kernel: Pid: 37306, comm: java Not tainted > 3.8.13-68.2.2.el6uek.x86_64 #2 > Feb 15 11:49:20 moon kernel: Call Trace: > > Am I correct to assume that whatever caused the java to ask for more > memory, and oracle to be killed was related only to an old app? > In case this was confusing here is a short summary of all the software > versions > server 1 (ip address 192.168.1.8) > java version 8.333 > tomcat version 7.0.92 > App name: Pres > oracle schema: moon > > server 2 (ip address 192.168.1.9) > java version 8.202 > tomcat version 9.0.64 > app name Education > oracle schema used: moonutf8 > > there is no oracle installed on server 2 and both tomcats use jdbc to > connect , both server have RHEL 6 installed > > > > > > > > > > > Hi, The question is not Tomcat related and shall be noted that Tomcat 7 is out of support. Based on the information provided, it is reasonable to assume that the memory issue, triggering the OOM-killer and affecting Oracle by the memory contention, is primarily due to the application leaking memory.
