Jersey Robot

@glassfishrobot Commented khurram_kk said: In variables the header variable having value ``` {Content-Type=[application/json], Access-Control-Allow-Origin=[http://localhost:9000 ], Access-Control-Allow-Methods=[GET, POST, DELETE, PUT], Access-Control-Allow-Headers=[Content-Type, USER-TOKEN], X-Jersey-Tracing-000=[START [ ---- / ---- ms | ---- %]...

@glassfishrobot Commented @pavelbucek said: Well, that seems like Jersey returned HTTP 200 and the container converted it to something else. (Assuming that you are debugging the right requires/response pair, but...

@glassfishrobot Commented khurram_kk said: I told you same in very start that jersey returning 200, it is with container. I haven't got any servlet filter but yes there are two...

@glassfishrobot Commented khurram_kk said: Break point at Line 194 ``` public void commit() { try { callSendError();******** ``` The variables are ``` this ResponseWriter (id=83) asyncExt AsyncContextDelegateProviderImpl$ExtensionImpl (id=119) configSetStatusOverSendError false...

@glassfishrobot Commented khurram_kk said: Added break point on 239 ``` public void failure(final Throwable error) { try { if (!response.isCommitted()) {******* ``` It never reached.

@glassfishrobot Commented khurram_kk said: Oooooops, even if failure is not reching and every thing fine, let me check keepAliveTimeout setting of tomcat ... as first time it takes a bit...

@glassfishrobot Commented khurram_kk said: But during debug, it took very long time but connection was not closed .... confusing

@glassfishrobot Commented This issue was imported from java.net JIRA JERSEY-3156

* **Issue Imported From:** https://github.com/jersey/jersey/issues/3384 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @mpotociar

@glassfishrobot Commented Reported by djairball