I essentially asked the same question in May. In my case, I observed with thrift 0.7 and 0.8 that the Java and C++ servers were different. The C++ server would toss it back as TApplicationException, while the Java server does not.
http://mail-archives.apache.org/mod_mbox/thrift-user/201205.mbox/browser No helpful replies. Since you say it works correctly in 0.6, apparently there was a regression moving to 0.7. I'm not a thrift developer, so I never pursued fixing it. Instead, I jumped through a lot of hoops in my server code to catch it and rethrow it myself. I hope it gets fixed. -craig ---------------------------------------- > Date: Wed, 25 Jul 2012 14:38:20 -0400 > Subject: Not seeing TApplicationException in 0.8.0 > From: [email protected] > To: [email protected] > > I am an Accumulo developer. We have been using thrift for many years, > with few issues. We recently switched Accumulo trunk from thrift > 0.6.1 to 0.8.0. Sever and client are java. Since switching to 0.8.0 > I am no longer seeing TApplicationExceptions on the client side when > an exception occurs on the server [1]. > > Looking into this, the Processor code generated by 0.6 catches > Throwable and returns TApplicationException to the client. The code > generated by 0.8 does not seem to do this. I am wondernig if this was > an intentional change or we are doing something wrong? > > Keith > > [1] : https://issues.apache.org/jira/browse/ACCUMULO-701
