code: public final void setLogWriter(final PrintWriter out) throws ResourceException {
          // removed content of this method.  This method is typically called by J2c.  J2c had some special
          // logic in their code not to call this method on the RRA since RRA seperates Resource Adapter logging/tracing
          // and database backend logging/tracing .  However, J2c changed their code and removed
          // special logic and started calling it indiscriminately on al resources adapters. That meant that
          // if the RRA trace is on, the database trace is on as well which is not a desired behavior.
          //  Therefore, we am making this method a no-op.
          // normal users won't go through this leg of code when setting the logwriter on their datasource.
          if (TraceComponent.isAnyTracingEnabled() && tc.isDebugEnabled()) 
              Tr.debug(this, tc, "setLogWriter on the mcf is a no-op when calling this method");
      }
docs: Set the log writer for this ManagedConnectionFactory instance.
  <p>
  The log writer is a character output stream to which all logging and tracing
  messages for this ManagedConnectionfactory instance will be printed.
  <p>
  ApplicationServer manages the association of output stream with the
  ManagedConnectionFactory. When a ManagedConnectionFactory object is created the
  log writer is initially null, in other words, logging is disabled. Once a log
  writer is associated with a ManagedConnectionFactory, logging and tracing for
  ManagedConnectionFactory instance is enabled.
  <p>
  The ManagedConnection instances created by ManagedConnectionFactory "inherits"
  the log writer, which can be overridden by ApplicationServer using
  ManagedConnection.setLogWriter to set ManagedConnection specific logging and
  tracing.
  
  @param PrintWriter out - an out stream for error logging and tracing
  @exception ResourceException - Possible causes for this exception are:
  1) setLogWriter on the physical datasource fails