Thanks for the capture. It looks as though it is indeed a CDS:Search problem in MC. At least I can see no other SOAP actions that might cause problems. Many of the CDS:Search requests are answered properly by MC by providing an HTTP 200 OK response with a respective resource payload. However towards the end of the log there seem to be requests where MC does not respond (or even responds with garbage). I cannot say why MC would crash on such requests. The JRiver guys will need to run the requests through their debugger..
Example of last CDS:Search in the log..
POST /ContentDirectory/control HTTP/1.1
Connection: Keep-Alive
HOST: 192.168.1.10:52101
User-Agent: LGMOBILE/7.0 UPnP/1.0 DLNADOC/1.50 (MS-DeviceCaps/1024) LGUPnP/2.1.022
Content-Type: text/xml; charset="utf-8"
Content-Length: 692
SOAPACTION: "urn:schemas-upnp-org:service:ContentDirectory:1#Search"
DLNADeviceName.lge.com: V20
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="
http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:Search xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1">
<ContainerID>0</ContainerID>
<SearchCriteria>upnp:class derivedfrom "object.item.imageItem"</SearchCriteria>
<Filter>@id,@parentID,@restricted,@refID,dc:title,upnp:class,upnp:artist,dc:date,upnp:albumArtURI,upnp:albumArtURI@dlna:profileID,dc:description,res,res@size,res@resolution,res@importUri</Filter>
<StartingIndex>50</StartingIndex>
<RequestedCount>50</RequestedCount>
<SortCriteria/>
</u:Search>
</s:Body>
</s:Envelope>
Author
Topic: MC Crashing - Android Phone is causing it (DLNA?) (Read 13769 times)