title: Oracle database alert opiodr aborting process ORA-609
body: <p>I am running a batch java application. The application runs every 10/20 minutes in my Production and UAT environment and I get database alerts like this:</p>
  
  <p>Thu Feb 06 15:15:08 2014
  opiodr aborting process unknown ospid (28246400) as a result of ORA-609</p>
  
  <p>After researching a bit on the internet the suggested fix for these alerts is to change INBOUND_CONNECT_TIMEOUT as:</p>
  
  <pre><code>Sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=180
  Listener.ora: INBOUND_CONNECT_TIMEOUT_listener_name=120
  </code></pre>
  
  <p>We have changed the setting on the database server side but don't know where to change in the client application. We are using c3p0 to create a connection pool and we are setting only these parameters:</p>
  
  <pre><code>dataSource.setAcquireRetryDelay(30000); 
  dataSource.setMaxPoolSize(50);
  dataSource.setMinPoolSize(20);
  dataSource.setInitialPoolSize(10);
  </code></pre>
  
  <p>We have other web services running on the same server as the batch application and they use Tomcat's DBCP pool and they don't seem to create any alerts. Also strangely enough, our batch application doesn't generate the alerts in lower test environments. They happen once in a while but the UAT and PROD environments get these alerts very frequently based on the schedule. Any suggestions what configurations to set in the c3p0 pool or should I try changing to another pool API like DBCP?</p>
  
  <p><strong>Update:</strong> I have added a few more parameters in the datasource and the frequency of alerts has reduced. I added the following and the number of alerts have gone down from 15 an hour to 4 an hour.</p>
  
  <pre><code>dataSource.setLoginTimeout(120);
  dataSource.setAcquireRetryAttempts(10);
  dataSource.setCheckoutTimeout(60000);
  </code></pre>