From: "NAKAMURA, Hiroshi" Date: 2006-08-08T10:54:13+09:00 Subject: Re: Soap and Http-access problem. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Ola Bini wrote: > I'm using Soap4R 1.5.5. Regarding the old_send, that's the result of > monkey_patching, since I add some big problems with another thing. Hmm. > old_send is just send renamed. But this shouldn't be the problem, it > works on another machine and has worked on this machine. The monkey > patching looks like this: [snip] Agreed. No suspicious part in old_send. I think "Bad file descriptor - connect(2) (, #0)" is caused by TCPSocket.new("0.0.0.0", 0). "0.0.0.0" and 0 is a default value of accessing Site representation in http-access2. Site is used for representing 1) destination http server and 2) http proxy server. And for now, with regard to 1), there's no suspicious part. Do your production and development environment both uses http proxy to access foreign WS? > module SOAP > class HTTPStreamHandler > alias :old_send :send > def send(endpoint_url, conn_data, soapaction = nil, charset = @charset) > ret = old_send(endpoint_url,conn_data,soapaction,charset) > if ret.receive_string =~ /.*?(<\?xml.*?<\/soapenv:Envelope>).*?/m > ret.receive_string = $1 > end > ret > end > end > end > > and the reason that is is necessary can you find here: > http://ola-bini.blogspot.com/2006/08/rails-soap4r-and-java.html Hmm. There must be an attachment interoperability problem. Can I see entire response XML? Regards, // NaHi -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) iQEVAwUBRNfuqB9L2jg5EEGlAQKjKQf/XA1NOxjVES2ioLSJ+EY2kfskwaldnq5t FWd8Deo3l9QkVPCej16egBhULm1q6uJWqgTFDcTK4Z7DpR11QaozWemjP+UvNgpJ 8NjfncgpJcgSKRZXLDEOsgVY9MIBup5q7VU4qgGJxWmpek0lLgzFLgLP4ewEI9C+ C4TUYmH70CCmDkkVGgSX1mtVYxSMJJvJiW8tEWsyALJx5MI0BosDtaj5677bRbRB Nyyo0r9G88yJF9NM4bmGnRZh8yiX+hMa5nFq+2aai8/LN0lQdfIcI/e4dK+JaW7w nus7O7tNgQGG9795QCu6uhge7qFUWPi+GI1bKagEJsduSPC5oX5UfA== =8enK -----END PGP SIGNATURE-----