Article Original Creation Date: 2012-07-03

Overview

2012-06-26 16:22:39,231 [10.109.26.125] INFO ACS - Unable to read device HTTP message java.net.SocketTimeoutException: Read timed out
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - Start logged SOAP message headers
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - header: name=host, value=acs.sunrise.ch
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - header: name=user-agent, value=Allegro-Software-WebClient/4.07
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - header: name=accept, value=*/*
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - header: name=content-type, value=text/xml; charset=utf-8
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - header: name=content-length, value=2863
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - End logged SOAP message headers
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - Start logged SOAP message content
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS -
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - End logged SOAP message content
2012-06-26 16:22:39,232 [10.109.26.125] INFO ACS - Unable to parse device message, returning code 400
2012-06-26 16:22:39,232 [10.109.26.125] DEBUG ACS - HTTP request processing time 20007 ms.

The same information shows up in Wireshark traces.

Environment

• Solaris 10
• Oracle 10
• JBoss 4.0.4GA

Root Cause

There are a few possible causes for the error discussed previously:

• The device is faulty.
• The Tomcat (server.xml) has a configuration for connection timeout of 20000 ms.
• There are network troubles during these device communications.

Information

In this case, it was found the devices acted faulty, causing the communication to end abruptly.