Debug Log started at: 2025-05-10 12:05:19[2025-05-10 12:05:21:043] [] [main] DeviceConnectTest INFO : Starting DeviceConnectTest on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:21:048] [] [main] DeviceConnectTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:21:049] [] [main] DeviceConnectTest INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:25:284] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:25:284] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:25:285] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:05:26:691] [] [main] DeviceConnectTest INFO : Started DeviceConnectTest in 5.932 seconds (JVM running for 8.079)
[2025-05-10 12:05:26:813] [0005B9AAAA22] [main] ConnectionReqEventHandler INFO : Received a JMS message from Request Processor for initiating connection request
[2025-05-10 12:05:26:813] [0005B9AAAA22] [main] ConnectionReqEventProcessor INFO : Initiating connection request on the device. Connection request URL is : http://10.10.10.10:8888/connect/device
[2025-05-10 12:05:26:817] [0005B9AAAA22] [main] ConnectionReqEventProcessor DEBUG: Successfully started the timer task for connection request initiation on device : 0005B9AAAA22
[2025-05-10 12:05:26:817] [0005B9AAAA22] [main] ConnectionReqEventHandler DEBUG: Sent TR069 connection request to device
[2025-05-10 12:05:26:941] [] [main] AOOpResultTest INFO : Starting AOOpResultTest on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:26:942] [] [main] AOOpResultTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:26:943] [] [main] AOOpResultTest INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:27:539] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:27:539] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:27:540] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:05:28:078] [] [main] AOOpResultTest INFO : Started AOOpResultTest in 1.154 seconds (JVM running for 9.466)
[2025-05-10 12:05:28:142] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:28:144] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:28:144] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:28:144] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:28:144] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-05-10 12:05:28:225] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@7bd3a5e61265561012019-07-08T18:15:42.030Z2019-07-08T18:15:42.030Z
[2025-05-10 12:05:28:329] [] [main] CPEManagementService INFO : Event notified by the device is of type: DownloadResponse
[2025-05-10 12:05:28:329] [] [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-05-10 12:05:28:339] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-05-10 12:05:28:339] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-05-10 12:05:28:345] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DOWNLOAD
[2025-05-10 12:05:28:347] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DownloadResponse
[2025-05-10 12:05:28:348] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-05-10 12:05:28:348] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-05-10 12:05:28:349] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:28:349] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-05-10 12:05:28:350] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:28:350] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-05-10 12:05:28:351] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:28:351] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-05-10 12:05:28:351] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:28:352] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-05-10 12:05:28:352] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:28:352] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-05-10 12:05:28:353] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-05-10 12:05:28:353] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:28:354] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-05-10 12:05:28:354] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:28:372] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:28:386] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:28:386] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:28:386] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:28:570] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:28:570] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:28:571] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:28:571] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:28:571] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-05-10 12:05:28:574] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@6c1e6438914620
[2025-05-10 12:05:28:576] [] [main] CPEManagementService INFO : Event notified by the device is of type: FactoryResetResponse
[2025-05-10 12:05:28:577] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.FactoryResetResponse@26486a0d
[2025-05-10 12:05:28:577] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-05-10 12:05:28:577] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-05-10 12:05:28:578] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation FACTORY_RESET
[2025-05-10 12:05:28:578] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is FRResponse
[2025-05-10 12:05:28:579] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-05-10 12:05:28:579] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-05-10 12:05:28:579] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:28:579] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-05-10 12:05:28:579] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:28:579] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-05-10 12:05:28:579] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:28:580] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-05-10 12:05:28:580] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:28:580] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-05-10 12:05:28:580] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:28:580] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-05-10 12:05:28:580] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-05-10 12:05:28:580] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:28:580] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-05-10 12:05:28:581] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:28:581] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:28:581] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:28:581] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:28:581] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:28:593] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:28:593] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:28:593] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:28:593] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:28:594] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-05-10 12:05:28:595] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@6f9e90dd12653738
[2025-05-10 12:05:28:597] [] [main] CPEManagementService INFO : Event notified by the device is of type: SetParameterAttributesResponse
[2025-05-10 12:05:28:597] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.SetParameterAttributesResponse@6898f258
[2025-05-10 12:05:28:598] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-05-10 12:05:28:598] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-05-10 12:05:28:600] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation SET_PARAMETER_ATTRIBUTES
[2025-05-10 12:05:28:600] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is SPAResponse
[2025-05-10 12:05:28:601] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-05-10 12:05:28:601] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-05-10 12:05:28:601] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:28:601] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-05-10 12:05:28:601] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:28:601] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-05-10 12:05:28:602] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:28:602] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-05-10 12:05:28:602] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:28:602] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-05-10 12:05:28:602] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:28:602] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-05-10 12:05:28:602] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-05-10 12:05:28:603] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:28:603] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-05-10 12:05:28:603] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:28:603] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:28:603] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:28:603] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:28:604] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:28:614] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:28:615] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:28:615] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:28:615] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:28:616] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-05-10 12:05:28:617] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@459cf81b12655897Device.Hosts.HostNumberOfEntries1
[2025-05-10 12:05:28:621] [] [main] CPEManagementService INFO : Event notified by the device is of type: GetParameterValuesResponse
[2025-05-10 12:05:28:621] [] [main] CPEManagementService DEBUG: Received Operation Result response Device.Hosts.HostNumberOfEntries=1
[2025-05-10 12:05:28:622] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-05-10 12:05:28:622] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-05-10 12:05:28:623] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation GET_PARAMETER_VALUES
[2025-05-10 12:05:28:623] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is GPVResponse
[2025-05-10 12:05:28:624] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-05-10 12:05:28:624] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-05-10 12:05:28:625] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:28:625] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-05-10 12:05:28:625] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:28:625] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-05-10 12:05:28:625] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:28:625] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-05-10 12:05:28:626] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:28:626] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-05-10 12:05:28:626] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:28:626] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-05-10 12:05:28:626] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-05-10 12:05:28:626] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:28:627] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-05-10 12:05:28:627] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:28:627] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:28:628] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:28:628] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:28:628] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:28:637] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:28:637] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:28:637] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:28:637] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:28:638] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-05-10 12:05:28:639] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4d452f6f133062910
[2025-05-10 12:05:28:641] [] [main] CPEManagementService INFO : Event notified by the device is of type: DeleteObjectResponse
[2025-05-10 12:05:28:641] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.DeleteObjectResponse@20b5eabf
[2025-05-10 12:05:28:642] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-05-10 12:05:28:642] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-05-10 12:05:28:642] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DELETE_OBJECT
[2025-05-10 12:05:28:643] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DOResponse
[2025-05-10 12:05:28:643] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-05-10 12:05:28:643] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-05-10 12:05:28:643] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:28:643] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-05-10 12:05:28:643] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:28:643] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-05-10 12:05:28:643] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:28:644] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-05-10 12:05:28:644] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:28:644] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-05-10 12:05:28:644] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:28:644] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-05-10 12:05:28:644] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-05-10 12:05:28:644] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:28:644] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-05-10 12:05:28:645] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:28:645] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:28:645] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:28:645] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:28:645] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:28:653] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:28:654] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:28:654] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:28:654] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:28:654] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-05-10 12:05:28:655] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@73b950d1913870
[2025-05-10 12:05:28:657] [] [main] CPEManagementService INFO : Event notified by the device is of type: RebootResponse
[2025-05-10 12:05:28:657] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.RebootResponse@6b7b9547
[2025-05-10 12:05:28:658] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-05-10 12:05:28:658] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-05-10 12:05:28:658] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation REBOOT
[2025-05-10 12:05:28:659] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is RebootResponse
[2025-05-10 12:05:28:659] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-05-10 12:05:28:659] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-05-10 12:05:28:659] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:28:659] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-05-10 12:05:28:659] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:28:659] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-05-10 12:05:28:660] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:28:660] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-05-10 12:05:28:660] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:28:660] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-05-10 12:05:28:660] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:28:660] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-05-10 12:05:28:660] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-05-10 12:05:28:660] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:28:661] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-05-10 12:05:28:661] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:28:661] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:28:661] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:28:661] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:28:661] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:28:669] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:28:670] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:28:670] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:28:670] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:28:670] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-05-10 12:05:28:671] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@5dea619c1265443140
[2025-05-10 12:05:28:673] [] [main] CPEManagementService INFO : Event notified by the device is of type: AddObjectResponse
[2025-05-10 12:05:28:673] [] [main] CPEManagementService DEBUG: Received Operation Result response AddObjectResponse: status=0 instance=4
[2025-05-10 12:05:28:673] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-05-10 12:05:28:674] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-05-10 12:05:28:674] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation ADD_OBJECT
[2025-05-10 12:05:28:674] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is AOResponse
[2025-05-10 12:05:28:674] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-05-10 12:05:28:674] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-05-10 12:05:28:675] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:28:676] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-05-10 12:05:28:676] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-05-10 12:05:28:676] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:28:676] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-05-10 12:05:28:676] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:28:676] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:28:676] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:28:676] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:28:677] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:28:693] [] [main] InvokeRPCTest INFO : Starting InvokeRPCTest on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:28:694] [] [main] InvokeRPCTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:28:694] [] [main] InvokeRPCTest INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:29:267] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:29:267] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:29:267] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:05:29:825] [] [main] InvokeRPCTest INFO : Started InvokeRPCTest in 1.145 seconds (JVM running for 11.214)
[2025-05-10 12:05:29:862] [] [main] MapperRequestRESTService DEBUG: Received a Device operation request from Mapper
[2025-05-10 12:05:29:863] [0005B95196D0] [main] ACSServiceAPIImpl INFO : Received request to perform device operation. OperationCode: SET_PARAMETER_VALUES
[2025-05-10 12:05:29:863] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: The operation ID generated for processing the Device RPC request is - 1746878729863
[2025-05-10 12:05:29:863] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: Successfully posted the Mapper Request to Queue with OperationId : 1746878729863 OperationCode : SET_PARAMETER_VALUES
[2025-05-10 12:05:29:863] [] [main] MapperRequestRESTService DEBUG: Successfully initiated device operation, The operation id for the request is: 1746878729863
[2025-05-10 12:05:30:044] [] [main] RPCResponseForwarderTest INFO : Starting RPCResponseForwarderTest on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:30:045] [] [main] RPCResponseForwarderTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:30:045] [] [main] RPCResponseForwarderTest INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:30:566] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:30:566] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:30:567] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:05:31:133] [] [main] RPCResponseForwarderTest INFO : Started RPCResponseForwarderTest in 1.102 seconds (JVM running for 12.521)
[2025-05-10 12:05:31:146] [] [main] DeviceRPCResponseForwarder DEBUG: NBIOperationResult message is received for deviceId : 0005B9519095, , OprationId: 1000
[2025-05-10 12:05:31:146] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-05-10 12:05:31:146] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Operation result from NBI
[2025-05-10 12:05:31:146] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the operation request to WebService: null
[2025-05-10 12:05:31:147] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the NBI operation request to SBI Service
[2025-05-10 12:05:31:147] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-05-10 12:05:31:147] [] [main] DeviceRPCResponseForwarder DEBUG: Successfully processed NBI operation result.
[2025-05-10 12:05:31:221] [] [main] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519095 , Notification Type(s): [BOOTSTRAP]
[2025-05-10 12:05:31:221] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-05-10 12:05:31:221] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI
[2025-05-10 12:05:31:221] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null
[2025-05-10 12:05:31:222] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the Device Notification to SBI Service
[2025-05-10 12:05:31:222] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-05-10 12:05:31:222] [] [main] DeviceInformForwarder DEBUG: Successfully processed device notification.
[2025-05-10 12:05:31:241] [] [main] DeviceRPCRequestHandlerTests INFO : Starting DeviceRPCRequestHandlerTests on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:31:241] [] [main] DeviceRPCRequestHandlerTests DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:31:241] [] [main] DeviceRPCRequestHandlerTests INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:31:581] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:31:581] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:31:581] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:05:32:063] [] [main] DeviceRPCRequestHandlerTests INFO : Started DeviceRPCRequestHandlerTests in 0.836 seconds (JVM running for 13.451)
[2025-05-10 12:05:32:076] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation
[2025-05-10 12:05:32:077] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10
[2025-05-10 12:05:32:077] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10
[2025-05-10 12:05:32:084] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:32:084] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:32:085] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10
[2025-05-10 12:05:32:085] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10
[2025-05-10 12:05:32:135] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request
[2025-05-10 12:05:32:135] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: No active session exists, hence requesting for Connection request
[2025-05-10 12:05:32:135] [0005B95196D0] [main] TR069RequestProcessEngineHelper INFO : Initiating Connection request on device: 0005B95196D0
[2025-05-10 12:05:32:136] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 0005B95196D0_10, listener bean=SessionTimeoutHandler
[2025-05-10 12:05:32:137] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 started
[2025-05-10 12:05:32:143] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 successfully completed
[2025-05-10 12:05:32:143] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 0005B95196D0_10
[2025-05-10 12:05:32:143] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device RPC request with operation ID : 10
[2025-05-10 12:05:32:144] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10
[2025-05-10 12:05:32:144] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation
[2025-05-10 12:05:32:302] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation
[2025-05-10 12:05:32:302] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10
[2025-05-10 12:05:32:303] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10
[2025-05-10 12:05:32:303] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:32:304] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:32:304] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10
[2025-05-10 12:05:32:305] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10
[2025-05-10 12:05:32:308] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request
[2025-05-10 12:05:32:309] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Session is in processing state, Will be notified to session manager to pick the request on session availability
[2025-05-10 12:05:32:309] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10
[2025-05-10 12:05:32:309] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation
[2025-05-10 12:05:32:330] [] [main] BootstrapInformTest INFO : Starting BootstrapInformTest on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:32:331] [] [main] BootstrapInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:32:331] [] [main] BootstrapInformTest INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:32:684] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:32:685] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:32:685] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:05:43:212] [] [main] BootstrapInformTest INFO : Started BootstrapInformTest in 10.895 seconds (JVM running for 24.6)
[2025-05-10 12:05:43:219] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:43:220] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:43:220] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:43:220] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:43:222] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@1f8e03b710005B9LTE_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-05-10 12:05:43:230] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-05-10 12:05:43:230] [0005B9423910] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-05-10 12:05:43:230] [0005B9423910] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-05-10 12:05:43:231] [0005B9423910] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-05-10 12:05:43:231] [0005B9423910] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-05-10 12:05:43:231] [0005B9423910] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-05-10 12:05:43:231] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9423910_CONNECTION_REQUEST
[2025-05-10 12:05:43:231] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9423910_CONNECTION_REQUEST
[2025-05-10 12:05:43:232] [0005B9423910] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-05-10 12:05:43:232] [0005B9423910] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform
[2025-05-10 12:05:43:232] [0005B9423910] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-05-10 12:05:43:233] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-05-10 12:05:43:234] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP'
[2025-05-10 12:05:43:234] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-05-10 12:05:43:251] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists
[2025-05-10 12:05:43:251] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-05-10 12:05:43:251] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9423910
[2025-05-10 12:05:43:252] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:43:252] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:43:417] [0005B9423910] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device
[2025-05-10 12:05:43:426] [0005B9423910] [main] SessionManager DEBUG: Creating a new session for the device
[2025-05-10 12:05:43:435] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:43:450] [0005B9423910] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-05-10 12:05:43:450] [0005B9423910] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9423910
[2025-05-10 12:05:43:455] [0005B9423910] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-05-10 12:05:43:459] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: 192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:460] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:43:460] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-05-10 12:05:43:462] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9423910
[2025-05-10 12:05:43:463] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-05-10 12:05:43:463] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-05-10 12:05:43:463] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:43:464] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 192e462a-2d97-11f0-b79e-0242df564c1b, listener bean=SessionTimeoutHandler
[2025-05-10 12:05:43:464] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 192e462a-2d97-11f0-b79e-0242df564c1b started
[2025-05-10 12:05:43:464] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 192e462a-2d97-11f0-b79e-0242df564c1b successfully completed
[2025-05-10 12:05:43:464] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:465] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : 192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:465] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-05-10 12:05:43:473] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-05-10 12:05:43:793] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:43:794] [] [main] CPEManagementService INFO : 11
[2025-05-10 12:05:43:797] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:43:797] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:43:801] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:43:801] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:43:801] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:43:801] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:43:802] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:43:802] [] [main] CPEManagementService DEBUG: The session id is 192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:802] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:43:802] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-05-10 12:05:43:803] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: 192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:817] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: 192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:818] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-05-10 12:05:43:818] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-05-10 12:05:43:818] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:43:818] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:43:820] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: 192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:820] [0005B9423910] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:43:820] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:43:821] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-05-10 12:05:43:821] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9423910
[2025-05-10 12:05:43:821] [0005B9423910] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-05-10 12:05:43:821] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:43:821] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:822] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 192e462a-2d97-11f0-b79e-0242df564c1b started
[2025-05-10 12:05:43:822] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 192e462a-2d97-11f0-b79e-0242df564c1b successfully completed
[2025-05-10 12:05:43:822] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:822] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : 192e462a-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:05:43:823] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:43:823] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:43:823] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-05-10 12:05:43:825] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:43:825] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:43:825] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:43:825] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:44:033] [] [main] ConnRequestInformTest INFO : Starting ConnRequestInformTest on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:44:033] [] [main] ConnRequestInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:44:034] [] [main] ConnRequestInformTest INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:44:461] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:44:462] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:44:462] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:05:44:859] [] [main] ConnRequestInformTest INFO : Started ConnRequestInformTest in 0.85 seconds (JVM running for 26.247)
[2025-05-10 12:05:44:866] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:44:866] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:44:866] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:44:866] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:44:869] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@1052eace1Airvana0005B9LTE_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-05-10 12:05:44:873] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-05-10 12:05:44:873] [0005B9519092] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-05-10 12:05:44:873] [0005B9519092] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-05-10 12:05:44:874] [0005B9519092] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-05-10 12:05:44:874] [0005B9519092] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-05-10 12:05:44:874] [0005B9519092] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-05-10 12:05:44:874] [0005B9519092] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-05-10 12:05:44:874] [0005B9519092] [main] DeviceInformBuilder DEBUG: Constructing Connection Request Inform
[2025-05-10 12:05:44:874] [0005B9519092] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-05-10 12:05:44:875] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-05-10 12:05:44:875] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '6 CONNECTION REQUEST'
[2025-05-10 12:05:44:875] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-05-10 12:05:44:875] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:44:881] [0005B9519092] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-05-10 12:05:44:881] [0005B9519092] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519092
[2025-05-10 12:05:44:886] [0005B9519092] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-05-10 12:05:44:889] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid9
[2025-05-10 12:05:44:890] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:44:890] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-05-10 12:05:44:892] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519092
[2025-05-10 12:05:44:892] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-05-10 12:05:44:892] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-05-10 12:05:44:892] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:44:892] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid9
[2025-05-10 12:05:44:892] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-05-10 12:05:44:896] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-05-10 12:05:44:897] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:44:897] [] [main] CPEManagementService INFO : 11
[2025-05-10 12:05:44:898] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:44:898] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:44:900] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:44:900] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:44:900] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:44:900] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:44:900] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:44:900] [] [main] CPEManagementService DEBUG: The session id is sessionid9
[2025-05-10 12:05:44:900] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:44:900] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-05-10 12:05:44:901] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid9
[2025-05-10 12:05:44:903] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid9
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid9
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:44:904] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-05-10 12:05:44:904] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519092
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid9
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:44:904] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:44:905] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-05-10 12:05:44:905] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:44:905] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:44:905] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:44:905] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:45:113] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:45:113] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:45:113] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:45:113] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:45:116] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@282eb4ec1Airvana0005B9LTE_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-05-10 12:05:45:120] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-05-10 12:05:45:121] [0005B9519094] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-05-10 12:05:45:121] [0005B9519094] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-05-10 12:05:45:121] [0005B9519094] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-05-10 12:05:45:121] [0005B9519094] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-05-10 12:05:45:121] [0005B9519094] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-05-10 12:05:45:121] [0005B9519094] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-05-10 12:05:45:121] [0005B9519094] [main] DeviceInformBuilder DEBUG: Constructing Transfer Complete Inform
[2025-05-10 12:05:45:121] [0005B9519094] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-05-10 12:05:45:121] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-05-10 12:05:45:122] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE'
[2025-05-10 12:05:45:122] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-05-10 12:05:45:122] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:45:124] [0005B9519094] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-05-10 12:05:45:124] [0005B9519094] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519094
[2025-05-10 12:05:45:125] [0005B9519094] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-05-10 12:05:45:127] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-05-10 12:05:45:128] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:45:128] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-05-10 12:05:45:129] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519094
[2025-05-10 12:05:45:129] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-05-10 12:05:45:129] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-05-10 12:05:45:129] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:45:130] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-05-10 12:05:45:130] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-05-10 12:05:45:132] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-05-10 12:05:45:133] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:45:133] [] [main] CPEManagementService INFO : 11
[2025-05-10 12:05:45:133] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:45:133] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:45:134] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:45:135] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:45:135] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:45:135] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:45:135] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:45:135] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-05-10 12:05:45:135] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:45:135] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-05-10 12:05:45:135] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-05-10 12:05:45:137] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:45:138] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-05-10 12:05:45:138] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519094
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:45:138] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:45:139] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-05-10 12:05:45:139] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:45:139] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:45:139] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:45:139] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:45:147] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:45:147] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:45:147] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:45:147] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:45:150] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@7a6088d61Airvana0005B9LTE_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-05-10 12:05:45:154] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-05-10 12:05:45:154] [0005B9519091] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-05-10 12:05:45:154] [0005B9519091] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-05-10 12:05:45:154] [0005B9519091] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-05-10 12:05:45:154] [0005B9519091] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-05-10 12:05:45:154] [0005B9519091] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-05-10 12:05:45:154] [0005B9519091] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-05-10 12:05:45:154] [0005B9519091] [main] DeviceInformBuilder DEBUG: Constructing BOOT Inform
[2025-05-10 12:05:45:155] [0005B9519091] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-05-10 12:05:45:155] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-05-10 12:05:45:155] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '1 BOOT'
[2025-05-10 12:05:45:155] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-05-10 12:05:45:155] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOT, hence aborting all the pending operations if any exists
[2025-05-10 12:05:45:155] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-05-10 12:05:45:155] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9519091
[2025-05-10 12:05:45:155] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:45:157] [0005B9519091] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-05-10 12:05:45:157] [0005B9519091] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519091
[2025-05-10 12:05:45:158] [0005B9519091] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-05-10 12:05:45:163] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-05-10 12:05:45:163] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:45:163] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-05-10 12:05:45:165] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519091
[2025-05-10 12:05:45:165] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-05-10 12:05:45:165] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-05-10 12:05:45:165] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:45:165] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-05-10 12:05:45:166] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-05-10 12:05:45:169] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-05-10 12:05:45:169] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:45:169] [] [main] CPEManagementService INFO : 11
[2025-05-10 12:05:45:170] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:45:170] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:45:171] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:45:171] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:45:172] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:45:172] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:45:172] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:45:172] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-05-10 12:05:45:172] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:45:172] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-05-10 12:05:45:172] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-05-10 12:05:45:174] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-05-10 12:05:45:174] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-05-10 12:05:45:174] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-05-10 12:05:45:174] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:45:175] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-05-10 12:05:45:175] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519091
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:45:175] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-05-10 12:05:45:175] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:45:175] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:45:175] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:45:175] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:45:190] [] [main] TransferCompleteTest INFO : Starting TransferCompleteTest on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:45:190] [] [main] TransferCompleteTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:45:190] [] [main] TransferCompleteTest INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:45:507] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:45:507] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:45:507] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:05:55:989] [] [main] TransferCompleteTest INFO : Started TransferCompleteTest in 10.809 seconds (JVM running for 37.377)
[2025-05-10 12:05:55:997] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:55:997] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:55:997] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:55:997] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:55:998] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@c9e1e1100005B9AAAA2202019-07-08T18:15:43.032Z2019-07-08T18:15:43.032Z
[2025-05-10 12:05:56:000] [] [main] CPEManagementService INFO : Event notified by the device is of type: TransferComplete
[2025-05-10 12:05:56:000] [] [main] DeviceEventHandler DEBUG: Processing Transfer Complete
[2025-05-10 12:05:56:000] [0005B9AAAA22] [main] DeviceEventHandler DEBUG: TransferComplete inform received with Start time
[2025-05-10 12:05:56:002] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-05-10 12:05:56:002] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE'
[2025-05-10 12:05:56:002] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-05-10 12:05:56:002] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:56:002] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: newSessionId
[2025-05-10 12:05:56:002] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:56:002] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-05-10 12:05:56:002] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper WARN : Notification do not contains either connection request URL or swVer or hwVer of the device
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for newSessionId, listener bean=SessionTimeoutHandler
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId started
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId successfully completed
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for newSessionId
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : newSessionId
[2025-05-10 12:05:56:003] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-05-10 12:05:56:003] [] [main] DeviceEventHandler DEBUG: Successfully processed the TRANSFER COMPLETE Inform
[2025-05-10 12:05:56:005] [] [main] TR069RPC DEBUG: Key element is: 0
[2025-05-10 12:05:56:005] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:56:006] [] [main] CPEManagementService INFO : 1
[2025-05-10 12:05:56:006] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:56:006] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:56:007] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:05:56:008] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:05:56:008] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:05:56:008] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:05:56:008] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:05:56:008] [] [main] CPEManagementService DEBUG: The session id is newSessionId
[2025-05-10 12:05:56:008] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:05:56:008] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-05-10 12:05:56:008] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: newSessionId
[2025-05-10 12:05:56:008] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: newSessionId
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: newSessionId
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9AAAA22
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:05:56:009] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.newSessionId
[2025-05-10 12:05:56:010] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId started
[2025-05-10 12:05:56:010] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId successfully completed
[2025-05-10 12:05:56:010] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.newSessionId
[2025-05-10 12:05:56:010] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : newSessionId
[2025-05-10 12:05:56:010] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:05:56:010] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:05:56:010] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-05-10 12:05:56:010] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:05:56:010] [] [main] CPEManagementService INFO :
[2025-05-10 12:05:56:010] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:05:56:010] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:05:56:150] [] [main] InformSwVersionUpdatedTest INFO : Starting InformSwVersionUpdatedTest on prd-ubuntu1804-docker-4c-4g-659 with PID 2815 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-05-10 12:05:56:151] [] [main] InformSwVersionUpdatedTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-05-10 12:05:56:151] [] [main] InformSwVersionUpdatedTest INFO : No active profile set, falling back to default profiles: default
[2025-05-10 12:05:56:486] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-05-10 12:05:56:486] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-05-10 12:05:56:487] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-05-10 12:06:06:931] [] [main] InformSwVersionUpdatedTest INFO : Started InformSwVersionUpdatedTest in 10.796 seconds (JVM running for 48.319)
[2025-05-10 12:06:06:937] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:06:06:937] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:06:06:937] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:06:06:937] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:06:06:939] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@5865496d1Airvana0005B9LTE_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-05-10 12:06:06:943] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-05-10 12:06:06:944] [0005B9519090] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-05-10 12:06:06:944] [0005B9519090] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-05-10 12:06:06:944] [0005B9519090] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-05-10 12:06:06:944] [0005B9519090] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-05-10 12:06:06:944] [0005B9519090] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-05-10 12:06:06:944] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9519090_CONNECTION_REQUEST
[2025-05-10 12:06:06:944] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9519090_CONNECTION_REQUEST
[2025-05-10 12:06:06:944] [0005B9519090] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-05-10 12:06:06:944] [0005B9519090] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform
[2025-05-10 12:06:06:944] [0005B9519090] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-05-10 12:06:06:945] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-05-10 12:06:06:945] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP'
[2025-05-10 12:06:06:945] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-05-10 12:06:06:947] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists
[2025-05-10 12:06:06:947] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-05-10 12:06:06:953] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Grouping the records based on operationId
[2025-05-10 12:06:06:953] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists 0 pending NBI requests for the device
[2025-05-10 12:06:06:953] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:06:953] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:06:957] [0005B9519090] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device
[2025-05-10 12:06:06:957] [0005B9519090] [main] SessionManager DEBUG: Creating a new session for the device
[2025-05-10 12:06:06:959] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:06:963] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: 2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:06:963] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:06:06:963] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-05-10 12:06:06:963] [0005B9519090] [main] TR069EventNotificationService DEBUG: Device Inform Event received: '0 BOOTSTRAP'
[2025-05-10 12:06:07:033] [0005B9519090] [main] TR069EventNotificationService DEBUG: Successfully posted the device inform event to DM to forward to NBI
[2025-05-10 12:06:07:033] [] [main] TR069RequestProcessEngineHelper DEBUG: Device details are changed
[2025-05-10 12:06:07:033] [] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details
[2025-05-10 12:06:07:034] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-05-10 12:06:07:034] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-05-10 12:06:07:034] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:06:07:035] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 2734d1db-2d97-11f0-b79e-0242df564c1b, listener bean=SessionTimeoutHandler
[2025-05-10 12:06:07:035] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 2734d1db-2d97-11f0-b79e-0242df564c1b started
[2025-05-10 12:06:07:035] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 2734d1db-2d97-11f0-b79e-0242df564c1b successfully completed
[2025-05-10 12:06:07:036] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:036] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : 2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:036] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-05-10 12:06:07:060] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-05-10 12:06:07:062] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:06:07:062] [] [main] CPEManagementService INFO : 11
[2025-05-10 12:06:07:062] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:06:07:062] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:06:07:066] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:06:07:066] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:06:07:066] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:06:07:066] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:06:07:066] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:06:07:066] [] [main] CPEManagementService DEBUG: The session id is 2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:066] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:06:07:066] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-05-10 12:06:07:067] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: 2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:071] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: 2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:072] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-05-10 12:06:07:072] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-05-10 12:06:07:072] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:07:072] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:07:074] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: 2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:074] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:06:07:074] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:06:07:074] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-05-10 12:06:07:076] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519090
[2025-05-10 12:06:07:077] [0005B9519090] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-05-10 12:06:07:077] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:06:07:077] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:077] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 2734d1db-2d97-11f0-b79e-0242df564c1b started
[2025-05-10 12:06:07:078] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 2734d1db-2d97-11f0-b79e-0242df564c1b successfully completed
[2025-05-10 12:06:07:078] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:079] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : 2734d1db-2d97-11f0-b79e-0242df564c1b
[2025-05-10 12:06:07:079] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:06:07:079] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:06:07:080] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-05-10 12:06:07:086] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:06:07:086] [] [main] CPEManagementService INFO :
[2025-05-10 12:06:07:089] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:06:07:089] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:06:07:104] [] [DefaultMessageListenerContainer-2] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519090 , Notification Type(s): [BOOTSTRAP]
[2025-05-10 12:06:07:109] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-05-10 12:06:07:109] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI
[2025-05-10 12:06:07:109] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null
[2025-05-10 12:06:07:116] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService ERROR: Unable to post the Device Notification, Reason: URI is not absolute
[2025-05-10 12:06:07:116] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-05-10 12:06:07:117] [] [DefaultMessageListenerContainer-2] DeviceInformForwarder DEBUG: Successfully processed device notification.
[2025-05-10 12:06:07:336] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:06:07:336] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:06:07:336] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:06:07:336] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:06:07:339] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@7b76d2061Airvana0005B9LTE_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-05-10 12:06:07:348] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-05-10 12:06:07:348] [0005B9519093] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-05-10 12:06:07:348] [0005B9519093] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-05-10 12:06:07:348] [0005B9519093] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-05-10 12:06:07:348] [0005B9519093] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-05-10 12:06:07:348] [0005B9519093] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-05-10 12:06:07:349] [0005B9519093] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-05-10 12:06:07:349] [0005B9519093] [main] DeviceInformBuilder DEBUG: Constructing PERIODIC Inform
[2025-05-10 12:06:07:349] [0005B9519093] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-05-10 12:06:07:349] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-05-10 12:06:07:349] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '2 PERIODIC'
[2025-05-10 12:06:07:349] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-05-10 12:06:07:350] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:07:354] [0005B9519093] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-05-10 12:06:07:354] [0005B9519093] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519093
[2025-05-10 12:06:07:358] [0005B9519093] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-05-10 12:06:07:362] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid10
[2025-05-10 12:06:07:362] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:06:07:362] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-05-10 12:06:07:365] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519093
[2025-05-10 12:06:07:366] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-05-10 12:06:07:366] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-05-10 12:06:07:366] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:06:07:366] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid10
[2025-05-10 12:06:07:366] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-05-10 12:06:07:370] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-05-10 12:06:07:371] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:06:07:371] [] [main] CPEManagementService INFO : 11
[2025-05-10 12:06:07:372] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:06:07:372] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:06:07:374] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:06:07:374] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:06:07:374] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:06:07:374] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:06:07:375] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:06:07:375] [] [main] CPEManagementService DEBUG: The session id is sessionid10
[2025-05-10 12:06:07:375] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:06:07:375] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-05-10 12:06:07:376] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid10
[2025-05-10 12:06:07:379] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid10
[2025-05-10 12:06:07:380] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-05-10 12:06:07:380] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-05-10 12:06:07:380] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:07:380] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid10
[2025-05-10 12:06:07:380] [0005B9519093] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:06:07:381] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:06:07:381] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-05-10 12:06:07:381] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519093
[2025-05-10 12:06:07:381] [0005B9519093] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-05-10 12:06:07:382] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:06:07:382] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid10
[2025-05-10 12:06:07:382] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:06:07:383] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:06:07:383] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-05-10 12:06:07:384] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:06:07:384] [] [main] CPEManagementService INFO :
[2025-05-10 12:06:07:384] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:06:07:384] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:06:07:394] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:06:07:394] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:06:07:394] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:06:07:394] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:06:07:396] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@6aaa0ef71Airvana0005B9LTE_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-05-10 12:06:07:411] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-05-10 12:06:07:411] [0005B9519095] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-05-10 12:06:07:411] [0005B9519095] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-05-10 12:06:07:411] [0005B9519095] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-05-10 12:06:07:411] [0005B9519095] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-05-10 12:06:07:411] [0005B9519095] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-05-10 12:06:07:412] [0005B9519095] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-05-10 12:06:07:412] [0005B9519095] [main] DeviceInformBuilder DEBUG: Constructing VALUECHANGE Inform
[2025-05-10 12:06:07:412] [0005B9519095] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-05-10 12:06:07:413] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-05-10 12:06:07:414] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '4 VALUE CHANGE'
[2025-05-10 12:06:07:414] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-05-10 12:06:07:414] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:07:419] [0005B9519095] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-05-10 12:06:07:419] [0005B9519095] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519095
[2025-05-10 12:06:07:424] [0005B9519095] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-05-10 12:06:07:429] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-05-10 12:06:07:429] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:06:07:429] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-05-10 12:06:07:431] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519095
[2025-05-10 12:06:07:431] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-05-10 12:06:07:431] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-05-10 12:06:07:431] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:06:07:432] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-05-10 12:06:07:432] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-05-10 12:06:07:436] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-05-10 12:06:07:437] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:06:07:438] [] [main] CPEManagementService INFO : 11
[2025-05-10 12:06:07:438] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:06:07:438] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-05-10 12:06:07:445] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-05-10 12:06:07:445] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-05-10 12:06:07:446] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-05-10 12:06:07:446] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-05-10 12:06:07:446] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-05-10 12:06:07:447] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-05-10 12:06:07:449] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-05-10 12:06:07:449] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-05-10 12:06:07:451] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-05-10 12:06:07:456] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-05-10 12:06:07:457] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-05-10 12:06:07:457] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-05-10 12:06:07:457] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-05-10 12:06:07:457] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-05-10 12:06:07:458] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-05-10 12:06:07:458] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-05-10 12:06:07:458] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-05-10 12:06:07:458] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519095
[2025-05-10 12:06:07:458] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-05-10 12:06:07:459] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-05-10 12:06:07:459] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-05-10 12:06:07:459] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-05-10 12:06:07:459] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-05-10 12:06:07:459] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-05-10 12:06:07:460] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-05-10 12:06:07:461] [] [main] CPEManagementService INFO :
[2025-05-10 12:06:07:461] [] [main] CPEManagementService DEBUG: End of processing
[2025-05-10 12:06:07:461] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request