Logging to weblogic.log

hi
i need couple of clarifications with regard to implementation of logging with
weblogic.
a) Is logging implemented using JMS? ( Is logging asynchronous?)
b) I am wondering if i can use logging api into some helper classes that wouldn't
be run in weblogic server. If weblogic server is a pre-requisite, then i will
not be able to use this logging api in these classes.
Thanks
Rob Woollen <[email protected]> wrote:
From server-side code (ie servlets or EJB). do
LogServiceDef log = T3Services.getT3Services().log();
to get the log, and then you can use log.inform(), log.debug, or
log.error as appropriate.
See
http://www.weblogic.com/docs45/classdocs/weblogic.common.LogServicesDef.html
-- Rob
Rob Woollen
Software Engineer
BEA WebLogic
[email protected]
Vinny Carpenter wrote:
Hi there. I have a cluster of WebLogic 4.5.1 servers running under
Solaris 2.6. My application consists of two EJB's and a couple of
servlets as front end. As part of the application logging process,I
output certain text using System.out.println and System.err.printlnthat
are typically displayed on the console.
How can I redirect those messages to the machine's weblogic.log file??
Is there a logging mechanism that will allow me to do that?? thanks
--Vinny

Similar Messages

Disabling logging to weblogic.log during startup of WLS

Hello,
Does anybody know how to disable logging to the weblogic.log file during startup
of WLS (v5.1.0).
Specifically I would like to hide parameters such as username and password that
show up as clear text for example when a database pool is created.
Thanks,
Murtaza.

Hi under WLS5.1.0, you can not do it.
thanks
Yu
Murtaza Sonaseth <[email protected]> wrote in message
news:3b5c729e$[email protected]..
>
Hello,
Does anybody know how to disable logging to the weblogic.log file duringstartup
of WLS (v5.1.0).
Specifically I would like to hide parameters such as username and passwordthat
show up as clear text for example when a database pool is created.
Thanks,
Murtaza.

Rolling of access.log and weblogic.log

I could successfully set parameters for rolling of the above log files. But I could see that the resultant file is being named as access.log0001, access.log0002. Similarly, weblogic.log0001 etc...But I want to name the backup files as access.logMMDDYYYY. What parameter do I set to make this happen?

i am pasting the entries below which i see in the log( access_log ) . I don't see DEBUG in them.
<AGENT_IP_ADDRESS> - - [29/Jun/2007:09:48:23 -0400] "GET /em/upload?ACTION=HEARTBEAT&EMD
_URL=https%3a%2f%2flph010%2egep%2ege%2ecom%3a3872%2femd%2fmain%2f&HEARTBEAT_TI
ME=2007-06-29+09%3a40%3a09&OUTSTANDING_SEVS=FALSE&EMD_UPTIME=2007-06-18+10%3a20%
3a23&OLDEST_COLL_TIME=2007-06-29+09%3a40%3a09&INSTALL_TYPE=agent&X-ORCL-EMOV=4%2
e0%2e0&X-ORCL-EMCV=10%2e2%2e0%2e1%2e0&X-ORCL-EMSV=10%2e2%2e0%2e1%2e0 HTTP/1.1" 2
00 5
<AGENT_IP_ADDRESS>- - [29/Jun/2007:09:48:23 -0400] "GET /em/upload?ACTION=HEARTBEAT&EM
D_URL=https%3a%2f%2fprdes%2eeur%2egep%2ege%2ecom%3a3872%2femd%2fmain%2f&HE
ARTBEAT_TIME=2007-06-29+15%3a48%3a23&OUTSTANDING_SEVS=FALSE&EMD_UPTIME=2007-06-1
8+18%3a27%3a33&OLDEST_COLL_TIME=2007-06-29+15%3a48%3a23&INSTALL_TYPE=agent&X-ORC
L-EMOV=4%2e0%2e0&X-ORCL-EMCV=10%2e2%2e0%2e1%2e0&X-ORCL-EMSV=10%2e2%2e0%2e1%2e0 H
TTP/1.1" 200 5
<AGENT_IP_ADDRESS> - - [29/Jun/2007:09:48:24 -0400] "GET /em/upload?ACTION=HEARTBEAT&E
MD_URL=https%3a%2f%2fug038%2egep%2ege%2ecom%3a3872%2femd%2fmain%2f&HEARTBEAT_
TIME=2007-06-29+22%3a19%3a35&OUTSTANDING_SEVS=FALSE&EMD_UPTIME=2007-06-18+18%3a3
7%3a03&OLDEST_COLL_TIME=2007-06-29+22%3a19%3a35&INSTALL_TYPE=agent&X-ORCL-EMOV=4
%2e0%2e0&X-ORCL-EMCV=10%2e2%2e0%2e1%2e0&X-ORCL-EMSV=10%2e2%2e0%2e1%2e0 HTTP/1.1"
200 5

