using the deployment script we deploy an lca after about 10 minutes the script errors with the following message, but the deployment continues and completes successfully.
ALC-DSC-099-000: com.adobe.idp.applicationmanager.application.ApplicationManagerException: java.net.SocketTimeoutException: Read timed out
at com.adobe.idp.applicationmanager.client.ApplicationManagerClient.callApplicationManager(ApplicationManagerClient.java:98)
at com.adobe.idp.applicationmanager.client.ApplicationManager.importApplicationArchive(ApplicationManager.java:165)
at com.adobe.idp.applicationmanager.deployment.ScriptedLCADeployment.importApplication(ScriptedLCADeployment.java:104)
at com.adobe.idp.applicationmanager.deployment.ScriptedLCADeployment.main(ScriptedLCADeployment.java:150)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
at org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatcher.java:127)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:66)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.idp.applicationmanager.client.ApplicationManagerClient.callApplicationManager(ApplicationManagerClient.java:78)
... 3 more
Has anyone encountered this and do you have a solution? we have tried modifying several websphere timeout value settings with no success.
We are working with LiveCycle ES3 (10.0) running on a Linux server hosted in WebSphere 8.0.
Views
Replies
Total Likes
Please increase SOAP timeout for WAS : AEM forms * 9.3 Configuring WebSphere time-out settings
Thanks
Wasil
Check out new AEM Forms 6.2
Views
Replies
Total Likes
Already increased the soap timeout to 1800. That doesn't resolve or affect the issue. Timeout occurs in less then 10 minutes.
Views
Replies
Total Likes
This actually uses Application Manager API : Adobe LiveCycle * Application Manager Service API Quick Starts
In ES4 onward SOAP timeout property was added for client SDK configuration : Adobe LiveCycle * Setting connection properties
You can try that (with ES4 or higher version)
Thanks
Wasil
Views
Replies
Total Likes
Wasil,
Not sure what you are suggesting for a solution to my ES3 timeout problem. Please clarify.
Thanks,
Andrew
Views
Replies
Total Likes
I suspect this is client side socket timeout issue with the script while deploying LCA. Setting timeout is available in ES4 onward. So, upgrade to ES4 or AEM Forms 6.0/6.1/6.2(latest AEM Forms 6.2). Therefore, in case after upgrade, same issue occurs you can use API to modify the behavior and write your own code.
HTH.
Thanks
Wasil
Views
Replies
Total Likes
Views
Likes
Replies