@Rahul
> Can you try to remove SSL, authentication and see if it makes a difference?
>
No I can't remove SSL, the webservice I'm calling is not really under my
control.
Once again its really weird that if I run the same jersey-client code as a
standalone java program, there are no problems. But when I try to broker
the communication between other clients and the webservice by acting as a
man-in-the-middle via the jersey-servlet ... then this issue pops up. Has
there ever been any history of jersey-client and jersey-server butting
heads when running on tomcat, in the past?