search

danielgary / xmlrpcnet

Automatically exported from code.google.com/p/xmlrpcnet
0 stars 0 forks source link

Stream Closed Error when a ResponseEvent has been assigned. #74

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
Issue - If a proxy call is made with a ResponseEvent assigned, the call crashes 
with a "Stream Closed" error.

Note: I am using Microsoft Visual C# 2008 Express Edition and the call that I 
am making is failing because of a Serialization error.

What is the expected output? What do you see instead?
The crash occurs in XmlRpcClientProtocol.cs at line 214.

What version of the product are you using? On what operating system?
xml-rpc.net.2.5.0
Windows XP SP3

Please provide any additional information below.

Original issue reported on code.google.com by pe...@whitechsolutions.com on 10 Sep 2010 at 5:56

GoogleCodeExporter commented 8 years ago

Original comment by ChasC...@gmail.com on 23 Sep 2010 at 7:30

GoogleCodeExporter commented 8 years ago 
The exact exception message is: Cannot access a closed Stream.
Stack trace:
   at System.IO.MemoryStream.set_Position(Int64 value)
   at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, MethodInfo mi, Object[] parameters)
   at XmlRpcProxy94ff141c-ce80-45b7-8ec5-e625b41c4148.GetAccount(Object request)

Original comment by eran.bet...@gmail.com on 11 Oct 2010 at 8:44

GoogleCodeExporter commented 8 years ago 
Found the problem at XmlRpcSerializer.cs:512 - the "using" need to be removed.

Original comment by eran.bet...@gmail.com on 12 Oct 2010 at 9:53

GoogleCodeExporter commented 8 years ago 
Have added a failing unit test for this.

Original comment by ChasC...@gmail.com on 12 Oct 2010 at 7:11

GoogleCodeExporter commented 8 years ago 
Fixed in revision 130.

Original comment by ChasC...@gmail.com on 12 Oct 2010 at 7:40

GoogleCodeExporter commented 8 years ago

Original comment by ChasC...@gmail.com on 12 Oct 2010 at 7:40

GoogleCodeExporter commented 8 years ago

Original comment by ChasC...@gmail.com on 6 Mar 2011 at 10:24

GoogleCodeExporter commented 8 years ago 
Should be possible that this bug affects 2.5.0 production release?

My application, using an XmlRpcLogger, crashes after sending an rpc call with:

System.ObjectDisposedException: Cannot access a closed Stream.
   at System.IO.__Error.StreamIsClosed()
   at System.IO.MemoryStream.set_Position(Int64 value)
   at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, MethodInfo mi, Object[] parameters)
   at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(MethodInfo mi, Object[] Parameters)
   at XmlRpcProxyf4467cc2-996d-4b1d-b60a-8584618b362d.Install(InstallRequest param)
   at Magenta.FZPFProxy.Operations.SystemUpgrade.XmlRpcPackageManager.Install(Manifest manifest, String source, DateTime activationDate, String labelVersion, Uri origin) in C:\Sviluppo\fzpf\FzpfProxy\Operations\SystemUpgrade\XmlRpcPackageManager.cs:line 140

But if I remove the XmlRpcLogger will work as expected.

Original comment by alessio....@magentalab.it on 10 Jan 2013 at 11:17

GoogleCodeExporter commented 8 years ago 
My bad. I didn't noticed the version on the report. It will surely affects 
2.5.0 release.

There's any hope of a 2.5.1 bugfix release ? Or should I cross my finger and 
upgrade to 3.0.0 snapshot?

Original comment by alessio....@magentalab.it on 10 Jan 2013 at 11:19

albgen commented 4 years ago

hello,

any news on this. This bug is still present and there is no way we can log/analyze the xml request/response.

thank you.