HTTP Status 500 - Could not write content: Object is null 解决方法

本文介绍在使用jqGrid过程中遇到的JSON数据处理异常问题,主要表现为返回的JSON数据中存在null值导致页面显示错误。文章提供了具体的异常堆栈信息,并提出了解决方案:在JSON数据转换时对null值进行特殊处理,避免异常发生。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

错误描述:使用jqGrid获取json数据并插入至表中,System.out.print可以正常输出jsonObject对象数据,但返回至页面时抛出异常

GET http://localhost:8080/*.do?500 (Internal Server Error)

type Exception report

message Could not write content: Object is null (through reference chain: net.sf.json.JSONObject["rows"]->net.sf.json.JSONArray[5]->net.sf.json.JSONObject["cell"]->net.sf.json.JSONArray[4]->net.sf.json.JSONNull["empty"]);
nested exception is com.fasterxml.jackson.databind.JsonMappingException: Object is null (through reference chain: net.sf.json.JSONObject["rows"]->net.sf.json.JSONArray[5]->net.sf.json.JSONObject["cell"]
->net.sf.json.JSONArray[4]->net.sf.json.JSONNull["empty"]) description The server encountered an internal error that prevented it from fulfilling this request. exception org.springframework.http.converter.HttpMessageNotWritableException: Could not write content: Object is null (through reference chain: net.sf.json.JSONObject["rows"]->net.sf.json.JSONArray[5]->net.sf.json.JSONObject["cell"]
->net.sf.json.JSONArray[4]->net.sf.json.JSONNull["empty"]); nested exception is com.fasterxml.jackson.databind.JsonMappingException: Object is null (through reference chain: net.sf.json.JSONObject["rows"]
->net.sf.json.JSONArray[5]->net.sf.json.JSONObject["cell"]->net.sf.json.JSONArray[4]->net.sf.json.JSONNull["empty"]) org.springframework.http.converter.json.AbstractJackson2HttpMessageConverter.writeInternal(AbstractJackson2HttpMessageConverter.java:238) org.springframework.http.converter.AbstractHttpMessageConverter.write(AbstractHttpMessageConverter.java:208) org.springframework.web.servlet.mvc.method.annotation.AbstractMessageConverterMethodProcessor.writeWithMessageConverters(AbstractMessageConverterMethodProcessor.java:161) org.springframework.web.servlet.mvc.method.annotation.AbstractMessageConverterMethodProcessor.writeWithMessageConverters(AbstractMessageConverterMethodProcessor.java:101) org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.handleReturnValue(RequestResponseBodyMethodProcessor.java:167) org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:71) org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:776) org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:705) org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:966) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:857) javax.servlet.http.HttpServlet.service(HttpServlet.java:624) org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:842) javax.servlet.http.HttpServlet.service(HttpServlet.java:731) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

 返回500错误有很多种可能性,上述错误问题其实很简单,jsonObject对象内包含别的对象,且存在某object值为NULL。

如果你的返回值中不存在null,不会报错,一旦有null字段,则无法插入到jqGrid中,并报上述错误。

解决方案:为了程序的健壮性,最好不要在json数据中直接存null,可以在转json格式时加一个判断,存在字段为null则将其赋值为“ ”(空字符串),然后传输时就不会出现上述错误了。

 

 

解决异常还是要仔细看错误提示,自己看提示调试有时候比直接百度来的更有效。

 

啦啦啦 ……

 

 

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

 

500其他可能性:

1.json序列化的问题{ 

                                   1.1没有写@responseBody

          1.2可以尝试使用MappingJacksonView做解析

                               }

2.确认json序列化没问题,通过其他方式你可以正常输出的话,可以看一下是否因为数据量过大而造成异常,修改web.config配置文件

以上具体解决方法百度上都有详解。

转载于:https://www.cnblogs.com/Janine-S/p/7202026.html

