Find the root cause of Java Bridge Bug

Having spent so long time on this bug and finally I found the root cause of this bug:http://bugzilla.gnome.org/show_bug.cgi?id=526700

At first, I tried to make orbit to output its log, but at-spi-registryd output too many logs and it is nearly unuseful for the investigation.

Later I wrote two simple test applications, one is the corba server: bonobo-echo-2 and the other is java test client. This can help me narrow the problem.

ORBit2 can output its log information also, but there are two kinds of log: orbit2 log and linc2 log. Until I enable the linc2 log (I don't know until I look at the source code), I could see the communication information to orbit2 server.

truss is a good tool which can help to see system call. truss -t open process name
snoop can get the tcp packets in the ethenet network.

About one year ago, Brian changed /etc/orbitrc as the requirement of Secure by Default. java access bridge didn't work any more since then. It would have been easy If we had notify Brian about this problem.