/*
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
*
* under the terms of the GNU General Public License version 2 only, as
* published by the Free Software Foundation.
*
* This code is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
* version 2 for more details (a copy is included in the LICENSE file that
* accompanied this code).
*
* You should have received a copy of the GNU General Public License version
* 2 along with this work; if not, write to the Free Software Foundation,
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
*
* Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
* or visit www.oracle.com if you need additional information or have any
* questions.
*/
/* @test
* @bug 6409194
* @summary There should be no console output caused by the RMI
* implementation's logging, except as explicitly configured in the
* logging properties file, if none of the legacy sun.rmi.*.logLevel
* system properties are set.
*
* @author Peter Jones
*
* @library ../../../../../java/rmi/testlibrary
* @build TestLibrary JavaVM
*/
public class NoConsoleOutput {
/*
* Exdecute a subprocess VM that does a bunch of RMI activity
* with a logging configuration file that does not specify a
* ConsoleHandler and with no legacy sun.rmi.*.logLevel system
* properties set.
*/
// We instantiate a JavaVM that should not produce any console output
// (neither on standard output, nor on standard err streams).
"-Djava.util.logging.config.file=" + loggingPropertiesFile,
/*
* Verify that the subprocess had no System.out or System.err
* output.
*/
throw new Error("TEST FAILED: unexpected subprocess output");
}
}
public static class DoRMIStuff {
}
FooImpl() { }
}
}
}
}