ORA-12518

Question

Hello, I'm using Oracle 11r1 on a Windows Server Standard SP2 32-bit OS with 4GB of RAM. I've been tasked with load-testing our application running our database through JBoss, and at around 300 threads I begin to encounter this error:
Listener refused the connection with the following error:
ORA-12518, TNS:listener could not hand off client connection
My listener.ora file looks like this:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = db1)(PORT = 1521))
     (DIRECT_HANDOFF_TTC_LISTENER=OFF)
#DIRECT_HANDOFF_TTC_LISTENER=OFF added after reading suggestions from other threads
And tnsnames.ora looks like this:
REMOTE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = db1)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = REMOTE.emb)
I modified this line in init.ora, guessing that the processes might have been getting starved:
processes = 1000
I also tried this in case the processes/sessions parameters for the database were insufficient:
SQL>alter system set processes=1000 scope=spfile;
I tried using this 3GB switch to increase the memory alloted for Oracle, though it had no apparent effect:
C:\>BCDEdit.exe /set IncreaseUserVa 3072
Can anyone suggest a solution to this problem? Several sources indicate that it could simply be a lack of available memory, so if anyone can confirm this, I may be willing to accept defeat. I've browsed other answers to this problem but they were either unresolved or unrelated.
Note: I'm very new to Oracle, but willing to learn. If the solution is apparent, I apologize. If more information is needed, please specify the location and process to attain it and which sections are pertinent.
Thanks for your assistance,
-Paul

Answer 1

@BelMan:
I added that line to my listener.ora, modifying the file to look like this:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = db1)(PORT = 1521))
     (INBOUND_CONNECT_TIMEOUT_LISTENER=0)
     (DIRECT_HANDOFF_TTC_LISTENER=OFF)
I also attempted setting the value equal to one (in similar situations, setting parameters equal to zero may cause infinite connection times), but neither of the values worked.
I also tried setting it using LSNRCTL>SET INBOUND_CONNECT_TIMEOUT 0. I read on here to "set the value of the INBOUND_CONNECT_TIMEOUT_listener_name parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT parameter", with recommended values such as 2 and 3, respectfully. However, when I try and set either SQLNET.INBOUND_CONNECT_TIMEOUT or INBOUND_CONNECT_TIMEOUT_LISTENER from LSNRCTL, I get this error:
NL-00853: undefined set command "inbound_connect_timeout_listener". Try "help set"
I'm unsure of how to configure this value otherwise.
@gjilevski1:
I turned on listener tracing, and re-executed the operation, and this was output to the listener log:
13-AUG-2010 10:35:30 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=EMB01$))(SERVER=DEDICATED)(SERVICE_NAME=REMOTE.emb)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.100.186)(PORT=59653)) * establish * REMOTE.emb * 12518
TNS-12518: TNS:listener could not hand off client connection
TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error
32-bit Windows Error: 233: Unknown error
Apparently the Windows Error 233 means "ERROR_PIPE_NOT_CONNECTED"
I verified that the listener was configured for direct handoff (DIRECT_HANDOFF_TTC_LISTENER=OFF), but how would I configure the database instance for direct handoff, as that note also recommends? Also, what would be considered the 'proper' configuration for both the listener and the database instance, in this situation?
@sb92075:
Connection pooling is being used. Could it be that the sizes are not configured correctly?
Thanks again for your assistance,
-Paul
Edited by: user13279755 on Aug 13, 2010 4:20 PM