FATAL EXCEPTION: cling-11

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

FATAL EXCEPTION: cling-11

Jose Luis Larraz
This exception is happening when i try to browse pictures with the xbox, before cling 2.0 this exception dont happen, so if anyone has found a solution for this, could post it here. Meanwhile i will try to find a solution by myself.

02-19 17:13:07.730: E/AndroidRuntime(12488): FATAL EXCEPTION: cling-11
02-19 17:13:07.730: E/AndroidRuntime(12488): java.lang.IllegalStateException: IDLE,initial
02-19 17:13:07.730: E/AndroidRuntime(12488): at org.eclipse.jetty.server.AsyncContinuation.complete(AsyncContinuation.java:574)
02-19 17:13:07.730: E/AndroidRuntime(12488): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.complete(AsyncServletUpnpStream.java:87)
02-19 17:13:07.730: E/AndroidRuntime(12488): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.run(AsyncServletUpnpStream.java:123)
02-19 17:13:07.730: E/AndroidRuntime(12488): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
02-19 17:13:07.730: E/AndroidRuntime(12488): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
02-19 17:13:07.730: E/AndroidRuntime(12488): at java.lang.Thread.run(Thread.java:856)
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Christian Bauer
Administrator
Version of Cling?

Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Jose Luis Larraz
The last, upgrade it yesterday from github
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Christian Bauer
Administrator
Need the minimal code that produces the problem. I guess you run a MediaServer with Cling? Also definitely need a debug-level log. Read the manual about logging on Android.

Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Jose Luis Larraz
I suspect that the problem is in my code, when i try to browse all the pictures, its a lot of work and i start to think that this is the problem. when i have more information i will try to put it here, the curious is that this only happend with xbox not with ps3 or other clients.
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Jose Luis Larraz
The problem is that Xbox try to browse all the pictures in one folder (nearly 4000 in my case) at once, other clients try with 20 each time or something like that. so when you try to create the response to that in the browse(....) method of the class that extends from AbstractContentDirectoryService, it tooks too much time to do the work and the thread exception is thrown. A quick solution to that is limit the maximum number of elements for response to 50 for example. I suspect that with the other version of cling the exception wasnt through due to i don have too many pictures in my test folder so less work to do.
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Christian Bauer
Administrator
Did you override AndroidUpnpServiceConfiguration and/or provide custom timeouts for the network transports? What you are saying is that a long-running browse() method on a Cling/Android server will cause this exception if a client access it?

Can you try to trigger this with a Thread.sleep() in your browse() method please.
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Jose Luis Larraz
Ok, but i will do it tomorrow. Now i want to eat something
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Jose Luis Larraz
i forgot to put my configuration

protected AndroidUpnpServiceConfiguration createConfiguration()
        {
        //return new AndroidUpnpServiceConfiguration();
                return new AndroidUpnpServiceConfiguration() {

            // DOC:REGISTRY
            @Override
            public int getRegistryMaintenanceIntervalMillis() {
                return 7000;
            }
            // DOC:REGISTRY

            // DOC:SERVICE_TYPE
            @Override
            public ServiceType[] getExclusiveServiceTypes() {
                return new ServiceType[]
                {
                    new UDAServiceType("AVTransport"),
                    new UDAServiceType("RenderingControl")
                };
            }
            // DOC:SERVICE_TYPE
        };
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Jose Luis Larraz
I have done the test that you suggest to me, but i dont know if its my fault or what (but with the limitation to 50 is working fine for me)

After putting this

Thread.sleep(100000);

I get this

02-20 11:12:01.175: W/ReceivingAction(4206): Error reading action request XML body: org.fourthline.cling.model.UnsupportedDataException: Can't transform null or non-string/zero-length body of: (IncomingActionRequestMessage) POST /upnp/dev/87b8db85-a086-43bd-bfd5-a339f822b2eb/svc/upnp-org/ContentDirectory/action
02-20 11:12:01.175: W/ReceivingAction(4206): org.fourthline.cling.model.UnsupportedDataException: Can't transform null or non-string/zero-length body of: (IncomingActionRequestMessage) POST /upnp/dev/87b8db85-a086-43bd-bfd5-a339f822b2eb/svc/upnp-org/ContentDirectory/action
02-20 11:12:01.175: W/ReceivingAction(4206): at org.fourthline.cling.transport.impl.SOAPActionProcessorImpl.getMessageBody(SOAPActionProcessorImpl.java:510)
02-20 11:12:01.175: W/ReceivingAction(4206): at org.fourthline.cling.transport.impl.PullSOAPActionProcessorImpl.readBody(PullSOAPActionProcessorImpl.java:57)
02-20 11:12:01.175: W/ReceivingAction(4206): at org.fourthline.cling.transport.impl.RecoveringSOAPActionProcessorImpl.readBody(RecoveringSOAPActionProcessorImpl.java:59)
02-20 11:12:01.175: W/ReceivingAction(4206): at org.fourthline.cling.protocol.sync.ReceivingAction.executeSync(ReceivingAction.java:101)
02-20 11:12:01.175: W/ReceivingAction(4206): at org.fourthline.cling.protocol.ReceivingSync.execute(ReceivingSync.java:63)
02-20 11:12:01.175: W/ReceivingAction(4206): at org.fourthline.cling.protocol.ReceivingAsync.run(ReceivingAsync.java:71)
02-20 11:12:01.175: W/ReceivingAction(4206): at org.fourthline.cling.transport.spi.UpnpStream.process(UpnpStream.java:82)
02-20 11:12:01.175: W/ReceivingAction(4206): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.run(AsyncServletUpnpStream.java:97)
02-20 11:12:01.175: W/ReceivingAction(4206): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
02-20 11:12:01.175: W/ReceivingAction(4206): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
02-20 11:12:01.175: W/ReceivingAction(4206): at java.lang.Thread.run(Thread.java:856)
02-20 11:12:41.136: W/pnpServiceConfiguration(4206): Thread terminated () abruptly with exception: java.lang.IllegalStateException: IDLE,initial
02-20 11:12:41.136: W/pnpServiceConfiguration(4206): Root cause: java.lang.IllegalStateException: IDLE,initial
02-20 11:12:41.136: W/dalvikvm(4206): threadid=23: thread exiting with uncaught exception (group=0x41c34300)
02-20 11:12:41.144: E/AndroidRuntime(4206): FATAL EXCEPTION: cling-11
02-20 11:12:41.144: E/AndroidRuntime(4206): java.lang.IllegalStateException: IDLE,initial
02-20 11:12:41.144: E/AndroidRuntime(4206): at org.eclipse.jetty.server.AsyncContinuation.complete(AsyncContinuation.java:574)
02-20 11:12:41.144: E/AndroidRuntime(4206): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.complete(AsyncServletUpnpStream.java:87)
02-20 11:12:41.144: E/AndroidRuntime(4206): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.run(AsyncServletUpnpStream.java:123)
02-20 11:12:41.144: E/AndroidRuntime(4206): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
02-20 11:12:41.144: E/AndroidRuntime(4206): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
02-20 11:12:41.144: E/AndroidRuntime(4206): at java.lang.Thread.run(Thread.java:856)
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Christian Bauer
Administrator
Can you enable debug logging please, FINEST level.

Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Jose Luis Larraz
where can i find the jar necessary to import this

new org.seamless.android.FixedAndroidLogHandler();

i am not using maven, at this moment the only jars that i have with seamless are:
seamless-http-1.0-alpha2.jar
seamless-util-1.0-alpha2.jar
seamless-xml-1.0-alpha2.jar

Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Jose Luis Larraz
02-26 17:00:58.656: D/Registry(6594): Maintaining registry...
02-26 17:00:58.660: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:1c002264-1dd2-11b2-93b5-a29a04d9a783, Descriptor: http://192.168.1.129:37904/MediaRenderer1.xml, Root: true' expires in seconds: 1718
02-26 17:00:58.668: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:0f7f4900-0004-1000-b5d8-c4731e31d709, Descriptor: http://192.168.1.128:7676/smp_14_, Root: true' expires in seconds: 1718
02-26 17:00:58.679: D/Registry(6594): Executing pending operations: 0
02-26 17:01:01.679: D/Registry(6594): Maintaining registry...
02-26 17:01:01.679: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:1c002264-1dd2-11b2-93b5-a29a04d9a783, Descriptor: http://192.168.1.129:37904/MediaRenderer1.xml, Root: true' expires in seconds: 1715
02-26 17:01:01.679: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:0f7f4900-0004-1000-b5d8-c4731e31d709, Descriptor: http://192.168.1.128:7676/smp_14_, Root: true' expires in seconds: 1715
02-26 17:01:01.679: D/Registry(6594): Executing pending operations: 0
02-26 17:01:04.679: D/Registry(6594): Maintaining registry...
02-26 17:01:04.691: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:1c002264-1dd2-11b2-93b5-a29a04d9a783, Descriptor: http://192.168.1.129:37904/MediaRenderer1.xml, Root: true' expires in seconds: 1712
02-26 17:01:04.703: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:0f7f4900-0004-1000-b5d8-c4731e31d709, Descriptor: http://192.168.1.128:7676/smp_14_, Root: true' expires in seconds: 1712
02-26 17:01:04.703: D/Registry(6594): Executing pending operations: 0
02-26 17:01:07.707: D/Registry(6594): Maintaining registry...
02-26 17:01:07.711: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:1c002264-1dd2-11b2-93b5-a29a04d9a783, Descriptor: http://192.168.1.129:37904/MediaRenderer1.xml, Root: true' expires in seconds: 1709
02-26 17:01:07.726: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:0f7f4900-0004-1000-b5d8-c4731e31d709, Descriptor: http://192.168.1.128:7676/smp_14_, Root: true' expires in seconds: 1709
02-26 17:01:07.738: D/Registry(6594): Executing pending operations: 0
02-26 17:01:10.738: D/Registry(6594): Maintaining registry...
02-26 17:01:10.750: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:1c002264-1dd2-11b2-93b5-a29a04d9a783, Descriptor: http://192.168.1.129:37904/MediaRenderer1.xml, Root: true' expires in seconds: 1706
02-26 17:01:10.761: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:0f7f4900-0004-1000-b5d8-c4731e31d709, Descriptor: http://192.168.1.128:7676/smp_14_, Root: true' expires in seconds: 1706
02-26 17:01:10.777: D/Registry(6594): Executing pending operations: 0
02-26 17:01:13.777: D/Registry(6594): Maintaining registry...
02-26 17:01:13.789: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:1c002264-1dd2-11b2-93b5-a29a04d9a783, Descriptor: http://192.168.1.129:37904/MediaRenderer1.xml, Root: true' expires in seconds: 1703
02-26 17:01:13.800: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:0f7f4900-0004-1000-b5d8-c4731e31d709, Descriptor: http://192.168.1.128:7676/smp_14_, Root: true' expires in seconds: 1703
02-26 17:01:13.804: D/Registry(6594): Executing pending operations: 0
02-26 17:01:16.379: D/MulticastReceiver(6594): UDP datagram received from: 192.168.1.131:4502 on local interface: wlan0 and address: 192.168.1.132
02-26 17:01:16.379: D/DatagramProcessor(6594): ===================================== DATAGRAM BEGIN ============================================
02-26 17:01:16.390: D/DatagramProcessor(6594): M-SEARCH * HTTP/1.1
02-26 17:01:16.390: D/DatagramProcessor(6594): ST: upnp:rootdevice
02-26 17:01:16.390: D/DatagramProcessor(6594): MX: 3
02-26 17:01:16.390: D/DatagramProcessor(6594): MAN: "ssdp:discover"
02-26 17:01:16.390: D/DatagramProcessor(6594): HOST: 239.255.255.250:1900
02-26 17:01:16.390: D/DatagramProcessor(6594):
02-26 17:01:16.390: D/DatagramProcessor(6594): ����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������
02-26 17:01:16.394: D/DatagramProcessor(6594): -===================================== DATAGRAM END =============================================
02-26 17:01:16.418: D/ProtocolFactory(6594): Creating protocol for incoming asynchronous: (IncomingDatagramMessage) M-SEARCH
02-26 17:01:16.422: D/AbstractActionExecutor(6594): Attempting to retrieve output argument values using accessor: 4
02-26 17:01:16.422: D/AbstractActionExecutor(6594): Calling acccessor method for: (ActionArgument, OUT) Result
02-26 17:01:16.425: D/AbstractActionExecutor(6594): Calling accessor to read output argument value: (GetterStateVariableAccessor) Method: public java.lang.String org.fourthline.cling.support.model.BrowseResult.getResult()
02-26 17:01:16.425: D/Router(6594): Received asynchronous message: (IncomingDatagramMessage) M-SEARCH
02-26 17:01:16.425: D/AbstractActionExecutor(6594): Calling acccessor method for: (ActionArgument, OUT) NumberReturned
02-26 17:01:16.425: D/UpnpHeaders(6594): Parsing all HTTP headers for known UPnP headers: 4
02-26 17:01:16.425: D/UpnpHeader(6594): Trying to parse 'MAN' with class: MANHeader
02-26 17:01:16.425: D/UpnpHeaders(6594): Adding parsed header: (MANHeader) 'ssdp:discover'
02-26 17:01:16.425: D/UpnpHeader(6594): Trying to parse 'MX' with class: MXHeader
02-26 17:01:16.425: D/UpnpHeaders(6594): Adding parsed header: (MXHeader) '3'
02-26 17:01:16.425: D/UpnpHeader(6594): Trying to parse 'HOST' with class: HostHeader
02-26 17:01:16.425: D/UpnpHeaders(6594): Adding parsed header: (HostHeader) '239.255.255.250:1900'
02-26 17:01:16.425: D/UpnpHeader(6594): Trying to parse 'ST' with class: STAllHeader
02-26 17:01:16.425: D/UpnpHeader(6594): Invalid header value for tested type: STAllHeader - Invalid ST header value (not ALL): upnp:rootdevice
02-26 17:01:16.425: D/UpnpHeader(6594): Trying to parse 'ST' with class: RootDeviceHeader
02-26 17:01:16.429: D/UpnpHeaders(6594): Adding parsed header: (RootDeviceHeader) 'upnp:rootdevice'
02-26 17:01:16.429: D/ReceivingSearch(6594): Sleeping 2401 milliseconds to avoid flooding with search responses
02-26 17:01:16.429: D/AbstractActionExecutor(6594): Calling accessor to read output argument value: (GetterStateVariableAccessor) Method: public org.fourthline.cling.model.types.UnsignedIntegerFourBytes org.fourthline.cling.support.model.BrowseResult.getCount()
02-26 17:01:16.429: D/AbstractActionExecutor(6594): Calling acccessor method for: (ActionArgument, OUT) TotalMatches
02-26 17:01:16.429: D/AbstractActionExecutor(6594): Calling accessor to read output argument value: (GetterStateVariableAccessor) Method: public org.fourthline.cling.model.types.UnsignedIntegerFourBytes org.fourthline.cling.support.model.BrowseResult.getTotalMatches()
02-26 17:01:16.429: D/AbstractActionExecutor(6594): Calling acccessor method for: (ActionArgument, OUT) UpdateID
02-26 17:01:16.429: D/AbstractActionExecutor(6594): Calling accessor to read output argument value: (GetterStateVariableAccessor) Method: public org.fourthline.cling.model.types.UnsignedIntegerFourBytes org.fourthline.cling.support.model.BrowseResult.getContainerUpdateID()
02-26 17:01:16.429: D/MethodActionExecutor(6594): Accessors returned Object[], setting output argument values: 4
02-26 17:01:16.433: D/AbstractActionExecutor(6594): Result of invocation is Object, setting single output argument value
02-26 17:01:16.433: D/AbstractActionExecutor(6594): Result of invocation is Object, setting single output argument value
02-26 17:01:16.433: D/AbstractActionExecutor(6594): Result of invocation is Object, setting single output argument value
02-26 17:01:16.433: D/AbstractActionExecutor(6594): Result of invocation is Object, setting single output argument value
02-26 17:01:16.433: D/DefaultServiceManager(6594): Releasing lock
02-26 17:01:16.433: D/ReceivingAction(6594): Writing body of response message
02-26 17:01:16.433: D/SOAPActionProcessor(6594): Writing body of (OutgoingActionResponseMessage) 200 OK for: (RemoteActionInvocation) (Action, Arguments: 10) Browse
02-26 17:01:16.433: D/SOAPActionProcessor(6594): Writing action response element: Browse
02-26 17:01:16.437: D/SOAPActionProcessor(6594): Writing action output argument: Result
02-26 17:01:16.437: D/SOAPActionProcessor(6594): Writing action output argument: NumberReturned
02-26 17:01:16.437: D/SOAPActionProcessor(6594): Writing action output argument: TotalMatches
02-26 17:01:16.437: D/SOAPActionProcessor(6594): Writing action output argument: UpdateID
02-26 17:01:16.445: D/SOAPActionProcessor(6594): ===================================== SOAP BODY BEGIN ============================================
02-26 17:01:16.449: D/SOAPActionProcessor(6594): <?xml version="1.0" encoding="utf-8" standalone="yes"?><s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><u:BrowseResponse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1"><Result><DIDL-Lite xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:sec="http://www.sec.co.kr/dlna"><container id="0" parentID="-1" childCount="3" restricted="true" searchable="false"><dc:title>Root</dc:title><dc:creator>System</dc:creator><upnp:writeStatus>NOT_WRITABLE</upnp:writeStatus><upnp:class>object.container</upnp:class></container></DIDL-Lite></Result><NumberReturned>1</NumberReturned><TotalMatches>1</TotalMatches><UpdateID>0</UpdateID></u:BrowseResponse></s:Body></s:Envelope>
02-26 17:01:16.449: D/SOAPActionProcessor(6594): -===================================== SOAP BODY END ============================================
02-26 17:01:16.449: D/ReceivingAction(6594): Returning finished response message: (OutgoingActionResponseMessage) 200 OK
02-26 17:01:16.449: D/UpnpStream(6594): Protocol returned response: (OutgoingActionResponseMessage) 200 OK
02-26 17:01:16.449: D/UpnpStream(6594): Preparing HTTP response message: (OutgoingActionResponseMessage) 200 OK
02-26 17:01:16.449: D/UpnpStream(6594): Sending HTTP response status: 200
02-26 17:01:16.449: D/UpnpStream(6594): Response message has body, writing bytes to stream...
02-26 17:01:16.449: D/UpnpStream(6594): Exception occurred during UPnP stream processing: java.io.IOException: Closed
02-26 17:01:16.453: D/UpnpStream(6594): Cause: java.io.IOException: Closed
02-26 17:01:16.453: D/UpnpStream(6594): java.io.IOException: Closed
02-26 17:01:16.453: D/UpnpStream(6594): at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:140)
02-26 17:01:16.453: D/UpnpStream(6594): at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:117)
02-26 17:01:16.453: D/UpnpStream(6594): at org.seamless.util.io.IO.write(IO.java:667)
02-26 17:01:16.453: D/UpnpStream(6594): at org.seamless.util.io.IO.writeBytes(IO.java:123)
02-26 17:01:16.453: D/UpnpStream(6594): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.writeResponseMessage(AsyncServletUpnpStream.java:248)
02-26 17:01:16.453: D/UpnpStream(6594): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.run(AsyncServletUpnpStream.java:102)
02-26 17:01:16.453: D/UpnpStream(6594): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
02-26 17:01:16.453: D/UpnpStream(6594): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
02-26 17:01:16.453: D/UpnpStream(6594): at java.lang.Thread.run(Thread.java:856)
02-26 17:01:16.453: D/UpnpStream(6594): Returning INTERNAL SERVER ERROR to client
02-26 17:01:16.453: W/pnpServiceConfiguration(6594): Thread terminated () abruptly with exception: java.lang.IllegalStateException: IDLE,initial
02-26 17:01:16.453: W/pnpServiceConfiguration(6594): Root cause: java.lang.IllegalStateException: IDLE,initial
02-26 17:01:16.453: W/dalvikvm(6594): threadid=33: thread exiting with uncaught exception (group=0x41105300)
02-26 17:01:16.457: E/AndroidRuntime(6594): FATAL EXCEPTION: cling-23
02-26 17:01:16.457: E/AndroidRuntime(6594): java.lang.IllegalStateException: IDLE,initial
02-26 17:01:16.457: E/AndroidRuntime(6594): at org.eclipse.jetty.server.AsyncContinuation.complete(AsyncContinuation.java:574)
02-26 17:01:16.457: E/AndroidRuntime(6594): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.complete(AsyncServletUpnpStream.java:87)
02-26 17:01:16.457: E/AndroidRuntime(6594): at org.fourthline.cling.transport.impl.AsyncServletUpnpStream.run(AsyncServletUpnpStream.java:123)
02-26 17:01:16.457: E/AndroidRuntime(6594): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
02-26 17:01:16.457: E/AndroidRuntime(6594): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
02-26 17:01:16.457: E/AndroidRuntime(6594): at java.lang.Thread.run(Thread.java:856)
02-26 17:01:16.804: D/Registry(6594): Maintaining registry...
02-26 17:01:16.808: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:1c002264-1dd2-11b2-93b5-a29a04d9a783, Descriptor: http://192.168.1.129:37904/MediaRenderer1.xml, Root: true' expires in seconds: 1700
02-26 17:01:16.808: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:0f7f4900-0004-1000-b5d8-c4731e31d709, Descriptor: http://192.168.1.128:7676/smp_14_, Root: true' expires in seconds: 1700
02-26 17:01:16.808: D/Registry(6594): Executing pending operations: 0
02-26 17:01:18.847: D/Router(6594): Trying to obtain lock with timeout milliseconds '15000': ReadLock
02-26 17:01:18.855: D/Router(6594): Acquired router lock: ReadLock
02-26 17:01:18.953: D/dalvikvm(6594): GC_FOR_ALLOC freed 1365K, 16% free 14640K/17287K, paused 68ms, total 70ms
02-26 17:01:18.976: D/Router(6594): Releasing router lock: ReadLock
02-26 17:01:18.976: D/ReceivingSearch(6594): Responding to root device search with advertisement messages for all local root devices
02-26 17:01:18.980: D/Router(6594): Trying to obtain lock with timeout milliseconds '15000': ReadLock
02-26 17:01:18.980: D/Router(6594): Acquired router lock: ReadLock
02-26 17:01:18.980: D/DatagramIO(6594): Sending message from address: 192.168.1.132/192.168.1.132:0
02-26 17:01:18.980: D/DatagramProcessor(6594): Writing message data for: (OutgoingSearchResponseRootDevice) 200 OK
02-26 17:01:18.980: D/DatagramProcessor(6594): ---------------------------------------------------------------------------------
02-26 17:01:18.980: D/DatagramProcessor(6594): HTTP/1.1 200 OK
02-26 17:01:18.980: D/DatagramProcessor(6594): Cache-control: max-age=1800
02-26 17:01:18.980: D/DatagramProcessor(6594): X-cling-iface-mac: 78:D6:F0:F1:A7:32
02-26 17:01:18.980: D/DatagramProcessor(6594): Usn: uuid:87b8db85-a086-43bd-bfd5-a339f822b2eb::upnp:rootdevice
02-26 17:01:18.980: D/DatagramProcessor(6594): Location: http://192.168.1.132:33981/upnp/dev/87b8db85-a086-43bd-bfd5-a339f822b2eb/desc
02-26 17:01:18.980: D/DatagramProcessor(6594): Server: Linux/3.0.31-g5894150 UPnP/1.0 Cling/2.0
02-26 17:01:18.980: D/DatagramProcessor(6594): Ext:
02-26 17:01:18.980: D/DatagramProcessor(6594): St: upnp:rootdevice
02-26 17:01:18.980: D/DatagramProcessor(6594): ---------------------------------------------------------------------------------
02-26 17:01:18.980: D/DatagramProcessor(6594): Writing new datagram packet with 318 bytes for: (OutgoingSearchResponseRootDevice) 200 OK
02-26 17:01:18.980: D/DatagramIO(6594): Sending UDP datagram packet to: /192.168.1.131:4502
02-26 17:01:18.980: D/DatagramIO(6594): Sending message from address: 192.168.1.132/192.168.1.132:0
02-26 17:01:18.984: D/Router(6594): Releasing router lock: ReadLock
02-26 17:01:19.812: D/Registry(6594): Maintaining registry...
02-26 17:01:19.816: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:1c002264-1dd2-11b2-93b5-a29a04d9a783, Descriptor: http://192.168.1.129:37904/MediaRenderer1.xml, Root: true' expires in seconds: 1697
02-26 17:01:19.828: D/Registry(6594): Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:0f7f4900-0004-1000-b5d8-c4731e31d709, Descriptor: http://192.168.1.128:7676/smp_14_, Root: true' expires in seconds: 1697
02-26 17:01:19.840: D/Registry(6594): Executing pending operations: 0
Reply | Threaded
Open this post in threaded view
|

Re: FATAL EXCEPTION: cling-11

Christian Bauer
Administrator
This last log trace shows a potential issue. I have no idea how this is related to your other problems, or if it's the same problem, or whatever. You have not provided enough information to reproduce anything.

So I made a guess and now hide this warning/error message, it seems to be simply the consequence of a dead client connection with Jetty's async servlet stuff.