Weblogic.log error levels

I am trying to find some more information on the different error levels that are logged to weblogic.log. Does anyone know if the levels are described anywhere?

Or see weblogic.logging.Severities @
http://e-docs/wls/docs60/javadocs/index.html
Brad Stone <[email protected]> wrote in message
news:[email protected]...
WebLogic uses the following severities, in order of criticality:
Emergency The server is in an unusable state. This should only be used to
designate severe system failures or panics.
Alert A particular service is in an unusable state. Other parts of the
system continue to function. Automatic recovery is not possible and the
immediate attention of the administrator is required to resolve theproblem.
>
Critical A system/service level error has occurred. The system is ableto
recover, perhaps with a momentary loss or permanent degradation ofservice.
>
Notice A particularly important warning or informational message.
Messages, such as notification of successful recovery from a failure,which
is of particular importance to an administrator monitoring the server.
Error A user level error has occurred. The system is able to handle the
error with no interruption and limited degradation in service. Make this
severity less 'severe' than NOTICE.
Warning A warning message. A suspicious operation or configuration which
doesn't affect the normal operation of the server.
Informational An informational message. Used for the logging of normal
operations for later examination.
Debug A debug message. Should be output only when the server isconfigured
in a debug mode. May contain detailed information about operations or the
state of the server.
"Beth" <[email protected]> wrote in message
news:[email protected]...
I never found anything in the documentation. But if you are using
LogOutputStream, there is the following:
- emergency
- alert
- critical
- error
- notice
- warning
- info
- debug
All take parameters of either just a String or a String and Throwable.
I don't know of a way to tell Weblogic just to log certain levels andignore
others so when you are done debugging you don't log any of the debug
messages to the log file.
This can be found by doing a
javap weblogic.logging.LogOutputStream
Hope this is what you are looking for.
"Jennifer Edwards" <[email protected]> wrote in message
news:[email protected]...
I am trying to find some more information on the different error
levels
that are logged to weblogic.log. Does anyone know if the levels are
described anywhere?

WebLogic logging services, SMTPHandler project

I wrote an SMTPHandler for java.util.logging
The SMTPHandler is similar to Log4j's SMTPAppender.
The SMTPHandler code is open source (Apache Public License)
If you are using Weblogic's Logging Services, I'd like to get feedback
from you.
I'd like to know if the SMTPHandler works for you in your
Weblogic 8.1 environment.
http://smtphandler.sourceforge.net/
http://edocs.bea.com/wls/docs81/logging/

Can you debug print the LogFactory.getFactory().getClass().getName() to stdout and see what class is being initialized as the LogFactory? You can try to set the commons logging property on the command line of the server with the -Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl and see if this helps. When Commons Logging is initialized with the WebLogic Commons Log factory implementation you should see Commons log messages being directed to the Server logs.

Overhead in weblogic logging

Does anyone have an info on the performance overhead of logging within
weblogic (6.1 sp2). There doesn't seem to be a way to turn down the
logging to weblogic.log from info to something like error or warning
level. I thought the StdoutSeverityLevel parameter would do that but it
only controls what is written to standard out not the weblogic.log.
Also, should the access log be enabled in production systems? Since it
writes a line to the log for every http hit, I was wondering what kind
of performance overhead that might make.
Kirk

