Hi Paul, we added the filter. The server resource is defined as my example
below (just a different URL and jaxb type).
And the exception happens more often if we are increasing the threads
accessing the server.
This is the request:
4 * Out-bound request
4 > GET
http://as2-srv-ts:8080/OspWS/V1/BorderGuardOrganisation/sector/ids/
4 > Authorization: Basic b3NyOmNvcw==
4 > Accept: application/xml
4 >
This is the received request on server side:
75 * In-bound request received
75 > GET
http://as2-srv-ts:8080/OspWS/V1/BorderGuardOrganisation/sector/ids/
75 > authorization: Basic b3NyOmNvcw==
75 > connection: keep-alive
75 > cache-control: no-cache
75 > host: as2-srv-ts:8080
75 > user-agent: Java/1.6.0_07
75 > pragma: no-cache
75 > accept: application/xml
75 >
And this is the received (wrong) response (I've shortened the binary stuff):
4 < 200
4 < Transfer-Encoding: chunked
4 < Server: Apache-Coyote/1.1
4 < Date: Fri, 10 Jul 2009 11:20:06 GMT
4 <
Cb?6???O?ll?0?&?x?9?n???eĀ??w??1??(i6d?3?R?????=?Z?^?
??^??? Ҙ?{?}+
?m
OB??TM?Ed???8Rr?-fߺ??/?????ѱC???/?????ɎCw?e????QnJa???)K?D1?<Pj
???[?wPL??d??Q?????荌???E?ܿ?]_4?/??vkp??}|B?r??KvN3z?=???k
???p4?As'4$??\???q???~?pwn????%??????<jt?»?9,?:E{??֪?p?v/'???ir?^??1p??y???
C?k?W?X~u?l? ??g%O
HfITE?VHS? Y?_o?
4 * In-bound response
ERROR [Thread-337] .eads.web.rrs.DataManager Unable to load Sectors/RRSs
com.eads.ospws.client.service.OspWSServiceException: Failure to process the
HTTP request or HTTP response
in Class: com.eads.ospws.client.service.BorderEventClientService
in Method: getSectors
at
com.eads.ospws.client.service.BorderEventClientService.getSectors_aroundBody
1$advice(BorderEventClientService.java:25)
at
com.eads.ospws.client.service.BorderEventClientService.getSectors(BorderEven
tClientService.java:1)
at com.eads.web.rrs.DataManager.loadSectors(DataManager.java:282)
at com.eads.web.rrs.InitialDataLoader.run(InitialDataLoader.java:28)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.jersey.api.client.ClientHandlerException: A message body
reader for Java type, class com.eads.ospws.resource.jaxb.IdArray, and MIME
media type, application/octet-stream, was not found
at
com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:255)
at
com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:220)
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:561)
at com.sun.jersey.api.client.WebResource.access$300(WebResource.java:69)
at
com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:451)
at
com.eads.ospws.client.service.BorderEventClientService.getSectors_aroundBody
0(BorderEventClientService.java:59)
at
com.eads.ospws.client.service.BorderEventClientService.getSectors_aroundBody
1$advice(BorderEventClientService.java:23)
... 4 more
Regards Christopher
Am 10.07.09 10:48 schrieb "Paul Sandoz" unter <Paul.Sandoz_at_Sun.COM>:
>
> On Jul 10, 2009, at 8:22 AM, Christopher Schmidt wrote:
>
>> Hi Paul, we are using also a Servlet as a client.
>
> OK, i thought so.
>
>
>> The servers logging is configured like this:
>>
>> <init-param>
>>
>> <param-name>com.sun.jersey.spi.container.ContainerRequestFilters</param-name>
>>
>> <param-value>com.sun.jersey.api.container.filter.LoggingFilter</param-value>
>> </init-param>
>>
>
> Can you also add:
>
> <init-param>
>
> <param-name>com.sun.jersey.spi.container.ContainerResponseFilters</param-name>
>
> <param-value>com.sun.jersey.api.container.filter.LoggingFilter</param-value>
> </init-param>
>
> So that the responses get logged?
>
>
>> Can I do something like this for your mentioned client filter as well?
>>
>
> Yes.
>
> Client c = ...
> c.addFilter(
> new com.sun.jersey.api.client.filter.LoggingFilter());
>
>
> Hopefully that should give us additional information to close in on where the
> problem is located.
>
> Paul.
>
>> Regards Christopher
>>
>>
>> Am 09.07.09 13:18 schrieb "Paul Sandoz" unter <Paul.Sandoz_at_Sun.COM>:
>>
>>
>>> Hi Christopher,
>>>
>>> Given that this happens about 0.01 % of the time i am wondering if there is
>>> a subtle race condition in the Tomcat server when setting response headers.
>>> All Jersey does is pass it's headers over to the servlet response.
>>>
>>> Do you have also logging of the "Out-bound response sent" from the server
>>> to the client? it would be useful to know if the content-type was set
>>> correctly by Jersey.
>>>
>>> You can also ad logging to the client side as well:
>>>
>>>
>>> https://jersey.dev.java.net/nonav/apidocs/1.1.0-ea/jersey/com/sun/jersey/api
>>> /client/filter/LoggingFilter.html
>>>
>>> Maybe some tomcat-level logging of response headers would also be useful?
>>>
>>> Paul.
>>>
>>> On Jul 9, 2009, at 9:40 AM, Christopher Schmidt wrote:
>>>
>>>
>>>> Hello, sometimes when I access the following resource method (TargetEnh is
>>>> a subclassed JAXB object):
>>>>
>>>> @GET @Produces("application/xml") @Path("target/object/{tId}/")
>>>> @RequiresMorphSession public Target getTarget(@PathParam("tId") String
>>>> tId) { ... return new TargetEnh(oi, getUser()); }
>>>>
>>>> With the following client code:
>>>>
>>>> return getTargetResource().path("target/object/" +
>>>> targetId).header("Authorization", user.userCredentials()).accept(
>>>> MediaType.APPLICATION_XML).get(Target.class);
>>>>
>>>> I get sometimes the following exception.
>>>>
>>>> 115131 * In-bound request received
>>>> 115131 > GET
>>>> http://as2-srv-ts:8080/OspWS/V1/Target/target/object/953111100000169
>>>> 115131 > authorization: Basic b3NyOmNvcw==
>>>> 115131 > connection: keep-alive
>>>> 115131 > cache-control: no-cache
>>>> 115131 > host: as2-srv-ts:8080
>>>> 115131 > user-agent: Java/1.6.0_07
>>>> 115131 > pragma: no-cache
>>>> 115131 > accept: application/xml
>>>> 115131 >
>>>> ERROR [Thread-156] .eads.web.rrs.DataManager <http://web.rrs.DataManager>
>>>> <http://web.rrs.DataManager> Unable to update Track
>>>> com.eads.ospws.client.service.OspWSServiceException: Failure to process
>>>> the HTTP request or HTTP response
>>>> in Class: com.eads.ospws.client.service.BorderEventClientService
>>>> in Method: getTarget
>>>> at
>>>> com.eads.ospws.client.service.BorderEventClientService.getTarget_aroundBody
>>>> 19$advice(BorderEventClientService.java:25)
>>>> at
>>>> com.eads.ospws.client.service.BorderEventClientService.getTarget(BorderEven
>>>> tClientService.java:1)
>>>> at com.eads.web.rrs.WebObjectFactory.updateLocation
>>>> <http://web.rrs.WebObjectFactory.updateLocation>
>>>> <http://web.rrs.WebObjectFactory.updateLocation> (WebObjectFactory.java:84)
>>>> at com.eads.web.rrs.DataManager.updateTrack
>>>> <http://web.rrs.DataManager.updateTrack>
>>>> <http://web.rrs.DataManager.updateTrack> (DataManager.java:865)
>>>> at com.eads.web.rrs.DataManager.fireNotification
>>>> <http://web.rrs.DataManager.fireNotification>
>>>> <http://web.rrs.DataManager.fireNotification> (DataManager.java:784)
>>>> at com.eads.web.rrs.notification.NotificationQueue.run
>>>> <http://web.rrs.notification.NotificationQueue.run>
>>>> <http://web.rrs.notification.NotificationQueue.run>
>>>> (NotificationQueue.java:74)
>>>> Caused by: com.sun.jersey.api.client.ClientHandlerException: A message
>>>> body reader for Java type, class com.eads.ospws.resource.jaxb.Target, and
>>>> MIME media type, application/octet-stream, was not found
>>>> at
>>>> com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:255)
>>>> at
>>>> com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:220)
>>>> at com.sun.jersey.api.client.WebResource.handle(WebResource.java:561)
>>>> at
>>>> com.sun.jersey.api.client.WebResource.access$300(WebResource.java:69)
>>>> at
>>>> com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:451)
>>>> at
>>>> com.eads.ospws.client.service.BorderEventClientService.getTarget_aroundBody
>>>> 18(BorderEventClientService.java:194)
>>>> at
>>>> com.eads.ospws.client.service.BorderEventClientService.getTarget_aroundBody
>>>> 19$advice(BorderEventClientService.java:23)
>>>> ... 5 more
>>>>
>>>>
>>>> It seams to me that the response header does not contain a “content-type”
>>>> field.
>>>> This only happens about 3-10 times per day calling this GET method about
>>>> 2 times per second.
>>>>
>>>> (using Tomcat 6, Jersey 1.0.3 on a linux 64bit system)
>>>>
>>>> Any suggestions?
>>>>
>>>> Best regards
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>