Red Hat Bugzilla – Bug 605311
condor_schedd double free on SOAP transaction timeout
Last modified: 2010-10-14 11:57:47 EDT
Description of problem:
The stack trace is not consistent because it is the result of corrupted memory. However, it often follows,
SOAP entered abortTransaction(), transaction: 1234
SOAP leaving abortTransaction() result=0
Steps to Reproduce:
1. run a schedd with soap enabled
2. start a soap transaction
Condor's SOAP testsuite (SubmitExpireTest) should reproduce.
Fixed post 7.4.3-0.19, upstream #1463
Tested with (version):
RHEL5 i386 - passed
RHEL5 x86_64 - passed
RHEL4 i386 - passed
RHEL4 x86_64 - passed
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Running a 'condor_schedd' job scheduler with SOAP (Simple Object Access Protocol) enabled and starting a SOAP transaction resulted in a crash of 'condor_shedd'. With this update, SOAP transactions no longer cause the aforementioned crash.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.