Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause
XMLRPC requests can fail if the environment value MOD_PERL is defined.
Consequence
XMLRPC request fail.
Fix
The standard read instead of sysread is now used, when environment MOD_PERL is defined.
Result
XMLRPC request doesn't fail.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
When using XMLRPC::Transport::HTTP with mod_perl the HTTP request can't be deserialized by SOAP::Transport::HTTP due to a bug in the SOAP::Lite package.
An error message is returned by the XMLRPC web service along the lines of:
Application failed during request deserialization:
no element found at line 1, column 0, byte -1 at /usr/lib64/perl5/XML/Parser.pm line 187
This bug was introduced upstream in version 0.710.08 and fixed in upstream version 0.713.
Full details of the bug and patch can be found in the CPAN bug report at:
https://rt.cpan.org/Public/Bug/Display.html?id=58538
Reproducible: Always
Steps to Reproduce:
1. Create an XMLRPC web service
2. Configure Apache to use mod_perl on the service URL
3. Make an XMLRPC request
Actual Results:
XMLRPC Fault returned,
Application failed during request deserialization:
no element found at line 1, column 0, byte -1 at /usr/lib64/perl5/XML/Parser.pm line 187
Expected Results:
Successful web service call.
https://rt.cpan.org/Public/Bug/Display.html?id=58538
Comment 2RHEL Program Management
2011-10-24 10:28:49 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3Marcela Mašláňová
2012-08-03 12:12:29 UTC
Comment 7Marcela Mašláňová
2012-08-07 12:56:44 UTC
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.
New Contents:
Cause
XMLRPC requests can fail if the environment value MOD_PERL is defined.
Consequence
XMLRPC request fail.
Fix
The standard read instead of sysread is now used, when environment MOD_PERL is defined.
Result
XMLRPC request doesn't fail.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-1388.html