We are trying to set up an export from a web service using a Webs Service SOAP datastore. Everything works fine, I can import the functions from the data store and place it in a query transform. All looks good until I run the job and get the following error:
"SOAP-ENV:Fault SOAP-ENV:Server An error has occurred while generating the page.
No: x00000009
Source: WizMod6_0_2
Description: Subscript out of range </SOAP-ENV:Fault>
"
DS patch level is 14.2.2.446
The webservice URL is an https:// address
the error is coming from the Server hosting the webService, is the SERVER_CERT correctly in the axis2.xml ? I don’t think it’s a https issue else you would see a different error
I think the input that you are sending from DS may not be correct
and the followig in the axis2.xml
<module=“logging”/>
before
<module=“addressing”/>
and run the job from command line with additional -D -np, check the %DS_COMMON_DIR%\log\axis2_log.txt file for the SoapMessage that is send from DS and check what is difference between that and the one that you are using in SoapUI
Thanks for the reply Manoj. We’ve run it via command line and it returns an error that I’ve read before that we should ignore, and the
We are ignoring this error as per other findings on the net, including this forum.
[Mon Aug 18 13:35:53 2014] [error] …\axiom\src\parser\libxml2\libxml2_reader_wrapper.c(305) Error occurred creating XML stream reader
[Mon Aug 18 13:35:53 2014] [error] …\neethi\src\util.c(37) Out of memory
We then get the following in the log file which to me, doesn’t show any errors at all.
[Mon Aug 18 13:35:53 2014] [info] Starting addressing out handler
[Mon Aug 18 13:35:53 2014] [debug] …\src\modules\mod_addr\addr_out_handler.c(133) No action present. Stop processing addressing
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\transport\http\sender\http_transport_sender.c(246) ctx_epr:https://url
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\transport\http\sender\http_transport_sender.c(805) using axis2 native http sender.
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\transport\http\sender\http_sender.c(416) msg_ctx_id:urn:uuid:4d591f66-10fc-4772-be0c-026839d087b0
[Mon Aug 18 13:35:53 2014] [info] [ssl client] Client certificate chain filenot specified
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\transport\http\sender\http_transport_sender.c(822) OP name axutil_qname_get_localpart = http://www.w3.org/2004/08/wsdl/out-in
[Mon Aug 18 13:35:53 2014] [debug] …\axiom\src\soap\soap_builder.c(930) Identified soap version is soap11
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler request_uri_based_dispatcher within the phase Transport
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler AddressingInHandler within the phase Transport
[Mon Aug 18 13:35:53 2014] [info] Starting addressing in handler
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler addressing_based_dispatcher within the phase Transport
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler LoggingInHandler within the phase PreDispatch
[Mon Aug 18 13:35:53 2014] [info] Starting logging in handler …
[Mon Aug 18 13:35:53 2014] [info] Input message: <SOAP-ENV:Envelope xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:Encoding=“http://schemas.xmlsoap.org/soap/encoding/” xmlns:SOAP-ENV=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsd=“http://www.w3.org/2001/XMLSchema”>
<SOAP-ENV:Body SOAP-ENV:encodingStyle=“http://schemas.xmlsoap.org/soap/encoding/”> SOAP-ENV:Fault </SOAP-ENV:Fault> </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler rest_dispatcher within the phase Dispatch
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\soap_body_disp.c(127) Checking for service using SOAP message body’s first child’s namespace URI : http://schemas.xmlsoap.org/soap/envelope/
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler soap_action_based_dispatcher within the phase Dispatch
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\soap_action_disp.c(89) Checking for service using SOAPAction is not implemented
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch
[Mon Aug 18 13:35:53 2014] [debug] …\src\core\engine\phase.c(210) Invoke the handler context_handler within the phase PostDispatch
[Mon Aug 18 13:35:53 2014] [info] [rampart][rampart_mod] rampart_mod shutdown
search for Output message in the axis2_log.txt file, you see the SoapMessage that is sent by DS WS Client, copy that XML and use SoapUI to send the same input message, if you get the exact same error ,then check the input for missing element or incorrect XML
you will have to fix the Dataflow to generate a correct input if the problem is with the input
Thanks again Manoj. I took the output from the axis log and sure enough, got the same error when running it in SOAP UI.
I was able to fix this in SOAP UI by moving the SOAPHeader tags outside of the BODY tag. After that it works. Not sure how to do this in DS just yet though.
how does the Input Schema Looks like in DS for the function ? did you modify the WSDL ? will it be possible for you to post the WSDL or email it to me at mdhyani at hotmail
(BOB member since 2012-03-19)