2025-07-02 20:15:21.873 2949-3506 ActivityManagerWrapper com.miui.home E getRecentTasks: mainTaskId=491 userId=0 baseIntent=Intent { act=android.intent.action.MAIN flag=270532608 cmp=ComponentInfo{com.example.test360/com.example.test360.MainActivity} } 2025-07-02 20:15:21.881 2949-3506 ActivityManagerWrapper com.miui.home E getRecentTasks: mainTaskId=491 userId=0 baseIntent=Intent { act=android.intent.action.MAIN flag=270532608 cmp=ComponentInfo{com.example.test360/com.example.test360.MainActivity} } 2025-07-02 20:15:21.938 27328-27328 FileUtils com.example.test360 E err open mi_exception_log errno=2 2025-07-02 20:15:21.938 27328-27328 FileUtils com.example.test360 E err write to mi_exception_log 2025-07-02 20:15:21.999 27328-27328 MiuiMultiWindowUtils com.example.test360 E initFreeFormResolutionArgs failed, device is elish 2025-07-02 20:15:22.076 27328-27328 FileUtils com.example.test360 E err write to mi_exception_log 2025-07-02 20:15:22.100 27328-27328 SurfaceSyncer com.example.test360 E Failed to find sync for id=0 2025-07-02 20:15:22.100 27328-27328 SurfaceSyncer com.example.test360 E Failed to find sync for id=0 2025-07-02 20:15:22.100 27328-27328 SurfaceSyncer com.example.test360 E Failed to find sync for id=0 2025-07-02 20:15:22.107 27328-27357 libEGL com.example.test360 E pre_cache appList: ,, 2025-07-02 20:15:22.120 27328-27357 LB com.example.test360 E fail to open node: No such file or directory 2025-07-02 20:15:22.140 8572-8572 BaseInputMethodService com.sohu.inputmethod.sogou.xiaomi E onStartInput app:com.example.test360 restarting:false 2025-07-02 20:15:22.149 2949-3506 ActivityManagerWrapper com.miui.home E getRecentTasks: mainTaskId=491 userId=0 baseIntent=Intent { act=android.intent.action.MAIN flag=270532608 cmp=ComponentInfo{com.example.test360/com.example.test360.MainActivity} } 2025-07-02 20:15:22.151 2949-3506 ActivityManagerWrapper com.miui.home E getRecentTasks: mainTaskId=491 userId=0 baseIntent=Intent { act=android.intent.action.MAIN flag=270532608 cmp=ComponentInfo{com.example.test360/com.example.test360.MainActivity} } 2025-07-02 20:15:22.217 27328-27380 libEGL com.example.test360 E pre_cache appList: ,, 2025-07-02 20:15:22.273 27328-27387 send_data_to_xlog com.example.test360 E send_video_play_to_xlog, start 2025-07-02 20:15:22.273 27328-27389 send_data_to_xlog com.example.test360 E send_video_play_to_xlog, start 2025-07-02 20:15:22.273 27328-27387 xlog_client com.example.test360 E xlog_open: Error in open xlog 2025-07-02 20:15:22.273 27328-27387 xlog_client com.example.test360 E xlog open fail 2025-07-02 20:15:22.273 27328-27389 xlog_client com.example.test360 E xlog_open: Error in open xlog 2025-07-02 20:15:22.273 27328-27389 xlog_client com.example.test360 E xlog open fail 2025-07-02 20:15:22.309 1224-2386 AudioPolicyIntefaceImpl audioserver E getInputForAttr permission denied: recording not allowed for AttributionSourceState{pid: 27328, uid: 10134, packageName: com.example.test360, attributionTag: (null), token: {no toString() implemented}, renouncedPermissions: [], next: []} 2025-07-02 20:15:22.309 1224-29515 AudioPolicyIntefaceImpl audioserver E getInputForAttr permission denied: recording not allowed for AttributionSourceState{pid: 27328, uid: 10134, packageName: com.example.test360, attributionTag: (null), token: {no toString() implemented}, renouncedPermissions: [], next: []} 2025-07-02 20:15:22.309 27328-27364 AudioRecord com.example.test360 E createRecord_l(0): AudioFlinger could not create record track, status: -1 2025-07-02 20:15:22.309 27328-27367 AudioRecord com.example.test360 E createRecord_l(0): AudioFlinger could not create record track, status: -1 2025-07-02 20:15:22.309 27328-27364 AudioRecord-JNI com.example.test360 E Error creating AudioRecord instance: initialization check failed with status -1. 2025-07-02 20:15:22.309 27328-27364 android.me...udioRecord com.example.test360 E Error code -20 when initializing native AudioRecord object. 2025-07-02 20:15:22.310 27328-27364 VideoCapture com.example.test360 E AudioRecord object cannot initialized correctly! 2025-07-02 20:15:22.311 27328-27367 AudioRecord-JNI com.example.test360 E Error creating AudioRecord instance: initialization check failed with status -1. 2025-07-02 20:15:22.311 27328-27364 FileUtils com.example.test360 E err open mi_exception_log errno=2 2025-07-02 20:15:22.311 27328-27364 FileUtils com.example.test360 E err write to mi_exception_log 2025-07-02 20:15:22.311 27328-27367 android.me...udioRecord com.example.test360 E Error code -20 when initializing native AudioRecord object. 2025-07-02 20:15:22.311 27328-27367 VideoCapture com.example.test360 E AudioRecord object cannot initialized correctly! 2025-07-02 20:15:22.311 27328-27367 FileUtils com.example.test360 E err open mi_exception_log errno=2 2025-07-02 20:15:22.311 27328-27367 FileUtils com.example.test360 E err write to mi_exception_log 2025-07-02 20:15:22.315 27328-27387 send_data_to_xlog com.example.test360 E send_video_play_to_xlog, start 2025-07-02 20:15:22.315 27328-27387 xlog_client com.example.test360 E xlog_open: Error in open xlog 2025-07-02 20:15:22.315 27328-27387 xlog_client com.example.test360 E xlog open fail 2025-07-02 20:15:22.329 27328-27420 send_data_to_xlog com.example.test360 E send_video_play_to_xlog, start 2025-07-02 20:15:22.329 27328-27420 xlog_client com.example.test360 E xlog_open: Error in open xlog 2025-07-02 20:15:22.329 27328-27420 xlog_client com.example.test360 E xlog open fail 2025-07-02 20:15:22.352 1224-2386 AudioPolicyIntefaceImpl audioserver E getInputForAttr permission denied: recording not allowed for AttributionSourceState{pid: 27328, uid: 10134, packageName: com.example.test360, attributionTag: (null), token: {no toString() implemented}, renouncedPermissions: [], next: []} 2025-07-02 20:15:22.352 27328-27367 AudioRecord com.example.test360 E createRecord_l(0): AudioFlinger could not create record track, status: -1 2025-07-02 20:15:22.352 27328-27367 AudioRecord-JNI com.example.test360 E Error creating AudioRecord instance: initialization check failed with status -1. 2025-07-02 20:15:22.352 27328-27367 android.me...udioRecord com.example.test360 E Error code -20 when initializing native AudioRecord object. 2025-07-02 20:15:22.352 27328-27367 VideoCapture com.example.test360 E AudioRecord object cannot initialized correctly! 2025-07-02 20:15:22.355 27328-27420 send_data_to_xlog com.example.test360 E send_video_play_to_xlog, start 2025-07-02 20:15:22.356 27328-27420 xlog_client com.example.test360 E xlog_open: Error in open xlog 2025-07-02 20:15:22.356 27328-27420 xlog_client com.example.test360 E xlog open fail 2025-07-02 20:15:22.368 27328-27437 send_data_to_xlog com.example.test360 E send_video_play_to_xlog, start 2025-07-02 20:15:22.368 27328-27437 xlog_client com.example.test360 E xlog_open: Error in open xlog 2025-07-02 20:15:22.368 27328-27437 xlog_client com.example.test360 E xlog open fail 2025-07-02 20:15:22.392 1224-2386 AudioPolicyIntefaceImpl audioserver E getInputForAttr permission denied: recording not allowed for AttributionSourceState{pid: 27328, uid: 10134, packageName: com.example.test360, attributionTag: (null), token: {no toString() implemented}, renouncedPermissions: [], next: []} 2025-07-02 20:15:22.392 27328-27367 AudioRecord com.example.test360 E createRecord_l(0): AudioFlinger could not create record track, status: -1 2025-07-02 20:15:22.400 27328-27367 AudioRecord-JNI com.example.test360 E Error creating AudioRecord instance: initialization check failed with status -1. 2025-07-02 20:15:22.401 27328-27367 android.me...udioRecord com.example.test360 E Error code -20 when initializing native AudioRecord object. 2025-07-02 20:15:22.401 27328-27367 VideoCapture com.example.test360 E AudioRecord object cannot initialized correctly! 请解析错误的原因
07-03
PS C:\Users\Administrator> # 带空格的URL请求 PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://api.example.com/path with space" -Verbose 详细信息: 鎵ц curl 鍛戒护: curl https://api.example.com/path with space -X GET --silent --show-error --write-out HTTP_STATUS:%{http_code} -H User-Agent: PowerShell CurlTools/1.0 curl: (6) Could not resolve host: api.example.com HTTP_STATUS:000 curl: (6) Could not resolve host: with HTTP_STATUS:000 curl: (6) Could not resolve host: space HTTP_STATUS:000 curl: (6) Could not resolve host: PowerShell HTTP_STATUS:000 curl: (6) Could not resolve host: CurlTools HTTP_STATUS:000 PS C:\Users\Administrator> PS C:\Users\Administrator> # 文件下载(自动创建目录) PS C:\Users\Administrator> Invoke-CurlRequest -Url "https://example.com/file.zip" -OutputFile "C:\Downloads\New Folder\file.zip" curl: (23) Failure writing output to destination HTTP_STATUS:404 curl: (3) URL rejected: Bad hostname HTTP_STATUS:000 curl: (6) Could not resolve host: PowerShell HTTP_STATUS:000 curl: (6) Could not resolve host: CurlTools HTTP_STATUS:000 Status : Error Content : 无法将“ExtractCurlError”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写,如果包括路径,请确保路径正确,然后再试一次。 Data : ErrorMessage : 无法将“ExtractCurlError”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写,如果包括路径,请确保路径正确,然后再试一次。 ErrorType : Url : https://example.com/file.zip Method : GET StatusCode : Headers : Latency : 17159 Size : 0 Timestamp : 2025/8/16 0:59:49 RawOutput : PS C:\Users\Administrator> PS C:\Users\Administrator> # 带特殊字符的请求头 PS C:\Users\Administrator> $headers = @{ >> "Authorization" = "Bearer token:123" >> "Custom-Header" = "value;with;special=chars" >> } >> $response = Invoke-CurlRequest -Url "https://api.example.com" -Headers $headers >> curl: (6) Could not resolve host: api.example.com HTTP_STATUS:000 curl: (3) URL rejected: Bad hostname HTTP_STATUS:000 curl: (6) Could not resolve host: Bearer HTTP_STATUS:000 curl: (6) Could not resolve host: token HTTP_STATUS:000 curl: (6) Could not resolve host: PowerShell HTTP_STATUS:000 curl: (6) Could not resolve host: CurlTools HTTP_STATUS:000 PS C:\Users\Administrator> # 忽略SSL证书验证(显示警告) PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://self-signed.example" -Insecure 警告: 绂佺敤SSL璇佷功楠岃瘉 - 瀹夊叏椋庨櫓! curl: (6) Could not resolve host: self-signed.example HTTP_STATUS:000 curl: (6) Could not resolve host: PowerShell HTTP_STATUS:000 curl: (6) Could not resolve host: CurlTools HTTP_STATUS:000 PS C:\Users\Administrator> PS C:\Users\Administrator> # 带重试的API调用 PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://api.example.com/data" ` >> -Method GET ` >> -RetryCount 3 ` >> -RetryInterval 2 ` >> -RetryOnStatusCodes 500, 503 ` >> -RetryOnTimeout >> Invoke-CurlRequest : 找不到与参数名称“RetryCount”匹配的参数。 所在位置 行:3 字符: 5 + -RetryCount 3 ` + ~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Invoke-CurlRequest],ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Invoke-CurlRequest PS C:\Users\Administrator> # 文件下载带重试 PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://example.com/largefile.zip" ` >> -OutputFile "download.zip" ` >> -RetryCount 2 ` >> -RetryInterval 1 >> Invoke-CurlRequest : 找不到与参数名称“RetryCount”匹配的参数。 所在位置 行:3 字符: 5 + -RetryCount 2 ` + ~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Invoke-CurlRequest],ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Invoke-CurlRequest PS C:\Users\Administrator> # 详细错误诊断 PS C:\Users\Administrator> if ($response.Status -eq "JsonParseError") { >> Write-Host "JSON解析失败:" >> Write-Host $response.Data.ErrorContext >> } >> PS C:\Users\Administrator>
最新发布
08-17
PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://api.example.com/data" -OutputType Object PS C:\Users\Administrator> if ($response.Status -eq "Success") { >> $response.Data | Format-Table >> } elseif ($response.Status -eq "Error") { >> Write-Host "请求失败: $($response.ErrorMessage)" >> } >> 请求失败: Could not resolve host: api.example.com PS C:\Users\Administrator> $headers = @{ >> "Authorization" = "Bearer token123" >> "X-Custom-Header" = "value" >> } >> PS C:\Users\Administrator> $body = @{ >> name = "John" >> age = 30 >> } | ConvertTo-Json >> PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://api.example.com/users" ` >> -Method POST ` >> -Headers $headers ` >> -Body $body ` >> -FollowRedirect ` >> -OutputType Object >> PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://example.com" -IncludeHeaders PS C:\Users\Administrator> if ($response.Status -eq "Success") { >> Write-Host "响应头:" >> $response.Headers.GetEnumerator() | ForEach-Object { >> Write-Host "$($_.Key): $($_.Value)" >> } >> } >> 响应头: PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://invalid-domain.example" PS C:\Users\Administrator> if ($response.Status -eq "Error") { >> Write-Host "错误: $($response.ErrorMessage)" -ForegroundColor Red >> # 输出: 错误: Could not resolve host: invalid-domain.example >> } >> 错误: Could not resolve host: invalid-domain.example PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://example.com/html-page" -OutputType Object PS C:\Users\Administrator> if ($response.Status -eq "NonJsonResponse") { >> Write-Host "接收到非JSON响应,长度: $($response.Content.Length)" >> } >> 接收到非JSON响应,长度: 1255 PS C:\Users\Administrator> $response = Invoke-CurlRequest -Url "https://api.example.com/error-endpoint" PS C:\Users\Administrator> if ($response.StatusCode -eq 404) { >> Write-Host "资源未找到" -ForegroundColor Yellow >> } elseif ($response.StatusCode -eq 500) { >> Write-Host "服务器错误" -ForegroundColor Red >> } >> PS C:\Users\Administrator>
08-17
Line 3507: 01-01 19:26:38.540 01744 01744 I adbd : persist.adb.watchdog set to '' Line 3508: 01-01 19:26:38.542 01744 01744 I adbd : persist.sys.test_harness set to '' Line 3510: 01-01 19:26:38.542 01744 01744 I adbd : adb watchdog timeout set to 600 seconds Line 3511: 01-01 19:26:38.543 01744 01744 I adbd : adbd started Line 3511: 01-01 19:26:38.543 01744 01744 I adbd : adbd started Line 3513: 01-01 19:26:38.543 01744 01759 I adbd : opening control endpoint /dev/usb-ffs/adb/ep0 Line 3514: 01-01 19:26:38.544 01744 01757 I adbd : Waiting for persist.adb.tls_server.enable=1 Line 3517: 01-01 19:26:38.554 01744 01759 I adbd : UsbFfsConnection constructed Line 3526: 01-01 19:26:38.570 01744 01761 I adbd : UsbFfs-monitor thread spawned Line 4331: 01-01 19:26:39.572 01744 01761 W adbd : timed out while waiting for FUNCTIONFS_BIND, trying again Line 4332: 01-01 19:26:39.572 01744 01761 I adbd : UsbFfs: connection terminated: monitor thread finished Line 4333: 01-01 19:26:39.573 01744 01744 I adbd : UsbFfs: already offline Line 4334: 01-01 19:26:39.573 01744 01744 I adbd : destroying transport UsbFfs Line 4335: 01-01 19:26:39.573 01744 01744 I adbd : UsbFfsConnection being destroyed Line 4353: 01-01 19:26:39.642 01744 01759 I adbd : opening control endpoint /dev/usb-ffs/adb/ep0 Line 4355: 01-01 19:26:39.648 01744 01759 I adbd : UsbFfsConnection constructed Line 4363: 01-01 19:26:39.652 01744 01965 I adbd : UsbFfs-monitor thread spawned Line 6044: 01-01 19:26:40.669 01744 01965 W adbd : timed out while waiting for FUNCTIONFS_BIND, trying again Line 6045: 01-01 19:26:40.669 01744 01965 I adbd : UsbFfs: connection terminated: monitor thread finished Line 6046: 01-01 19:26:40.670 01744 01744 I adbd : UsbFfs: already offline Line 6047: 01-01 19:26:40.670 01744 01744 I adbd : destroying transport UsbFfs Line 6048: 01-01 19:26:40.670 01744 01744 I adbd : UsbFfsConnection being destroyed Line 6641: 01-01 19:26:40.810 01744 01759 I adbd : opening control endpoint /dev/usb-ffs/adb/ep0 Line 6703: 01-01 19:26:40.815 01744 01759 I adbd : UsbFfsConnection constructed Line 6726: 01-01 19:26:40.820 01744 02220 I adbd : UsbFfs-monitor thread spawned Line 7858: 01-01 19:26:41.384 01744 02220 I adbd : USB event: FUNCTIONFS_BIND Line 12899: 01-01 19:26:45.298 02952 02958 E Diag_Lib: DPL : gIsQXDMDisabled 0, gIsADBDisabled 0, gIsDebugDisabled 0, gIsIMSLogsDisabled 0 gIsDebugDataPathDisabled = 0 Line 13319: 01-01 19:26:45.317 02952 02958 E Diag_Lib: DPL : gIsQXDMDisabled 0, gIsADBDisabled 0, gIsDebugDisabled 0, gIsIMSLogsDisabled 0 gIsDebugDataPathDisabled = 0 Line 13978: 01-01 19:26:45.534 02924 02924 D CompatConfig: No directory /apex/com.android.adbd/etc/compatconfig, skipping Line 17407: 01-01 19:26:47.093 02924 02924 W PackageManager: No package known for package restrictions com.google.android.adbd Line 17766: 01-01 19:26:47.274 02924 02924 D PackageManager: Directories scanned as system partitions: [/system:0, /vendor:524288, /odm:4194304, /oem:262144, /product:1048576, /system_ext:2097152, /my_product/non_overlay:1048576, /mnt/opex/com.oplus.odmf@15002009:2097152, /mnt/opex/com.oplus.moduleservices@15000014:2097152, /mnt/opex/com.oplus.fancyIconLoader@1000000:2097152, /mnt/opex/com.oplus.NetworkAssistSys@15002031:2097152, /mnt/opex/com.oplus.CustCore@15000029:2097152, /my_company:1048576, /my_carrier:1048576, /my_bigball:1048576, /my_product/cust/TR:1048576, /apex/com.android.ipsec:41943040, /apex/com.android.ondevicepersonalization:41943040, /apex/com.android.cellbroadcast:41943040, /apex/com.android.profiling:41943040, /apex/com.android.nfcservices:41943040, /apex/com.android.media.swcodec:41943040, /apex/com.android.conscrypt:41943040, /apex/vendor.oplus.hardware.stability.aidl:42467328, /apex/com.android.os.statsd:41943040, /apex/com.android.wifi:41943040, /apex/com.android.uwb:41943040, /apex/com.android.virt:41943040, /apex/com.android.adservices:41943040, /apex/com.android.configinfrastructure:41943040, /apex/com.android.devicelock:41943040, /apex/com.android.appsearch:41943040, /apex/com.google.mainline.primary.libs:41943040, /apex/com.android.compos:44040192, /apex/com.android.tethering:41943040, /apex/com.android.resolv:41943040, /apex/com.android.mediaprovider:41943040, /apex/com.android.runtime:41943040, /apex/com.android.neuralnetworks:41943040, /apex/com.android.permission:41943040, /apex/com.android.adbd:41943040, /apex/com.android.i18n:41943040, /apex/com.android.scheduling:41943040, /apex/com.android.media:41943040, /apex/com.android.tzdata:41943040, /apex/vendor.oplus.hardware.engineer.aidl:42467328, /apex/com.android.sdkext:41943040, /apex/com.android.rkpd:41943040, /apex/com.android.apex.cts.shim:41943040, /apex/com.android.art:41943040, /apex/com.android.extservices:41943040, /apex/com.android.vndk.v33:44040192, /apex/com.android.healthfitness:41943040] Line 17819: 01-01 19:26:47.410 02924 02924 I PackageManager: /data/apex/decompressed/com.android.adbd@351010000.decompressed.apex changed; collecting certs Line 17823: 01-01 19:26:47.422 02924 02924 E PackageManagerServiceUtilsExtImpl: Fix up user restrict data of pkg: com.google.android.adbd Line 19413: 01-01 19:26:51.224 02924 02924 D PackageManager: No files in app dir /apex/com.android.adbd/priv-app Line 19414: 01-01 19:26:51.224 02924 02924 D PackageManager: No files in app dir /apex/com.android.adbd/app Line 20634: 01-01 19:26:52.985 02924 02924 W PackageSettings: Couldn't write -1 to /config/sdcardfs/com.google.android.adbd/appid Line 21520: 01-01 19:26:53.270 02924 02924 D OverlayManager: -> Updating overlay: target=com.google.android.adbd overlays=[OverlayPaths { resourceDirs = [], overlayPaths = [/data/resource-cache/com.android.systemui-neutral-coSn.frro, /data/resource-cache/com.android.systemui-accent-n7sV.frro, /data/resource-cache/com.android.systemui-dynamic-EysW.frro] }] userId=0 Line 29901: 01-01 19:26:55.625 02924 03113 I UsbDeviceManager: failed to write to /sys/class/android_usb/android0/f_rndis/ethaddr Line 29902: 01-01 19:26:55.626 02924 03113 D UsbPortManager: Querying USB Gadget HAL version Line 29915: 01-01 19:26:55.630 02924 03113 E UsbDeviceManager: connectToProxy: usb gadget hidl hal service not found. Line 29922: at com.android.server.usb.UsbDeviceManager.<init>(UsbDeviceManager.java:332) Line 29922: at com.android.server.usb.UsbDeviceManager.<init>(UsbDeviceManager.java:332) Line 29935: 01-01 19:26:55.630 02924 03113 E UsbPortManager: USB Gadget HAL AIDL/HIDL not present Line 29936: 01-01 19:26:55.630 02924 03113 D UsbDeviceManager: getInstance done Line 29946: 01-01 19:26:55.636 02924 03113 I UsbDeviceManager: mResetUsbGadgetDisableDebounce:false connected:0configured:0 Line 29948: 01-01 19:26:55.636 02924 03113 I UsbDeviceManager: removeMessages MSG_UPDATE_STATE Line 30039: 01-01 19:26:55.647 02924 03113 D UsbPortManager: Querying USB HAL version Line 30082: 01-01 19:26:55.658 02924 03113 I UsbPortManager: USB HAL HIDL present Line 30093: 01-01 19:26:55.665 02924 03304 I UsbPortManager: Usb hal service started android.hardware.usb@1.0::IUsb default Line 30103: 01-01 19:26:55.671 02924 03113 D UsbPortManager: getInstance done Line 33157: 01-01 19:26:56.637 02924 02969 I UsbDeviceManager: handleMessage MSG_UPDATE_STATE mConnected:false mConfigured:false Line 46190: 01-01 19:26:58.809 02924 03298 D UsbDeviceManager: systemReady Line 46192: 01-01 19:26:58.810 02924 02969 D UsbDeviceManager: UsbBootInfo: [mSystemReady: true, mBootCompleted: false, mConnected: false, mConfigured: false, mCurrentUsbFunctionsReceived: true, mPendingBootBroadcast: true, mScreenLocked: true, screenUnlockedFunctions: , isAdbEnabled: true] Line 46221: 01-01 19:26:58.814 02924 03304 I UsbPortManager: ClientCallback V1_2: port0 Line 46245: 01-01 19:26:58.818 02924 02969 I UsbPortManager: USB port added: port=UsbPort{id=port0, supportedModes=dual, audio_acc, supportedContaminantProtectionModes=0, supportsEnableContaminantPresenceProtection=false, supportsEnableContaminantPresenceDetection=false, supportsComplianceWarnings=false, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device], contaminantDetectionStatus=0, contaminantProtectionStatus=0, usbDataStatus=unknown, isPowerTransferLimited=false, powerBrickConnectionStatus=unknown, complianceWarnings=[], plugState=0, displayPortAltModeInfo=null}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false, connectedAtMillis=36033, lastConnectDurationMillis=0 Line 70581: 01-01 19:27:06.142 02924 02972 V UsbDeviceManager: onKeyguardStateChanged: isShowing:true secure:false user:0 Line 72918: 01-01 19:27:07.024 02924 02924 I UsbDeviceManager: updateHostState UsbPort{id=port0, supportedModes=dual, audio_acc, supportedContaminantProtectionModes=0, supportsEnableContaminantPresenceProtection=false, supportsEnableContaminantPresenceDetection=false, supportsComplianceWarnings=false status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device], contaminantDetectionStatus=0, contaminantProtectionStatus=0, usbDataStatus=unknown, isPowerTransferLimited=false, powerBrickConnectionStatus=unknown, complianceWarnings=[], plugState=0, displayPortAltModeInfo=null} Line 77542: 01-01 19:27:08.412 02924 02972 D UsbDeviceManager: boot completed Line 77613: 01-01 19:27:08.420 02924 02969 D UsbDeviceManager: UsbBootInfo: [mSystemReady: true, mBootCompleted: true, mConnected: false, mConfigured: false, mCurrentUsbFunctionsReceived: true, mPendingBootBroadcast: true, mScreenLocked: false, screenUnlockedFunctions: , isAdbEnabled: true] Line 77621: 01-01 19:27:08.421 02924 02969 D UsbDeviceManager: broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31100000 (has extras) } extras: Bundle[{host_connected=false, connected=false, unlocked=false, adb=true, configured=false}] Line 77637: 01-01 19:27:08.423 02924 02969 D UsbDeviceManager: setEnabledFunctions [functions= ,forceRestart=false ,usbDataUnlocked=false ,mUsbDataUnlocked=false ,operationId=6] Line 77692: 01-01 19:27:08.444 02924 02969 D UsbDeviceManager: oplusFunctions: adb Line 77696: 01-01 19:27:08.446 02924 02969 D UsbDeviceManager: UsbFunc: [functions: adb, oemFunctions: adb, mCurrentFunctionsStr: adb, mCurrentOemFunctions: adb, forceRestart: false, mCurrentFunctionsApplied: true] Line 77700: 01-01 19:27:08.446 02924 02969 D UsbDeviceManager: updateMtpFunction , mtpEnabled: false, ptpEnabled: false, mIsMtpServiceBound: false Line 77814: 01-01 19:27:08.471 01744 01758 I adbd : adbd_auth: received a new framework connection Line 77814: 01-01 19:27:08.471 01744 01758 I adbd : adbd_auth: received a new framework connection Line 77815: 01-01 19:27:08.472 01744 01758 I adbd : adbd_auth: received new framework fd 16 (current = -1) Line 77815: 01-01 19:27:08.472 01744 01758 I adbd : adbd_auth: received new framework fd 16 (current = -1) Line 81135: 01-01 19:27:09.113 04893 04893 D vold_prepare_subdirs: Setting up mode 771 uid 0 gid 1000 context u:object_r:apex_module_data_file:s0 on path: /data/misc_ce/0/apexdata/com.android.adbd Line 82329: 01-01 19:27:09.362 02924 04870 W PackageManager: Skipping preparing app data for com.google.android.adbd Line 83351: 01-01 19:27:09.715 02924 02996 V UsbDeviceManager: onKeyguardStateChanged: isShowing:false secure:false user:0 分析adb链接中断原因
08-12
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值