Stack traces mysteriously disappear from Exceptions

Question

I'm using Sun Java System Application Server Platform Edition 8.0.0_01 on Solaris 8 on a Sun-Fire machine. The problem is that some exceptions thrown in session beans make it to the presentation tier without their stack traces.
Here is a session bean method:
* @ejb.interface-method
public void generateException() throws SbankInternalException
try { System.exit(0); }
catch (Exception e) {
throw new SbankInternalException("Unexpected exception", e);
SbankInternalException is a simple wrapper on Exception:
public class SbankInternalException
extends Exception
public SbankInternalException() {}
public SbankInternalException(String message)
super(message);
public SbankInternalException(String message, Throwable cause)
super(message, cause);
public SbankInternalException(Throwable cause)
super(cause);
Here is the code that triggers the problem:
<h3>Exception testing:</h3>
<%
try {
maintenanceServices.generateException();
} catch (Exception E) {
Throwable e = (Throwable) E;
%>
<h3>Caught exception <%=E%></h3>
<pre>
<%
do {
%>CLASS: <%=e.getClass().getName()%>
MESSAGE: <%=e.getMessage()%><br><%
StackTraceElement se[] = e.getStackTrace();
if (se.length == 0) {
%> EMPTY STACK TRACE<br><br><%
} else {
for (int i = 0; i < se.length; i++) {
%> <%=se.toString()%><br><%
%> <br><br><%
e = e.getCause();
} while (e != null);
%>
</pre>
And here is what I get:
<h3>Exception testing:</h3>
     <h3>Caught exception sbank.services.SbankInternalException: Unexpected exception</h3>
     <pre>
CLASS: sbank.services.SbankInternalException
MESSAGE: Unexpected exception<br>
EMPTY STACK TRACE<br><br>
CLASS: java.security.AccessControlException
MESSAGE: access denied (java.lang.RuntimePermission exitVM)<br>
EMPTY STACK TRACE<br><br>
     </pre>
Server log does not contain any message about that.
This only seems to be the problem for exceptions declared in bean interface. When a RuntimeException is thrown in the bean, then it is properly logged to the server log (with strack trace), and I catch a nice RemoteException in the presentation layer, as expected (also with stack trace, though the top frame is somewhere in the demarshalling code of application server guts, so it's not very useful).
Is it my error, or a bug?
regards
Marcin

Answer 1

I'm not complaining that the exceptions declared to be thrown from session bean interface are not logged. AFAIR that is OK with the EJB spec.
I'm complaining that the stack traces are stripped from the exception on its way from the session bean to the client (presentation layer in this case).
I know that I could log the error in the session bean, that is just a workaround. I still would like to know why my exceptions are being broken? After all the whole point of exceptions is that they can be generated in one place, and investigated/displayed in another.
The only explanation I can think of that there is some silly optimization, that omits stack frames when serializing the exceptions, so that they propagate faster. If it is so, can I disable that?
Marcin