SOAP Native service flop: "Connection closed..", ready for production???
seanzhMar 17 2011 — edited Mar 17 2011Our system: Oracle 11GR2 on Linux X64 CentOS.
I followed instructions like here: http://www.oracle-base.com/articles/11g/NativeOracleXmlDbWebServices_11gR1.php, so far so good, I can display the WSDL on broswer. Now for real world testing, I wrote a Visual studio.net 2010 application to use the service, after the very first time ( successfullly returned value), I got exception like:
The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
I googled and tried all kinds of tricks, like keepalive=TRUE but no joy. Some people suggested .net has a bug so I use SOAPUI and SOAPsonar, which returnes the same "The Underlying connection was closed" error; I tried to make the session timeout as long as possible still no help, I seem to run out of options, so I tried to configure Oracle HTTP server(instead of the Embeded Gateway) an entry point for /orawsv ( I found no existing sample for this kind of using HTTP server with web service configuration so I took one from APEX configuration inside the dads.conf file ) but it did not work out, so there is almost the end of my native web service miracle(no coding) solution....
The only working case for Oracle SOAP service is : when I use Oracle APEX, it's working fine without any flops. looks like any non-Oracle client won't take Oracle SOAP service from XDB......
Questions:
1. Does anyone else have real working case by using NON-Oracle client application with Oracle XMLDB native web serivices?
2. is it possible to configure Oracle HTTP server 10G working with this native services?
3. Did I miss any parameters on xdbconfig.xml so this kind of death sentence won't happen? ( almost everything is default except the HTTP PORT#)
Any suggestions and advises are greatly appreciated
Edited by: seanzh on Mar 17, 2011 10:28 AM
Edited by: seanzh on Mar 17, 2011 10:29 AM
Edited by: seanzh on Mar 17, 2011 10:31 AM