We only use the Apache HttpClient if requested.  To do this, initialize an object of class EsuRestApiApache instead of the usual EsuRestApi.  I just tested the log4j setting above and got the low-level tracing:   15:09:07,447 DEBUG [main] ThreadSafeClientConnManager$1: Get connection: HttpRoute[{}->[URL] timeout = 0 15:09:07,447 DEBUG [main] ConnPoolByRoute: [HttpRoute[{}->[URL] total kept alive: 0, total issued: 0, total allocated: 0 out of 200 15:09:07,447 DEBUG [main] ConnPoolByRoute: No free connections [HttpRoute[{}->[URL] 15:09:07,447 DEBUG [main] ConnPoolByRoute: Available capacity: 200 out of 200 [HttpRoute[{}->[URL] 15:09:07,448 DEBUG [main] ConnPoolByRoute: Creating new connection [HttpRoute[{}->[URL] 15:09:07,448 DEBUG [main] DefaultClientConnectionOperator: Connecting to /10.242.26.242:80 
Its my understanding that Atmos Java API uses Apache HttpClient to make REST calls. Since HttpClient can log to the console (see [URL] I was hopeful to see the GET commands in my Eclipse console by adding to my log4j.properties file:             log4j.logger.org.apache.http=DEBUG  I know the logging works since I deliberatedly added a few logging lines to make sure log4j was setup correctly. Any ideas would be appreciated.  Sincerely,  Jeff
Logging Atmos Java API HttpClient calls