[jboss-jira] [JBoss JIRA] (WFLY-7748) JBoss does not return exception with stack trace if the service address is not localhost or loopback ip

[Khoa Tran (JIRA)]

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

Khoa Tran commented on WFLY-7748:
---------------------------------

Thank Tomaz, will try as advised.

Just wonder if this is documented, maybe its just me but I couldn't find document about it.

A little context, my GWT application  (client side) depends on the exception having stack trace, so that base on the stack trace information it can generate appropriate message. When moving to JBOSS 7, without knowing this setting, all the exception lost information, thus result in my application behave incorrectly

> JBoss does not return exception with stack trace if the service address is not localhost or loopback ip 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-7748
>                 URL: https://issues.jboss.org/browse/WFLY-7748
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 10.1.0.Final
>         Environment: Window OS: win 7
> JDK version: 1.8.0_112
>            Reporter: Khoa Tran
>            Priority: Critical
>         Attachments: Replication.docx, WebException.zip, standalone.xml
>
>
> For this JBOSS release 7.0.1.GA, exception return to client upon processing HTTP Request is not consistent. How the exception return surprisingly depends on the ipaddress (of the server).
> What I mean is:
> - Using 127.0.0.1 or localhost as part of address, exception is return fine, with proper stack trace
> - Using PC domain name, or lan ip adrress, the exception return is just "Internal Server Error", no stack trace - this look like JBoss error to me.
> Please view attach document for detail, also there is sample project and standalone xml included. 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)