Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-2237

Exception message and StackTrace do not correlate

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Obsolete
    • Icon: Major Major
    • No Release
    • JBossAS-4.0.3RC2
    • Naming
    • None
    • 4.0.3RC2

      Since JBoss thrown/caught exceptions contain only cluttered messages, one must analyze the stacktrace itself, to give the enduser a feedback, it is able to understand.

      However, this becomes even hard, since completely wrong stacktraces are thrown. E.g.:
      11:35:47,456 [Thread-4] WARN (AppServerSettingsDialog.java:305) - Could not obtain connection to any of these urls: https://localhost:8443/invoker/JNDIFactory and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
      11:35:47,457 [Thread-4] DEBUG (AppServerSettingsDialog.java:307) - run
      javax.naming.CommunicationException: Could not obtain connection to any of these urls: https://localhost:8443/invoker/JNDIFactory and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server https:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server https:1099 [Root exception is java.net.UnknownHostException: https: https]]]
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1399)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
      at javax.naming.InitialContext.lookup(InitialContext.java:351)
      at com.ehsbe.commons.gui.AppServerSettingsDialog$ServerTestThread.run(AppServerSettingsDialog.java:280)
      Caused by: javax.naming.CommunicationException: Failed to connect to server https:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server https:1099 [Root exception is java.net.UnknownHostException: https: https]]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:254)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1370)
      ... 4 more
      Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server https:1099 [Root exception is java.net.UnknownHostException: https: https]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:228)
      ... 5 more
      Caused by: java.net.UnknownHostException: https: https
      at java.net.InetAddress.getAllByName0(InetAddress.java:1128)
      at java.net.InetAddress.getAllByName0(InetAddress.java:1098)
      at java.net.InetAddress.getAllByName(InetAddress.java:1061)
      at java.net.InetAddress.getByName(InetAddress.java:958)
      at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:61)
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:224)
      ... 5 more

      Either correct stack traces should be returned, or localized messages, which a normal enduser (i.e. not a developer) is able to understand...

              Unassigned Unassigned
              elkner Jens Elkner (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: