[java] dbus disconnecting / threaded use of dbus

Colby M White colby.white at utexas.edu
Tue Sep 4 10:38:07 PDT 2012


If it was the body of the message, then why would the same body be
malformed at some times and not others?

For the sake of having a full message, here's another excerpt from the
logging. I made sure to run a test that had a substantial map in its body:

[org.freedesktop.dbus.AbstractConnection$_sender.run()] Got message:
DataChanged(0,4) { Path=>/test/two, Interface=>dbus.topics.Topic,
Member=>DataChanged, Signature=>a{sv} } { {Name=[Downstairs],
Active=[COOLING], Ambient=[85], Local=[true], Setpoint=[75],
Abandoned=[false], Fan=[AUTO], Id=[two], Mode=[COOLING]} }
[org.freedesktop.dbus.Message.append()] Appending sig: a{sv} data:
[{Name=[Downstairs], Active=[COOLING], Ambient=[85], Local=[true],
Setpoint=[75], Abandoned=[false], Fan=[AUTO], Id=[two], Mode=[COOLING]}]
[org.freedesktop.dbus.MessageWriter.writeMessage()] <= DataChanged(0,4) {
Path=>/test/two, Interface=>dbus.topics.Topic, Member=>DataChanged,
Signature=>a{sv} } { {Name=[Downstairs], Active=[COOLING], Ambient=[85],
Local=[true], Setpoint=[75], Abandoned=[false], Fan=[AUTO], Id=[two],
Mode=[COOLING]} }
[org.freedesktop.dbus.MessageWriter.writeMessage()] Writing all 102 buffers
simultaneously to Unix Socket
[org.freedesktop.dbus.DBusConnection.disconnect()] Disconnecting
DBusConnection

-- 
Colby M. White



On Tue, Sep 4, 2012 at 12:08 PM, Will Thompson <
will.thompson at collabora.co.uk> wrote:

> [re-CCing the list so others can see this wasn't the issue.]
>
>
> On 04/09/12 13:02, Colby M White wrote:
>
>> My objectpaths seem valid. They are alphanumeric strings. In my test
>> example, I'm just using words. getId() returns something like "one" or
>> "two" every time. Here is that line of logging done again with the path
>> intact:
>>
>> [org.freedesktop.dbus.**AbstractConnection$_sender.**run()] Got message:
>> DataChanged(0,365) { Path=>/seventeen, Interface=>dbus.topics.Topic,
>>
>> Member=>DataChanged, Signature=>a{sv} } { {Name=[seventeen],// the rest
>> of the map//} }
>>
>
> Okay, then it's not the path. But maybe it's some invalid data in the body
> of the message (which is elided above).
>
> It might be useful to compare a signal which is successfully emitted with
> one which causes the disconnection.
>
> (Or it could be some other bug totally unrelated to the body of the
> messages!)
>
> --
> Will
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20120904/ffab69e7/attachment-0001.html>


More information about the dbus mailing list