FYI: The LogToStdOut option only applies to the console output, not the
weblogic.log file.
Nils
Pamal wrote:
>
Hi,
You can turn off complete logging by unchecking the Log to Stdout in WebLogic
administration console. Or the same can be achieved by giving the following in
config.xml
<WebServer DefaultWebApp=""
LogFileName="./config/petstore/logs/access.log"
LoggingEnabled="false" Name=""/>
You can also set the level of logging to Info, Debug etc
Regards,
Pamal
Rob Woollen <[email protected]> wrote:
I don't believe there's any current way to limit what gets written to
the
weblogic.log.
Writes to the access.log are buffered internally in the server so their
performance impact shouldn't be too big.
FWIW, I'd recommend that you run performance tests on your application
first and
then consider turning off logging only if it has a significant impact.
-- Rob
Kirk Everett wrote:
I totally agree and was only thinking about doing this in a productionenv. I
just wanted to know if you could (or should) turn off the access.logand the
weblogic.log. Is there even a way to turn down what gets put in the
weblogic.log?
Kirk
Cameron Purdy wrote:
Logging can be expensive, but only consider this once you have a
stable
application. Usually the application-level (not server-level) loggingis the
prime culprit, and you can reduce this with clever use of the deletekey in
source code files. You can also redirect stdout and stderr to nuland you
can turn off logging options once you are sure that things are stable.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you shouldbe!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Kirk Everett" <[email protected]> wrote in message
news:[email protected]...
Does anyone have an info on the performance overhead of logging
within
weblogic (6.1 sp2). There doesn't seem to be a way to turn downthe
logging to weblogic.log from info to something like error or warning
level. I thought the StdoutSeverityLevel parameter would do thatbut it
only controls what is written to standard out not the weblogic.log.
Also, should the access log be enabled in production systems? Sinceit
writes a line to the log for every http hit, I was wondering whatkind
of performance overhead that might make.
Kirk
============================
[email protected]

Cluster & Weblogic logs

Hi.,
          I have set up a weblogic cluster running from a shared disk. Currently both
          servers create their log files (Weblogic.log) in their directories on the
          shared disk. I would like the log to be on the local drive. When I try and
          change the file location with a fully qualified directory and filename,
          instead of creating the logfile on the local drive as expected, for some
          reason the fully qualified path is appended to the cluster directory on the
          shared disk.
          Is this a bug ?
          Eran


We ran into a similar problem and solved it by making the per-server
          directories underneath the cluster home directory symlinks to the local
          disk, rather than actual directories on the shared filesystem.
          So if your cluster directory is /cluster:
          /cluster
          /cluster/server1 -> /var/log
          /cluster/server2 -> /var/log
          /cluster/server3 -> /var/log
          The symlinks get resolved relative to the NFS client they're on - so each
          server ends up writing its logs to local disk at /var/log. The drawback is
          that your per-server properties files (if any) need to be on the local
          disks, rather than on the shared filesystem. But you could probably get
          around this by linking from /var/log back into the shared filesystem (not
          sure...we don't have per-server props files).
          Ideally I'd rather be able to just give the logfile a fully-qualified
          pathname rather than this weird symlink stuff, but this seems to work...
          Mike Benham <[email protected]> wrote in message
          news:[email protected]...
          >
          > Yes this is a bug that has been identified. We should accept both
          > fully qualified and relative path names. It should be fixed in the next
          > maintenance release, but I suppose you could hack functionality by using
          > relative pathnames until then:
          > "../../../../dir/outside/of/weblogic/install" =)
          >
          > - Mike
          >
          >
          >
          > Jean-François ESPERET wrote:
          > >
          > > Eran Shtiegman a écrit :
          > >
          > > > Hi.,
          > > >
          > > > I have set up a weblogic cluster running from a shared disk.
          Currently both
          > > > servers create their log files (Weblogic.log) in their directories on
          the
          > > > shared disk. I would like the log to be on the local drive. When I
          try and
          > > > change the file location with a fully qualified directory and
          filename,
          > > > instead of creating the logfile on the local drive as expected, for
          some
          > > > reason the fully qualified path is appended to the cluster directory
          on the
          > > > shared disk.
          > > >
          > > > Is this a bug ?
          > > >
          > > > Eran
          > >
          > > I've got the same problem and it seems to be a bug and I'll tell you why
          I think
          > > so:
          > > we're running Weblogic under Solaris 2.6 Sparc and when we put a fully
          qualified
          > > directory and filename (unix), it creates a directory starting with 'c:'
          . I
          > > mean it creates a MS Windows like directory into an Unix filesystem.

