Geronimo
  1. Geronimo
  2. GERONIMO-3828

Provide jaxws-tools stack traces to the server.log

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.2, 2.1.1, 2.2
    • Fix Version/s: 2.0.3, 2.1.1, 2.2
    • Component/s: webservices, Wish List
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      Even with the logging level set to DEBUG, if jaxws-tools throws an Exception, it does not seem to show up in the server log or console output. This seems to be the case even if "-Dorg.apache.geronimo.jaxws.wsgen.fork=false" is set. Logging the output of wsgen is critical to debug issues with @WebService classes.

        Activity

        Cedric Hurst created issue -
        Jarek Gawor made changes -
        Field Original Value New Value
        Assignee Jarek Gawor [ gawor@mcs.anl.gov ]
        Jarek Gawor made changes -
        Affects Version/s 2.1.1 [ 12312941 ]
        Affects Version/s 2.2 [ 12312965 ]
        Affects Version/s 2.0.x [ 12312601 ]
        Hide
        Jarek Gawor added a comment -

        I modified the code so that when wsgen is forked the stdout/stderr of the process will be logged. In most cases when wsgen fails, the wsgen output will be logged as an error. Otherwise, the output is logged as a debug message. It is possible for wsgen to fail and not indicate so. In such cases debugging must be explicitly enabled to see the wsgen output. To enable debugging for wsgen add the following to server-log4j.properties file:

        log4j.logger.org.apache.geronimo.jaxws.builder=DEBUG

        The wsgen output will appear in the geronimo.log file.

        Committed the changes to trunk (revision 631679) and branches/2.1 (revision 631680).

        Show
        Jarek Gawor added a comment - I modified the code so that when wsgen is forked the stdout/stderr of the process will be logged. In most cases when wsgen fails, the wsgen output will be logged as an error. Otherwise, the output is logged as a debug message. It is possible for wsgen to fail and not indicate so. In such cases debugging must be explicitly enabled to see the wsgen output. To enable debugging for wsgen add the following to server-log4j.properties file: log4j.logger.org.apache.geronimo.jaxws.builder=DEBUG The wsgen output will appear in the geronimo.log file. Committed the changes to trunk (revision 631679) and branches/2.1 (revision 631680).
        Jarek Gawor made changes -
        Fix Version/s 2.2 [ 12312965 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 2.1.1 [ 12312941 ]
        Resolution Fixed [ 1 ]
        Hide
        Donald Woods added a comment -

        Merged into branches/2.0 as Rev634285

        Show
        Donald Woods added a comment - Merged into branches/2.0 as Rev634285
        Donald Woods made changes -
        Fix Version/s 2.0.x [ 12312601 ]
        Joe Bohn made changes -
        Fix Version/s 2.0.3 [ 12313315 ]
        Affects Version/s 2.0.2 [ 12312731 ]
        Affects Version/s 2.0.x [ 12312601 ]
        Fix Version/s 2.0.x [ 12312601 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        20d 26m 1 Jarek Gawor 27/Feb/08 19:10

          People

          • Assignee:
            Jarek Gawor
            Reporter:
            Cedric Hurst
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development