Debug Log started at: 2025-02-01 12:05:22[2025-02-01 12:05:23:361] [] [main] DeviceConnectTest INFO : Starting DeviceConnectTest on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:23:380] [] [main] DeviceConnectTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:23:384] [] [main] DeviceConnectTest INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:27:906] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:27:907] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:27:908] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:05:29:522] [] [main] DeviceConnectTest INFO : Started DeviceConnectTest in 6.494 seconds (JVM running for 8.821) [2025-02-01 12:05:29:620] [0005B9AAAA22] [main] ConnectionReqEventHandler INFO : Received a JMS message from Request Processor for initiating connection request [2025-02-01 12:05:29:621] [0005B9AAAA22] [main] ConnectionReqEventProcessor INFO : Initiating connection request on the device. Connection request URL is : http://10.10.10.10:8888/connect/device [2025-02-01 12:05:29:625] [0005B9AAAA22] [main] ConnectionReqEventProcessor DEBUG: Successfully started the timer task for connection request initiation on device : 0005B9AAAA22 [2025-02-01 12:05:29:625] [0005B9AAAA22] [main] ConnectionReqEventHandler DEBUG: Sent TR069 connection request to device [2025-02-01 12:05:29:736] [] [main] AOOpResultTest INFO : Starting AOOpResultTest on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:29:737] [] [main] AOOpResultTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:29:737] [] [main] AOOpResultTest INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:30:446] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:30:446] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:30:447] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:05:31:028] [] [main] AOOpResultTest INFO : Started AOOpResultTest in 1.316 seconds (JVM running for 10.328) [2025-02-01 12:05:31:113] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:31:114] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:31:115] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:31:115] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:31:115] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-02-01 12:05:31:159] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@169b4b1a1265561012019-07-08T18:15:42.030Z2019-07-08T18:15:42.030Z [2025-02-01 12:05:31:269] [] [main] CPEManagementService INFO : Event notified by the device is of type: DownloadResponse [2025-02-01 12:05:31:270] [] [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-02-01 12:05:31:278] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-02-01 12:05:31:279] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-02-01 12:05:31:285] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DOWNLOAD [2025-02-01 12:05:31:288] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DownloadResponse [2025-02-01 12:05:31:288] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-02-01 12:05:31:288] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-02-01 12:05:31:289] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:31:289] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-02-01 12:05:31:289] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:31:290] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-02-01 12:05:31:290] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:31:290] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-02-01 12:05:31:290] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:31:290] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-02-01 12:05:31:291] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:31:291] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-02-01 12:05:31:291] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-02-01 12:05:31:291] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:31:291] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-02-01 12:05:31:292] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:31:292] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:31:302] [] [main] CPEManagementService INFO : [2025-02-01 12:05:31:303] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:31:303] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:31:500] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:31:503] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:31:504] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:31:504] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:31:504] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-02-01 12:05:31:508] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@45a55153914620 [2025-02-01 12:05:31:520] [] [main] CPEManagementService INFO : Event notified by the device is of type: FactoryResetResponse [2025-02-01 12:05:31:521] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.FactoryResetResponse@6ce69272 [2025-02-01 12:05:31:521] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-02-01 12:05:31:521] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-02-01 12:05:31:522] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation FACTORY_RESET [2025-02-01 12:05:31:522] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is FRResponse [2025-02-01 12:05:31:523] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-02-01 12:05:31:523] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-02-01 12:05:31:523] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:31:523] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-02-01 12:05:31:523] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:31:523] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-02-01 12:05:31:523] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:31:524] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-02-01 12:05:31:524] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:31:524] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-02-01 12:05:31:524] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:31:524] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-02-01 12:05:31:524] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-02-01 12:05:31:524] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:31:525] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-02-01 12:05:31:525] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:31:525] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:31:525] [] [main] CPEManagementService INFO : [2025-02-01 12:05:31:525] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:31:526] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:31:544] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:31:544] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:31:545] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:31:545] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:31:545] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-02-01 12:05:31:546] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@1c3f35b712653738 [2025-02-01 12:05:31:549] [] [main] CPEManagementService INFO : Event notified by the device is of type: SetParameterAttributesResponse [2025-02-01 12:05:31:549] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.SetParameterAttributesResponse@25b1a6cd [2025-02-01 12:05:31:550] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-02-01 12:05:31:551] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-02-01 12:05:31:553] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation SET_PARAMETER_ATTRIBUTES [2025-02-01 12:05:31:553] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is SPAResponse [2025-02-01 12:05:31:554] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-02-01 12:05:31:554] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-02-01 12:05:31:554] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:31:554] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-02-01 12:05:31:554] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:31:554] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-02-01 12:05:31:555] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:31:555] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-02-01 12:05:31:555] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:31:555] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-02-01 12:05:31:555] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:31:555] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-02-01 12:05:31:555] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-02-01 12:05:31:555] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:31:556] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-02-01 12:05:31:556] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:31:556] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:31:556] [] [main] CPEManagementService INFO : [2025-02-01 12:05:31:556] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:31:556] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:31:567] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:31:567] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:31:567] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:31:567] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:31:568] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-02-01 12:05:31:569] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4e3ca6912655897Device.Hosts.HostNumberOfEntries1 [2025-02-01 12:05:31:572] [] [main] CPEManagementService INFO : Event notified by the device is of type: GetParameterValuesResponse [2025-02-01 12:05:31:573] [] [main] CPEManagementService DEBUG: Received Operation Result response Device.Hosts.HostNumberOfEntries=1 [2025-02-01 12:05:31:573] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-02-01 12:05:31:574] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-02-01 12:05:31:574] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation GET_PARAMETER_VALUES [2025-02-01 12:05:31:575] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is GPVResponse [2025-02-01 12:05:31:576] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-02-01 12:05:31:576] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-02-01 12:05:31:577] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:31:577] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-02-01 12:05:31:577] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:31:577] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-02-01 12:05:31:578] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:31:578] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-02-01 12:05:31:578] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:31:579] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-02-01 12:05:31:579] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:31:579] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-02-01 12:05:31:579] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-02-01 12:05:31:580] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:31:580] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-02-01 12:05:31:580] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:31:580] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:31:581] [] [main] CPEManagementService INFO : [2025-02-01 12:05:31:581] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:31:581] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:31:592] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:31:592] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:31:593] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:31:593] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:31:593] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-02-01 12:05:31:595] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@2867b0af133062910 [2025-02-01 12:05:31:597] [] [main] CPEManagementService INFO : Event notified by the device is of type: DeleteObjectResponse [2025-02-01 12:05:31:597] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.DeleteObjectResponse@43133ef1 [2025-02-01 12:05:31:598] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-02-01 12:05:31:598] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-02-01 12:05:31:599] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DELETE_OBJECT [2025-02-01 12:05:31:599] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DOResponse [2025-02-01 12:05:31:599] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-02-01 12:05:31:599] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-02-01 12:05:31:599] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:31:600] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-02-01 12:05:31:600] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:31:600] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-02-01 12:05:31:600] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:31:600] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-02-01 12:05:31:600] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:31:600] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-02-01 12:05:31:600] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:31:601] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-02-01 12:05:31:601] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-02-01 12:05:31:601] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:31:601] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-02-01 12:05:31:601] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:31:601] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:31:602] [] [main] CPEManagementService INFO : [2025-02-01 12:05:31:602] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:31:602] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:31:611] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:31:611] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:31:612] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:31:612] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:31:612] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-02-01 12:05:31:613] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@1a7781f3913870 [2025-02-01 12:05:31:616] [] [main] CPEManagementService INFO : Event notified by the device is of type: RebootResponse [2025-02-01 12:05:31:616] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.RebootResponse@33c6e4e7 [2025-02-01 12:05:31:616] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-02-01 12:05:31:617] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-02-01 12:05:31:617] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation REBOOT [2025-02-01 12:05:31:618] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is RebootResponse [2025-02-01 12:05:31:618] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-02-01 12:05:31:618] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-02-01 12:05:31:618] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:31:618] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-02-01 12:05:31:618] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:31:618] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-02-01 12:05:31:618] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:31:619] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-02-01 12:05:31:619] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:31:619] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-02-01 12:05:31:619] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:31:619] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-02-01 12:05:31:619] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-02-01 12:05:31:619] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:31:619] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-02-01 12:05:31:620] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:31:621] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:31:621] [] [main] CPEManagementService INFO : [2025-02-01 12:05:31:621] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:31:621] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:31:630] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:31:631] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:31:631] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:31:631] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:31:632] [] [main] CPEManagementService DEBUG: The session id is sessionId [2025-02-01 12:05:31:633] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@7a49c8ac1265443140 [2025-02-01 12:05:31:635] [] [main] CPEManagementService INFO : Event notified by the device is of type: AddObjectResponse [2025-02-01 12:05:31:635] [] [main] CPEManagementService DEBUG: Received Operation Result response AddObjectResponse: status=0 instance=4 [2025-02-01 12:05:31:636] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId [2025-02-01 12:05:31:636] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId [2025-02-01 12:05:31:636] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation ADD_OBJECT [2025-02-01 12:05:31:637] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is AOResponse [2025-02-01 12:05:31:637] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response [2025-02-01 12:05:31:637] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device [2025-02-01 12:05:31:637] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:31:637] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId [2025-02-01 12:05:31:637] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed. [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002 [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper [2025-02-01 12:05:31:638] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:31:639] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response [2025-02-01 12:05:31:639] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:31:639] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:31:639] [] [main] CPEManagementService INFO : [2025-02-01 12:05:31:639] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:31:639] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:31:658] [] [main] InvokeRPCTest INFO : Starting InvokeRPCTest on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:31:658] [] [main] InvokeRPCTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:31:658] [] [main] InvokeRPCTest INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:32:271] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:32:272] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:32:272] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:05:42:975] [] [main] InvokeRPCTest INFO : Started InvokeRPCTest in 11.33 seconds (JVM running for 22.275) [2025-02-01 12:05:42:989] [] [main] MapperRequestRESTService DEBUG: Received a Device operation request from Mapper [2025-02-01 12:05:42:989] [0005B95196D0] [main] ACSServiceAPIImpl INFO : Received request to perform device operation. OperationCode: SET_PARAMETER_VALUES [2025-02-01 12:05:42:989] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: The operation ID generated for processing the Device RPC request is - 1738411542989 [2025-02-01 12:05:42:989] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: Successfully posted the Mapper Request to Queue with OperationId : 1738411542989 OperationCode : SET_PARAMETER_VALUES [2025-02-01 12:05:42:990] [] [main] MapperRequestRESTService DEBUG: Successfully initiated device operation, The operation id for the request is: 1738411542989 [2025-02-01 12:05:43:196] [] [main] RPCResponseForwarderTest INFO : Starting RPCResponseForwarderTest on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:43:196] [] [main] RPCResponseForwarderTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:43:197] [] [main] RPCResponseForwarderTest INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:43:696] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:43:697] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:43:697] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:05:44:298] [] [main] RPCResponseForwarderTest INFO : Started RPCResponseForwarderTest in 1.121 seconds (JVM running for 23.597) [2025-02-01 12:05:44:318] [] [main] DeviceRPCResponseForwarder DEBUG: NBIOperationResult message is received for deviceId : 0005B9519095, , OprationId: 1000 [2025-02-01 12:05:44:318] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-02-01 12:05:44:318] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Operation result from NBI [2025-02-01 12:05:44:319] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the operation request to WebService: null [2025-02-01 12:05:44:319] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the NBI operation request to SBI Service [2025-02-01 12:05:44:319] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-02-01 12:05:44:319] [] [main] DeviceRPCResponseForwarder DEBUG: Successfully processed NBI operation result. [2025-02-01 12:05:44:388] [] [main] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519095 , Notification Type(s): [BOOTSTRAP] [2025-02-01 12:05:44:389] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-02-01 12:05:44:389] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI [2025-02-01 12:05:44:389] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null [2025-02-01 12:05:44:390] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the Device Notification to SBI Service [2025-02-01 12:05:44:390] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-02-01 12:05:44:390] [] [main] DeviceInformForwarder DEBUG: Successfully processed device notification. [2025-02-01 12:05:44:406] [] [main] DeviceRPCRequestHandlerTests INFO : Starting DeviceRPCRequestHandlerTests on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:44:406] [] [main] DeviceRPCRequestHandlerTests DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:44:406] [] [main] DeviceRPCRequestHandlerTests INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:44:799] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:44:799] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:44:799] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:05:45:369] [] [main] DeviceRPCRequestHandlerTests INFO : Started DeviceRPCRequestHandlerTests in 0.975 seconds (JVM running for 24.669) [2025-02-01 12:05:45:386] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation [2025-02-01 12:05:45:386] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10 [2025-02-01 12:05:45:386] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10 [2025-02-01 12:05:45:393] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:45:393] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:45:394] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10 [2025-02-01 12:05:45:394] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10 [2025-02-01 12:05:45:441] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request [2025-02-01 12:05:45:442] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: No active session exists, hence requesting for Connection request [2025-02-01 12:05:45:442] [0005B95196D0] [main] TR069RequestProcessEngineHelper INFO : Initiating Connection request on device: 0005B95196D0 [2025-02-01 12:05:45:442] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 0005B95196D0_10, listener bean=SessionTimeoutHandler [2025-02-01 12:05:45:443] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 started [2025-02-01 12:05:45:451] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 successfully completed [2025-02-01 12:05:45:451] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 0005B95196D0_10 [2025-02-01 12:05:45:452] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device RPC request with operation ID : 10 [2025-02-01 12:05:45:452] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10 [2025-02-01 12:05:45:452] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation [2025-02-01 12:05:45:584] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation [2025-02-01 12:05:45:585] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10 [2025-02-01 12:05:45:585] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10 [2025-02-01 12:05:45:586] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:45:587] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:45:587] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10 [2025-02-01 12:05:45:588] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10 [2025-02-01 12:05:45:591] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request [2025-02-01 12:05:45:591] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Session is in processing state, Will be notified to session manager to pick the request on session availability [2025-02-01 12:05:45:592] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10 [2025-02-01 12:05:45:592] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation [2025-02-01 12:05:45:615] [] [main] BootstrapInformTest INFO : Starting BootstrapInformTest on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:45:615] [] [main] BootstrapInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:45:615] [] [main] BootstrapInformTest INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:45:956] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:45:957] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:45:957] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:05:46:542] [] [main] BootstrapInformTest INFO : Started BootstrapInformTest in 0.942 seconds (JVM running for 25.842) [2025-02-01 12:05:46:549] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:46:549] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:46:549] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:46:550] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:46:551] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@67ff185110005B9LTE_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-02-01 12:05:46:558] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-02-01 12:05:46:558] [0005B9423910] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-02-01 12:05:46:558] [0005B9423910] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-02-01 12:05:46:559] [0005B9423910] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-02-01 12:05:46:559] [0005B9423910] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-02-01 12:05:46:559] [0005B9423910] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-02-01 12:05:46:559] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9423910_CONNECTION_REQUEST [2025-02-01 12:05:46:560] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9423910_CONNECTION_REQUEST [2025-02-01 12:05:46:560] [0005B9423910] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-02-01 12:05:46:560] [0005B9423910] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform [2025-02-01 12:05:46:561] [0005B9423910] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-02-01 12:05:46:562] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-02-01 12:05:46:562] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP' [2025-02-01 12:05:46:562] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-02-01 12:05:46:587] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists [2025-02-01 12:05:46:587] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests [2025-02-01 12:05:46:588] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9423910 [2025-02-01 12:05:46:588] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:46:588] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:46:758] [0005B9423910] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device [2025-02-01 12:05:46:763] [0005B9423910] [main] SessionManager DEBUG: Creating a new session for the device [2025-02-01 12:05:46:774] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:46:793] [0005B9423910] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-02-01 12:05:46:794] [0005B9423910] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9423910 [2025-02-01 12:05:46:799] [0005B9423910] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-02-01 12:05:46:804] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:46:804] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:46:804] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-02-01 12:05:46:806] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9423910 [2025-02-01 12:05:46:807] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-02-01 12:05:46:807] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-02-01 12:05:46:807] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:46:808] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for deaff65e-e094-11ef-a7cc-0242d1c73add, listener bean=SessionTimeoutHandler [2025-02-01 12:05:46:808] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job deaff65e-e094-11ef-a7cc-0242d1c73add started [2025-02-01 12:05:46:808] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job deaff65e-e094-11ef-a7cc-0242d1c73add successfully completed [2025-02-01 12:05:46:808] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:46:809] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:46:809] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-02-01 12:05:46:817] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-02-01 12:05:47:145] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:47:145] [] [main] CPEManagementService INFO : 11 [2025-02-01 12:05:47:146] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:47:146] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:47:149] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:47:149] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:47:149] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:47:149] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:47:150] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:47:150] [] [main] CPEManagementService DEBUG: The session id is deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:47:150] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:47:150] [] [main] CPEManagementService INFO : Received Empty Device response [2025-02-01 12:05:47:151] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:47:166] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:47:168] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-02-01 12:05:47:168] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-02-01 12:05:47:168] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:47:169] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:47:171] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:47:172] [0005B9423910] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:47:172] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:47:172] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-02-01 12:05:47:172] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9423910 [2025-02-01 12:05:47:173] [0005B9423910] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-02-01 12:05:47:173] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:47:173] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:47:173] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job deaff65e-e094-11ef-a7cc-0242d1c73add started [2025-02-01 12:05:47:174] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job deaff65e-e094-11ef-a7cc-0242d1c73add successfully completed [2025-02-01 12:05:47:174] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:47:174] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : deaff65e-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:05:47:175] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:47:175] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:47:175] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-02-01 12:05:47:178] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:47:178] [] [main] CPEManagementService INFO : [2025-02-01 12:05:47:179] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:47:179] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:47:295] [] [main] ConnRequestInformTest INFO : Starting ConnRequestInformTest on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:47:296] [] [main] ConnRequestInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:47:297] [] [main] ConnRequestInformTest INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:47:786] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:47:786] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:47:786] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:05:48:250] [] [main] ConnRequestInformTest INFO : Started ConnRequestInformTest in 0.973 seconds (JVM running for 27.55) [2025-02-01 12:05:48:259] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:48:259] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:48:260] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:48:260] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:48:264] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@571678401Airvana0005B9LTE_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-02-01 12:05:48:274] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-02-01 12:05:48:274] [0005B9519092] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-02-01 12:05:48:274] [0005B9519092] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-02-01 12:05:48:275] [0005B9519092] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-02-01 12:05:48:275] [0005B9519092] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-02-01 12:05:48:275] [0005B9519092] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-02-01 12:05:48:276] [0005B9519092] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-02-01 12:05:48:276] [0005B9519092] [main] DeviceInformBuilder DEBUG: Constructing Connection Request Inform [2025-02-01 12:05:48:277] [0005B9519092] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-02-01 12:05:48:278] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-02-01 12:05:48:278] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '6 CONNECTION REQUEST' [2025-02-01 12:05:48:278] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-02-01 12:05:48:279] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:48:286] [0005B9519092] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-02-01 12:05:48:286] [0005B9519092] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519092 [2025-02-01 12:05:48:291] [0005B9519092] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-02-01 12:05:48:295] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid9 [2025-02-01 12:05:48:295] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:48:296] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-02-01 12:05:48:299] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519092 [2025-02-01 12:05:48:299] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-02-01 12:05:48:299] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-02-01 12:05:48:300] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:48:300] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid9 [2025-02-01 12:05:48:300] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-02-01 12:05:48:306] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-02-01 12:05:48:307] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:48:307] [] [main] CPEManagementService INFO : 11 [2025-02-01 12:05:48:308] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:48:308] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:48:310] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:48:310] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:48:311] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:48:311] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:48:311] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:48:311] [] [main] CPEManagementService DEBUG: The session id is sessionid9 [2025-02-01 12:05:48:311] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:48:311] [] [main] CPEManagementService INFO : Received Empty Device response [2025-02-01 12:05:48:312] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid9 [2025-02-01 12:05:48:316] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid9 [2025-02-01 12:05:48:317] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-02-01 12:05:48:317] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-02-01 12:05:48:317] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:48:318] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid9 [2025-02-01 12:05:48:318] [0005B9519092] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:48:318] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:48:319] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-02-01 12:05:48:319] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519092 [2025-02-01 12:05:48:319] [0005B9519092] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-02-01 12:05:48:320] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:48:320] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid9 [2025-02-01 12:05:48:320] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:48:321] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:48:321] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-02-01 12:05:48:322] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:48:322] [] [main] CPEManagementService INFO : [2025-02-01 12:05:48:322] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:48:323] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:48:494] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:48:495] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:48:495] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:48:495] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:48:497] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4e81b8991Airvana0005B9LTE_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-02-01 12:05:48:501] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-02-01 12:05:48:501] [0005B9519094] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-02-01 12:05:48:501] [0005B9519094] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-02-01 12:05:48:502] [0005B9519094] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-02-01 12:05:48:502] [0005B9519094] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-02-01 12:05:48:502] [0005B9519094] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-02-01 12:05:48:502] [0005B9519094] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-02-01 12:05:48:502] [0005B9519094] [main] DeviceInformBuilder DEBUG: Constructing Transfer Complete Inform [2025-02-01 12:05:48:502] [0005B9519094] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-02-01 12:05:48:502] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-02-01 12:05:48:502] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE' [2025-02-01 12:05:48:502] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-02-01 12:05:48:503] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:48:505] [0005B9519094] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-02-01 12:05:48:505] [0005B9519094] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519094 [2025-02-01 12:05:48:507] [0005B9519094] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-02-01 12:05:48:509] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5 [2025-02-01 12:05:48:509] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:48:509] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-02-01 12:05:48:511] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519094 [2025-02-01 12:05:48:511] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-02-01 12:05:48:511] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-02-01 12:05:48:511] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:48:511] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5 [2025-02-01 12:05:48:511] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-02-01 12:05:48:513] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-02-01 12:05:48:514] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:48:514] [] [main] CPEManagementService INFO : 11 [2025-02-01 12:05:48:514] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:48:514] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:48:516] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:48:516] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:48:516] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:48:516] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:48:516] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:48:516] [] [main] CPEManagementService DEBUG: The session id is sessionid5 [2025-02-01 12:05:48:516] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:48:516] [] [main] CPEManagementService INFO : Received Empty Device response [2025-02-01 12:05:48:517] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5 [2025-02-01 12:05:48:519] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5 [2025-02-01 12:05:48:519] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-02-01 12:05:48:519] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-02-01 12:05:48:519] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:48:519] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5 [2025-02-01 12:05:48:519] [0005B9519094] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:48:519] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:48:519] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-02-01 12:05:48:520] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519094 [2025-02-01 12:05:48:520] [0005B9519094] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-02-01 12:05:48:520] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:48:520] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5 [2025-02-01 12:05:48:520] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:48:520] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:48:520] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-02-01 12:05:48:520] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:48:520] [] [main] CPEManagementService INFO : [2025-02-01 12:05:48:520] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:48:520] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:48:529] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:48:529] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:48:530] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:48:530] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:48:532] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@423a0fe51Airvana0005B9LTE_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-02-01 12:05:48:536] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-02-01 12:05:48:536] [0005B9519091] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-02-01 12:05:48:536] [0005B9519091] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-02-01 12:05:48:536] [0005B9519091] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-02-01 12:05:48:536] [0005B9519091] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-02-01 12:05:48:536] [0005B9519091] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-02-01 12:05:48:537] [0005B9519091] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-02-01 12:05:48:537] [0005B9519091] [main] DeviceInformBuilder DEBUG: Constructing BOOT Inform [2025-02-01 12:05:48:537] [0005B9519091] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-02-01 12:05:48:537] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-02-01 12:05:48:537] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '1 BOOT' [2025-02-01 12:05:48:537] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-02-01 12:05:48:537] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOT, hence aborting all the pending operations if any exists [2025-02-01 12:05:48:537] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests [2025-02-01 12:05:48:537] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9519091 [2025-02-01 12:05:48:537] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:48:539] [0005B9519091] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-02-01 12:05:48:539] [0005B9519091] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519091 [2025-02-01 12:05:48:541] [0005B9519091] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-02-01 12:05:48:543] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5 [2025-02-01 12:05:48:543] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:48:543] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-02-01 12:05:48:545] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519091 [2025-02-01 12:05:48:545] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-02-01 12:05:48:545] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-02-01 12:05:48:545] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:48:545] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5 [2025-02-01 12:05:48:545] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-02-01 12:05:48:548] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-02-01 12:05:48:549] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:48:549] [] [main] CPEManagementService INFO : 11 [2025-02-01 12:05:48:549] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:48:549] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:48:550] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:48:551] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:48:551] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:48:551] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:48:551] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:48:551] [] [main] CPEManagementService DEBUG: The session id is sessionid5 [2025-02-01 12:05:48:551] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:48:551] [] [main] CPEManagementService INFO : Received Empty Device response [2025-02-01 12:05:48:551] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5 [2025-02-01 12:05:48:553] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5 [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5 [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:48:554] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-02-01 12:05:48:554] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519091 [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5 [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:48:554] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-02-01 12:05:48:554] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:48:555] [] [main] CPEManagementService INFO : [2025-02-01 12:05:48:555] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:48:555] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:48:574] [] [main] TransferCompleteTest INFO : Starting TransferCompleteTest on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:48:574] [] [main] TransferCompleteTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:48:574] [] [main] TransferCompleteTest INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:48:871] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:48:871] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:48:871] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:05:49:383] [] [main] TransferCompleteTest INFO : Started TransferCompleteTest in 0.824 seconds (JVM running for 28.682) [2025-02-01 12:05:49:391] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:49:392] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:49:392] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:49:392] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:49:394] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@3bc92e9c00005B9AAAA2202019-07-08T18:15:43.032Z2019-07-08T18:15:43.032Z [2025-02-01 12:05:49:398] [] [main] CPEManagementService INFO : Event notified by the device is of type: TransferComplete [2025-02-01 12:05:49:398] [] [main] DeviceEventHandler DEBUG: Processing Transfer Complete [2025-02-01 12:05:49:398] [0005B9AAAA22] [main] DeviceEventHandler DEBUG: TransferComplete inform received with Start time [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE' [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: newSessionId [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper WARN : Notification do not contains either connection request URL or swVer or hwVer of the device [2025-02-01 12:05:49:401] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details [2025-02-01 12:05:49:402] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-02-01 12:05:49:402] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-02-01 12:05:49:402] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:49:402] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for newSessionId, listener bean=SessionTimeoutHandler [2025-02-01 12:05:49:402] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId started [2025-02-01 12:05:49:402] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId successfully completed [2025-02-01 12:05:49:402] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for newSessionId [2025-02-01 12:05:49:403] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : newSessionId [2025-02-01 12:05:49:403] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-02-01 12:05:49:403] [] [main] DeviceEventHandler DEBUG: Successfully processed the TRANSFER COMPLETE Inform [2025-02-01 12:05:49:407] [] [main] TR069RPC DEBUG: Key element is: 0 [2025-02-01 12:05:49:408] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:49:408] [] [main] CPEManagementService INFO : 1 [2025-02-01 12:05:49:408] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:49:408] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:49:411] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:05:49:411] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:05:49:412] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:05:49:412] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:05:49:412] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:05:49:412] [] [main] CPEManagementService DEBUG: The session id is newSessionId [2025-02-01 12:05:49:413] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:05:49:413] [] [main] CPEManagementService INFO : Received Empty Device response [2025-02-01 12:05:49:414] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: newSessionId [2025-02-01 12:05:49:414] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: newSessionId [2025-02-01 12:05:49:415] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-02-01 12:05:49:415] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-02-01 12:05:49:415] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:05:49:415] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: newSessionId [2025-02-01 12:05:49:415] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:05:49:415] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:05:49:416] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-02-01 12:05:49:416] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9AAAA22 [2025-02-01 12:05:49:416] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-02-01 12:05:49:416] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:05:49:416] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.newSessionId [2025-02-01 12:05:49:416] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId started [2025-02-01 12:05:49:417] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId successfully completed [2025-02-01 12:05:49:417] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.newSessionId [2025-02-01 12:05:49:417] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : newSessionId [2025-02-01 12:05:49:417] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:05:49:417] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:05:49:417] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-02-01 12:05:49:418] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:05:49:418] [] [main] CPEManagementService INFO : [2025-02-01 12:05:49:418] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:05:49:418] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:05:49:595] [] [main] InformSwVersionUpdatedTest INFO : Starting InformSwVersionUpdatedTest on prd-ubuntu1804-docker-4c-4g-3354 with PID 2802 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter) [2025-02-01 12:05:49:596] [] [main] InformSwVersionUpdatedTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE [2025-02-01 12:05:49:596] [] [main] InformSwVersionUpdatedTest INFO : No active profile set, falling back to default profiles: default [2025-02-01 12:05:49:957] [] [main] QuartzSchedulerManager DEBUG: init started [2025-02-01 12:05:49:957] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service [2025-02-01 12:05:49:957] [] [main] QuartzSchedulerManager DEBUG: init complete [2025-02-01 12:06:00:551] [] [main] InformSwVersionUpdatedTest INFO : Started InformSwVersionUpdatedTest in 10.972 seconds (JVM running for 39.851) [2025-02-01 12:06:00:566] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:06:00:566] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:06:00:566] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:06:00:566] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:06:00:569] [] [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-02-01 12:06:00:575] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-02-01 12:06:00:575] [0005B9519090] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-02-01 12:06:00:575] [0005B9519090] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-02-01 12:06:00:575] [0005B9519090] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-02-01 12:06:00:575] [0005B9519090] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-02-01 12:06:00:575] [0005B9519090] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-02-01 12:06:00:575] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9519090_CONNECTION_REQUEST [2025-02-01 12:06:00:586] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9519090_CONNECTION_REQUEST [2025-02-01 12:06:00:587] [0005B9519090] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-02-01 12:06:00:587] [0005B9519090] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform [2025-02-01 12:06:00:587] [0005B9519090] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-02-01 12:06:00:588] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-02-01 12:06:00:588] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP' [2025-02-01 12:06:00:588] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-02-01 12:06:00:590] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists [2025-02-01 12:06:00:591] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests [2025-02-01 12:06:00:599] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Grouping the records based on operationId [2025-02-01 12:06:00:600] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists 0 pending NBI requests for the device [2025-02-01 12:06:00:600] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:00:600] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:00:604] [0005B9519090] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device [2025-02-01 12:06:00:605] [0005B9519090] [main] SessionManager DEBUG: Creating a new session for the device [2025-02-01 12:06:00:611] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:00:618] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:619] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:06:00:619] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-02-01 12:06:00:619] [0005B9519090] [main] TR069EventNotificationService DEBUG: Device Inform Event received: '0 BOOTSTRAP' [2025-02-01 12:06:00:697] [0005B9519090] [main] TR069EventNotificationService DEBUG: Successfully posted the device inform event to DM to forward to NBI [2025-02-01 12:06:00:698] [] [main] TR069RequestProcessEngineHelper DEBUG: Device details are changed [2025-02-01 12:06:00:698] [] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details [2025-02-01 12:06:00:698] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-02-01 12:06:00:703] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-02-01 12:06:00:703] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:06:00:705] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for e6f0157f-e094-11ef-a7cc-0242d1c73add, listener bean=SessionTimeoutHandler [2025-02-01 12:06:00:705] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job e6f0157f-e094-11ef-a7cc-0242d1c73add started [2025-02-01 12:06:00:706] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job e6f0157f-e094-11ef-a7cc-0242d1c73add successfully completed [2025-02-01 12:06:00:706] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:706] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:707] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-02-01 12:06:00:729] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-02-01 12:06:00:730] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:06:00:730] [] [main] CPEManagementService INFO : 11 [2025-02-01 12:06:00:731] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:06:00:731] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:06:00:735] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:06:00:735] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:06:00:735] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:06:00:735] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:06:00:735] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:06:00:735] [] [main] CPEManagementService DEBUG: The session id is e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:735] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:06:00:735] [] [main] CPEManagementService INFO : Received Empty Device response [2025-02-01 12:06:00:736] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:742] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:743] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-02-01 12:06:00:743] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-02-01 12:06:00:743] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:00:743] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:00:744] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:744] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:06:00:744] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:06:00:744] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-02-01 12:06:00:745] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519090 [2025-02-01 12:06:00:745] [0005B9519090] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-02-01 12:06:00:745] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:06:00:745] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:745] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job e6f0157f-e094-11ef-a7cc-0242d1c73add started [2025-02-01 12:06:00:746] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job e6f0157f-e094-11ef-a7cc-0242d1c73add successfully completed [2025-02-01 12:06:00:747] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:747] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : e6f0157f-e094-11ef-a7cc-0242d1c73add [2025-02-01 12:06:00:747] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:06:00:747] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:06:00:747] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-02-01 12:06:00:750] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:06:00:750] [] [main] CPEManagementService INFO : [2025-02-01 12:06:00:750] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:06:00:751] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:06:00:785] [] [DefaultMessageListenerContainer-1] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519090 , Notification Type(s): [BOOTSTRAP] [2025-02-01 12:06:00:785] [] [DefaultMessageListenerContainer-1] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-02-01 12:06:00:785] [] [DefaultMessageListenerContainer-1] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI [2025-02-01 12:06:00:785] [] [DefaultMessageListenerContainer-1] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null [2025-02-01 12:06:00:791] [] [DefaultMessageListenerContainer-1] DeviceEventsMapperNotificationService ERROR: Unable to post the Device Notification, Reason: URI is not absolute [2025-02-01 12:06:00:791] [] [DefaultMessageListenerContainer-1] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-02-01 12:06:00:791] [] [DefaultMessageListenerContainer-1] DeviceInformForwarder DEBUG: Successfully processed device notification. [2025-02-01 12:06:00:969] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:06:00:969] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:06:00:969] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:06:00:969] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:06:00:982] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4a870b461Airvana0005B9LTE_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-02-01 12:06:00:996] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-02-01 12:06:00:996] [0005B9519093] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-02-01 12:06:00:996] [0005B9519093] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-02-01 12:06:00:997] [0005B9519093] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-02-01 12:06:00:997] [0005B9519093] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-02-01 12:06:00:997] [0005B9519093] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-02-01 12:06:00:998] [0005B9519093] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-02-01 12:06:00:998] [0005B9519093] [main] DeviceInformBuilder DEBUG: Constructing PERIODIC Inform [2025-02-01 12:06:00:999] [0005B9519093] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-02-01 12:06:00:999] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-02-01 12:06:00:999] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '2 PERIODIC' [2025-02-01 12:06:00:999] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-02-01 12:06:00:999] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:01:001] [0005B9519093] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-02-01 12:06:01:001] [0005B9519093] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519093 [2025-02-01 12:06:01:004] [0005B9519093] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-02-01 12:06:01:008] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid10 [2025-02-01 12:06:01:008] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:06:01:008] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-02-01 12:06:01:010] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519093 [2025-02-01 12:06:01:010] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-02-01 12:06:01:010] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-02-01 12:06:01:010] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:06:01:011] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid10 [2025-02-01 12:06:01:011] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-02-01 12:06:01:014] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-02-01 12:06:01:014] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:06:01:014] [] [main] CPEManagementService INFO : 11 [2025-02-01 12:06:01:014] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:06:01:014] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:06:01:017] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:06:01:017] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:06:01:017] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:06:01:017] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:06:01:017] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:06:01:017] [] [main] CPEManagementService DEBUG: The session id is sessionid10 [2025-02-01 12:06:01:017] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:06:01:017] [] [main] CPEManagementService INFO : Received Empty Device response [2025-02-01 12:06:01:017] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid10 [2025-02-01 12:06:01:020] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid10 [2025-02-01 12:06:01:020] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-02-01 12:06:01:020] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-02-01 12:06:01:020] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid10 [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:06:01:021] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-02-01 12:06:01:021] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519093 [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid10 [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:06:01:021] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-02-01 12:06:01:021] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:06:01:021] [] [main] CPEManagementService INFO : [2025-02-01 12:06:01:022] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:06:01:022] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:06:01:032] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:06:01:032] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:06:01:032] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:06:01:032] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:06:01:036] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@6a7ba1821Airvana0005B9LTE_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-02-01 12:06:01:040] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform [2025-02-01 12:06:01:040] [0005B9519095] [main] DeviceEventHandler INFO : Processing the device Inform event [2025-02-01 12:06:01:040] [0005B9519095] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic [2025-02-01 12:06:01:040] [0005B9519095] [main] DeviceEventHandler INFO : Is device authentication successful: true [2025-02-01 12:06:01:040] [0005B9519095] [main] DeviceEventHandler DEBUG: The root element is: Device [2025-02-01 12:06:01:040] [0005B9519095] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device [2025-02-01 12:06:01:041] [0005B9519095] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device [2025-02-01 12:06:01:041] [0005B9519095] [main] DeviceInformBuilder DEBUG: Constructing VALUECHANGE Inform [2025-02-01 12:06:01:041] [0005B9519095] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process [2025-02-01 12:06:01:041] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event [2025-02-01 12:06:01:041] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '4 VALUE CHANGE' [2025-02-01 12:06:01:041] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device [2025-02-01 12:06:01:041] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:01:043] [0005B9519095] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully. [2025-02-01 12:06:01:043] [0005B9519095] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519095 [2025-02-01 12:06:01:047] [0005B9519095] [main] DeviceOperationManager DEBUG: Successfully updated the device [2025-02-01 12:06:01:049] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5 [2025-02-01 12:06:01:049] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:06:01:049] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper [2025-02-01 12:06:01:051] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519095 [2025-02-01 12:06:01:052] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id [2025-02-01 12:06:01:052] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED [2025-02-01 12:06:01:052] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:06:01:052] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5 [2025-02-01 12:06:01:052] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event [2025-02-01 12:06:01:056] [] [main] TR069RPC DEBUG: Key element is: 1 [2025-02-01 12:06:01:056] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:06:01:056] [] [main] CPEManagementService INFO : 11 [2025-02-01 12:06:01:057] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:06:01:057] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request [2025-02-01 12:06:01:059] [] [main] CPEManagementService DEBUG: A device event occurred [2025-02-01 12:06:01:059] [] [main] CPEManagementService DEBUG: Request Headers Content-Type [2025-02-01 12:06:01:059] [] [main] CPEManagementService DEBUG: Request Headers Accept [2025-02-01 12:06:01:059] [] [main] CPEManagementService DEBUG: Request Headers Authorization [2025-02-01 12:06:01:059] [] [main] CPEManagementService DEBUG: Request Headers Cookie [2025-02-01 12:06:01:059] [] [main] CPEManagementService DEBUG: The session id is sessionid5 [2025-02-01 12:06:01:059] [] [main] CPEManagementService DEBUG: Next char is -1 [2025-02-01 12:06:01:060] [] [main] CPEManagementService INFO : Received Empty Device response [2025-02-01 12:06:01:062] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5 [2025-02-01 12:06:01:067] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5 [2025-02-01 12:06:01:068] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request [2025-02-01 12:06:01:068] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the empty request from device [2025-02-01 12:06:01:068] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device [2025-02-01 12:06:01:068] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5 [2025-02-01 12:06:01:068] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put [2025-02-01 12:06:01:068] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device [2025-02-01 12:06:01:068] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request [2025-02-01 12:06:01:069] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519095 [2025-02-01 12:06:01:069] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device [2025-02-01 12:06:01:069] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state [2025-02-01 12:06:01:069] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5 [2025-02-01 12:06:01:069] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED [2025-02-01 12:06:01:069] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session [2025-02-01 12:06:01:069] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request [2025-02-01 12:06:01:070] [] [main] CPEManagementService DEBUG: Clearing the cookies [2025-02-01 12:06:01:070] [] [main] CPEManagementService INFO : [2025-02-01 12:06:01:070] [] [main] CPEManagementService DEBUG: End of processing [2025-02-01 12:06:01:070] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request