Hi Vahram,

We are faced with similar issue resulting in the same kind of log statements. I 
have another thread with subject "Subscription Queue Full”. There is no 
resolution yet for that.

Thanks,
Mangesh


From: Vahram Aharonyan <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Monday, October 23, 2017 at 6:33 AM
To: "[email protected]" <[email protected]>
Subject: Client queue full

Hi,

We have partitioned region and trying to invoke create(key, value) on that. On 
the other side we have listener registered so once new entry is created we 
should get notified. Instead of that we’re hitting this kind of messages 
continuously:

[warning 2017/10/23 05:23:38.145 PDT 31d0a20b-d81d-490b-b2ff-19645ed52387 <Task 
Processor worker thread 4> tid=0x5c0] Client queue for 
_gfe_non_durable_client_with_id_remote(74e9ba70-d7fc-47a1-abbc-4d9066511049:20486:loner):44573:bbf05510:
 74e9ba70-d7fc-47a1-abbc-4d9066511049_2_queue client is full.

[info 2017/10/23 05:23:38.497 PDT 31d0a20b-d81d-490b-b2ff-19645ed52387 <Task 
Processor worker thread 4> tid=0x5c0] Resuming with processing puts ...

[warning 2017/10/23 05:43:54.778 PDT 31d0a20b-d81d-490b-b2ff-19645ed52387 
<SavePropertiesCompletionHandler> tid=0x100] Client queue for 
_gfe_non_durable_client_with_id_remote(74e9ba70-d7fc-47a1-abbc-4d9066511049:20486:loner):44573:bbf05510:
 74e9ba70-d7fc-47a1-abbc-4d9066511049_2_queue client is full.

[info 2017/10/23 05:43:54.879 PDT 31d0a20b-d81d-490b-b2ff-19645ed52387 
<SavePropertiesCompletionHandler> tid=0x100] Resuming with processing puts ...

Could someone provide some information in which circumstances this queue gets 
full and how it should be emptied?

Thanks,
Vahram.

Reply via email to