Skip to main content

Writing to WebLogic Server Logs

For J2EE developers who are not familiar with WebLogic, you can write debug and error messages to the server logs very easily.

When to Write to WebLogic Server Logs

Any debug, warning or error messages relating to the server or infrastructure. For example, information or errors with the following:
  • Connecting to other components/systems.
  • Database access, setup, etc.
  • LDAP
  • HTTP request/response
  • Deployment dependencies
Do not write to the server logs if you are handling the following:
  • Unexpected user input
  • Application debug/info/warning messages. (Write these to your own application logs.)

How to do it

Writing to the WebLogic server logs is simple. Just use LoggingHelper to get a Logger object and print messages to your heart's content. Here is some example code:

Put this in the class declaration:

private static java.util.logging.Logger serverLogger = LoggingHelper.getServerLogger();

Use these throughout your code:

serverLogger.log(Level.INFO, "Hello World!");
serverLogger.warning("This is a warning.");
serverLogger.severe("Something bad has happened!");

If you need more information about these classes, try these links:

BEA provides quite a lot of information about logging here:


Popular posts from this blog

BAD_CERTIFICATE - A corrupt or unuseable certificate...

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators.
In wls_utc, when trying to test a webservice using SSL, the following error message is received: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
If SSL debugging is enabled, the following error also appears in the logs: ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' <1254822672320>>
verification failed because RSA key public exponent [3] is too small
The certificate encryption is of a weaker strength than expected by newer versions of Java.
Add the flag "" to the server startup parameters.


Connection refused: No available router to destination

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators.

The following exception occurs in WebLogic server logs. Most likely to occur during WebLogic server start-up, but similar exceptions may occur at other times. t3://myserver:8000: Destination unreachable; nested exception is: Connection refused: connect; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException( at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException( at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext( at weblogic.jndi.Environment.getContext( at weblogic.jndi.Environment.getContext(
This message (Connection refused: connect; No available router to destination) is a kind of "catch…

BEASVC.EXE - WebLogic as a Windows Service

I remember the first time I had to work out why WebLogic wouldn't run as a service. It was a frustrating experience. There were no error messages. No Windows error dialog. No console output.

How do you troubleshoot something like this??!!

This short article will show you. For simplicity I'll talk about the node manager, but the same principles apply for running an admin or managed server as a service.

First Steps

First, you still have your server logs. Sure the console output is better, but it's a starting point. Check this log for errors and especially take note of the start up variables such as PATH and CLASSPATH. If the server log isn't being created, that tells you WebLogic probably isn't even being started. (Check that you have a license file if you haven't already.)

Ok, so the logs were no help. The next step is to look at how the service is trying to start WebLogic.

When you install WebLogic as a service, you're really setting up beasvc.exe as the service.…