Recent changes to bugs

PATCH_HTTP_KEEPALIVE breaks connection caching

John Hughes — Sat, 16 May 2015 09:20:43 -0000

The problem is that LWP::Protocol::http::request assumes that the collector sub will be called until it returns 0, at which point the $completed variable is set and the connection will be cached.

If the collector sub never returns 0 then the connection is not cached.

The "patch" calls the collector sub until it has accumulated the whole body but no more, so the collector sub never returns 0, so $completed is never set, so the connection is lost.

PATCH_HTTP_KEEPALIVE doc is wrong, it's on by default

John Hughes — Sat, 16 May 2015 09:16:41 -0000

The doc for SOAP::Constants says that PATCH_HTTP_KEEPALIVE is off by default but examination of the code shows that it's on (in v1.11 and 0.712 at least).

As having it on breaks connection caching -- the patch works badly with at least versions 6.08 and 5.836 of LWP -- this is rather anoying.

#183 "Incorrect parameter at SOAP/Lite.pm line 1994" encountered

dcunningham — Tue, 03 Sep 2013 08:33:21 -0000

Thank you!

#183 "Incorrect parameter at SOAP/Lite.pm line 1994" encountered

Michiel Beijen — Tue, 03 Sep 2013 08:32:43 -0000

The fix IS already on cpan, since version 0.716, which was released in May.

#183 "Incorrect parameter at SOAP/Lite.pm line 1994" encountered

dcunningham — Tue, 03 Sep 2013 08:30:35 -0000

Michiel, do you know if the CPAN maintainer can update with the fixed version? Thank you.

#183 "Incorrect parameter at SOAP/Lite.pm line 1994" encountered

Michiel Beijen — Tue, 03 Sep 2013 07:50:25 -0000

This is fixed in https://github.com/redhotpenguin/soaplite/commit/086aa7cf66417832e9094bbef5369e39810ea14e and version 0.716.

#186 Modification of a read-only value

Alex — Thu, 18 Jul 2013 06:24:53 -0000

I have to add that my system is 3.2.0-23-generic Ubuntu SMP x86_64 GNU/Linux
(Ubuntu 12.04 server)
perl version is 5.14.2 and OTRS is 3.1.4.
Call of OTRS function via SOAP looks like:

sub getOtrsQueues{

    return undef unless my $RPC = getOtrsRPC();

    my $som = $RPC->Dispatch($Include::OTRS_soap_login, $Include::OTRS_soap_pass, 'QueueObject','QueueList');
    return undef if not defined($som) or $som->fault;
    my $Queues = +{$som->paramsall};

    exists $Include::support_viewable_queues{$_}?'':delete($$Queues{$_}) foreach keys %$Queues;
    return $Queues;
}

Modification of a read-only value

Alex — Wed, 17 Jul 2013 13:10:40 -0000

I'm trying to use remote procedure call with OTRS ticket system and SOAP::Lite module. I have random crashes in Lite.pm line 3828 (0.716) with message "Modification of a read-only value attempted".
In the version 1.0 the line number is 3832.

I am only try to get queues or tickets list from OTRS so I create a client and SOAP fails on my side.
This fail happens randomly about one of 10-40 calls.

Some debugging info in attachment.

SOAP::Lite, SSL and timeout

Andreas Lamprecht — Fri, 12 Apr 2013 08:33:48 -0000

Hello!

I'm creating a soap handler with the following code:

$soap = new SOAP::Lite(uri => $URI);
$soap->proxy($ENDPOINT, timeout => $Conf::Timeout, proxy => [ "http" => $HTTP_PROXY ] );

The timeout is working for perfectly for HTTP connections. But if HTTPs is used, the timeout is always 60 seconds.
So i think the configured timeout is not forwared to SSLeay.

SOAP::Lite and Tibco

Andreas Lamprecht — Fri, 12 Apr 2013 08:27:09 -0000

We are using SOAP::Lite (version 0.712) for sending events to some Event correlation system from a company called "Tibco".
Our script talks to a Apache tomcat-server which is part of Tibco software suite.

There is a problem with one of the HTTP-headers sent by SOAP::Lite, namely "Accept". SOAP::Lite creates this header as an array, wich produces multiple "Accept" headers:

Accept: text/xml
Accept: multipart/*
Accept: application/soap

Unfortunately that Tibco tomcat-server is not able to handle such multiple headers and throws an internal server error.

As a quick fix, i changed line 151 in SOAP/Transport/HTTP.pm from

Accept => ['text/xml', 'multipart/*', 'application/soap'] );
to
Accept => 'text/xml, multipart/*, application/soap' );

This produces just one "Accept:" header and Tibco tomcat is happy again.

I'm quite sure that i will not succeed by blaming Tibco for writing software which doesn't accept standard HTTP headers, so is there a chance my little fix could be integrated into SOAP::Lite "officially"?