3 Replies Latest reply on Nov 3, 2016 1:53 AM by Panagiotis Chavariotis

    JBoss EAP 6.2.0  Connection Timeout and Keep Alive Settings

    Bisrat Dinka Newbie

      At my company we're utilizing JBoss EAP 6.2.0 (which is embedded with JBoss Application Server 7.x.x) for hosting Adobe LiveCycle application which performs a variety of manipulation to PDF documents:

      • Apply Watermwark
      • Apply Digital Signatures
      • Apply Rights Manage


      We're calling the the aforementioned functionalities to manipulate the PDF documents via SOAP protocol Web Service calls to the Adobe LiveCycle application.     The problem we're having is when calling these via SOAP Web Service calls we get connection timeout exceptions like one below:



      Caused by: java.net.SocketTimeoutException: Read timed out

      at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)

      at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)

      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 org.studentclearinghouse.to.digitaltranscript.livecycleclient.services.certify.CertifyPDFStub.invoke(CertifyPDFStub.java:156)

      at org.studentclearinghouse.to.digitaltranscript.DigitalTranscriptManager.certify(DigitalTranscriptManager.java:348)

      ... 45 more

      Caused by: java.net.SocketTimeoutException: Read timed out

      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.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583)

      at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)

      ... 56 more




      AS you can see from the Exception Stack Trace there is a "Socket Timeout Exception" being thrown.    I was curious what the configuration settings would be for increasing the HTTP Socket Timeout values in JBoss EAP 6.2.0.   


      I found the following link for setting system property values via standalone.conf file for JBoss Web:  http://docs.jboss.org/jbossweb/7.0.x/sysprops.html for the following two properties:


      • org.apache.coyote.http11.DEFAULT_CONNECTION_TIMEOUT    Default socket timeout. The default value is 60000 ms.
      • org.apache.coyote.http11.DEFAULT_KEEP_ALIVE_TIMEOUT    Default socket timeout for keep alive. The default value is -1 ms, which means it will use the default socket timeout.


      I also found the following Stack Overflow Post which mentions the above two configuration parameters are only available in JBoss Application Server 7.1.2:   jboss7.x - JBoss 7.1.1 Http Connection Timeout - Stack Overflow.


      So my question is are the above two parameter available for JBoss EAP 6.2.0 which is embedded with JBoss Application Server 7.x.x.


      Looking forward to hearing back from someone on this issue.