Posts tagged "webservice"

LiveCycle ES: java.net.SocketException using WebServices

Issue

 If you are using web services in your processes in LiveCycle ES or ES2, you may receive the following exception in the logs:

2011-04-20 17:30:44,072 ERROR [com.eviware.soapui.impl.wsdl.WsdlSubmit] Exception in request: java.net.SocketException: Software caused connection abort: recv failed
2011-04-20 17:30:44,072 ERROR [com.eviware.soapui.SoapUI] An error occured [Software caused connection abort: recv failed], see error log for details
2011-04-20 17:30:44,072 ERROR [soapui.errorlog] java.net.SocketException: Software caused connection abort: recv failed
java.net.SocketException: Software caused connection abort: recv failed
 at java.net.SocketInputStream.socketRead0(Native Method)
 at java.net.SocketInputStream.read(SocketInputStream.java:129)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
 at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
 at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)

This exception occus when the web service WSDL cannot be reached (i.e. network issues, port numbers, firewall).  It can also be related to database problems.

Troubleshooting

1. Check the web service is reachable and responds as expected.

2. Try to restart the database server.

Additional information

 http://forums.adobe.com/message/3203930

reference: (182264455)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.3/10 (4 votes cast)

LiveCycle ES: SAXParseException: White spaces are required between publicId and systemId.

Issue

If you have migrated from LiveCycle 7 to LiveCycle ES you may encounter the following exception when attempting to call a web service from an orchestration at runtime:

####<Feb 18, 2010 5:09:56 PM MET> <Warning> <com.adobe.workflow.AWS> <sunc01016> <wl01qalc01> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-56EAC5B49D0141CB0D30> <> <1266509396427> <000000> <ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error. 
...
Caused by: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error. 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:683) 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:688) 
 at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:970) 
 at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:836) 
 at com.adobe.workflow.datatype.runtime.support.AbstractDataTypeRuntimeHandler.coerceFrom(AbstractDataTypeRuntimeHandler.java:64) 
 at com.adobe.workflow.datatype.runtime.support.AbstractComplexDataTypeRuntimeHandler.getNode(AbstractComplexDataTypeRuntimeHandler.java:47) 
 at com.adobe.workflow.dom.VariableElement.setBoundValue(VariableElement.java:98) 
 at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataValue(PATExecutionContextImpl.java:813) 
 ... 116 more 
Caused by: org.xml.sax.SAXParseException: White spaces are required between publicId and systemId. 
 at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) 
 at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) 
 at com.adobe.idp.dsc.util.DOMUtil.parseDocumentFromString(DOMUtil.java:167) 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:607) 
 ... 123 more

When accessing the web service through the WebService component, you sometimes get a valid response using the test tab:

Solution

The web service is returning an invalid XML result. This error usually happens when the classpath for the server is not correctly set up. Check the classpath against the Adobe documentation, make any necessary changes, and then restart the application server.

In this case, the argument for the UTF-8 charset was not set correctly and therefore the input and output data for the WebService component was not correctly encoded.

reference: (181450296)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle 7: “Directory Exception javax.servlet.jsp.JspException” accessing webservice portal

Issue

When you try to access the web service portal in JBoss (http://localhost:8080/services/) using LiveCycle 7, you may receive the following error:

Web Service Directory Services
Directory Exception javax.servlet.jsp.JspException: 
An error occurred while evaluating custom action attribute "items" with value "${directoryBean.deployedServices}": 
An error occurred while getting property "deployedServices" from an instance of 
class com.adobe.workflow.service.WorkflowServiceDirectoryBean (java.lang.NullPointerException)

Solution

 Add the following lines to the service XML file: [appserver root]/server/all/conf/jboss-service.xml:

_____________________________________

<-- Isolate all ears in their own classloader space -->
<attribute name="Isolated">true</attribute>
<-- Enforce call by value to all remote interfaces -->
<attribute name="CallByValue">true</attribute>

_____________________________________

reference: (180009712)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)