How to write to weblogic.log from JSP ?

It is possible to write some messages to weblogic.log from JSP?


Use weblogic.logging.LogOutputStream class to log messages into
          weblogic.log file.
          javap on weblogic.logging.LogOutputStream
          for e.g
          <%@ page import="weblogic.logging.*" %>
          <%
          LogOutputStream los = new LogOutputStream("TEST");
          los.error("Writing into Log file");
          %>
          Hope this helps.
          --kumar allamraju
          Mikhail Ershov wrote:
          > It is possible to write some messages to weblogic.log from JSP?

Error in weblogic.log using weblogic 6.1

I have this error in my weblogic.log file. I do not know the reason for the
error. What is the error about?
####<Oct 7, 2002 1:23:34 PM PDT> <Error> <Management> <hewlett-yf9yyzb>
<myserver> <ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'>
<system> <> <140001> <Error getting attribute EJBName.MethodName on MBean
mydomain:Application=test,AssemblyDescriptor=AssemblyDescriptor-4,ContainerT
ransaction=ContainerTransaction-4,EJBComponent=sempire_bc,EJBDescriptor=EJBD
escriptor-4,EJBJar=EJBJar-9,Location=myserver,Name=Method-12,Type=Method.
Method: null>
javax.management.AttributeNotFoundException: EJBName.MethodName
at
weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBean
Impl.java:1643)
at
weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
java:502)
at
weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
java:477)
at
com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:118
3)
at
com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:115
3)
at
weblogic.management.internal.MBeanProxy.getOneAttribute(MBeanProxy.java:283)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:199)
at $Proxy77.getAttribute(Unknown Source)
at
weblogic.management.console.utils.MBeans.getDisplayNameFor(MBeans.java:705)
at
weblogic.management.console.utils.ConsoleComparator.compare(ConsoleComparato
r.java:83)
at java.util.Arrays.mergeSort(Arrays.java:1176)
at java.util.Arrays.sort(Arrays.java:1123)
at java.util.Collections.sort(Collections.java:116)
at weblogic.management.console.utils.MBeans.sort(MBeans.java:1101)
at
weblogic.management.console.tags.DeclareBeanSetTag.doStartTag(DeclareBeanSet
Tag.java:96)
at
weblogic.management.console.webapp._ejb._ejb20.__nav._jspService(__nav.java:
4606)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:482)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:308)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:116)
at
weblogic.management.console.webapp._ejb.__nav._jspService(__nav.java:177)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:242)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServl
et.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2546)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Ronak Parekh

It looks like an error/bug in the deployment descriptor editor in the
console.
-- Rob
Ronak Parekh wrote:
I have this error in my weblogic.log file. I do not know the reason for the
error. What is the error about?
####<Oct 7, 2002 1:23:34 PM PDT> <Error> <Management> <hewlett-yf9yyzb>
<myserver> <ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'>
<system> <> <140001> <Error getting attribute EJBName.MethodName on MBean
mydomain:Application=test,AssemblyDescriptor=AssemblyDescriptor-4,ContainerT
ransaction=ContainerTransaction-4,EJBComponent=sempire_bc,EJBDescriptor=EJBD
escriptor-4,EJBJar=EJBJar-9,Location=myserver,Name=Method-12,Type=Method.
Method: null>
javax.management.AttributeNotFoundException: EJBName.MethodName
at
weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBean
Impl.java:1643)
at
weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
java:502)
at
weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.
java:477)
at
com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:118
3)
at
com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:115
3)
at
weblogic.management.internal.MBeanProxy.getOneAttribute(MBeanProxy.java:283)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:199)
at $Proxy77.getAttribute(Unknown Source)
at
weblogic.management.console.utils.MBeans.getDisplayNameFor(MBeans.java:705)
at
weblogic.management.console.utils.ConsoleComparator.compare(ConsoleComparato
r.java:83)
at java.util.Arrays.mergeSort(Arrays.java:1176)
at java.util.Arrays.sort(Arrays.java:1123)
at java.util.Collections.sort(Collections.java:116)
at weblogic.management.console.utils.MBeans.sort(MBeans.java:1101)
at
weblogic.management.console.tags.DeclareBeanSetTag.doStartTag(DeclareBeanSet
Tag.java:96)
at
weblogic.management.console.webapp._ejb._ejb20.__nav._jspService(__nav.java:
4606)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:482)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:308)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:116)
at
weblogic.management.console.webapp._ejb.__nav._jspService(__nav.java:177)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
l.java:242)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServl
et.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2546)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Ronak Parekh

