[jboss-jira] [JBoss JIRA] (WFLY-4125) javax.ejb.NoSuchEJBException should not print a stacktrace on the server console

[Sande Gilda (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022934#comment-13022934 ] 

Sande Gilda commented on WFLY-4125:
-----------------------------------

This issue has also come up with stacktraces printed in the ejb-security-interceptors quickstart. It demonstrates how a secured EJB rejects unauthorized access. Again, it prints out something like the following, followed by a giant stacktrace. It would be nicer to just print the message. 

        javax.ejb.EJBAccessException: JBAS014502: Invocation on method: public abstract boolean org.jboss.as.quickstarts.ejb_security_interceptors.SecuredEJBRemote.roleTwoMethod() of bean: SecuredEJB is not allowed

See bug https://bugzilla.redhat.com/show_bug.cgi?id=1167640

>  javax.ejb.NoSuchEJBException should not print a stacktrace on the server console
> ---------------------------------------------------------------------------------
>
>                 Key: WFLY-4125
>                 URL: https://issues.jboss.org/browse/WFLY-4125
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>            Reporter: Sande Gilda
>            Assignee: David Lloyd
>
> See related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1167293
> The shopping-cart quickstart has a note in the README file that states: 
>     Note: You also see the following EJB Invocation failed and NoSuchEJBException messages in the server log. This is the expected result because method is annotated with @Remove. This means the next invocation after the shopping cart checkout fails because the container has destroyed the instance and it is no longer available.
> However, usually people see the stacktrace in the server and assume something is terribly wrong. (see https://bugzilla.redhat.com/show_bug.cgi?id=910868)
> I spoke with Brad Maxwell and David M Lloyd to see if there is a way to suppress the stacktrace and only print the exception message, but it is not possible. The stacktrace doesn't really provide any additional information, and since it's thrown, the caller has access to it.
> See related bug for JBoss EAP 6.4: https://bugzilla.redhat.com/show_bug.cgi?id=1167983
> David said: Looks like the place to make this change would be in org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.  Maybe a specific catch clause for exception types to not log?



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)