oracle - Inactive sessions in the database -

oracle - Inactive sessions in the database -

in short have - tomcat server running, connect database after user logs in page @ specific url. 1 time user disconnects application clicking logout, , closes browser; database still shows tomcat session running when check sessions. dba has go , kill inactive sessions avoid issues.

until ok, on period of time these 'inactive' sessions go on increasing limit requires application server re-start clean inactive sessions , avoid http 503 bad gateway error message users. missing out here? parts of application code seem have problem , checking that, apart that; else setting/changes need avoid issue? there way these sessions killed automatically after user logs out?

note - did go through question here - inactive jdbc sessions don't have db error reported. http 503 - bad gateway error message in browser users , database slows downwards crawl.

oracle apache tomcat webserver