Debug Log started at: 2025-03-29 12:05:20[2025-03-29 12:05:21:402] [] [main] DeviceConnectTest INFO : Starting DeviceConnectTest on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:21:411] [] [main] DeviceConnectTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:21:412] [] [main] DeviceConnectTest INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:25:487] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:25:488] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:25:488] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:26:988] [] [main] DeviceConnectTest INFO : Started DeviceConnectTest in 6.073 seconds (JVM running for 8.236)
[2025-03-29 12:05:27:079] [0005B9AAAA22] [main] ConnectionReqEventHandler INFO : Received a JMS message from Request Processor for initiating connection request
[2025-03-29 12:05:27:079] [0005B9AAAA22] [main] ConnectionReqEventProcessor INFO : Initiating connection request on the device. Connection request URL is : http://10.10.10.10:8888/connect/device
[2025-03-29 12:05:27:083] [0005B9AAAA22] [main] ConnectionReqEventProcessor DEBUG: Successfully started the timer task for connection request initiation on device : 0005B9AAAA22
[2025-03-29 12:05:27:083] [0005B9AAAA22] [main] ConnectionReqEventHandler DEBUG: Sent TR069 connection request to device
[2025-03-29 12:05:27:205] [] [main] AOOpResultTest INFO : Starting AOOpResultTest on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:27:205] [] [main] AOOpResultTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:27:206] [] [main] AOOpResultTest INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:27:805] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:27:805] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:27:806] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:28:305] [] [main] AOOpResultTest INFO : Started AOOpResultTest in 1.117 seconds (JVM running for 9.552)
[2025-03-29 12:05:28:357] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:28:358] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:28:358] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:28:358] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:28:358] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-03-29 12:05:28:414] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@c05d0341265561012019-07-08T18:15:42.030Z2019-07-08T18:15:42.030Z
[2025-03-29 12:05:28:544] [] [main] CPEManagementService INFO : Event notified by the device is of type: DownloadResponse
[2025-03-29 12:05:28:544] [] [main] CPEManagementService DEBUG: Received Operation Result response DownloadResponse: Status = 1 StartTime 2019-07-08T18:15:42.030Z CompleteTime 2019-07-08T18:15:42.030Z
[2025-03-29 12:05:28:553] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-03-29 12:05:28:554] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-03-29 12:05:28:559] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DOWNLOAD
[2025-03-29 12:05:28:562] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DownloadResponse
[2025-03-29 12:05:28:563] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-03-29 12:05:28:563] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-03-29 12:05:28:564] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:28:564] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-03-29 12:05:28:564] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:28:565] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-03-29 12:05:28:565] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:28:565] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-03-29 12:05:28:566] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:28:566] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-03-29 12:05:28:566] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:28:567] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-03-29 12:05:28:567] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-03-29 12:05:28:567] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:28:567] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-03-29 12:05:28:568] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:28:568] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:28:578] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:28:578] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:28:578] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:28:733] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:28:733] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:28:733] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:28:733] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:28:733] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-03-29 12:05:28:740] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@10c52f0e914620
[2025-03-29 12:05:28:746] [] [main] CPEManagementService INFO : Event notified by the device is of type: FactoryResetResponse
[2025-03-29 12:05:28:746] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.FactoryResetResponse@7fb0aded
[2025-03-29 12:05:28:747] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-03-29 12:05:28:747] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-03-29 12:05:28:748] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation FACTORY_RESET
[2025-03-29 12:05:28:748] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is FRResponse
[2025-03-29 12:05:28:749] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-03-29 12:05:28:749] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-03-29 12:05:28:749] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:28:749] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-03-29 12:05:28:750] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:28:750] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-03-29 12:05:28:750] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:28:750] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-03-29 12:05:28:750] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:28:751] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-03-29 12:05:28:751] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:28:751] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-03-29 12:05:28:751] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-03-29 12:05:28:751] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:28:752] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-03-29 12:05:28:752] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:28:752] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:28:753] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:28:753] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:28:754] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:28:776] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:28:777] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:28:778] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:28:778] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:28:779] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-03-29 12:05:28:781] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4eb8353412653738
[2025-03-29 12:05:28:783] [] [main] CPEManagementService INFO : Event notified by the device is of type: SetParameterAttributesResponse
[2025-03-29 12:05:28:783] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.SetParameterAttributesResponse@6f86209
[2025-03-29 12:05:28:784] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-03-29 12:05:28:784] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-03-29 12:05:28:790] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation SET_PARAMETER_ATTRIBUTES
[2025-03-29 12:05:28:791] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is SPAResponse
[2025-03-29 12:05:28:792] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-03-29 12:05:28:793] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-03-29 12:05:28:793] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:28:793] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-03-29 12:05:28:794] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:28:794] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-03-29 12:05:28:794] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:28:794] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-03-29 12:05:28:795] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:28:795] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-03-29 12:05:28:795] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:28:795] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-03-29 12:05:28:795] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-03-29 12:05:28:796] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:28:796] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-03-29 12:05:28:796] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:28:796] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:28:797] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:28:797] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:28:797] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:28:813] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:28:813] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:28:813] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:28:813] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:28:813] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-03-29 12:05:28:815] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@36c8f9df12655897Device.Hosts.HostNumberOfEntries1
[2025-03-29 12:05:28:818] [] [main] CPEManagementService INFO : Event notified by the device is of type: GetParameterValuesResponse
[2025-03-29 12:05:28:818] [] [main] CPEManagementService DEBUG: Received Operation Result response Device.Hosts.HostNumberOfEntries=1
[2025-03-29 12:05:28:818] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-03-29 12:05:28:819] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-03-29 12:05:28:819] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation GET_PARAMETER_VALUES
[2025-03-29 12:05:28:819] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is GPVResponse
[2025-03-29 12:05:28:820] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-03-29 12:05:28:820] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-03-29 12:05:28:820] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:28:821] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-03-29 12:05:28:821] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:28:821] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-03-29 12:05:28:821] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:28:821] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-03-29 12:05:28:821] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:28:822] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-03-29 12:05:28:822] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:28:822] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-03-29 12:05:28:822] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-03-29 12:05:28:822] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:28:822] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-03-29 12:05:28:823] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:28:823] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:28:823] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:28:823] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:28:823] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:28:834] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:28:834] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:28:834] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:28:834] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:28:834] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-03-29 12:05:28:835] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@45f462e0133062910
[2025-03-29 12:05:28:838] [] [main] CPEManagementService INFO : Event notified by the device is of type: DeleteObjectResponse
[2025-03-29 12:05:28:838] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.DeleteObjectResponse@245055d0
[2025-03-29 12:05:28:838] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-03-29 12:05:28:839] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-03-29 12:05:28:839] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DELETE_OBJECT
[2025-03-29 12:05:28:840] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DOResponse
[2025-03-29 12:05:28:840] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-03-29 12:05:28:840] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-03-29 12:05:28:840] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:28:840] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-03-29 12:05:28:840] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:28:840] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-03-29 12:05:28:841] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:28:841] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-03-29 12:05:28:841] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:28:841] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-03-29 12:05:28:841] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:28:841] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-03-29 12:05:28:841] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-03-29 12:05:28:841] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:28:842] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-03-29 12:05:28:842] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:28:842] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:28:842] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:28:842] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:28:842] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:28:851] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:28:851] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:28:851] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:28:851] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:28:851] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-03-29 12:05:28:852] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@6b9972d9913870
[2025-03-29 12:05:28:854] [] [main] CPEManagementService INFO : Event notified by the device is of type: RebootResponse
[2025-03-29 12:05:28:855] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.RebootResponse@57cb640d
[2025-03-29 12:05:28:855] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-03-29 12:05:28:855] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-03-29 12:05:28:856] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation REBOOT
[2025-03-29 12:05:28:856] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is RebootResponse
[2025-03-29 12:05:28:856] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-03-29 12:05:28:856] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-03-29 12:05:28:856] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:28:857] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-03-29 12:05:28:857] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:28:857] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-03-29 12:05:28:857] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:28:857] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-03-29 12:05:28:857] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:28:857] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-03-29 12:05:28:858] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:28:858] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-03-29 12:05:28:858] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-03-29 12:05:28:858] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:28:858] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-03-29 12:05:28:859] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:28:859] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:28:859] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:28:859] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:28:860] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:28:869] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:28:871] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:28:871] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:28:872] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:28:873] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-03-29 12:05:28:874] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@507953441265443140
[2025-03-29 12:05:28:876] [] [main] CPEManagementService INFO : Event notified by the device is of type: AddObjectResponse
[2025-03-29 12:05:28:877] [] [main] CPEManagementService DEBUG: Received Operation Result response AddObjectResponse: status=0 instance=4
[2025-03-29 12:05:28:877] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-03-29 12:05:28:877] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-03-29 12:05:28:878] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation ADD_OBJECT
[2025-03-29 12:05:28:878] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is AOResponse
[2025-03-29 12:05:28:878] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-03-29 12:05:28:879] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-03-29 12:05:28:879] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:28:879] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-03-29 12:05:28:879] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:28:879] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-03-29 12:05:28:879] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:28:879] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-03-29 12:05:28:879] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:28:880] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-03-29 12:05:28:880] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:28:880] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-03-29 12:05:28:880] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-03-29 12:05:28:880] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:28:880] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-03-29 12:05:28:880] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:28:881] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:28:881] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:28:881] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:28:881] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:28:898] [] [main] InvokeRPCTest INFO : Starting InvokeRPCTest on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:28:899] [] [main] InvokeRPCTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:28:899] [] [main] InvokeRPCTest INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:29:495] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:29:495] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:29:495] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:30:112] [] [main] InvokeRPCTest INFO : Started InvokeRPCTest in 1.226 seconds (JVM running for 11.36)
[2025-03-29 12:05:30:119] [] [main] MapperRequestRESTService DEBUG: Received a Device operation request from Mapper
[2025-03-29 12:05:30:119] [0005B95196D0] [main] ACSServiceAPIImpl INFO : Received request to perform device operation. OperationCode: SET_PARAMETER_VALUES
[2025-03-29 12:05:30:120] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: The operation ID generated for processing the Device RPC request is - 1743249930119
[2025-03-29 12:05:30:120] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: Successfully posted the Mapper Request to Queue with OperationId : 1743249930119 OperationCode : SET_PARAMETER_VALUES
[2025-03-29 12:05:30:120] [] [main] MapperRequestRESTService DEBUG: Successfully initiated device operation, The operation id for the request is: 1743249930119
[2025-03-29 12:05:30:330] [] [main] RPCResponseForwarderTest INFO : Starting RPCResponseForwarderTest on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:30:331] [] [main] RPCResponseForwarderTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:30:331] [] [main] RPCResponseForwarderTest INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:30:847] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:30:848] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:30:848] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:41:405] [] [main] RPCResponseForwarderTest INFO : Started RPCResponseForwarderTest in 11.087 seconds (JVM running for 22.652)
[2025-03-29 12:05:41:422] [] [main] DeviceRPCResponseForwarder DEBUG: NBIOperationResult message is received for deviceId : 0005B9519095, , OprationId: 1000
[2025-03-29 12:05:41:422] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-03-29 12:05:41:422] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Operation result from NBI
[2025-03-29 12:05:41:423] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the operation request to WebService: null
[2025-03-29 12:05:41:423] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the NBI operation request to SBI Service
[2025-03-29 12:05:41:423] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-03-29 12:05:41:423] [] [main] DeviceRPCResponseForwarder DEBUG: Successfully processed NBI operation result.
[2025-03-29 12:05:41:539] [] [main] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519095 , Notification Type(s): [BOOTSTRAP]
[2025-03-29 12:05:41:539] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-03-29 12:05:41:539] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI
[2025-03-29 12:05:41:540] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null
[2025-03-29 12:05:41:540] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the Device Notification to SBI Service
[2025-03-29 12:05:41:540] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-03-29 12:05:41:540] [] [main] DeviceInformForwarder DEBUG: Successfully processed device notification.
[2025-03-29 12:05:41:559] [] [main] DeviceRPCRequestHandlerTests INFO : Starting DeviceRPCRequestHandlerTests on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:41:560] [] [main] DeviceRPCRequestHandlerTests DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:41:560] [] [main] DeviceRPCRequestHandlerTests INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:41:897] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:41:897] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:41:897] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:42:448] [] [main] DeviceRPCRequestHandlerTests INFO : Started DeviceRPCRequestHandlerTests in 0.904 seconds (JVM running for 23.696)
[2025-03-29 12:05:42:462] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation
[2025-03-29 12:05:42:462] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10
[2025-03-29 12:05:42:462] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10
[2025-03-29 12:05:42:468] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:42:468] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:42:469] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10
[2025-03-29 12:05:42:469] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10
[2025-03-29 12:05:42:533] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request
[2025-03-29 12:05:42:533] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: No active session exists, hence requesting for Connection request
[2025-03-29 12:05:42:533] [0005B95196D0] [main] TR069RequestProcessEngineHelper INFO : Initiating Connection request on device: 0005B95196D0
[2025-03-29 12:05:42:533] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 0005B95196D0_10, listener bean=SessionTimeoutHandler
[2025-03-29 12:05:42:534] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 started
[2025-03-29 12:05:42:541] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 successfully completed
[2025-03-29 12:05:42:541] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 0005B95196D0_10
[2025-03-29 12:05:42:541] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device RPC request with operation ID : 10
[2025-03-29 12:05:42:541] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10
[2025-03-29 12:05:42:541] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation
[2025-03-29 12:05:42:677] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation
[2025-03-29 12:05:42:677] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10
[2025-03-29 12:05:42:677] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10
[2025-03-29 12:05:42:677] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:42:677] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:42:677] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10
[2025-03-29 12:05:42:677] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10
[2025-03-29 12:05:42:679] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request
[2025-03-29 12:05:42:679] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Session is in processing state, Will be notified to session manager to pick the request on session availability
[2025-03-29 12:05:42:679] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10
[2025-03-29 12:05:42:679] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation
[2025-03-29 12:05:42:697] [] [main] BootstrapInformTest INFO : Starting BootstrapInformTest on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:42:698] [] [main] BootstrapInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:42:698] [] [main] BootstrapInformTest INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:43:104] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:43:104] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:43:104] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:43:624] [] [main] BootstrapInformTest INFO : Started BootstrapInformTest in 0.938 seconds (JVM running for 24.872)
[2025-03-29 12:05:43:636] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:43:637] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:43:637] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:43:637] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:43:639] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@6c3ab21f10005B9LTE_Enterprise_C-RANSC_Cntrl0005B94239100 BOOTSTRAP12020-06-10T11:27:26.054Z0Device.DeviceInfo.HardwareVersion750742.00.13Device.DeviceInfo.SoftwareVersion4.3.00.229Device.DeviceInfo.ProvisioningCodeDevice.ManagementServer.ConnectionRequestURLhttp://172.20.0.9:30150/ConnectionRequest?command=cr&sn=0005B9423910Device.ManagementServer.ParameterKeyzzzzDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection.1.ExternalIPAddress172.17.19.193Device.Services.FAPService.1.FAPControl.LTE.AdminState0
[2025-03-29 12:05:43:644] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-03-29 12:05:43:644] [0005B9423910] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-03-29 12:05:43:644] [0005B9423910] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-03-29 12:05:43:644] [0005B9423910] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-03-29 12:05:43:644] [0005B9423910] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-03-29 12:05:43:645] [0005B9423910] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-03-29 12:05:43:645] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9423910_CONNECTION_REQUEST
[2025-03-29 12:05:43:645] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9423910_CONNECTION_REQUEST
[2025-03-29 12:05:43:645] [0005B9423910] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-03-29 12:05:43:645] [0005B9423910] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform
[2025-03-29 12:05:43:645] [0005B9423910] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-03-29 12:05:43:646] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-03-29 12:05:43:647] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP'
[2025-03-29 12:05:43:647] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-03-29 12:05:43:663] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists
[2025-03-29 12:05:43:663] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-03-29 12:05:43:664] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9423910
[2025-03-29 12:05:43:664] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:43:664] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:43:849] [0005B9423910] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device
[2025-03-29 12:05:43:853] [0005B9423910] [main] SessionManager DEBUG: Creating a new session for the device
[2025-03-29 12:05:43:868] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:43:888] [0005B9423910] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-03-29 12:05:43:888] [0005B9423910] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9423910
[2025-03-29 12:05:43:893] [0005B9423910] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-03-29 12:05:43:898] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: 2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:43:898] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:43:898] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-03-29 12:05:43:900] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9423910
[2025-03-29 12:05:43:901] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-03-29 12:05:43:901] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-03-29 12:05:43:901] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:43:902] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 2415ee2f-0c96-11f0-a279-02426695389d, listener bean=SessionTimeoutHandler
[2025-03-29 12:05:43:902] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 2415ee2f-0c96-11f0-a279-02426695389d started
[2025-03-29 12:05:43:902] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 2415ee2f-0c96-11f0-a279-02426695389d successfully completed
[2025-03-29 12:05:43:902] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:43:903] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : 2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:43:903] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-03-29 12:05:44:101] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-03-29 12:05:44:150] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:44:151] [] [main] CPEManagementService INFO : 11
[2025-03-29 12:05:44:151] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:44:151] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:44:155] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:44:155] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:44:155] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:44:155] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:44:155] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:44:155] [] [main] CPEManagementService DEBUG: The session id is 2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:44:156] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:44:156] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-03-29 12:05:44:157] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: 2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:44:171] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: 2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:44:172] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-03-29 12:05:44:172] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-03-29 12:05:44:172] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:44:172] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:44:175] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: 2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:44:175] [0005B9423910] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:44:175] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:44:175] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-03-29 12:05:44:175] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9423910
[2025-03-29 12:05:44:176] [0005B9423910] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-03-29 12:05:44:176] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:44:176] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:44:176] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 2415ee2f-0c96-11f0-a279-02426695389d started
[2025-03-29 12:05:44:177] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 2415ee2f-0c96-11f0-a279-02426695389d successfully completed
[2025-03-29 12:05:44:177] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:44:177] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : 2415ee2f-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:44:177] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:44:178] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:44:178] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-03-29 12:05:44:180] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:44:180] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:44:180] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:44:180] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:44:321] [] [main] ConnRequestInformTest INFO : Starting ConnRequestInformTest on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:44:322] [] [main] ConnRequestInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:44:322] [] [main] ConnRequestInformTest INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:44:750] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:44:751] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:44:751] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:45:154] [] [main] ConnRequestInformTest INFO : Started ConnRequestInformTest in 0.856 seconds (JVM running for 26.401)
[2025-03-29 12:05:45:169] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:45:169] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:45:170] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:45:170] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:45:173] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@17c8a1671Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190926 CONNECTION REQUEST12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519092Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-03-29 12:05:45:188] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-03-29 12:05:45:188] [0005B9519092] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-03-29 12:05:45:188] [0005B9519092] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-03-29 12:05:45:189] [0005B9519092] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-03-29 12:05:45:189] [0005B9519092] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-03-29 12:05:45:190] [0005B9519092] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-03-29 12:05:45:191] [0005B9519092] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-03-29 12:05:45:191] [0005B9519092] [main] DeviceInformBuilder DEBUG: Constructing Connection Request Inform
[2025-03-29 12:05:45:192] [0005B9519092] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-03-29 12:05:45:193] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-03-29 12:05:45:194] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '6 CONNECTION REQUEST'
[2025-03-29 12:05:45:194] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-03-29 12:05:45:195] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:45:203] [0005B9519092] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-03-29 12:05:45:204] [0005B9519092] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519092
[2025-03-29 12:05:45:208] [0005B9519092] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-03-29 12:05:45:211] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid9
[2025-03-29 12:05:45:212] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:45:212] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-03-29 12:05:45:214] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519092
[2025-03-29 12:05:45:215] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-03-29 12:05:45:216] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-03-29 12:05:45:216] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:45:216] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid9
[2025-03-29 12:05:45:217] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-03-29 12:05:45:222] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-03-29 12:05:45:224] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:45:225] [] [main] CPEManagementService INFO : 11
[2025-03-29 12:05:45:225] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:45:225] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:45:228] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:45:228] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:45:228] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:45:228] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:45:228] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:45:228] [] [main] CPEManagementService DEBUG: The session id is sessionid9
[2025-03-29 12:05:45:228] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:45:228] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-03-29 12:05:45:229] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid9
[2025-03-29 12:05:45:234] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid9
[2025-03-29 12:05:45:240] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-03-29 12:05:45:240] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-03-29 12:05:45:240] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:45:240] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid9
[2025-03-29 12:05:45:240] [0005B9519092] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:45:240] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:45:240] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-03-29 12:05:45:241] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519092
[2025-03-29 12:05:45:241] [0005B9519092] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-03-29 12:05:45:241] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:45:241] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid9
[2025-03-29 12:05:45:241] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:45:241] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:45:241] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-03-29 12:05:45:241] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:45:242] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:45:242] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:45:242] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:45:394] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:45:394] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:45:394] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:45:394] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:45:396] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@502f3b481Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190947 TRANSFER COMPLETE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519094Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-03-29 12:05:45:401] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-03-29 12:05:45:401] [0005B9519094] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-03-29 12:05:45:401] [0005B9519094] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-03-29 12:05:45:401] [0005B9519094] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-03-29 12:05:45:401] [0005B9519094] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-03-29 12:05:45:401] [0005B9519094] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-03-29 12:05:45:401] [0005B9519094] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-03-29 12:05:45:401] [0005B9519094] [main] DeviceInformBuilder DEBUG: Constructing Transfer Complete Inform
[2025-03-29 12:05:45:401] [0005B9519094] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-03-29 12:05:45:402] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-03-29 12:05:45:402] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE'
[2025-03-29 12:05:45:402] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-03-29 12:05:45:402] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:45:404] [0005B9519094] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-03-29 12:05:45:404] [0005B9519094] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519094
[2025-03-29 12:05:45:405] [0005B9519094] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-03-29 12:05:45:407] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-03-29 12:05:45:408] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:45:408] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-03-29 12:05:45:409] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519094
[2025-03-29 12:05:45:409] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-03-29 12:05:45:409] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-03-29 12:05:45:409] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:45:409] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-03-29 12:05:45:409] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-03-29 12:05:45:412] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-03-29 12:05:45:412] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:45:412] [] [main] CPEManagementService INFO : 11
[2025-03-29 12:05:45:412] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:45:413] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:45:414] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:45:414] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:45:414] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:45:414] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:45:415] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:45:415] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-03-29 12:05:45:415] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:45:415] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-03-29 12:05:45:416] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-03-29 12:05:45:418] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-03-29 12:05:45:419] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-03-29 12:05:45:419] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-03-29 12:05:45:419] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:45:419] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-03-29 12:05:45:420] [0005B9519094] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:45:420] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:45:420] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-03-29 12:05:45:420] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519094
[2025-03-29 12:05:45:420] [0005B9519094] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-03-29 12:05:45:420] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:45:420] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-03-29 12:05:45:420] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:45:420] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:45:420] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-03-29 12:05:45:420] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:45:421] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:45:421] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:45:421] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:45:429] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:45:430] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:45:430] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:45:430] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:45:433] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@748ba5031Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190911 BOOT4 VALUE CHANGE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519091Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-03-29 12:05:45:437] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-03-29 12:05:45:437] [0005B9519091] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-03-29 12:05:45:437] [0005B9519091] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-03-29 12:05:45:437] [0005B9519091] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-03-29 12:05:45:437] [0005B9519091] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-03-29 12:05:45:437] [0005B9519091] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-03-29 12:05:45:437] [0005B9519091] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-03-29 12:05:45:438] [0005B9519091] [main] DeviceInformBuilder DEBUG: Constructing BOOT Inform
[2025-03-29 12:05:45:438] [0005B9519091] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-03-29 12:05:45:438] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-03-29 12:05:45:438] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '1 BOOT'
[2025-03-29 12:05:45:438] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-03-29 12:05:45:438] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOT, hence aborting all the pending operations if any exists
[2025-03-29 12:05:45:439] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-03-29 12:05:45:439] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9519091
[2025-03-29 12:05:45:439] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:45:441] [0005B9519091] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-03-29 12:05:45:441] [0005B9519091] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519091
[2025-03-29 12:05:45:443] [0005B9519091] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-03-29 12:05:45:445] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-03-29 12:05:45:446] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:45:446] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-03-29 12:05:45:447] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519091
[2025-03-29 12:05:45:448] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-03-29 12:05:45:448] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-03-29 12:05:45:448] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:45:448] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-03-29 12:05:45:448] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-03-29 12:05:45:451] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-03-29 12:05:45:452] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:45:452] [] [main] CPEManagementService INFO : 11
[2025-03-29 12:05:45:452] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:45:452] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:45:454] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:45:454] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:45:454] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:45:455] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:45:455] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:45:455] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-03-29 12:05:45:455] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:45:455] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-03-29 12:05:45:456] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-03-29 12:05:45:458] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-03-29 12:05:45:459] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-03-29 12:05:45:459] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-03-29 12:05:45:459] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:45:459] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-03-29 12:05:45:459] [0005B9519091] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:45:459] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:45:459] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-03-29 12:05:45:459] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519091
[2025-03-29 12:05:45:460] [0005B9519091] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-03-29 12:05:45:460] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:45:460] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-03-29 12:05:45:460] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:45:460] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:45:460] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-03-29 12:05:45:461] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:45:461] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:45:462] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:45:462] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:45:478] [] [main] TransferCompleteTest INFO : Starting TransferCompleteTest on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:45:479] [] [main] TransferCompleteTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:45:479] [] [main] TransferCompleteTest INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:45:799] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:45:800] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:45:800] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:46:266] [] [main] TransferCompleteTest INFO : Started TransferCompleteTest in 0.799 seconds (JVM running for 27.514)
[2025-03-29 12:05:46:275] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:46:276] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:46:276] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:46:276] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:46:277] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@491bd99c00005B9AAAA2202019-07-08T18:15:43.032Z2019-07-08T18:15:43.032Z
[2025-03-29 12:05:46:280] [] [main] CPEManagementService INFO : Event notified by the device is of type: TransferComplete
[2025-03-29 12:05:46:280] [] [main] DeviceEventHandler DEBUG: Processing Transfer Complete
[2025-03-29 12:05:46:280] [0005B9AAAA22] [main] DeviceEventHandler DEBUG: TransferComplete inform received with Start time
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE'
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: newSessionId
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper WARN : Notification do not contains either connection request URL or swVer or hwVer of the device
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for newSessionId, listener bean=SessionTimeoutHandler
[2025-03-29 12:05:46:282] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId started
[2025-03-29 12:05:46:283] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId successfully completed
[2025-03-29 12:05:46:283] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for newSessionId
[2025-03-29 12:05:46:283] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : newSessionId
[2025-03-29 12:05:46:283] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-03-29 12:05:46:283] [] [main] DeviceEventHandler DEBUG: Successfully processed the TRANSFER COMPLETE Inform
[2025-03-29 12:05:46:284] [] [main] TR069RPC DEBUG: Key element is: 0
[2025-03-29 12:05:46:285] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:46:285] [] [main] CPEManagementService INFO : 1
[2025-03-29 12:05:46:285] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:46:285] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:46:286] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:46:286] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:46:286] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:46:286] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:46:286] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:46:287] [] [main] CPEManagementService DEBUG: The session id is newSessionId
[2025-03-29 12:05:46:287] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:46:287] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-03-29 12:05:46:287] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: newSessionId
[2025-03-29 12:05:46:287] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: newSessionId
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: newSessionId
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9AAAA22
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.newSessionId
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId started
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId successfully completed
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.newSessionId
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : newSessionId
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:46:288] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:46:289] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-03-29 12:05:46:289] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:46:289] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:46:289] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:46:289] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:46:451] [] [main] InformSwVersionUpdatedTest INFO : Starting InformSwVersionUpdatedTest on prd-ubuntu1804-docker-4c-4g-3830 with PID 2847 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-03-29 12:05:46:452] [] [main] InformSwVersionUpdatedTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-03-29 12:05:46:452] [] [main] InformSwVersionUpdatedTest INFO : No active profile set, falling back to default profiles: default
[2025-03-29 12:05:46:787] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-03-29 12:05:46:787] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-03-29 12:05:46:787] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-03-29 12:05:47:247] [] [main] InformSwVersionUpdatedTest INFO : Started InformSwVersionUpdatedTest in 0.811 seconds (JVM running for 28.495)
[2025-03-29 12:05:47:253] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:47:253] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:47:253] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:47:253] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:47:255] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@2b9f37a01Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190900 BOOTSTRAP12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519090Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-03-29 12:05:47:259] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-03-29 12:05:47:259] [0005B9519090] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-03-29 12:05:47:259] [0005B9519090] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-03-29 12:05:47:259] [0005B9519090] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-03-29 12:05:47:259] [0005B9519090] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-03-29 12:05:47:259] [0005B9519090] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-03-29 12:05:47:259] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9519090_CONNECTION_REQUEST
[2025-03-29 12:05:47:259] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9519090_CONNECTION_REQUEST
[2025-03-29 12:05:47:259] [0005B9519090] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-03-29 12:05:47:259] [0005B9519090] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform
[2025-03-29 12:05:47:259] [0005B9519090] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-03-29 12:05:47:263] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-03-29 12:05:47:263] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP'
[2025-03-29 12:05:47:263] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-03-29 12:05:47:265] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists
[2025-03-29 12:05:47:265] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-03-29 12:05:47:273] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Grouping the records based on operationId
[2025-03-29 12:05:47:273] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists 0 pending NBI requests for the device
[2025-03-29 12:05:47:274] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:274] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:279] [0005B9519090] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device
[2025-03-29 12:05:47:279] [0005B9519090] [main] SessionManager DEBUG: Creating a new session for the device
[2025-03-29 12:05:47:282] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:285] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: 2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:285] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:47:285] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-03-29 12:05:47:285] [0005B9519090] [main] TR069EventNotificationService DEBUG: Device Inform Event received: '0 BOOTSTRAP'
[2025-03-29 12:05:47:370] [0005B9519090] [main] TR069EventNotificationService DEBUG: Successfully posted the device inform event to DM to forward to NBI
[2025-03-29 12:05:47:376] [] [main] TR069RequestProcessEngineHelper DEBUG: Device details are changed
[2025-03-29 12:05:47:376] [] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details
[2025-03-29 12:05:47:376] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-03-29 12:05:47:377] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-03-29 12:05:47:377] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:47:382] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 2620b250-0c96-11f0-a279-02426695389d, listener bean=SessionTimeoutHandler
[2025-03-29 12:05:47:382] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 2620b250-0c96-11f0-a279-02426695389d started
[2025-03-29 12:05:47:382] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 2620b250-0c96-11f0-a279-02426695389d successfully completed
[2025-03-29 12:05:47:385] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:385] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : 2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:385] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-03-29 12:05:47:402] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-03-29 12:05:47:404] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:47:404] [] [main] CPEManagementService INFO : 11
[2025-03-29 12:05:47:405] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:47:406] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:47:409] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:47:409] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:47:409] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:47:409] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:47:409] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:47:410] [] [main] CPEManagementService DEBUG: The session id is 2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:410] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:47:410] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-03-29 12:05:47:411] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: 2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:416] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: 2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:417] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-03-29 12:05:47:417] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-03-29 12:05:47:418] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:418] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:420] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: 2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:423] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:47:424] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:47:424] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-03-29 12:05:47:423] [] [DefaultMessageListenerContainer-5] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519090 , Notification Type(s): [BOOTSTRAP]
[2025-03-29 12:05:47:424] [] [DefaultMessageListenerContainer-5] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-03-29 12:05:47:424] [] [DefaultMessageListenerContainer-5] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI
[2025-03-29 12:05:47:426] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519090
[2025-03-29 12:05:47:426] [0005B9519090] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-03-29 12:05:47:426] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:47:426] [] [DefaultMessageListenerContainer-5] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null
[2025-03-29 12:05:47:426] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:426] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 2620b250-0c96-11f0-a279-02426695389d started
[2025-03-29 12:05:47:427] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 2620b250-0c96-11f0-a279-02426695389d successfully completed
[2025-03-29 12:05:47:427] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:427] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : 2620b250-0c96-11f0-a279-02426695389d
[2025-03-29 12:05:47:427] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:47:427] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:47:428] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-03-29 12:05:47:429] [] [DefaultMessageListenerContainer-5] DeviceEventsMapperNotificationService DEBUG: Successfully posted the Device Notification to SBI Service
[2025-03-29 12:05:47:429] [] [DefaultMessageListenerContainer-5] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-03-29 12:05:47:429] [] [DefaultMessageListenerContainer-5] DeviceInformForwarder DEBUG: Successfully processed device notification.
[2025-03-29 12:05:47:429] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:47:430] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:47:430] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:47:430] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:47:636] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:47:636] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:47:637] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:47:637] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:47:639] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@75c7efa51Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190932 PERIODIC12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519093Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-03-29 12:05:47:643] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-03-29 12:05:47:643] [0005B9519093] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-03-29 12:05:47:644] [0005B9519093] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-03-29 12:05:47:644] [0005B9519093] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-03-29 12:05:47:644] [0005B9519093] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-03-29 12:05:47:644] [0005B9519093] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-03-29 12:05:47:644] [0005B9519093] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-03-29 12:05:47:644] [0005B9519093] [main] DeviceInformBuilder DEBUG: Constructing PERIODIC Inform
[2025-03-29 12:05:47:644] [0005B9519093] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-03-29 12:05:47:645] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-03-29 12:05:47:645] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '2 PERIODIC'
[2025-03-29 12:05:47:645] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-03-29 12:05:47:645] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:647] [0005B9519093] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-03-29 12:05:47:647] [0005B9519093] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519093
[2025-03-29 12:05:47:649] [0005B9519093] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-03-29 12:05:47:651] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid10
[2025-03-29 12:05:47:651] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:47:651] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-03-29 12:05:47:653] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519093
[2025-03-29 12:05:47:653] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-03-29 12:05:47:653] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-03-29 12:05:47:653] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:47:653] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid10
[2025-03-29 12:05:47:653] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-03-29 12:05:47:656] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-03-29 12:05:47:656] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:47:656] [] [main] CPEManagementService INFO : 11
[2025-03-29 12:05:47:656] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:47:657] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:47:658] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:47:658] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:47:658] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:47:658] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:47:658] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:47:658] [] [main] CPEManagementService DEBUG: The session id is sessionid10
[2025-03-29 12:05:47:658] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:47:658] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-03-29 12:05:47:658] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid10
[2025-03-29 12:05:47:661] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid10
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid10
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:47:662] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-03-29 12:05:47:662] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519093
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid10
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:47:662] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:47:663] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-03-29 12:05:47:663] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:47:663] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:47:663] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:47:663] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:47:671] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:47:671] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:47:671] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:47:671] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:47:672] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@743b5f321Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190954 VALUE CHANGE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519095Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-03-29 12:05:47:677] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-03-29 12:05:47:678] [0005B9519095] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-03-29 12:05:47:678] [0005B9519095] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-03-29 12:05:47:678] [0005B9519095] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-03-29 12:05:47:678] [0005B9519095] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-03-29 12:05:47:678] [0005B9519095] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-03-29 12:05:47:678] [0005B9519095] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-03-29 12:05:47:678] [0005B9519095] [main] DeviceInformBuilder DEBUG: Constructing VALUECHANGE Inform
[2025-03-29 12:05:47:678] [0005B9519095] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-03-29 12:05:47:678] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-03-29 12:05:47:678] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '4 VALUE CHANGE'
[2025-03-29 12:05:47:678] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-03-29 12:05:47:679] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:681] [0005B9519095] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-03-29 12:05:47:681] [0005B9519095] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519095
[2025-03-29 12:05:47:684] [0005B9519095] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-03-29 12:05:47:686] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-03-29 12:05:47:686] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:47:686] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-03-29 12:05:47:687] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519095
[2025-03-29 12:05:47:687] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-03-29 12:05:47:687] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-03-29 12:05:47:687] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:47:687] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-03-29 12:05:47:687] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-03-29 12:05:47:689] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-03-29 12:05:47:690] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:47:690] [] [main] CPEManagementService INFO : 11
[2025-03-29 12:05:47:691] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:47:691] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-03-29 12:05:47:692] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-03-29 12:05:47:692] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-03-29 12:05:47:692] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-03-29 12:05:47:692] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-03-29 12:05:47:692] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-03-29 12:05:47:692] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-03-29 12:05:47:692] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-03-29 12:05:47:692] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-03-29 12:05:47:692] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-03-29 12:05:47:694] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-03-29 12:05:47:694] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-03-29 12:05:47:695] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-03-29 12:05:47:695] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519095
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-03-29 12:05:47:695] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-03-29 12:05:47:695] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-03-29 12:05:47:695] [] [main] CPEManagementService INFO :
[2025-03-29 12:05:47:695] [] [main] CPEManagementService DEBUG: End of processing
[2025-03-29 12:05:47:695] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request