My mobile application consumes REST services from Glassfish/Jersey.
In order to optimize bandwidth and minimize wait times for the user, I
have been progressively implementing HTTP 1.1 support in Java ME using
only a SocketConnection. So far, I have gotten gzip encoding and a
persistent connection to work.
However, I am unable to reliably pipeline requests. I am unsure what
I am doing wrong here but it seems after 2 to 4 responses, the
connection is closed on the server. My main problem however is that
Glassfish/Grizzly log absolutely nothing about what is going on.
The sequence usually is this:
1. Send 10 requests
2. Read back and process between 2-4 responses
3. Long blocking read
4. Read times out/connection closed
5. Glassfish log file has nothing in it
My question is this: Is there some obscure option here that I could
turn on that could provide insight into this problem? If I could see
the traffic that Grizzly is generating and the reason why it's closing
the connection, this would be of great value to me. Setting log
levels to FINEST in the glassfish consoles produces nothing of value
either.
thank you,
--
http://www.spectrumdt.com
http://codepimps.org