Debug Log started at: 2025-03-22 12:05:17[2025-03-22 12:05:19:120] [] [main] DeviceConnectTest INFO : Starting DeviceConnectTest on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:19:130] [] [main] DeviceConnectTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:19:131] [] [main] DeviceConnectTest INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:23:418] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:23:418] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:23:419] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:24:938] [] [main] DeviceConnectTest INFO : Started DeviceConnectTest in 6.207 seconds (JVM running for 8.506) [2025-03-22 12:05:25:023] [0005B9AAAA22] [main] ConnectionReqEventHandler INFO : Received a JMS message from Request Processor for initiating connection request [2025-03-22 12:05:25:024] [0005B9AAAA22] [main] ConnectionReqEventProcessor INFO : Initiating connection request on the device. Connection request URL is : http://10.10.10.10:8888/connect/device [2025-03-22 12:05:25:031] [0005B9AAAA22] [main] ConnectionReqEventProcessor DEBUG: Successfully started the timer task for connection request initiation on device : 0005B9AAAA22 [2025-03-22 12:05:25:031] [0005B9AAAA22] [main] ConnectionReqEventHandler DEBUG: Sent TR069 connection request to device [2025-03-22 12:05:25:192] [] [main] AOOpResultTest INFO : Starting AOOpResultTest on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:25:193] [] [main] AOOpResultTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:25:193] [] [main] AOOpResultTest INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:25:794] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:25:794] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:25:795] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:26:288] [] [main] AOOpResultTest INFO : Started AOOpResultTest in 1.125 seconds (JVM running for 9.856) [2025-03-22 12:05:26:352] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:26:353] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:26:353] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:26:353] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:26:354] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-03-22 12:05:26:394] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@400a89351265561012019-07-08T18:15:42.030Z2019-07-08T18:15:42.030Z [2025-03-22 12:05:26:558] [] [main] CPEManagementService INFO : Event notified by the device is of type: DownloadResponse [2025-03-22 12:05:26:559] [] [main] CPEManagementService DEBUG: Received Operation Result response DownloadResponse: Status = 1 StartTime 2019-07-08T18:15:42.030Z CompleteTime 2019-07-08T18:15:42.030Z [2025-03-22 12:05:26:568] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-03-22 12:05:26:569] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-03-22 12:05:26:574] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DOWNLOAD [2025-03-22 12:05:26:577] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DownloadResponse [2025-03-22 12:05:26:578] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-03-22 12:05:26:578] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-03-22 12:05:26:578] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:26:579] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-03-22 12:05:26:579] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:26:580] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-03-22 12:05:26:580] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:26:580] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-03-22 12:05:26:581] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:26:581] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-03-22 12:05:26:581] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:26:582] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-03-22 12:05:26:582] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-03-22 12:05:26:582] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:26:582] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-03-22 12:05:26:583] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:26:583] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:26:593] [] [main] CPEManagementService INFO : [2025-03-22 12:05:26:593] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:26:593] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:26:725] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:26:725] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:26:725] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:26:725] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:26:725] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-03-22 12:05:26:729] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@7f85cb8c914620 [2025-03-22 12:05:26:731] [] [main] CPEManagementService INFO : Event notified by the device is of type: FactoryResetResponse [2025-03-22 12:05:26:731] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.FactoryResetResponse@271dc56b [2025-03-22 12:05:26:732] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-03-22 12:05:26:732] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-03-22 12:05:26:732] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation FACTORY_RESET [2025-03-22 12:05:26:733] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is FRResponse [2025-03-22 12:05:26:733] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-03-22 12:05:26:733] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-03-22 12:05:26:733] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:26:733] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-03-22 12:05:26:733] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:26:734] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-03-22 12:05:26:734] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:26:734] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-03-22 12:05:26:734] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:26:734] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-03-22 12:05:26:734] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:26:734] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-03-22 12:05:26:735] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-03-22 12:05:26:735] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:26:736] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-03-22 12:05:26:736] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:26:736] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:26:736] [] [main] CPEManagementService INFO : [2025-03-22 12:05:26:736] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:26:737] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:26:758] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:26:758] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:26:758] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:26:759] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:26:759] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-03-22 12:05:26:760] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@2bcf23d912653738 [2025-03-22 12:05:26:762] [] [main] CPEManagementService INFO : Event notified by the device is of type: SetParameterAttributesResponse [2025-03-22 12:05:26:763] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.SetParameterAttributesResponse@2ed73bd5 [2025-03-22 12:05:26:763] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-03-22 12:05:26:763] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-03-22 12:05:26:765] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation SET_PARAMETER_ATTRIBUTES [2025-03-22 12:05:26:765] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is SPAResponse [2025-03-22 12:05:26:766] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-03-22 12:05:26:766] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-03-22 12:05:26:766] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:26:766] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-03-22 12:05:26:766] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:26:766] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-03-22 12:05:26:766] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:26:767] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-03-22 12:05:26:767] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:26:767] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-03-22 12:05:26:767] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:26:767] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-03-22 12:05:26:767] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-03-22 12:05:26:768] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:26:768] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-03-22 12:05:26:768] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:26:768] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:26:769] [] [main] CPEManagementService INFO : [2025-03-22 12:05:26:769] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:26:769] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:26:778] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:26:778] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:26:778] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:26:778] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:26:778] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-03-22 12:05:26:779] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@2c62dded12655897Device.Hosts.HostNumberOfEntries1 [2025-03-22 12:05:26:782] [] [main] CPEManagementService INFO : Event notified by the device is of type: GetParameterValuesResponse [2025-03-22 12:05:26:783] [] [main] CPEManagementService DEBUG: Received Operation Result response Device.Hosts.HostNumberOfEntries=1 [2025-03-22 12:05:26:783] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-03-22 12:05:26:784] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-03-22 12:05:26:784] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation GET_PARAMETER_VALUES [2025-03-22 12:05:26:785] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is GPVResponse [2025-03-22 12:05:26:785] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-03-22 12:05:26:785] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-03-22 12:05:26:786] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:26:786] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-03-22 12:05:26:786] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:26:786] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-03-22 12:05:26:786] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:26:786] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-03-22 12:05:26:786] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:26:787] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-03-22 12:05:26:787] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:26:787] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-03-22 12:05:26:787] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-03-22 12:05:26:787] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:26:787] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-03-22 12:05:26:787] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:26:788] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:26:788] [] [main] CPEManagementService INFO : [2025-03-22 12:05:26:788] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:26:788] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:26:796] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:26:796] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:26:796] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:26:796] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:26:796] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-03-22 12:05:26:798] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@50034039133062910 [2025-03-22 12:05:26:800] [] [main] CPEManagementService INFO : Event notified by the device is of type: DeleteObjectResponse [2025-03-22 12:05:26:800] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.DeleteObjectResponse@7eee131d [2025-03-22 12:05:26:800] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-03-22 12:05:26:801] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-03-22 12:05:26:801] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DELETE_OBJECT [2025-03-22 12:05:26:801] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DOResponse [2025-03-22 12:05:26:802] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-03-22 12:05:26:802] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-03-22 12:05:26:802] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:26:802] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-03-22 12:05:26:802] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:26:802] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-03-22 12:05:26:802] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:26:803] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-03-22 12:05:26:803] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:26:803] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-03-22 12:05:26:803] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:26:803] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-03-22 12:05:26:803] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-03-22 12:05:26:803] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:26:803] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-03-22 12:05:26:804] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:26:804] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:26:804] [] [main] CPEManagementService INFO : [2025-03-22 12:05:26:804] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:26:804] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:26:813] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:26:813] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:26:813] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:26:813] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:26:813] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-03-22 12:05:26:815] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4dc70e40913870 [2025-03-22 12:05:26:817] [] [main] CPEManagementService INFO : Event notified by the device is of type: RebootResponse [2025-03-22 12:05:26:817] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.RebootResponse@53ae53cf [2025-03-22 12:05:26:817] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-03-22 12:05:26:817] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-03-22 12:05:26:818] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation REBOOT [2025-03-22 12:05:26:818] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is RebootResponse [2025-03-22 12:05:26:819] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-03-22 12:05:26:819] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-03-22 12:05:26:819] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:26:819] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-03-22 12:05:26:819] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:26:819] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-03-22 12:05:26:819] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:26:820] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-03-22 12:05:26:820] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:26:820] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-03-22 12:05:26:820] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:26:820] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-03-22 12:05:26:820] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-03-22 12:05:26:820] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:26:820] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-03-22 12:05:26:821] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:26:821] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:26:821] [] [main] CPEManagementService INFO : [2025-03-22 12:05:26:821] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:26:821] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:26:831] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:26:831] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:26:831] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:26:831] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:26:831] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-03-22 12:05:26:832] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@6441fd4f1265443140 [2025-03-22 12:05:26:835] [] [main] CPEManagementService INFO : Event notified by the device is of type: AddObjectResponse [2025-03-22 12:05:26:835] [] [main] CPEManagementService DEBUG: Received Operation Result response AddObjectResponse: status=0 instance=4 [2025-03-22 12:05:26:835] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-03-22 12:05:26:836] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-03-22 12:05:26:837] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation ADD_OBJECT [2025-03-22 12:05:26:837] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is AOResponse [2025-03-22 12:05:26:837] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:26:838] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-03-22 12:05:26:839] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:26:839] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-03-22 12:05:26:839] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-03-22 12:05:26:839] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:26:839] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-03-22 12:05:26:839] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:26:839] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:26:840] [] [main] CPEManagementService INFO : [2025-03-22 12:05:26:840] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:26:840] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:26:858] [] [main] InvokeRPCTest INFO : Starting InvokeRPCTest on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:26:859] [] [main] InvokeRPCTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:26:859] [] [main] InvokeRPCTest INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:27:474] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:27:475] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:27:475] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:28:050] [] [main] InvokeRPCTest INFO : Started InvokeRPCTest in 1.206 seconds (JVM running for 11.619) [2025-03-22 12:05:28:094] [] [main] MapperRequestRESTService DEBUG: Received a Device operation request from Mapper [2025-03-22 12:05:28:095] [0005B95196D0] [main] ACSServiceAPIImpl INFO : Received request to perform device operation. OperationCode: SET_PARAMETER_VALUES [2025-03-22 12:05:28:095] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: The operation ID generated for processing the Device RPC request is - 1742645128095 [2025-03-22 12:05:28:095] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: Successfully posted the Mapper Request to Queue with OperationId : 1742645128095 OperationCode : SET_PARAMETER_VALUES [2025-03-22 12:05:28:095] [] [main] MapperRequestRESTService DEBUG: Successfully initiated device operation, The operation id for the request is: 1742645128095 [2025-03-22 12:05:28:288] [] [main] RPCResponseForwarderTest INFO : Starting RPCResponseForwarderTest on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:28:289] [] [main] RPCResponseForwarderTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:28:289] [] [main] RPCResponseForwarderTest INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:28:825] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:28:825] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:28:825] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:29:378] [] [main] RPCResponseForwarderTest INFO : Started RPCResponseForwarderTest in 1.104 seconds (JVM running for 12.946) [2025-03-22 12:05:29:390] [] [main] DeviceRPCResponseForwarder DEBUG: NBIOperationResult message is received for deviceId : 0005B9519095, , OprationId: 1000 [2025-03-22 12:05:29:390] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-03-22 12:05:29:390] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Operation result from NBI [2025-03-22 12:05:29:390] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the operation request to WebService: null [2025-03-22 12:05:29:390] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the NBI operation request to SBI Service [2025-03-22 12:05:29:390] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-03-22 12:05:29:391] [] [main] DeviceRPCResponseForwarder DEBUG: Successfully processed NBI operation result. [2025-03-22 12:05:29:451] [] [main] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519095 , Notification Type(s): [BOOTSTRAP] [2025-03-22 12:05:29:451] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-03-22 12:05:29:451] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI [2025-03-22 12:05:29:451] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null [2025-03-22 12:05:29:452] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the Device Notification to SBI Service [2025-03-22 12:05:29:452] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-03-22 12:05:29:452] [] [main] DeviceInformForwarder DEBUG: Successfully processed device notification. [2025-03-22 12:05:29:471] [] [main] DeviceRPCRequestHandlerTests INFO : Starting DeviceRPCRequestHandlerTests on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:29:472] [] [main] DeviceRPCRequestHandlerTests DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:29:472] [] [main] DeviceRPCRequestHandlerTests INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:29:800] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:29:800] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:29:800] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:30:351] [] [main] DeviceRPCRequestHandlerTests INFO : Started DeviceRPCRequestHandlerTests in 0.894 seconds (JVM running for 13.919) [2025-03-22 12:05:30:375] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation [2025-03-22 12:05:30:375] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10 [2025-03-22 12:05:30:375] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10 [2025-03-22 12:05:30:382] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:30:382] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:30:383] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10 [2025-03-22 12:05:30:383] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10 [2025-03-22 12:05:30:427] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request [2025-03-22 12:05:30:427] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: No active session exists, hence requesting for Connection request [2025-03-22 12:05:30:427] [0005B95196D0] [main] TR069RequestProcessEngineHelper INFO : Initiating Connection request on device: 0005B95196D0 [2025-03-22 12:05:30:428] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 0005B95196D0_10, listener bean=SessionTimeoutHandler [2025-03-22 12:05:30:430] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 started [2025-03-22 12:05:30:443] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 successfully completed [2025-03-22 12:05:30:443] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 0005B95196D0_10 [2025-03-22 12:05:30:443] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device RPC request with operation ID : 10 [2025-03-22 12:05:30:443] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10 [2025-03-22 12:05:30:443] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation [2025-03-22 12:05:30:568] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation [2025-03-22 12:05:30:569] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10 [2025-03-22 12:05:30:569] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10 [2025-03-22 12:05:30:569] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:30:569] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:30:569] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10 [2025-03-22 12:05:30:569] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10 [2025-03-22 12:05:30:571] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request [2025-03-22 12:05:30:571] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Session is in processing state, Will be notified to session manager to pick the request on session availability [2025-03-22 12:05:30:571] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10 [2025-03-22 12:05:30:571] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation [2025-03-22 12:05:30:591] [] [main] BootstrapInformTest INFO : Starting BootstrapInformTest on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:30:591] [] [main] BootstrapInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:30:591] [] [main] BootstrapInformTest INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:31:057] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:31:059] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:31:059] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:31:547] [] [main] BootstrapInformTest INFO : Started BootstrapInformTest in 0.969 seconds (JVM running for 15.116) [2025-03-22 12:05:31:558] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:31:558] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:31:558] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:31:558] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:31:560] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@26641b2210005B9LTE_Enterprise_C-RANSC_Cntrl0005B94239100 BOOTSTRAP12020-06-10T11:27:26.054Z0Device.DeviceInfo.HardwareVersion750742.00.13Device.DeviceInfo.SoftwareVersion4.3.00.229Device.DeviceInfo.ProvisioningCodeDevice.ManagementServer.ConnectionRequestURLhttp://172.20.0.9:30150/ConnectionRequest?command=cr&sn=0005B9423910Device.ManagementServer.ParameterKeyzzzzDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection.1.ExternalIPAddress172.17.19.193Device.Services.FAPService.1.FAPControl.LTE.AdminState0 [2025-03-22 12:05:31:565] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-03-22 12:05:31:565] [0005B9423910] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-03-22 12:05:31:565] [0005B9423910] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-03-22 12:05:31:566] [0005B9423910] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-03-22 12:05:31:566] [0005B9423910] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-03-22 12:05:31:566] [0005B9423910] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-03-22 12:05:31:566] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9423910_CONNECTION_REQUEST [2025-03-22 12:05:31:566] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9423910_CONNECTION_REQUEST [2025-03-22 12:05:31:566] [0005B9423910] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-03-22 12:05:31:566] [0005B9423910] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform [2025-03-22 12:05:31:567] [0005B9423910] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-03-22 12:05:31:568] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-03-22 12:05:31:568] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP' [2025-03-22 12:05:31:568] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-03-22 12:05:31:589] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists [2025-03-22 12:05:31:589] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests [2025-03-22 12:05:31:590] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9423910 [2025-03-22 12:05:31:590] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:31:590] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:31:750] [0005B9423910] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device [2025-03-22 12:05:31:755] [0005B9423910] [main] SessionManager DEBUG: Creating a new session for the device [2025-03-22 12:05:31:762] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:31:774] [0005B9423910] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-03-22 12:05:31:775] [0005B9423910] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9423910 [2025-03-22 12:05:31:778] [0005B9423910] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-03-22 12:05:31:781] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:31:781] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:31:781] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-03-22 12:05:31:783] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9423910 [2025-03-22 12:05:31:783] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-03-22 12:05:31:783] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-03-22 12:05:31:783] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:31:784] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for f3fb856a-0715-11f0-8b2e-0242e9defec0, listener bean=SessionTimeoutHandler [2025-03-22 12:05:31:784] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job f3fb856a-0715-11f0-8b2e-0242e9defec0 started [2025-03-22 12:05:31:784] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job f3fb856a-0715-11f0-8b2e-0242e9defec0 successfully completed [2025-03-22 12:05:31:784] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:31:784] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:31:784] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-03-22 12:05:31:793] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-03-22 12:05:32:112] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:32:113] [] [main] CPEManagementService INFO : 11 [2025-03-22 12:05:32:115] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:32:115] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:32:121] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:32:122] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:32:123] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:32:123] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:32:124] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:32:124] [] [main] CPEManagementService DEBUG: The session id is f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:32:124] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:32:124] [] [main] CPEManagementService INFO : Received Empty Device response [2025-03-22 12:05:32:125] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:32:137] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:32:138] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-03-22 12:05:32:138] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-03-22 12:05:32:138] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:32:138] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:32:140] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:32:140] [0005B9423910] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:32:140] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:32:140] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-03-22 12:05:32:141] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9423910 [2025-03-22 12:05:32:141] [0005B9423910] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-03-22 12:05:32:141] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:32:141] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:32:141] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job f3fb856a-0715-11f0-8b2e-0242e9defec0 started [2025-03-22 12:05:32:141] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job f3fb856a-0715-11f0-8b2e-0242e9defec0 successfully completed [2025-03-22 12:05:32:141] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:32:141] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : f3fb856a-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:32:141] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:32:142] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:32:142] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-03-22 12:05:32:144] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:32:144] [] [main] CPEManagementService INFO : [2025-03-22 12:05:32:144] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:32:144] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:32:325] [] [main] ConnRequestInformTest INFO : Starting ConnRequestInformTest on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:32:326] [] [main] ConnRequestInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:32:326] [] [main] ConnRequestInformTest INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:32:755] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:32:755] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:32:756] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:33:179] [] [main] ConnRequestInformTest INFO : Started ConnRequestInformTest in 0.877 seconds (JVM running for 16.747) [2025-03-22 12:05:33:187] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:33:188] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:33:188] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:33:188] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:33:191] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@417c29081Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190926 CONNECTION REQUEST12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519092Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1 [2025-03-22 12:05:33:199] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-03-22 12:05:33:199] [0005B9519092] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-03-22 12:05:33:199] [0005B9519092] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-03-22 12:05:33:200] [0005B9519092] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-03-22 12:05:33:200] [0005B9519092] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-03-22 12:05:33:200] [0005B9519092] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-03-22 12:05:33:201] [0005B9519092] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-03-22 12:05:33:201] [0005B9519092] [main] DeviceInformBuilder DEBUG: Constructing Connection Request Inform [2025-03-22 12:05:33:201] [0005B9519092] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-03-22 12:05:33:202] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-03-22 12:05:33:202] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '6 CONNECTION REQUEST' [2025-03-22 12:05:33:203] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-03-22 12:05:33:203] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:33:209] [0005B9519092] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-03-22 12:05:33:209] [0005B9519092] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519092 [2025-03-22 12:05:33:214] [0005B9519092] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-03-22 12:05:33:216] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid9 [2025-03-22 12:05:33:217] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:33:217] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-03-22 12:05:33:218] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519092 [2025-03-22 12:05:33:218] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-03-22 12:05:33:218] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-03-22 12:05:33:218] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:33:219] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid9 [2025-03-22 12:05:33:219] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-03-22 12:05:33:232] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-03-22 12:05:33:233] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:33:234] [] [main] CPEManagementService INFO : 11 [2025-03-22 12:05:33:234] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:33:234] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:33:237] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:33:237] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:33:237] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:33:237] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:33:237] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:33:237] [] [main] CPEManagementService DEBUG: The session id is sessionid9 [2025-03-22 12:05:33:237] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:33:238] [] [main] CPEManagementService INFO : Received Empty Device response [2025-03-22 12:05:33:238] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid9 [2025-03-22 12:05:33:242] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid9 [2025-03-22 12:05:33:243] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-03-22 12:05:33:243] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-03-22 12:05:33:243] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:33:243] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid9 [2025-03-22 12:05:33:243] [0005B9519092] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:33:243] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:33:243] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-03-22 12:05:33:243] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519092 [2025-03-22 12:05:33:243] [0005B9519092] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-03-22 12:05:33:243] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:33:244] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid9 [2025-03-22 12:05:33:244] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:33:244] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:33:244] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-03-22 12:05:33:244] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:33:245] [] [main] CPEManagementService INFO : [2025-03-22 12:05:33:245] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:33:245] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:33:382] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:33:383] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:33:383] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:33:383] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:33:389] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@46117fc21Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190947 TRANSFER COMPLETE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519094Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1 [2025-03-22 12:05:33:399] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-03-22 12:05:33:400] [0005B9519094] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-03-22 12:05:33:400] [0005B9519094] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-03-22 12:05:33:400] [0005B9519094] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-03-22 12:05:33:400] [0005B9519094] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-03-22 12:05:33:400] [0005B9519094] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-03-22 12:05:33:401] [0005B9519094] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-03-22 12:05:33:401] [0005B9519094] [main] DeviceInformBuilder DEBUG: Constructing Transfer Complete Inform [2025-03-22 12:05:33:401] [0005B9519094] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-03-22 12:05:33:402] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-03-22 12:05:33:402] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE' [2025-03-22 12:05:33:402] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-03-22 12:05:33:402] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:33:405] [0005B9519094] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-03-22 12:05:33:405] [0005B9519094] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519094 [2025-03-22 12:05:33:408] [0005B9519094] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-03-22 12:05:33:411] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5 [2025-03-22 12:05:33:411] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:33:411] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-03-22 12:05:33:414] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519094 [2025-03-22 12:05:33:414] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-03-22 12:05:33:414] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-03-22 12:05:33:414] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:33:415] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5 [2025-03-22 12:05:33:415] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-03-22 12:05:33:419] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-03-22 12:05:33:419] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:33:420] [] [main] CPEManagementService INFO : 11 [2025-03-22 12:05:33:420] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:33:421] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:33:422] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:33:422] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:33:422] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:33:423] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:33:423] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:33:423] [] [main] CPEManagementService DEBUG: The session id is sessionid5 [2025-03-22 12:05:33:424] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:33:424] [] [main] CPEManagementService INFO : Received Empty Device response [2025-03-22 12:05:33:424] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5 [2025-03-22 12:05:33:427] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5 [2025-03-22 12:05:33:428] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-03-22 12:05:33:428] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-03-22 12:05:33:428] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:33:429] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5 [2025-03-22 12:05:33:429] [0005B9519094] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:33:429] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:33:429] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-03-22 12:05:33:429] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519094 [2025-03-22 12:05:33:429] [0005B9519094] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-03-22 12:05:33:430] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:33:430] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5 [2025-03-22 12:05:33:430] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:33:430] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:33:430] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-03-22 12:05:33:431] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:33:431] [] [main] CPEManagementService INFO : [2025-03-22 12:05:33:431] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:33:431] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:33:448] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:33:448] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:33:449] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:33:449] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:33:455] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4b2bd0921Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190911 BOOT4 VALUE CHANGE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519091Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1 [2025-03-22 12:05:33:462] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-03-22 12:05:33:462] [0005B9519091] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-03-22 12:05:33:462] [0005B9519091] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-03-22 12:05:33:463] [0005B9519091] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-03-22 12:05:33:463] [0005B9519091] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-03-22 12:05:33:463] [0005B9519091] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-03-22 12:05:33:463] [0005B9519091] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-03-22 12:05:33:463] [0005B9519091] [main] DeviceInformBuilder DEBUG: Constructing BOOT Inform [2025-03-22 12:05:33:464] [0005B9519091] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-03-22 12:05:33:464] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-03-22 12:05:33:464] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '1 BOOT' [2025-03-22 12:05:33:464] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-03-22 12:05:33:464] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOT, hence aborting all the pending operations if any exists [2025-03-22 12:05:33:464] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests [2025-03-22 12:05:33:465] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9519091 [2025-03-22 12:05:33:465] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:33:467] [0005B9519091] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-03-22 12:05:33:467] [0005B9519091] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519091 [2025-03-22 12:05:33:469] [0005B9519091] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-03-22 12:05:33:472] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5 [2025-03-22 12:05:33:472] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:33:472] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-03-22 12:05:33:473] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519091 [2025-03-22 12:05:33:473] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-03-22 12:05:33:473] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-03-22 12:05:33:473] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:33:473] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5 [2025-03-22 12:05:33:473] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-03-22 12:05:33:476] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-03-22 12:05:33:477] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:33:477] [] [main] CPEManagementService INFO : 11 [2025-03-22 12:05:33:477] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:33:477] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:33:479] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:33:479] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:33:479] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:33:479] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:33:479] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:33:479] [] [main] CPEManagementService DEBUG: The session id is sessionid5 [2025-03-22 12:05:33:480] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:33:480] [] [main] CPEManagementService INFO : Received Empty Device response [2025-03-22 12:05:33:480] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5 [2025-03-22 12:05:33:483] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5 [2025-03-22 12:05:33:483] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-03-22 12:05:33:483] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-03-22 12:05:33:483] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:33:483] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5 [2025-03-22 12:05:33:484] [0005B9519091] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:33:484] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:33:484] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-03-22 12:05:33:484] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519091 [2025-03-22 12:05:33:484] [0005B9519091] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-03-22 12:05:33:484] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:33:484] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5 [2025-03-22 12:05:33:484] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:33:484] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:33:484] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-03-22 12:05:33:485] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:33:485] [] [main] CPEManagementService INFO : [2025-03-22 12:05:33:485] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:33:485] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:33:501] [] [main] TransferCompleteTest INFO : Starting TransferCompleteTest on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:33:501] [] [main] TransferCompleteTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:33:502] [] [main] TransferCompleteTest INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:33:825] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:33:826] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:33:826] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:34:333] [] [main] TransferCompleteTest INFO : Started TransferCompleteTest in 0.844 seconds (JVM running for 17.902) [2025-03-22 12:05:34:342] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:34:342] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:34:342] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:34:342] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:34:344] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@25e0a6b300005B9AAAA2202019-07-08T18:15:43.032Z2019-07-08T18:15:43.032Z [2025-03-22 12:05:34:348] [] [main] CPEManagementService INFO : Event notified by the device is of type: TransferComplete [2025-03-22 12:05:34:348] [] [main] DeviceEventHandler DEBUG: Processing Transfer Complete [2025-03-22 12:05:34:349] [0005B9AAAA22] [main] DeviceEventHandler DEBUG: TransferComplete inform received with Start time [2025-03-22 12:05:34:350] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-03-22 12:05:34:350] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE' [2025-03-22 12:05:34:351] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-03-22 12:05:34:351] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:34:351] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: newSessionId [2025-03-22 12:05:34:351] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:34:351] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-03-22 12:05:34:352] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper WARN : Notification do not contains either connection request URL or swVer or hwVer of the device [2025-03-22 12:05:34:352] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details [2025-03-22 12:05:34:352] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-03-22 12:05:34:352] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-03-22 12:05:34:352] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:34:352] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for newSessionId, listener bean=SessionTimeoutHandler [2025-03-22 12:05:34:353] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId started [2025-03-22 12:05:34:353] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId successfully completed [2025-03-22 12:05:34:353] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for newSessionId [2025-03-22 12:05:34:353] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : newSessionId [2025-03-22 12:05:34:354] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-03-22 12:05:34:354] [] [main] DeviceEventHandler DEBUG: Successfully processed the TRANSFER COMPLETE Inform [2025-03-22 12:05:34:355] [] [main] TR069RPC DEBUG: Key element is: 0 [2025-03-22 12:05:34:356] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:34:356] [] [main] CPEManagementService INFO : 1 [2025-03-22 12:05:34:357] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:34:357] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:34:358] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:34:359] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:34:359] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:34:359] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:34:359] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:34:359] [] [main] CPEManagementService DEBUG: The session id is newSessionId [2025-03-22 12:05:34:359] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:34:359] [] [main] CPEManagementService INFO : Received Empty Device response [2025-03-22 12:05:34:360] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: newSessionId [2025-03-22 12:05:34:360] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: newSessionId [2025-03-22 12:05:34:360] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-03-22 12:05:34:361] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-03-22 12:05:34:361] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:34:361] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: newSessionId [2025-03-22 12:05:34:361] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:34:361] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:34:361] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-03-22 12:05:34:361] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9AAAA22 [2025-03-22 12:05:34:362] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-03-22 12:05:34:362] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:34:362] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.newSessionId [2025-03-22 12:05:34:362] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId started [2025-03-22 12:05:34:362] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId successfully completed [2025-03-22 12:05:34:363] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.newSessionId [2025-03-22 12:05:34:363] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : newSessionId [2025-03-22 12:05:34:363] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:34:363] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:34:363] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-03-22 12:05:34:363] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:34:364] [] [main] CPEManagementService INFO : [2025-03-22 12:05:34:364] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:34:364] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:34:524] [] [main] InformSwVersionUpdatedTest INFO : Starting InformSwVersionUpdatedTest on prd-ubuntu1804-docker-4c-4g-3265 with PID 2806 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-03-22 12:05:34:524] [] [main] InformSwVersionUpdatedTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-03-22 12:05:34:525] [] [main] InformSwVersionUpdatedTest INFO : No active profile set, falling back to default profiles: default [2025-03-22 12:05:34:865] [] [main] QuartzSchedulerManager DEBUG: init started [2025-03-22 12:05:34:866] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-03-22 12:05:34:866] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-03-22 12:05:35:336] [] [main] InformSwVersionUpdatedTest INFO : Started InformSwVersionUpdatedTest in 0.826 seconds (JVM running for 18.904) [2025-03-22 12:05:35:344] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:35:344] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:35:344] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:35:344] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:35:347] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@3b0c6d5e1Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190900 BOOTSTRAP12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519090Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1 [2025-03-22 12:05:35:353] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-03-22 12:05:35:353] [0005B9519090] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-03-22 12:05:35:354] [0005B9519090] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-03-22 12:05:35:354] [0005B9519090] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-03-22 12:05:35:354] [0005B9519090] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-03-22 12:05:35:354] [0005B9519090] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-03-22 12:05:35:354] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9519090_CONNECTION_REQUEST [2025-03-22 12:05:35:354] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9519090_CONNECTION_REQUEST [2025-03-22 12:05:35:354] [0005B9519090] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-03-22 12:05:35:355] [0005B9519090] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform [2025-03-22 12:05:35:355] [0005B9519090] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-03-22 12:05:35:356] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-03-22 12:05:35:356] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP' [2025-03-22 12:05:35:356] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-03-22 12:05:35:358] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists [2025-03-22 12:05:35:358] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests [2025-03-22 12:05:35:364] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Grouping the records based on operationId [2025-03-22 12:05:35:364] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists 0 pending NBI requests for the device [2025-03-22 12:05:35:364] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:364] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:368] [0005B9519090] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device [2025-03-22 12:05:35:368] [0005B9519090] [main] SessionManager DEBUG: Creating a new session for the device [2025-03-22 12:05:35:371] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:374] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:374] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:35:374] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-03-22 12:05:35:374] [0005B9519090] [main] TR069EventNotificationService DEBUG: Device Inform Event received: '0 BOOTSTRAP' [2025-03-22 12:05:35:456] [0005B9519090] [main] TR069EventNotificationService DEBUG: Successfully posted the device inform event to DM to forward to NBI [2025-03-22 12:05:35:456] [] [main] TR069RequestProcessEngineHelper DEBUG: Device details are changed [2025-03-22 12:05:35:457] [] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details [2025-03-22 12:05:35:461] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-03-22 12:05:35:462] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-03-22 12:05:35:462] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:35:463] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for f622f94b-0715-11f0-8b2e-0242e9defec0, listener bean=SessionTimeoutHandler [2025-03-22 12:05:35:463] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job f622f94b-0715-11f0-8b2e-0242e9defec0 started [2025-03-22 12:05:35:464] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job f622f94b-0715-11f0-8b2e-0242e9defec0 successfully completed [2025-03-22 12:05:35:464] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:464] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:465] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-03-22 12:05:35:478] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-03-22 12:05:35:479] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:35:479] [] [main] CPEManagementService INFO : 11 [2025-03-22 12:05:35:479] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:35:479] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:35:481] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:35:481] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:35:481] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:35:481] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:35:481] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:35:481] [] [main] CPEManagementService DEBUG: The session id is f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:482] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:35:482] [] [main] CPEManagementService INFO : Received Empty Device response [2025-03-22 12:05:35:482] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:493] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:494] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-03-22 12:05:35:494] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-03-22 12:05:35:494] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:494] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:496] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:496] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:35:496] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:35:496] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-03-22 12:05:35:501] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519090 [2025-03-22 12:05:35:501] [0005B9519090] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-03-22 12:05:35:501] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:35:501] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:501] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job f622f94b-0715-11f0-8b2e-0242e9defec0 started [2025-03-22 12:05:35:501] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job f622f94b-0715-11f0-8b2e-0242e9defec0 successfully completed [2025-03-22 12:05:35:502] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:502] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : f622f94b-0715-11f0-8b2e-0242e9defec0 [2025-03-22 12:05:35:502] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:35:502] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:35:502] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-03-22 12:05:35:506] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:35:506] [] [main] CPEManagementService INFO : [2025-03-22 12:05:35:506] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:35:506] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:35:517] [] [DefaultMessageListenerContainer-4] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519090 , Notification Type(s): [BOOTSTRAP] [2025-03-22 12:05:35:518] [] [DefaultMessageListenerContainer-4] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-03-22 12:05:35:518] [] [DefaultMessageListenerContainer-4] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI [2025-03-22 12:05:35:518] [] [DefaultMessageListenerContainer-4] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null [2025-03-22 12:05:35:525] [] [DefaultMessageListenerContainer-4] DeviceEventsMapperNotificationService ERROR: Unable to post the Device Notification, Reason: URI is not absolute [2025-03-22 12:05:35:525] [] [DefaultMessageListenerContainer-4] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-03-22 12:05:35:525] [] [DefaultMessageListenerContainer-4] DeviceInformForwarder DEBUG: Successfully processed device notification. [2025-03-22 12:05:35:677] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:35:677] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:35:677] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:35:677] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:35:680] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@760ce5a71Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190932 PERIODIC12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519093Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1 [2025-03-22 12:05:35:685] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-03-22 12:05:35:685] [0005B9519093] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-03-22 12:05:35:685] [0005B9519093] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-03-22 12:05:35:686] [0005B9519093] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-03-22 12:05:35:686] [0005B9519093] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-03-22 12:05:35:686] [0005B9519093] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-03-22 12:05:35:686] [0005B9519093] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-03-22 12:05:35:687] [0005B9519093] [main] DeviceInformBuilder DEBUG: Constructing PERIODIC Inform [2025-03-22 12:05:35:687] [0005B9519093] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-03-22 12:05:35:688] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-03-22 12:05:35:689] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '2 PERIODIC' [2025-03-22 12:05:35:689] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-03-22 12:05:35:689] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:692] [0005B9519093] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-03-22 12:05:35:692] [0005B9519093] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519093 [2025-03-22 12:05:35:696] [0005B9519093] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-03-22 12:05:35:700] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid10 [2025-03-22 12:05:35:700] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:35:700] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-03-22 12:05:35:702] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519093 [2025-03-22 12:05:35:703] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-03-22 12:05:35:704] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-03-22 12:05:35:704] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:35:705] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid10 [2025-03-22 12:05:35:705] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-03-22 12:05:35:714] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-03-22 12:05:35:715] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:35:715] [] [main] CPEManagementService INFO : 11 [2025-03-22 12:05:35:715] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:35:715] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:35:716] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:35:716] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:35:716] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:35:716] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:35:716] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:35:716] [] [main] CPEManagementService DEBUG: The session id is sessionid10 [2025-03-22 12:05:35:717] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:35:717] [] [main] CPEManagementService INFO : Received Empty Device response [2025-03-22 12:05:35:717] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid10 [2025-03-22 12:05:35:721] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid10 [2025-03-22 12:05:35:722] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-03-22 12:05:35:722] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-03-22 12:05:35:722] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:722] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid10 [2025-03-22 12:05:35:722] [0005B9519093] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:35:722] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:35:722] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-03-22 12:05:35:723] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519093 [2025-03-22 12:05:35:723] [0005B9519093] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-03-22 12:05:35:723] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:35:723] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid10 [2025-03-22 12:05:35:723] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:35:724] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:35:724] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-03-22 12:05:35:725] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:35:725] [] [main] CPEManagementService INFO : [2025-03-22 12:05:35:725] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:35:726] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:35:736] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:35:736] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:35:736] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:35:736] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:35:738] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@23b6ce371Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190954 VALUE CHANGE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519095Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1 [2025-03-22 12:05:35:746] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-03-22 12:05:35:746] [0005B9519095] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-03-22 12:05:35:746] [0005B9519095] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-03-22 12:05:35:746] [0005B9519095] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-03-22 12:05:35:747] [0005B9519095] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-03-22 12:05:35:747] [0005B9519095] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-03-22 12:05:35:747] [0005B9519095] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-03-22 12:05:35:747] [0005B9519095] [main] DeviceInformBuilder DEBUG: Constructing VALUECHANGE Inform [2025-03-22 12:05:35:747] [0005B9519095] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-03-22 12:05:35:748] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-03-22 12:05:35:748] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '4 VALUE CHANGE' [2025-03-22 12:05:35:748] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-03-22 12:05:35:748] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:750] [0005B9519095] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-03-22 12:05:35:751] [0005B9519095] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519095 [2025-03-22 12:05:35:756] [0005B9519095] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-03-22 12:05:35:760] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5 [2025-03-22 12:05:35:760] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:35:760] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-03-22 12:05:35:763] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519095 [2025-03-22 12:05:35:763] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-03-22 12:05:35:763] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-03-22 12:05:35:763] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:35:763] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5 [2025-03-22 12:05:35:763] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-03-22 12:05:35:767] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-03-22 12:05:35:768] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:35:769] [] [main] CPEManagementService INFO : 11 [2025-03-22 12:05:35:770] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:35:770] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-03-22 12:05:35:772] [] [main] CPEManagementService DEBUG: A device event occurred [2025-03-22 12:05:35:772] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-03-22 12:05:35:772] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-03-22 12:05:35:772] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-03-22 12:05:35:772] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-03-22 12:05:35:772] [] [main] CPEManagementService DEBUG: The session id is sessionid5 [2025-03-22 12:05:35:773] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-03-22 12:05:35:773] [] [main] CPEManagementService INFO : Received Empty Device response [2025-03-22 12:05:35:773] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5 [2025-03-22 12:05:35:776] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5 [2025-03-22 12:05:35:778] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-03-22 12:05:35:778] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-03-22 12:05:35:779] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-03-22 12:05:35:780] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5 [2025-03-22 12:05:35:781] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-03-22 12:05:35:781] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-03-22 12:05:35:781] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-03-22 12:05:35:781] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519095 [2025-03-22 12:05:35:781] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-03-22 12:05:35:781] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-03-22 12:05:35:782] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5 [2025-03-22 12:05:35:782] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-03-22 12:05:35:782] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-03-22 12:05:35:782] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-03-22 12:05:35:783] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-03-22 12:05:35:784] [] [main] CPEManagementService INFO : [2025-03-22 12:05:35:784] [] [main] CPEManagementService DEBUG: End of processing [2025-03-22 12:05:35:784] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request