Providing developers with access to WebLogic logs

Hi all,
I keep getting asked by developers for access to WebLogic logs in restricted test environments. But due to security policies, I can't just create an account for them. In one of my previous roles we just gave developers access to a WeLogic monitor account (read-only), but I find the WebLogic admin console is not user friendly for viewing logs.
To overcome this, I created a really simple WebLogic app that lets the developers access all logs files on the managed servers.
I've blogged a quick how-to here for anyone interested in doing the same: [http://connectionserver.blogspot.com/2009/05/listing-directories-simple-weblogic.html|http://connectionserver.blogspot.com/2009/05/listing-directories-simple-weblogic.html]
Hope it helps someone :)
P.S. Perhaps someone could modify it to restrict access to certain roles.
-Mr Jones.

You may run into incompatible class versions issue. Basically you have altogehter 2 different JVMs. One for EJBs (utility framework as you defiined using 1.3). Another JVM is weblogic server using JDK 1.6 where you have Client to remotely access those EJBs methods. Going back, when you generate the client stubs and skeletons, and refer them on your client side, did you ran into any issues like with incompatible class versions.
Goud

How to use commons.logging in weblogic (8.1)?

Greetings,
I'm trying to use commons.logging framework to manage the logs of my
application. With Weblogic I will use an implementation that works with
weblogic.logging package but with other J2EE products I'll use another
native log implementations or frameworks (for instance, for jboss I will
use log4j).
1) I created a class WeblogicLogger which implements the Log interface::
public final class WeblogicLogger implements Log {
I packaged this class in a jar file with a properties file,
commons-logging.properties, which has the property setting my class
below has the default logger:
org.apache.commons.logging.Log=pt.ptinovacao.weblogic.logging.WeblogicLogger
2) My sample code has the following code:
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
private static final Log log = LogFactory.getLog(
LogTimeStartHandler.class.getName());
something(){
log.info(this.getClass()+" test log");
3) I added the commons-logging jars and my jar with my custom wrapper
weblogic logger in ${WL_HOME}/common/bin/commEnv.sh:
WEBLOGIC_CLASSPATH=
(...)${CLASSPATHSEP}${WL_HOME}/server/lib/weblogiclogger.jar${CLASSPATHSEP}${WL_HOME}/server/lib/commons-logging-api.jar${CLASSPATHSEP}${WL_HOME}/server/lib/commons-logging.jar
However, my loggings still not appear in my weblogic server. Did I miss
something?
thanks,
Pedro Salazar

Did you manage to get this working?
If yes ... what did you do?
I am having the same problem implementing commons-logging with log4j

How to view weblogic log files from a browser

Hi,
I am running WebLogic Server 7.03 on Solaris 8.
I have one Admin and multiple Managed servers running.
Each creates its own log file.
Is there anyway I can access this log files from the browser ?
In Apache, you can create a link from htdocs dir to the logs dir
and then view the log files from the browser. Is there a similar
mechanism in Weblogic server.
A quick response is well appreciated.
Thanks in advance.
-Anil Varma

If you are on a unix system you can do something similar by making an open
directory webapp with symbolic links to the weblogic log directories. I suggest
that you protect that webapp with administration access only.
Sam
Anil Varma wrote:
Hi,
I am running WebLogic Server 7.03 on Solaris 8.
I have one Admin and multiple Managed servers running.
Each creates its own log file.
Is there anyway I can access this log files from the browser ?
In Apache, you can create a link from htdocs dir to the logs dir
and then view the log files from the browser. Is there a similar
mechanism in Weblogic server.
A quick response is well appreciated.
Thanks in advance.
-Anil Varma

