Connection Was Refused With Error Ora-12519
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn ora-12519 no appropriate service handler found more about Stack Overflow the company Business Learn more about hiring developers or posting ora 12519 sql developer ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack
Ora-12519 Oracle 11g
Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up java.sql.SQLException: Listener refused the connection with the following error: ORA-12519, TNS:no
Ora-12519, Tns:no Appropriate Service Handler Found Solution
appropriate service handler found up vote 0 down vote favorite 2 I am passing Resultset object to each thread. Each thread is connecting to the database and inserting data. Untill thread 110 it is working fine. After it crosses 111 thread it throws the above exception. I am using oracle 11g. My sample Thread code is: class MyThreadClass implements Runnable { public Connection connection; public Statement statement2; public ora-12519 intermittent ResultSet rs2; public String cookie; public MyThreadClass(ResultSet rs1) { rs2=rs1; } public void run() { try { cookie=rs2.getString("COOKIE"); driver = "oracle.jdbc.driver.OracleDriver"; url = "jdbc:oracle:thin:@127.0.0.1:1521:xx"; /* connection statement2.executeUpdate("INSERT INTO visit_header VALUES ('"+cookie+"')"); } I am not getting how to handle this exception. java oracle jdbc share|improve this question edited Apr 26 '13 at 7:00 Rahul Bobhate 2,71311232 asked Apr 26 '13 at 6:56 user2314206 13125 add a comment| 2 Answers 2 active oldest votes up vote 11 down vote Your multi-threaded application is opening too many Connections/Sessions. Hence, the listener is dropping and blocking new connections for a while. Check your DB resource usage first: SELECT * FROM v$resource_limit WHERE resource_name IN ('processes','sessions'); Check to see if your MAX_UTILIZATION for either your Processes or Sessions is getting too close to the LIMIT_VALUE. If yes, you should either: Use DB Connection pooling to share Connection objects between threads. Or, Increase the number of processes/sessions that Oracle can service simultaneously. Actually, Connection Pooling (#1) should always be done. An application cannot scale up otherwise. Check Apache Commons DBCP for details. For #2, open a new SQL*Plus session as SYSTEM and run: ALTER system SET processes=
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta
Java.sql.sqlexception: Listener Refused The Connection
Discuss the workings and policies of this site About Us Learn ora-00020: maximum number of processes (100) exceeded more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us how to run lsnrctl services Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like http://stackoverflow.com/questions/16230446/java-sql-sqlexception-listener-refused-the-connection-with-the-following-error you, helping each other. Join them; it only takes a minute: Sign up Why do I get this Oracle connections error? ORA-12519, TNS:no appropriate service handler found up vote 0 down vote favorite I'm building a JSF2 app with GlassFish, Hibernate, Spring (for transaction mgmt), and Oracle 11g. After the application has been running for a while, http://stackoverflow.com/questions/6795580/why-do-i-get-this-oracle-connections-error-ora-12519-tnsno-appropriate-servic the app fails to query the db and I get the following error in the GlassFish log: Caused by: java.sql.SQLException: Listener refused the connection with the following error: ORA-12519, TNS:no appropriate service handler found This sounds like Oracle is running out of connections, but the processes in Oracle are set to 150 (which I think means it will accept 150 connections) which seems like plenty. My Hibernate config appears to be set to use 1 connection (as follows). Why would the application be opening more than 150 connections? And how would you suggest I address this? Any suggestions are greatly appreciated.
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books http://www.dba-oracle.com/sf_ora_12519_tns_no_appropriate_service_handler_found.htm Oracle Scripts Ion Excel-DB Don Burleson Blog https://logbuffer.wordpress.com/2013/07/02/oracle-ora-12519-tnsno-appropriate-service-handler-found-on-jdbc-connection/
ORA-12519: TNS:no appropriate service handler foundtips Oracle Error Tips by Burleson Consulting Oracle docs note this about ORA-12519: ORA-12519: TNS:no appropriate service handler found Cause: The listener could not find any available service handlers no appropriate that are appropriate for the client connection. Action: Run "lsnrctl services" to ensure that the instance(s) have registered with the listener, and are accepting connections. ORA-12519 and Shared Servers: What has commonly happened here is that moving from a dedicated server to a shared server (MTS) ORA-12519 is thrown even though you have correctly changed al of no appropriate service the necessary parameters. ORA-12519 and listener configuration: ORA-12519 occurs here because the listener has not been properly set to the default port and the PMON automatic listener registration fails with ORA-12519. You may also notice with this ORA-12519 error that the RDA LOCAL_LISTENER reads NULL. To resolve ORA-12519, register the listener manually after the MTS change if you still wish to use non-default ports. ORA-12519 and "processes" parameter: Also, on Oracle DBA Forums, there is information referring to ORA-12519. Here, it is pointed out that ORA-12519 can be caused by low "processes" values, which can be resolved by increasing he DB parameter, "parallel_max_servers". Also, ORA-12519 can be thrown because of DB and client versions which do not match. Burleson is the American Team Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals. Feel free to ask questions on our Oracle forum. Verify experience! Anyone considering using the services of an Oracle suppCreate database-link in another user'sschema → Oracle: "ORA-12519, TNS:no appropriate service handler found" onJDBC-Connection July 2, 2013 Leave a comment In the context of a Java/Liferay/JackRabbit-Setting developer wants to export all stored files from database to filesystem for migration-purposes. After some uncertain time this always runs repeatedly on errors of this kind: 12:19:31,488 DEBUG [MaintenanceUtil:64] Executing com.liferay.portal.convert.ConvertDocumentLibrary 12:19:31,497 INFO [ConvertProcess:41] Starting conversion for com.liferay.portal.convert.ConvertDocumentLibrary 12:19:31,537 DEBUG [MaintenanceUtil:64] Migrating 276 document library files 12:21:07,739 ERROR [DatabaseFileSystem:225] failed to initialize file system java.sql.SQLException: Listener refused the connection with the following error: ORA-12519, TNS:no appropriate service handler found (stacktrace follows...) After this error the application goes on until next occurrence of that error. Monitoring the listener.log while executing the migration-application shows a massive increase of connection-requests. [oracle@serv1 ~]$ tail -f ./diag/tnslsnr/serv1/listener/trace/listener.log | egrep -i "hostdb|ORA-|TNS-" 28-JUN-2013 16:52:31 * (CONNECT_DATA=(SID=hostdb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=appuser))) * (ADDRESS=(PR OTOCOL=tcp)(HOST=10.107.108.140)(PORT=57601)) * establish * hostdb * 0 28-JUN-2013 16:52:31 * (CONNECT_DATA=(SID=hostdb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=appuser))) * (ADDRESS=(PR OTOCOL=tcp)(HOST=10.107.108.140)(PORT=57602)) * establish * hostdb * 0 28-JUN-2013 16:52:31 * (CONNECT_DATA=(SID=hostdb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=appuser))) * (ADDRESS=(PR OTOCOL=tcp)(HOST=10.107.108.140)(PORT=57603)) * establish * hostdb * 0 28-JUN-2013 16:52:31 * (CONNECT_DATA=(SID=hostdb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=appuser))) * (ADDRESS=(PR OTOCOL=tcp)(HOST=10.107.108.140)(PORT=57604)) * establish * hostdb * 0 28-JUN-2013 16:52:31 * (CONNECT_DATA=(SID=hostdb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=appuser))) * (ADDRESS=(PR OTOCOL=tcp)(HOST=10.107.108.140)(PORT=57605)) * establish * hostdb * 0 28-JUN-2013 16:52:31 * (CONNECT_DATA=(SID=hostdb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=appuser))) * (ADDRESS=(PR OTOCOL=tcp)(HOST=10.107.108.140)(PORT=57606)) * establish * hostdb * 0 28-JUN-2013 16:52:31