Debug Log started at: 2025-02-22 12:05:17[2025-02-22 12:05:18:243] [] [main] DeviceConnectTest INFO : Starting DeviceConnectTest on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:18:251] [] [main] DeviceConnectTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:18:252] [] [main] DeviceConnectTest INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:22:479] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:22:480] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:22:480] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:23:936] [] [main] DeviceConnectTest INFO : Started DeviceConnectTest in 6.016 seconds (JVM running for 8.318)
[2025-02-22 12:05:24:035] [0005B9AAAA22] [main] ConnectionReqEventHandler INFO : Received a JMS message from Request Processor for initiating connection request
[2025-02-22 12:05:24:036] [0005B9AAAA22] [main] ConnectionReqEventProcessor INFO : Initiating connection request on the device. Connection request URL is : http://10.10.10.10:8888/connect/device
[2025-02-22 12:05:24:040] [0005B9AAAA22] [main] ConnectionReqEventProcessor DEBUG: Successfully started the timer task for connection request initiation on device : 0005B9AAAA22
[2025-02-22 12:05:24:041] [0005B9AAAA22] [main] ConnectionReqEventHandler DEBUG: Sent TR069 connection request to device
[2025-02-22 12:05:24:226] [] [main] AOOpResultTest INFO : Starting AOOpResultTest on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:24:227] [] [main] AOOpResultTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:24:230] [] [main] AOOpResultTest INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:24:908] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:24:908] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:24:909] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:25:362] [] [main] AOOpResultTest INFO : Started AOOpResultTest in 1.162 seconds (JVM running for 9.744)
[2025-02-22 12:05:25:427] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:25:428] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:25:429] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:25:429] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:25:429] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-02-22 12:05:25:476] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@3e315a351265561012019-07-08T18:15:42.030Z2019-07-08T18:15:42.030Z
[2025-02-22 12:05:25:616] [] [main] CPEManagementService INFO : Event notified by the device is of type: DownloadResponse
[2025-02-22 12:05:25:616] [] [main] CPEManagementService DEBUG: Received Operation Result response DownloadResponse: Status = 1 StartTime 2019-07-08T18:15:42.030Z CompleteTime 2019-07-08T18:15:42.030Z
[2025-02-22 12:05:25:626] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-02-22 12:05:25:627] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-02-22 12:05:25:633] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DOWNLOAD
[2025-02-22 12:05:25:636] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DownloadResponse
[2025-02-22 12:05:25:636] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-02-22 12:05:25:637] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-02-22 12:05:25:637] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:25:637] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-02-22 12:05:25:638] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:25:639] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-02-22 12:05:25:639] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:25:639] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-02-22 12:05:25:640] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:25:640] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-02-22 12:05:25:641] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:25:641] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-02-22 12:05:25:641] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-02-22 12:05:25:642] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:25:642] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-02-22 12:05:25:643] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:25:643] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:25:653] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:25:653] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:25:653] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:25:805] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:25:805] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:25:805] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:25:805] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:25:805] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-02-22 12:05:25:810] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@20b5eabf914620
[2025-02-22 12:05:25:813] [] [main] CPEManagementService INFO : Event notified by the device is of type: FactoryResetResponse
[2025-02-22 12:05:25:813] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.FactoryResetResponse@1108d5f1
[2025-02-22 12:05:25:814] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-02-22 12:05:25:814] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-02-22 12:05:25:815] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation FACTORY_RESET
[2025-02-22 12:05:25:816] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is FRResponse
[2025-02-22 12:05:25:816] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-02-22 12:05:25:816] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-02-22 12:05:25:817] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:25:817] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-02-22 12:05:25:818] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:25:818] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-02-22 12:05:25:818] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:25:819] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-02-22 12:05:25:819] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:25:820] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-02-22 12:05:25:820] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:25:820] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-02-22 12:05:25:821] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-02-22 12:05:25:821] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:25:821] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-02-22 12:05:25:822] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:25:822] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:25:823] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:25:823] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:25:823] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:25:840] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:25:840] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:25:840] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:25:840] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:25:840] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-02-22 12:05:25:844] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@6b7b954712653738
[2025-02-22 12:05:25:846] [] [main] CPEManagementService INFO : Event notified by the device is of type: SetParameterAttributesResponse
[2025-02-22 12:05:25:846] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.SetParameterAttributesResponse@45a55153
[2025-02-22 12:05:25:847] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-02-22 12:05:25:847] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-02-22 12:05:25:848] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation SET_PARAMETER_ATTRIBUTES
[2025-02-22 12:05:25:849] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is SPAResponse
[2025-02-22 12:05:25:849] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-02-22 12:05:25:849] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-02-22 12:05:25:849] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:25:850] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-02-22 12:05:25:850] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:25:850] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-02-22 12:05:25:850] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:25:850] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-02-22 12:05:25:850] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:25:850] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-02-22 12:05:25:850] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:25:851] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-02-22 12:05:25:851] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-02-22 12:05:25:851] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:25:851] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-02-22 12:05:25:852] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:25:852] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:25:852] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:25:852] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:25:852] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:25:873] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:25:885] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:25:885] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:25:885] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:25:885] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-02-22 12:05:25:887] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@55c09dc612655897Device.Hosts.HostNumberOfEntries1
[2025-02-22 12:05:25:889] [] [main] CPEManagementService INFO : Event notified by the device is of type: GetParameterValuesResponse
[2025-02-22 12:05:25:889] [] [main] CPEManagementService DEBUG: Received Operation Result response Device.Hosts.HostNumberOfEntries=1
[2025-02-22 12:05:25:890] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-02-22 12:05:25:890] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-02-22 12:05:25:891] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation GET_PARAMETER_VALUES
[2025-02-22 12:05:25:891] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is GPVResponse
[2025-02-22 12:05:25:892] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-02-22 12:05:25:892] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-02-22 12:05:25:892] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:25:892] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-02-22 12:05:25:892] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:25:893] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-02-22 12:05:25:893] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:25:893] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-02-22 12:05:25:893] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:25:898] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-02-22 12:05:25:898] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:25:898] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-02-22 12:05:25:898] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-02-22 12:05:25:898] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:25:899] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-02-22 12:05:25:899] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:25:899] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:25:900] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:25:900] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:25:900] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:25:909] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:25:909] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:25:909] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:25:909] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:25:910] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-02-22 12:05:25:911] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@5c8add0d133062910
[2025-02-22 12:05:25:913] [] [main] CPEManagementService INFO : Event notified by the device is of type: DeleteObjectResponse
[2025-02-22 12:05:25:913] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.DeleteObjectResponse@37ca335f
[2025-02-22 12:05:25:914] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-02-22 12:05:25:914] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-02-22 12:05:25:914] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation DELETE_OBJECT
[2025-02-22 12:05:25:915] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is DOResponse
[2025-02-22 12:05:25:915] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-02-22 12:05:25:915] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-02-22 12:05:25:915] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:25:916] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-02-22 12:05:25:916] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:25:916] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-02-22 12:05:25:916] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:25:916] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-02-22 12:05:25:916] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:25:916] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-02-22 12:05:25:917] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:25:917] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-02-22 12:05:25:917] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-02-22 12:05:25:917] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:25:917] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-02-22 12:05:25:918] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:25:918] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:25:918] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:25:918] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:25:918] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:25:926] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:25:926] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:25:926] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:25:926] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:25:926] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-02-22 12:05:25:928] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4f6f3c913870
[2025-02-22 12:05:25:930] [] [main] CPEManagementService INFO : Event notified by the device is of type: RebootResponse
[2025-02-22 12:05:25:930] [] [main] CPEManagementService DEBUG: Received Operation Result response org.commscope.tr069adapter.acs.cpe.rpc.RebootResponse@73796a6c
[2025-02-22 12:05:25:930] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-02-22 12:05:25:930] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-02-22 12:05:25:931] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation REBOOT
[2025-02-22 12:05:25:931] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is RebootResponse
[2025-02-22 12:05:25:932] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-02-22 12:05:25:932] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-02-22 12:05:25:933] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:25:933] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-02-22 12:05:25:933] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:25:933] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-02-22 12:05:25:933] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:25:934] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-02-22 12:05:25:934] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:25:934] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-02-22 12:05:25:934] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:25:934] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-02-22 12:05:25:934] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-02-22 12:05:25:934] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:25:934] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-02-22 12:05:25:935] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:25:935] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:25:935] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:25:935] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:25:935] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:25:943] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:25:944] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:25:944] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:25:944] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:25:944] [] [main] CPEManagementService DEBUG: The session id is sessionId
[2025-02-22 12:05:25:945] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@45eabb2e1265443140
[2025-02-22 12:05:25:948] [] [main] CPEManagementService INFO : Event notified by the device is of type: AddObjectResponse
[2025-02-22 12:05:25:948] [] [main] CPEManagementService DEBUG: Received Operation Result response AddObjectResponse: status=0 instance=4
[2025-02-22 12:05:25:949] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionId
[2025-02-22 12:05:25:949] [] [main] TR069RequestProcessEngine DEBUG: There exists pending operation request for the session: sessionId
[2025-02-22 12:05:25:949] [] [main] TR069RequestProcessEngine INFO : The pending operation request for the session is of operation ADD_OBJECT
[2025-02-22 12:05:25:951] [0005B9519095] [main] DeviceRPCResponseBuilder DEBUG: Response Msg is AOResponse
[2025-02-22 12:05:25:951] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device operation response
[2025-02-22 12:05:25:951] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the operation response from device
[2025-02-22 12:05:25:951] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:25:951] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the device RPC response is: sessionId
[2025-02-22 12:05:25:951] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:25:952] [0005B9519095] [main] TR069RequestProcessEngine INFO : Marking the Device RPC request with operation id - 10002 as processed.
[2025-02-22 12:05:25:952] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:25:952] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty response will be sent to the device
[2025-02-22 12:05:25:952] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:25:952] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionId
[2025-02-22 12:05:25:952] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:25:952] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device RPC request with operation ID : 10002
[2025-02-22 12:05:25:953] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Sending the Device RPC Response to the Mapper
[2025-02-22 12:05:25:953] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:25:953] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device operation response
[2025-02-22 12:05:25:953] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:25:953] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:25:954] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:25:954] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:25:954] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:25:973] [] [main] InvokeRPCTest INFO : Starting InvokeRPCTest on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:25:974] [] [main] InvokeRPCTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:25:974] [] [main] InvokeRPCTest INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:26:543] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:26:544] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:26:544] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:37:156] [] [main] InvokeRPCTest INFO : Started InvokeRPCTest in 11.196 seconds (JVM running for 21.538)
[2025-02-22 12:05:37:161] [] [main] MapperRequestRESTService DEBUG: Received a Device operation request from Mapper
[2025-02-22 12:05:37:161] [0005B95196D0] [main] ACSServiceAPIImpl INFO : Received request to perform device operation. OperationCode: SET_PARAMETER_VALUES
[2025-02-22 12:05:37:162] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: The operation ID generated for processing the Device RPC request is - 1740225937162
[2025-02-22 12:05:37:162] [0005B95196D0] [main] ACSServiceAPIImpl DEBUG: Successfully posted the Mapper Request to Queue with OperationId : 1740225937162 OperationCode : SET_PARAMETER_VALUES
[2025-02-22 12:05:37:162] [] [main] MapperRequestRESTService DEBUG: Successfully initiated device operation, The operation id for the request is: 1740225937162
[2025-02-22 12:05:37:391] [] [main] RPCResponseForwarderTest INFO : Starting RPCResponseForwarderTest on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:37:394] [] [main] RPCResponseForwarderTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:37:400] [] [main] RPCResponseForwarderTest INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:37:866] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:37:866] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:37:866] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:48:401] [] [main] RPCResponseForwarderTest INFO : Started RPCResponseForwarderTest in 11.036 seconds (JVM running for 32.784)
[2025-02-22 12:05:48:427] [] [main] DeviceRPCResponseForwarder DEBUG: NBIOperationResult message is received for deviceId : 0005B9519095, , OprationId: 1000
[2025-02-22 12:05:48:428] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-02-22 12:05:48:428] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Operation result from NBI
[2025-02-22 12:05:48:428] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the operation request to WebService: null
[2025-02-22 12:05:48:429] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the NBI operation request to SBI Service
[2025-02-22 12:05:48:429] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-02-22 12:05:48:429] [] [main] DeviceRPCResponseForwarder DEBUG: Successfully processed NBI operation result.
[2025-02-22 12:05:48:539] [] [main] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519095 , Notification Type(s): [BOOTSTRAP]
[2025-02-22 12:05:48:539] [] [main] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-02-22 12:05:48:539] [] [main] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI
[2025-02-22 12:05:48:540] [] [main] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null
[2025-02-22 12:05:48:540] [] [main] DeviceEventsMapperNotificationService DEBUG: Successfully posted the Device Notification to SBI Service
[2025-02-22 12:05:48:540] [] [main] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-02-22 12:05:48:540] [] [main] DeviceInformForwarder DEBUG: Successfully processed device notification.
[2025-02-22 12:05:48:577] [] [main] DeviceRPCRequestHandlerTests INFO : Starting DeviceRPCRequestHandlerTests on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:48:578] [] [main] DeviceRPCRequestHandlerTests DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:48:578] [] [main] DeviceRPCRequestHandlerTests INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:48:940] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:48:940] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:48:941] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:49:456] [] [main] DeviceRPCRequestHandlerTests INFO : Started DeviceRPCRequestHandlerTests in 0.906 seconds (JVM running for 33.838)
[2025-02-22 12:05:49:468] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation
[2025-02-22 12:05:49:468] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10
[2025-02-22 12:05:49:469] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10
[2025-02-22 12:05:49:475] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:49:475] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:49:476] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10
[2025-02-22 12:05:49:476] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10
[2025-02-22 12:05:49:522] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request
[2025-02-22 12:05:49:522] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: No active session exists, hence requesting for Connection request
[2025-02-22 12:05:49:522] [0005B95196D0] [main] TR069RequestProcessEngineHelper INFO : Initiating Connection request on device: 0005B95196D0
[2025-02-22 12:05:49:522] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 0005B95196D0_10, listener bean=SessionTimeoutHandler
[2025-02-22 12:05:49:523] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 started
[2025-02-22 12:05:49:529] [0005B95196D0] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 0005B95196D0_10 successfully completed
[2025-02-22 12:05:49:529] [0005B95196D0] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 0005B95196D0_10
[2025-02-22 12:05:49:529] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device RPC request with operation ID : 10
[2025-02-22 12:05:49:529] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10
[2025-02-22 12:05:49:529] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation
[2025-02-22 12:05:49:701] [] [main] DeviceRPCRequestHandler DEBUG: Received a JMS message from Mapper for TR069 Device RPC operation
[2025-02-22 12:05:49:701] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Received a TR069 operation request from Mapper with operation ID: 10
[2025-02-22 12:05:49:702] [0005B95196D0] [main] TR069RequestProcessEngine INFO : A Mapper request is received with operationID: 10
[2025-02-22 12:05:49:703] [0005B95196D0] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:49:703] [0005B95196D0] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:49:703] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully acquired the session lock for processing NBI request with operation ID: 10
[2025-02-22 12:05:49:703] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Persisting the Device RPC request, with operation ID: 10
[2025-02-22 12:05:49:705] [0005B95196D0] [main] TR069RequestProcessEngine INFO : Successfully persisted the Device RPC request
[2025-02-22 12:05:49:705] [0005B95196D0] [main] TR069RequestProcessEngine DEBUG: Session is in processing state, Will be notified to session manager to pick the request on session availability
[2025-02-22 12:05:49:705] [0005B95196D0] [main] DeviceRPCRequestHandler DEBUG: Processed a TR069 operation request from Mapper with operation ID: 10
[2025-02-22 12:05:49:706] [] [main] DeviceRPCRequestHandler DEBUG: Processed JMS message from Mapper for TR069 Device RPC operation
[2025-02-22 12:05:49:725] [] [main] BootstrapInformTest INFO : Starting BootstrapInformTest on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:49:726] [] [main] BootstrapInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:49:726] [] [main] BootstrapInformTest INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:50:125] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:50:125] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:50:125] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:50:636] [] [main] BootstrapInformTest INFO : Started BootstrapInformTest in 0.923 seconds (JVM running for 35.018)
[2025-02-22 12:05:50:643] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:50:643] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:50:644] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:50:644] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:50:646] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@47d1898810005B9LTE_Enterprise_C-RANSC_Cntrl0005B94239100 BOOTSTRAP12020-06-10T11:27:26.054Z0Device.DeviceInfo.HardwareVersion750742.00.13Device.DeviceInfo.SoftwareVersion4.3.00.229Device.DeviceInfo.ProvisioningCodeDevice.ManagementServer.ConnectionRequestURLhttp://172.20.0.9:30150/ConnectionRequest?command=cr&sn=0005B9423910Device.ManagementServer.ParameterKeyzzzzDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection.1.ExternalIPAddress172.17.19.193Device.Services.FAPService.1.FAPControl.LTE.AdminState0
[2025-02-22 12:05:50:652] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-02-22 12:05:50:653] [0005B9423910] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-02-22 12:05:50:653] [0005B9423910] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-02-22 12:05:50:653] [0005B9423910] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-02-22 12:05:50:653] [0005B9423910] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-02-22 12:05:50:654] [0005B9423910] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-02-22 12:05:50:654] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9423910_CONNECTION_REQUEST
[2025-02-22 12:05:50:654] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9423910_CONNECTION_REQUEST
[2025-02-22 12:05:50:654] [0005B9423910] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-02-22 12:05:50:654] [0005B9423910] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform
[2025-02-22 12:05:50:655] [0005B9423910] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-02-22 12:05:50:656] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-02-22 12:05:50:656] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP'
[2025-02-22 12:05:50:656] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-02-22 12:05:50:692] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists
[2025-02-22 12:05:50:692] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-02-22 12:05:50:692] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9423910
[2025-02-22 12:05:50:692] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:50:693] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:50:856] [0005B9423910] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device
[2025-02-22 12:05:50:860] [0005B9423910] [main] SessionManager DEBUG: Creating a new session for the device
[2025-02-22 12:05:50:868] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:50:884] [0005B9423910] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-02-22 12:05:50:885] [0005B9423910] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9423910
[2025-02-22 12:05:50:891] [0005B9423910] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-02-22 12:05:50:897] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: 5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:50:897] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:50:897] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-02-22 12:05:50:900] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9423910
[2025-02-22 12:05:50:901] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-02-22 12:05:50:901] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-02-22 12:05:50:901] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:50:902] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 5bcddd53-f115-11ef-a972-0242bf4b5cb0, listener bean=SessionTimeoutHandler
[2025-02-22 12:05:50:902] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 5bcddd53-f115-11ef-a972-0242bf4b5cb0 started
[2025-02-22 12:05:50:902] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 5bcddd53-f115-11ef-a972-0242bf4b5cb0 successfully completed
[2025-02-22 12:05:50:902] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:50:903] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : 5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:50:903] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-02-22 12:05:51:180] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-02-22 12:05:51:235] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:51:236] [] [main] CPEManagementService INFO : 11
[2025-02-22 12:05:51:238] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:51:238] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:51:242] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:51:242] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:51:242] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:51:243] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:51:243] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:51:243] [] [main] CPEManagementService DEBUG: The session id is 5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:51:243] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:51:243] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-02-22 12:05:51:244] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: 5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:51:257] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: 5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:51:258] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-02-22 12:05:51:258] [0005B9423910] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-02-22 12:05:51:258] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:51:258] [0005B9423910] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:51:260] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: 5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:51:260] [0005B9423910] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:51:260] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:51:260] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-02-22 12:05:51:261] [0005B9423910] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9423910
[2025-02-22 12:05:51:261] [0005B9423910] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-02-22 12:05:51:261] [0005B9423910] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:51:261] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:51:261] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 5bcddd53-f115-11ef-a972-0242bf4b5cb0 started
[2025-02-22 12:05:51:262] [0005B9423910] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 5bcddd53-f115-11ef-a972-0242bf4b5cb0 successfully completed
[2025-02-22 12:05:51:262] [0005B9423910] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:51:270] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : 5bcddd53-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:51:270] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:51:270] [0005B9423910] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:51:270] [0005B9423910] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-02-22 12:05:51:274] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:51:275] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:51:275] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:51:275] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:51:419] [] [main] ConnRequestInformTest INFO : Starting ConnRequestInformTest on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:51:420] [] [main] ConnRequestInformTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:51:420] [] [main] ConnRequestInformTest INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:51:862] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:51:862] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:51:862] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:52:285] [] [main] ConnRequestInformTest INFO : Started ConnRequestInformTest in 0.879 seconds (JVM running for 36.667)
[2025-02-22 12:05:52:293] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:52:294] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:52:294] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:52:294] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:52:297] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@70c444b01Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190926 CONNECTION REQUEST12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519092Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-02-22 12:05:52:302] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-02-22 12:05:52:303] [0005B9519092] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-02-22 12:05:52:303] [0005B9519092] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-02-22 12:05:52:303] [0005B9519092] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-02-22 12:05:52:303] [0005B9519092] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-02-22 12:05:52:303] [0005B9519092] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-02-22 12:05:52:303] [0005B9519092] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-02-22 12:05:52:303] [0005B9519092] [main] DeviceInformBuilder DEBUG: Constructing Connection Request Inform
[2025-02-22 12:05:52:303] [0005B9519092] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-02-22 12:05:52:304] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-02-22 12:05:52:304] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '6 CONNECTION REQUEST'
[2025-02-22 12:05:52:304] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-02-22 12:05:52:305] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:52:310] [0005B9519092] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-02-22 12:05:52:310] [0005B9519092] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519092
[2025-02-22 12:05:52:313] [0005B9519092] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-02-22 12:05:52:319] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid9
[2025-02-22 12:05:52:319] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:52:322] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-02-22 12:05:52:325] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519092
[2025-02-22 12:05:52:328] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-02-22 12:05:52:329] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-02-22 12:05:52:329] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:52:329] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid9
[2025-02-22 12:05:52:329] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-02-22 12:05:52:333] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-02-22 12:05:52:334] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:52:334] [] [main] CPEManagementService INFO : 11
[2025-02-22 12:05:52:334] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:52:335] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:52:336] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:52:336] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:52:336] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:52:336] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:52:336] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:52:336] [] [main] CPEManagementService DEBUG: The session id is sessionid9
[2025-02-22 12:05:52:337] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:52:337] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-02-22 12:05:52:337] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid9
[2025-02-22 12:05:52:339] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid9
[2025-02-22 12:05:52:345] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-02-22 12:05:52:345] [0005B9519092] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-02-22 12:05:52:346] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:52:346] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid9
[2025-02-22 12:05:52:346] [0005B9519092] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:52:347] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:52:347] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-02-22 12:05:52:347] [0005B9519092] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519092
[2025-02-22 12:05:52:347] [0005B9519092] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-02-22 12:05:52:348] [0005B9519092] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:52:348] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid9
[2025-02-22 12:05:52:349] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:52:349] [0005B9519092] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:52:350] [0005B9519092] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-02-22 12:05:52:354] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:52:354] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:52:355] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:52:355] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:52:507] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:52:508] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:52:508] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:52:508] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:52:511] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@3ed483301Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190947 TRANSFER COMPLETE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519094Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-02-22 12:05:52:518] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-02-22 12:05:52:519] [0005B9519094] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-02-22 12:05:52:519] [0005B9519094] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-02-22 12:05:52:519] [0005B9519094] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-02-22 12:05:52:519] [0005B9519094] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-02-22 12:05:52:519] [0005B9519094] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-02-22 12:05:52:519] [0005B9519094] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-02-22 12:05:52:520] [0005B9519094] [main] DeviceInformBuilder DEBUG: Constructing Transfer Complete Inform
[2025-02-22 12:05:52:520] [0005B9519094] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-02-22 12:05:52:520] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-02-22 12:05:52:520] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE'
[2025-02-22 12:05:52:521] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-02-22 12:05:52:521] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:52:523] [0005B9519094] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-02-22 12:05:52:524] [0005B9519094] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519094
[2025-02-22 12:05:52:526] [0005B9519094] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-02-22 12:05:52:529] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-02-22 12:05:52:529] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:52:529] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-02-22 12:05:52:531] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519094
[2025-02-22 12:05:52:532] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-02-22 12:05:52:532] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-02-22 12:05:52:532] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:52:532] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-02-22 12:05:52:532] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-02-22 12:05:52:536] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-02-22 12:05:52:537] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:52:537] [] [main] CPEManagementService INFO : 11
[2025-02-22 12:05:52:538] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:52:538] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:52:539] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:52:539] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:52:539] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:52:539] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:52:539] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:52:540] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-02-22 12:05:52:540] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:52:540] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-02-22 12:05:52:541] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-02-22 12:05:52:543] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-02-22 12:05:52:544] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-02-22 12:05:52:544] [0005B9519094] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-02-22 12:05:52:544] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:52:544] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-02-22 12:05:52:544] [0005B9519094] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:52:545] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:52:545] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-02-22 12:05:52:545] [0005B9519094] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519094
[2025-02-22 12:05:52:545] [0005B9519094] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-02-22 12:05:52:545] [0005B9519094] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:52:545] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-02-22 12:05:52:546] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:52:546] [0005B9519094] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:52:546] [0005B9519094] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-02-22 12:05:52:546] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:52:546] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:52:546] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:52:546] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:52:556] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:52:556] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:52:557] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:52:557] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:52:560] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@68b36861Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190911 BOOT4 VALUE CHANGE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519091Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-02-22 12:05:52:568] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-02-22 12:05:52:568] [0005B9519091] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-02-22 12:05:52:569] [0005B9519091] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-02-22 12:05:52:569] [0005B9519091] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-02-22 12:05:52:569] [0005B9519091] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-02-22 12:05:52:569] [0005B9519091] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-02-22 12:05:52:569] [0005B9519091] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-02-22 12:05:52:570] [0005B9519091] [main] DeviceInformBuilder DEBUG: Constructing BOOT Inform
[2025-02-22 12:05:52:570] [0005B9519091] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-02-22 12:05:52:570] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-02-22 12:05:52:570] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '1 BOOT'
[2025-02-22 12:05:52:571] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-02-22 12:05:52:571] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOT, hence aborting all the pending operations if any exists
[2025-02-22 12:05:52:571] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-02-22 12:05:52:571] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending RPC requests for the device: 0005B9519091
[2025-02-22 12:05:52:571] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:52:574] [0005B9519091] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-02-22 12:05:52:575] [0005B9519091] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519091
[2025-02-22 12:05:52:577] [0005B9519091] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-02-22 12:05:52:580] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-02-22 12:05:52:580] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:52:580] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-02-22 12:05:52:582] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519091
[2025-02-22 12:05:52:583] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-02-22 12:05:52:583] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-02-22 12:05:52:583] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:52:583] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-02-22 12:05:52:583] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-02-22 12:05:52:587] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-02-22 12:05:52:587] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:52:587] [] [main] CPEManagementService INFO : 11
[2025-02-22 12:05:52:588] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:52:588] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:52:590] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:52:590] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:52:590] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:52:590] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:52:590] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:52:590] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-02-22 12:05:52:591] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:52:591] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-02-22 12:05:52:591] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-02-22 12:05:52:595] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-02-22 12:05:52:595] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-02-22 12:05:52:596] [0005B9519091] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-02-22 12:05:52:596] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:52:596] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-02-22 12:05:52:596] [0005B9519091] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:52:596] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:52:596] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-02-22 12:05:52:597] [0005B9519091] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519091
[2025-02-22 12:05:52:597] [0005B9519091] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-02-22 12:05:52:597] [0005B9519091] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:52:597] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-02-22 12:05:52:597] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:52:597] [0005B9519091] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:52:597] [0005B9519091] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-02-22 12:05:52:598] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:52:598] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:52:598] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:52:598] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:52:625] [] [main] TransferCompleteTest INFO : Starting TransferCompleteTest on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:52:626] [] [main] TransferCompleteTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:52:626] [] [main] TransferCompleteTest INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:52:949] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:52:949] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:52:949] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:53:435] [] [main] TransferCompleteTest INFO : Started TransferCompleteTest in 0.831 seconds (JVM running for 37.818)
[2025-02-22 12:05:53:446] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:53:447] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:53:447] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:53:447] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:53:448] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@2568a23300005B9AAAA2202019-07-08T18:15:43.032Z2019-07-08T18:15:43.032Z
[2025-02-22 12:05:53:450] [] [main] CPEManagementService INFO : Event notified by the device is of type: TransferComplete
[2025-02-22 12:05:53:450] [] [main] DeviceEventHandler DEBUG: Processing Transfer Complete
[2025-02-22 12:05:53:450] [0005B9AAAA22] [main] DeviceEventHandler DEBUG: TransferComplete inform received with Start time
[2025-02-22 12:05:53:451] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-02-22 12:05:53:451] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '7 TRANSFER COMPLETE'
[2025-02-22 12:05:53:451] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-02-22 12:05:53:451] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: newSessionId
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper WARN : Notification do not contains either connection request URL or swVer or hwVer of the device
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for newSessionId, listener bean=SessionTimeoutHandler
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId started
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job newSessionId successfully completed
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for newSessionId
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : newSessionId
[2025-02-22 12:05:53:452] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-02-22 12:05:53:452] [] [main] DeviceEventHandler DEBUG: Successfully processed the TRANSFER COMPLETE Inform
[2025-02-22 12:05:53:454] [] [main] TR069RPC DEBUG: Key element is: 0
[2025-02-22 12:05:53:454] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:53:454] [] [main] CPEManagementService INFO : 1
[2025-02-22 12:05:53:455] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:53:455] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:53:456] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:53:456] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:53:456] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:53:456] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:53:456] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:53:456] [] [main] CPEManagementService DEBUG: The session id is newSessionId
[2025-02-22 12:05:53:456] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:53:456] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-02-22 12:05:53:457] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: newSessionId
[2025-02-22 12:05:53:457] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: newSessionId
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: newSessionId
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9AAAA22
[2025-02-22 12:05:53:457] [0005B9AAAA22] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.newSessionId
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId started
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job newSessionId successfully completed
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.newSessionId
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : newSessionId
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:53:458] [0005B9AAAA22] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-02-22 12:05:53:458] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:53:459] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:53:459] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:53:459] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:53:615] [] [main] InformSwVersionUpdatedTest INFO : Starting InformSwVersionUpdatedTest on prd-ubuntu1804-docker-4c-4g-955 with PID 2875 (started by jenkins in /w/workspace/oam-tr069-adapter-sonar/acs/application-booter)
[2025-02-22 12:05:53:616] [] [main] InformSwVersionUpdatedTest DEBUG: Running with Spring Boot v2.2.1.RELEASE, Spring v5.2.1.RELEASE
[2025-02-22 12:05:53:616] [] [main] InformSwVersionUpdatedTest INFO : No active profile set, falling back to default profiles: default
[2025-02-22 12:05:53:982] [] [main] QuartzSchedulerManager DEBUG: init started
[2025-02-22 12:05:53:982] [] [main] QuartzSchedulerManager DEBUG: Running on active server; hence marking quartz as active service
[2025-02-22 12:05:53:982] [] [main] QuartzSchedulerManager DEBUG: init complete
[2025-02-22 12:05:54:418] [] [main] InformSwVersionUpdatedTest INFO : Started InformSwVersionUpdatedTest in 0.821 seconds (JVM running for 38.8)
[2025-02-22 12:05:54:426] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:54:426] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:54:426] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:54:427] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:54:429] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@15b472db1Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190900 BOOTSTRAP12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519090Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-02-22 12:05:54:436] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-02-22 12:05:54:436] [0005B9519090] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-02-22 12:05:54:436] [0005B9519090] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-02-22 12:05:54:436] [0005B9519090] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-02-22 12:05:54:437] [0005B9519090] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-02-22 12:05:54:437] [0005B9519090] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-02-22 12:05:54:437] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.0005B9519090_CONNECTION_REQUEST
[2025-02-22 12:05:54:437] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.0005B9519090_CONNECTION_REQUEST
[2025-02-22 12:05:54:437] [0005B9519090] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-02-22 12:05:54:437] [0005B9519090] [main] DeviceInformBuilder DEBUG: Constructing BOOTSTRAP Inform
[2025-02-22 12:05:54:437] [0005B9519090] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-02-22 12:05:54:438] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-02-22 12:05:54:438] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '0 BOOTSTRAP'
[2025-02-22 12:05:54:439] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-02-22 12:05:54:441] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Device Inform event received is BOOTSTRAP, hence aborting all the pending operations if any exists
[2025-02-22 12:05:54:441] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving all the pending Device RPC requests
[2025-02-22 12:05:54:447] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Grouping the records based on operationId
[2025-02-22 12:05:54:447] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists 0 pending NBI requests for the device
[2025-02-22 12:05:54:448] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:448] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:452] [0005B9519090] [main] TR069RequestProcessEngineHelper INFO : Device is contacting ACS for the first time, creating the new session ID for the device
[2025-02-22 12:05:54:453] [0005B9519090] [main] SessionManager DEBUG: Creating a new session for the device
[2025-02-22 12:05:54:456] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:459] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: 5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:459] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:54:459] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-02-22 12:05:54:459] [0005B9519090] [main] TR069EventNotificationService DEBUG: Device Inform Event received: '0 BOOTSTRAP'
[2025-02-22 12:05:54:523] [0005B9519090] [main] TR069EventNotificationService DEBUG: Successfully posted the device inform event to DM to forward to NBI
[2025-02-22 12:05:54:529] [] [main] TR069RequestProcessEngineHelper DEBUG: Device details are changed
[2025-02-22 12:05:54:529] [] [main] TR069RequestProcessEngine INFO : The device data like connection request URL/ Device SW/HW version has changed, hence updating the device details
[2025-02-22 12:05:54:530] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-02-22 12:05:54:530] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-02-22 12:05:54:530] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:54:530] [] [main] TimerServiceManagerAPIImpl DEBUG: Requested to start timer for 5df21ce4-f115-11ef-a972-0242bf4b5cb0, listener bean=SessionTimeoutHandler
[2025-02-22 12:05:54:531] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 5df21ce4-f115-11ef-a972-0242bf4b5cb0 started
[2025-02-22 12:05:54:531] [] [main] QuartzSchedulerManager DEBUG: scheduleJob : Scheduing job 5df21ce4-f115-11ef-a972-0242bf4b5cb0 successfully completed
[2025-02-22 12:05:54:531] [] [main] TimerServiceManagerAPIImpl DEBUG: Successfully started timer for 5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:531] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : 5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:531] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-02-22 12:05:54:550] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-02-22 12:05:54:551] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:54:551] [] [main] CPEManagementService INFO : 11
[2025-02-22 12:05:54:551] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:54:551] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:54:556] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:54:559] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:54:559] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:54:559] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:54:559] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:54:559] [] [main] CPEManagementService DEBUG: The session id is 5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:559] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:54:559] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-02-22 12:05:54:560] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: 5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:583] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: 5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:584] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-02-22 12:05:54:584] [0005B9519090] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-02-22 12:05:54:584] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:584] [0005B9519090] [main] SessionManager DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:587] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: 5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:587] [0005B9519090] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:54:587] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:54:587] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-02-22 12:05:54:593] [0005B9519090] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519090
[2025-02-22 12:05:54:593] [0005B9519090] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-02-22 12:05:54:594] [0005B9519090] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:54:594] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Requested to stop the timer.5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:595] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 5df21ce4-f115-11ef-a972-0242bf4b5cb0 started
[2025-02-22 12:05:54:595] [0005B9519090] [main] QuartzSchedulerManager DEBUG: deleteSchedule : Deleting schedule for job 5df21ce4-f115-11ef-a972-0242bf4b5cb0 successfully completed
[2025-02-22 12:05:54:596] [0005B9519090] [main] TimerServiceManagerAPIImpl DEBUG: Successfully stopped the timer.5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:596] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : 5df21ce4-f115-11ef-a972-0242bf4b5cb0
[2025-02-22 12:05:54:597] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:54:597] [0005B9519090] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:54:599] [0005B9519090] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-02-22 12:05:54:602] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:54:602] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:54:602] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:54:602] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:54:607] [] [DefaultMessageListenerContainer-2] DeviceInformForwarder DEBUG: DeviceNotification message is received for deviceId : 0005B9519090 , Notification Type(s): [BOOTSTRAP]
[2025-02-22 12:05:54:607] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService DEBUG: ++++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-02-22 12:05:54:608] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService DEBUG: Received Notification from NBI
[2025-02-22 12:05:54:608] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService DEBUG: Posting the Device Notification to WebService: null
[2025-02-22 12:05:54:614] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService ERROR: Unable to post the Device Notification, Reason: URI is not absolute
[2025-02-22 12:05:54:614] [] [DefaultMessageListenerContainer-2] DeviceEventsMapperNotificationService DEBUG: +++++++++++++++++++++++++++++++++++++++++++++++++++++
[2025-02-22 12:05:54:614] [] [DefaultMessageListenerContainer-2] DeviceInformForwarder DEBUG: Successfully processed device notification.
[2025-02-22 12:05:54:781] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:54:782] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:54:782] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:54:782] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:54:784] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@4afc69c61Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190932 PERIODIC12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519093Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-02-22 12:05:54:788] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-02-22 12:05:54:788] [0005B9519093] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-02-22 12:05:54:788] [0005B9519093] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-02-22 12:05:54:788] [0005B9519093] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-02-22 12:05:54:788] [0005B9519093] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-02-22 12:05:54:788] [0005B9519093] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-02-22 12:05:54:788] [0005B9519093] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-02-22 12:05:54:788] [0005B9519093] [main] DeviceInformBuilder DEBUG: Constructing PERIODIC Inform
[2025-02-22 12:05:54:788] [0005B9519093] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-02-22 12:05:54:789] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-02-22 12:05:54:789] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '2 PERIODIC'
[2025-02-22 12:05:54:789] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-02-22 12:05:54:789] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:790] [0005B9519093] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-02-22 12:05:54:790] [0005B9519093] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519093
[2025-02-22 12:05:54:793] [0005B9519093] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-02-22 12:05:54:795] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid10
[2025-02-22 12:05:54:795] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:54:795] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-02-22 12:05:54:796] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519093
[2025-02-22 12:05:54:796] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-02-22 12:05:54:796] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-02-22 12:05:54:796] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:54:796] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid10
[2025-02-22 12:05:54:796] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-02-22 12:05:54:798] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-02-22 12:05:54:799] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:54:799] [] [main] CPEManagementService INFO : 11
[2025-02-22 12:05:54:799] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:54:799] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:54:800] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:54:801] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:54:801] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:54:801] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:54:801] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:54:801] [] [main] CPEManagementService DEBUG: The session id is sessionid10
[2025-02-22 12:05:54:801] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:54:801] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-02-22 12:05:54:801] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid10
[2025-02-22 12:05:54:802] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid10
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid10
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:54:803] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-02-22 12:05:54:803] [0005B9519093] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519093
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid10
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:54:803] [0005B9519093] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-02-22 12:05:54:803] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:54:804] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:54:804] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:54:804] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:54:810] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:54:810] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:54:810] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:54:810] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:54:812] [] [main] CPEManagementService DEBUG: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl@537173bc1Airvana0005B9LTE_Enterprise_C-RANSC_Cntrl0005B95190954 VALUE CHANGE12018-04-27T07:09:160Device.ManagementServer.ParameterKeyNoneDevice.ManagementServer.ConnectionRequestURLhttp://10.210.37.1/acscallDevice.DeviceInfo.ManufacturerAirvanaDevice.DeviceInfo.ManufacturerOUI0005B9Device.DeviceInfo.ProductClassLTE_Enterprise_C-RANSC_CntrlDevice.DeviceInfo.SerialNumber0005B9519095Device.DeviceInfo.HardwareVersion750742.00.04Device.DeviceInfo.SoftwareVersion3.0.00.073Device.DeviceInfo.ProvisioningCodeDevice.FAP.X_0005B9_RUWhiteListDevice.IP.Interface.1.IPv4Enable1Device.IP.Interface.1.IPv4Address.1.IPAddress10.210.37.1
[2025-02-22 12:05:54:816] [] [main] CPEManagementService INFO : Event notified by the device is of type: Inform
[2025-02-22 12:05:54:816] [0005B9519095] [main] DeviceEventHandler INFO : Processing the device Inform event
[2025-02-22 12:05:54:816] [0005B9519095] [main] DeviceEventHandler DEBUG: Authorization header received in the request -> basic
[2025-02-22 12:05:54:816] [0005B9519095] [main] DeviceEventHandler INFO : Is device authentication successful: true
[2025-02-22 12:05:54:816] [0005B9519095] [main] DeviceEventHandler DEBUG: The root element is: Device
[2025-02-22 12:05:54:816] [0005B9519095] [main] DeviceEventHandler DEBUG: Canceling the Connection initiation timer, as Inform is been sent by the device
[2025-02-22 12:05:54:816] [0005B9519095] [main] DeviceInformBuilder DEBUG: Building Device Inform event based on the event codes sent by the device
[2025-02-22 12:05:54:817] [0005B9519095] [main] DeviceInformBuilder DEBUG: Constructing VALUECHANGE Inform
[2025-02-22 12:05:54:817] [0005B9519095] [main] DeviceEventHandler DEBUG: Sending the device inform to TR069 Request Processor to process
[2025-02-22 12:05:54:817] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Device Inform Event
[2025-02-22 12:05:54:817] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the Device Inform Event: '4 VALUE CHANGE'
[2025-02-22 12:05:54:817] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Getting the existing Session Object for the device
[2025-02-22 12:05:54:817] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:819] [0005B9519095] [main] TR069RequestProcessEngine INFO : Creating the device record in TR069_DEVICE_ table, as the device is authenticated successfully.
[2025-02-22 12:05:54:819] [0005B9519095] [main] DeviceOperationManager DEBUG: Updating the TR069 device: 0005B9519095
[2025-02-22 12:05:54:821] [0005B9519095] [main] DeviceOperationManager DEBUG: Successfully updated the device
[2025-02-22 12:05:54:822] [] [main] TR069RequestProcessEngine DEBUG: The session id generated to process the device notification request is: sessionid5
[2025-02-22 12:05:54:823] [] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:54:823] [] [main] TR069RequestProcessEngine DEBUG: Sending the Device Inform Event to the Mapper
[2025-02-22 12:05:54:824] [] [main] TR069RequestProcessEngine INFO : Setting connection status as true for device: 0005B9519095
[2025-02-22 12:05:54:824] [] [main] TR069RequestProcessEngine DEBUG: Updating the session for the device with newly generated session id
[2025-02-22 12:05:54:824] [] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to LOCKED
[2025-02-22 12:05:54:824] [] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:54:824] [] [main] TR069RequestProcessEngineHelper DEBUG: Successfully started the timer task for Device request with session ID : sessionid5
[2025-02-22 12:05:54:824] [] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Device Inform Event
[2025-02-22 12:05:54:826] [] [main] TR069RPC DEBUG: Key element is: 1
[2025-02-22 12:05:54:826] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:54:827] [] [main] CPEManagementService INFO : 11
[2025-02-22 12:05:54:827] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:54:827] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request
[2025-02-22 12:05:54:828] [] [main] CPEManagementService DEBUG: A device event occurred
[2025-02-22 12:05:54:829] [] [main] CPEManagementService DEBUG: Request Headers Content-Type
[2025-02-22 12:05:54:829] [] [main] CPEManagementService DEBUG: Request Headers Accept
[2025-02-22 12:05:54:829] [] [main] CPEManagementService DEBUG: Request Headers Authorization
[2025-02-22 12:05:54:829] [] [main] CPEManagementService DEBUG: Request Headers Cookie
[2025-02-22 12:05:54:829] [] [main] CPEManagementService DEBUG: The session id is sessionid5
[2025-02-22 12:05:54:829] [] [main] CPEManagementService DEBUG: Next char is -1
[2025-02-22 12:05:54:829] [] [main] CPEManagementService INFO : Received Empty Device response
[2025-02-22 12:05:54:829] [] [main] TR069RequestProcessEngine DEBUG: Fetching Operation request details for session: sessionid5
[2025-02-22 12:05:54:831] [] [main] TR069RequestProcessEngine DEBUG: There exists no pending operation request for the session: sessionid5
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Processing Empty request
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngine INFO : Processing the empty request from device
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Acquiring the session lock for the device
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: The session id used to process the empty device request is: sessionid5
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessorCacheUtil DEBUG: Entering put
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Checking if any pending Device RPC requests exists for the device
[2025-02-22 12:05:54:831] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: Retrieving the oldest pending Device RPC request
[2025-02-22 12:05:54:831] [0005B9519095] [main] DeviceRPCRequestRepositoryHelper DEBUG: There exists no pending Device RPC requests for the device: 0005B9519095
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngine INFO : No pending Device RPC request exists for the device, hence empty device response will be sent to the device
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngine DEBUG: Updating the session to terminated state
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Successfully stopped the timer task for Device request with session ID : sessionid5
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Changing the session state from PROCESSING to TERMINATED
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069RequestProcessEngineHelper DEBUG: Updating the session
[2025-02-22 12:05:54:831] [0005B9519095] [main] TR069DeviceEventHandlerImpl DEBUG: Successfully processed Empty request
[2025-02-22 12:05:54:832] [] [main] CPEManagementService DEBUG: Clearing the cookies
[2025-02-22 12:05:54:832] [] [main] CPEManagementService INFO :
[2025-02-22 12:05:54:832] [] [main] CPEManagementService DEBUG: End of processing
[2025-02-22 12:05:54:832] [] [main] CPEManagementService DEBUG: End of processing the HTTP post request