Hi Frank, we've run into a problem with Qt 4.8 and the new threaded QNAM implementation too.
See QTBUG-20924. We guess that some socket closed notification arrives too late now because it is no longer a direct signal/slot connection but goes through the event loop now. The result is a 99 error too. Nils On Sun, Dec 18, 2011 at 6:00 PM, Frank Hemer <fr...@hemer.org> wrote: > Since qt4.8.0, qtsoap with payload size > 8Mb fails. > When using qt4.7.x, the _identical_ data transmission works like a charm. > > Watching the data transmission via tcpmon shows the request gets never sent. > QNetworkAccessManager reports 'Network transport error (99): Unknown error' > > Details: > This happens when issuing the mentioned SOAP call as a second call, the first > call (small data footprint) works without a problem. > Waiting a while (~1minute) before issuing the second (big) call makes it work. > > I happen to remember there were some changes in NetworkManager regarding > caching and repeated calls to the same address ... > Does this ring a bell for anyone? > > Thanx > Frank > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest -- Dipl. Inform. Nils Jeisecke fon: +49 (0) 521 - 329647-12 fax: +49 (0) 521 - 329647-40 email: jeise...@saltation.de --------------- saltation GmbH & Co. KG | Niederwall 43 | 33602 Bielefeld Sitz Bielefeld | Amtsgericht Bielefeld HRA 15344 Persönlich haftende Gesellschafterin: saltation Beteiligungs-GmbH | Niederwall 43 | 33602 Bielefeld Sitz Bielefeld | Amtsgericht Bielefeld HRB 39339 Geschäftsführer: Daniel Brün --------------- _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
