000034248 - RSA Identity Governance and Lifecycle Test Connector capabilities issue "Failed to create service" and "Unexpected EOF in prolog" messages

Document created by RSA Customer Support Employee on Nov 8, 2016•Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000034248
Applies ToRSA Product Set:  Identity Governance and Lifecycle
RSA Version/Condition:  6.9.1, 7.0.x
Product Description:  Access Fulfillment Express
IssueWhen testing connector capabilities, the following error is issued:
Failed to create service

Looking at the file with a name similar to <AFX_HOME>/mule/logs/mule.AFX_CONN_<connectorname>_test.log, we see first:
2016-09-27 07:59:22.091 [INFO] com.aveksa.AFX.server.runtime.mule.soap.mule.SoapDispatchComponent:197 - Issue encountered supported verb: 
CreateAccount, error is org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.
2016-09-27 07:59:22.093 [ERROR] com.aveksa.AFX.server.runtime.mule.soap.mule.SoapDispatchComponent:365 - Error occured while executing the capability
javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.
 at org.apache.cxf.jaxws.ServiceImpl.<init>

Further down the stack is the message:
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col,system-id]: [1,0,"http://xxxxxxxx:9080/WebSecurityWebService/services/WebSecurity?WSDL"]

The wsdl file works just fine in the SOAPUI.
CauseThe last error message, Unexpected EOF in prolog, indicates that there is a parsing issue in the wsdl file we try to reach.
When pulling up the wsdl file in Notepad++ or a similar editor, we can see that the lines are terminated by CRLF.
This indicates the wsdl file might have been created on Windows, and the Linux OS does not necessarily interpret this correctly; although SOAPUI is more forgiving and has no issue with the CR character.
ResolutionThe solution involves two steps:
  1. Edit the wsdl file and remove the CR characters at the end of the line. An example is provided below:
User-added image

  1. Convert the file to Unix format. For example, if you are using Notepad++, select Edit > EOL Conversion > UNIX/OSX Format. 
User-added image

  1. Save the file using File > Save.

Attachments

    Outcomes