Error for documents having large number of family members
Posted: Wed Feb 19, 2014 11:12 am
Hi,
We are currently using RESTful services 3.1 version for INPADOC family retrieval (family-and-legal-and-biblio-retrieval). Please see below the error logs in the response that i retrieved from OPS for publication number CN101563098A. But this document is having 597 family members in it.
04:20:20(02/19) DEBUG com.lxnx.ols.tp.search.model.FamilyInfoService : Response retrieved from OPS after REST request is sent : {X-RegisteredQuotaPerWeek-Used=[629910313], Cache-Control=[proxy-revalidate], Server=[Apache], X-IndividualQuotaPerHour-Used=[444], Content-Type=[application/xml], Connection=[Keep-Alive], X-API=[ops-v3.1], Content-Length=[222], Date=[Wed, 19 Feb 2014 09:20:38 GMT], Content-Language=[en], X-Throttling-Control=[idle (images=green:200, inpadoc=green:60, other=green:1000, retrieval=green:200, search=green:30)], null=[HTTP/1.1 413 Request Entity Too Large]}
04:20:20(02/19) DEBUG com.lxnx.ols.tp.search.model.FamilyInfoService : Error in FamilyInfoSerivce.getOPSFamilyAndLegalAndBiblioRetrieval() while retrieving response : <?xml version="1.0" encoding="UTF-8" standalone="yes"?><fault xmlns="http://ops.epo.org"> <code>SERVER.LimitedServerResources</code> <message>Please request bibliographic data in smaller chunks</message></fault>
Not only for this document, we are facing the similar issue for few other documents as well, which are having large number of family members for them. From the OPS document i can see
"In situations when the requested family is very large (several hundred members), all of
the members cannot be included in the response due to technical reasons. The patentfamily
structure is returned with attribute truncatedFamily="true" and only a
limited number of family members are returned." So, if the issue that we are facing is becuase of large family members, doesn't OPS provide atleast few family members in the response with truncated family attribute as true. Can you please let us know why are we facing this issue.
Please see below the request headers and request body that we sent to OPS.
Request URI : http://ops.epo.org/3.1/rest-services/fa ... blio,legal
Headers :
Content-Type : application/ops+xml
Authorization : "Bearer " + accessToken
Method : POST
Request Body : CN.101563098.A
Thanks,
Rohini
We are currently using RESTful services 3.1 version for INPADOC family retrieval (family-and-legal-and-biblio-retrieval). Please see below the error logs in the response that i retrieved from OPS for publication number CN101563098A. But this document is having 597 family members in it.
04:20:20(02/19) DEBUG com.lxnx.ols.tp.search.model.FamilyInfoService : Response retrieved from OPS after REST request is sent : {X-RegisteredQuotaPerWeek-Used=[629910313], Cache-Control=[proxy-revalidate], Server=[Apache], X-IndividualQuotaPerHour-Used=[444], Content-Type=[application/xml], Connection=[Keep-Alive], X-API=[ops-v3.1], Content-Length=[222], Date=[Wed, 19 Feb 2014 09:20:38 GMT], Content-Language=[en], X-Throttling-Control=[idle (images=green:200, inpadoc=green:60, other=green:1000, retrieval=green:200, search=green:30)], null=[HTTP/1.1 413 Request Entity Too Large]}
04:20:20(02/19) DEBUG com.lxnx.ols.tp.search.model.FamilyInfoService : Error in FamilyInfoSerivce.getOPSFamilyAndLegalAndBiblioRetrieval() while retrieving response : <?xml version="1.0" encoding="UTF-8" standalone="yes"?><fault xmlns="http://ops.epo.org"> <code>SERVER.LimitedServerResources</code> <message>Please request bibliographic data in smaller chunks</message></fault>
Not only for this document, we are facing the similar issue for few other documents as well, which are having large number of family members for them. From the OPS document i can see
"In situations when the requested family is very large (several hundred members), all of
the members cannot be included in the response due to technical reasons. The patentfamily
structure is returned with attribute truncatedFamily="true" and only a
limited number of family members are returned." So, if the issue that we are facing is becuase of large family members, doesn't OPS provide atleast few family members in the response with truncated family attribute as true. Can you please let us know why are we facing this issue.
Please see below the request headers and request body that we sent to OPS.
Request URI : http://ops.epo.org/3.1/rest-services/fa ... blio,legal
Headers :
Content-Type : application/ops+xml
Authorization : "Bearer " + accessToken
Method : POST
Request Body : CN.101563098.A
Thanks,
Rohini