# Session took too long to respond error when we commiting 100 paramter

**URL:** <https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681>\
**Category:** Uncategorized\
**Created:** [June 3, 2022, 7:52am UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681 "2022-06-03T07:52:31Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Regin](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@Regin](https://forum.genieacs.com/u/Regin)\
**Post date:** [June 3, 2022, 7:52am UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681/1 "2022-06-03T07:52:31Z")

</div>

Hi,  
Iam getting the "Session took too long to respond error when we commiting 100 paramter " error frequently. @zaidka

Does CPE device need reboot after a successfull commit ?

---

<div class="post-metadata">

**Author:** ![zaidka](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/zaidka/32/9_2.png) [@zaidka](https://forum.genieacs.com/u/zaidka)\
**Post date:** [June 3, 2022, 4:23pm UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681/2 "2022-06-03T16:23:57Z")

</div>

The ACS doesn’t trigger a reboot. But it’s possible that the CPE decides to reboots itself if it deems necessary after changing certain parameters. It’s entirely at the discretion of the CPE.

---

<div class="post-metadata">

**Author:** ![akcoder](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/akcoder/32/11_2.png) [@akcoder](https://forum.genieacs.com/u/akcoder)\
**Post date:** [June 3, 2022, 4:38pm UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681/3 "2022-06-03T16:38:34Z")

</div>

My experience has been its always best to reboot the CPE after provisioning. Some of them straight up act really weird when setting up things like PPPoE. Example, SmartRG CPEs will continue to try and auth PPPoE even after successfully authenticating PPPoE and traffic is being routed. Other times, the CPEs will be in this half-assed working state and rebooting them without making any other changes causes things to work successfully.

---

<div class="post-metadata">

**Author:** ![Regin](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@Regin](https://forum.genieacs.com/u/Regin)\
**Post date:** [June 6, 2022, 5:51pm UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681/4 "2022-06-06T17:51:23Z")

</div>

Iam getting the "Session took too long to respond error when we commiting 100 paramter " error frequently. @zaidka any explaination?

---

<div class="post-metadata">

**Author:** ![Regin](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@Regin](https://forum.genieacs.com/u/Regin)\
**Post date:** [June 10, 2022, 5:31am UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681/5 "2022-06-10T05:31:45Z")

</div>

Hi ,  
Can you please respond my query @zaidka

---

<div class="post-metadata">

**Author:** ![cdavid14](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/cdavid14/32/898_2.png) [@cdavid14](https://forum.genieacs.com/u/cdavid14)\
**Post date:** [June 10, 2022, 5:34pm UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681/6 "2022-06-10T17:34:15Z")

</div>

you had same error using [GitHub - genieacs/genieacs-sim: TR-069 client simulator for GenieACS](https://github.com/genieacs/genieacs-sim) instead a real CPE? maybe the CPE is just not good enough to process this amount of data and end the session before finish the processing.

---

<div class="post-metadata">

**Author:** ![akcoder](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/akcoder/32/11_2.png) [@akcoder](https://forum.genieacs.com/u/akcoder)\
**Post date:** [June 10, 2022, 9:27pm UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681/7 "2022-06-10T21:27:49Z")

</div>

@Regin to add to what @cdavid14 said, try adding the following config to admin/config

key: cwmp.gpnNextLevel value: 3  
key: cwmp.gpvBatchSize value: 24

This will cause genieacs to send smaller batches of data to the CPE.

-dan

---

<div class="post-metadata">

**Author:** ![Regin](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@Regin](https://forum.genieacs.com/u/Regin)\
**Post date:** [June 13, 2022, 7:29am UTC](https://forum.genieacs.com/t/session-took-too-long-to-respond-error-when-we-commiting-100-paramter/2681/8 "2022-06-13T07:29:00Z")

</div>

we tried but getting same error. does this issue related to mongoDB? Because, when we trying 100 commit , the system get stock some times  
.
