2 Replies Latest reply on May 27, 2010 8:29 AM by Gerard COLLIN

    Jboss 4.2.3: Error messages when logging using jdk log

    Gerard COLLIN Newbie

      Hi,

      I'm using JAX-WS reference implementation for deploying Web Services under JBoss Community 4.2.3, with jdk 1.5

       

      Everything works fine, except for the following error messages at the start of JBoss:

       

      2010-05-27 12:08:11,768 ERROR [STDERR] May 27, 2010 12:08:11 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
      INFO: WSSERVLET12: JAX-WS context listener initializing
      2010-05-27 12:08:13,331 ERROR [STDERR] May 27, 2010 12:08:13 PM com.sun.xml.ws.server.MonitorBase createRoot
      INFO: Metro monitoring rootname successfully set to: null
      2010-05-27 12:08:13,424 ERROR [STDERR] May 27, 2010 12:08:13 PM com.sun.xml.ws.server.MonitorBase createRoot
      INFO: Metro monitoring rootname successfully set to: null
      2010-05-27 12:08:13,440 ERROR [STDERR] May 27, 2010 12:08:13 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
      INFO: WSSERVLET14: JAX-WS servlet initializing

       

      Looking at the code of om.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized (), I've seen that it's using Jdk logging mechanism to log the "context listener initializing" info.

       

      But under JBoss, this gets converted to a ERROR [STDERR] error message, and I would like to get rid of it, because the exploitation guys don't like to have false error messages.

       

      I didn't see any other information on this, so please can someone help ?

       

      Regards,

       

      GC.