[ http://jira.jboss.com/jira/browse/JBSEAM-3052?page=all ] Peter Maedel updated JBSEAM-3052: --------------------------------- Description: Lots of people have been dealing with the issue of overwritten exceptions: http://www.seamframework.org/Community/ConnectionProblem http://www.seamframework.org/Community/TransactionIsNotActiveWithCreateAn... Although in some cases this behaviour is part of EJB specification (EJB Container overwriting Exception) I am unsure if there isnt a possibility within Seam to print exceptions when they occure rather than have them overwritten with useless junk (cannot open connection, transaction is abort_only) later on. If you want to reproduce try opening a page that references a bean with this @create method: @Create public void iCrash(){ new File("nonExistentDirectory").listFiles(); } Subsequent calls which involve Transactions (either in @create method or referenced beans) will result in the obscure "Transaction is abort_only" exception, leaving no trace which could lead to the actual cause of the failure. Honestly this behaviour has been a horrible waste of time so far! was: Lots of people have been dealing with the issue of overwritten exceptions: http://www.seamframework.org/Community/ConnectionProblem http://www.seamframework.org/Community/TransactionIsNotActiveWithCreateAn... Although in some cases this behaviour is part of EJB specification (EJB Container overwriting Exception) I am unsure if there isnt a possibility within Seam to print exceptions when they occure rather than have them overwritten with useless junk (cannot open connection, transaction is abort_only) later on. If you want to reproduce try opening a page that references a bean with this @create method: @Create public void iCrash(){ new File("nonExistentDirectory").listFiles(); } Honestly this behaviour has been a horrible waste of time so far! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3052?page=comments#action_12414840 ] Pete Muir commented on JBSEAM-3052: ----------------------------------- Most of the problem here is that jsf swallows exceptions in certain places. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3052?page=comments#action_12414845 ] Marvin Monroe commented on JBSEAM-3052: --------------------------------------- Yes, the lifecycle is the doom of all RuntimeExceptions... But Seam should not look away and tell us what went wrong. I think some interceptor or an extension to an existing one could be used to give at least a notification about an uncaught runtime exception. In a second step it could be made configurable by the seam.properties to print out more / less / nothing. Maybe one of the Seam committers knows a good place for such an output... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3052?page=comments#action_12415036 ] Peter Maedel commented on JBSEAM-3052: -------------------------------------- I just dealt with another of these Exceptions which real cause was a null pointer. Anyway I was able to determine the location of the exception being swallowed: RollbackInterceptor : 41 package org.jboss.seam.transaction; /** * Automatically sets the current transaction to rollback * only when an exception is thrown. * * @author Gavin King */ @Interceptor(stateless=true) public class RollbackInterceptor extends AbstractInterceptor { private static final long serialVersionUID = 5551801508325093417L; @AroundInvoke public Object aroundInvoke(InvocationContext invocation) throws Exception { try { return invocation.proceed(); } catch (Exception e) { if ( isRollbackRequired(e) ) { try { Transaction.instance().setRollbackOnly(); } catch (Exception te) {} //swallow } throw e; } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3052?page=comments#action_12415047 ] Peter Maedel commented on JBSEAM-3052: -------------------------------------- Well turns out this is not the right line after all. the exception getting swallowed is only the one which just got produced. Anyway I am able to see that Exception e is a NullPointer at this Time. So Seams Intereceptors do know about what went wrong (though stacktrace seems to be missing) next step you end up in MethodContextInterceptor:46 which is a finally block... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3052?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-3052: ----------------------------------- What was the swallowed cause? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3052?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-3052: ----------------------------------- If you can somehow reduce this to a simple example I can use to reproduce then I'll happily take a look as it sounds like something is going wrong, but I can't at initially see the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3052?page=com.atlassian.jira.pl... ] Pete Muir closed JBSEAM-3052. ----------------------------- Resolution: Rejected Assignee: Pete Muir Thanks. Yes, this is a known issue with facelets :( -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira