Wong Wah Meng-R32813
2011-10-04 10:27:19 UTC
Hello guys,
Has anyone seen this befote?
I am migrating my RMI application from python 1.5.2 (oracledb) to 2.7.1 (cx_Oracle). When I start up my DbAccessMgr, previously utilizing oracledb to connect to database, I encountered below error. I haven't traced down to exactly which code is producing this error however it seems that this is generated after I spawn off 4 parallel threads instance for the database connection from my application.
The funnier thing is I am able to launch my DbAccessMgr successfully without this error after every 2 failures. My DBA told me this should be application specific unless I can show otherwise. Appreciate any input out there. Thanks!
(PS: My platform in HP-UX11.31 and cx_Oracle was compiled against Oracle 11.1 library using HP-UX C Compiler)
ORA-24550: signal received: [si_signo=11] [si_errno=0] [si_code=2] [si_addr=0000000000000000]
sendsig: useracc failed. 0x9fffffff5feb6200 0x00000000005000
Pid 8162 was killed due to failure in writing the signal context - possible stack overflow.
Regards,
Wah Meng
Has anyone seen this befote?
I am migrating my RMI application from python 1.5.2 (oracledb) to 2.7.1 (cx_Oracle). When I start up my DbAccessMgr, previously utilizing oracledb to connect to database, I encountered below error. I haven't traced down to exactly which code is producing this error however it seems that this is generated after I spawn off 4 parallel threads instance for the database connection from my application.
The funnier thing is I am able to launch my DbAccessMgr successfully without this error after every 2 failures. My DBA told me this should be application specific unless I can show otherwise. Appreciate any input out there. Thanks!
(PS: My platform in HP-UX11.31 and cx_Oracle was compiled against Oracle 11.1 library using HP-UX C Compiler)
ORA-24550: signal received: [si_signo=11] [si_errno=0] [si_code=2] [si_addr=0000000000000000]
sendsig: useracc failed. 0x9fffffff5feb6200 0x00000000005000
Pid 8162 was killed due to failure in writing the signal context - possible stack overflow.
Regards,
Wah Meng