How to use weblogic.logging classes in 6.0

Hi,
We developed a number of logging classes under 5.1. One used
weblogic.logging.LogOutputStream to write messages out to the log. This
code no longer works under WLS 6.0. Everything compiles and runs but I
don't see any of our messages in any of the log files. Judging from the 6.0
JavaDoc, it looks like LogOutputStream is no longer supported. So I
switched over to using NonCatalogLogger. Same results - no output in the
logs.
What am I missing?
Thanks.
-brian

My coding error. weblogic.logging.* classes work just fine in 6.0 (he said
sheepishly)!
-b
"Brian J. Levine" <[email protected]> wrote in message
news:[email protected]..
Hi,
We developed a number of logging classes under 5.1. One used
weblogic.logging.LogOutputStream to write messages out to the log. This
code no longer works under WLS 6.0. Everything compiles and runs but I
don't see any of our messages in any of the log files. Judging from the6.0
JavaDoc, it looks like LogOutputStream is no longer supported. So I
switched over to using NonCatalogLogger. Same results - no output in the
logs.
What am I missing?
Thanks.
-brian

Application logging in weblogic 7.0

Just wanted to put a question out there as to how everyone else is doing application
logging. I want to provide a standardized error level logging capability to my
application developers, and I DO NOT want to use the weblogic logging as it appears
that it only can write to the server log - I worry about apps filling this filespace.
I tried ServletContext logging, and contrary to other implementations, it also
goes to the server log. According to the specs, it should go to a file that matches
up with the context name.
Is log4j the way to go?

Thanks for the feedback, anyone else that ones to chime in on log4j shoot.
Were looking now at how to leverage/intergate/avaliablate log4j within WLS.
Cheers
mbg
"Jon Mountjoy" <[email protected]> wrote in message
news:[email protected]..
Hi Mark,
I am curious about how log4j didn't work in a cluster, and what about
weblogic's logging was superior to log4j?Well, I didn't exactly say that it didn't work in a cluster ;-) I
implied that it didn't work beautifully in a cluster :-)
These are the advantages that I see to WebLogic's logging:
a) Distributed logging is a no-brainer
b) Integration with WebLogic's own notifications
WL:If you want to log in a cluster, then using WebLogic's logging is
simple and effective - it all works out of the box. You get a nice
domain log and all the underlying distribution is done for you.
Log4J: If you want to log in a cluster using Log4J, then as far as I
know you have to do some work (not much, just some) - which you don't
have to do using WL. AFAIK, to get the same functionality you have to
use SocketAppenders, and then have your administration server (or
whichever server you want to hold the domain log) run a socketnode.
Advantages: You have lots of nifty log4j features, more portable.
Disadvantages: More setup, more administration, no integration with WL
notifications.
To me the greatest advantage is the integration with WebLogic's own
notifications. Logging is not just about debugging info, but also
manageability. I want to see all important information consolidated.
Of course, I can write code to get this - perhaps writinng a
notification listener for WL messages and converting them to Log4J
messages. Hmm, perhaps if WL let me write my own 'appender' instead of
their default 'send a JMX event' I could get nice clean integration.
The nice thing about Log4J is that it's feature set is far richer, and
its more 'portable' if you are willing to do the integration work with
each app server.
Regards,
Jon

How to configur log4j logging for weblogic 10.1

Hi,
I am tried to set log4j logging for my application running in weblogic 10.1. I set a log4j.properties file and loaded the properties by a servlet. Where its load the properties files and configure it by PropertyConfigurator.
The same logic has worked out in websphere. But in weblogic, it is not working. I set the server logging and domain logging to Log4j in Admin console. Now it is writing all the log statements.
If i write a property for a package to Error level and root level is Debug. Its not working, all debug statements are getting written.
Can you please tell me the steps to configure log4j logging in weblogic 10.1.
Thanks & Regards,
Nasrin.N

Did you manage to get this working?
If yes ... what did you do?
I am having the same problem implementing commons-logging with log4j

Logging to weblogic.log

Similar Messages

Maybe you are looking for