Weblogic logging framework -- customization

Hello Gurus,
Currently I am using NonCatalogLogger to log my application logs into soa_server logs. Now that I want my application logs to be logged somewhere else (not in the soa_server logs), so that my app logs logged separately in the some other location.
Is there any way to do so??
Cheers,
Vitz

1) Bad question :-)
2) I'd like to modify it directly in config.xml, what is the property ? I've already modified any log entry in this file including *.tlog files with "TransactionLogFilePrefix" property. But in my config.xml file, I don't have any entry concerning *startup.log.
"Kumar Allamraju" <[email protected]> a écrit dans le message news: [email protected]..
Laurent PAILLARD wrote:
Weblogic 6.02 + C&P 3.5 on solaris 2.6 2 Questions : 1) Is there a way to change deployment directory in Weblogic 6.02. Every applications are deployed in hidden directories named '.wl_temp_do_not_delete_<server>' contained in 'config/<domain>/applications'.As all our applications are not placed in this directory, we'd like all temporary placed in the same directory.
You can deploy your apps outsideo f config/domain/applications
directory. Just go to console and select the "Install a new webapp
or ejb" and it will ask you to specify the absolute path.
2) Can we also move logs named like "<server>-startup.log" and "<server>.log" in other directories than they are by default.
Yes. You can specify the absolute path again via console.
[att1.html]

Similar Messages

  • Integration of Commons Logging framework with Weblogic

    Hi,
    We are trying to use Apache commons logging framework and trying to publish log mesages in Weblogic so that messages can be seen through console and all the Logging configurations can be managed from Admin console. I tried using the below steps:
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/logging/config_logs.html#using_commons
    But these does not seems to be working for User defined handlers. I am able to see the logs in the default odl-handler file but not able to log the messages through the handlers defined by me.
    Can anyone help me on this.
    Regards,
    Anuj

    Hi,
    We are able to see reports through Workspace. We are facing problem after
    integrating Hyperion Interactive Reporting with Weblogic Portal. we are able to see the sections like Query,Report,Results but we are not able to see the content after selecting any one of the section mentioned above.
    System Configuration:
    Hyperion Interactive Reporting 9.3.1
    App Server: Weblogic server 9.2
    Web Server: Apache 2.0.52
    Database: Oracle 9.0.1.
    Operating System: Windows 2003 with SP1
    Browser: I.E 6.0
    With Workspace everything is working fine. After Integration we are facing problem.
    Regards,
    S.Suresh.

  • 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 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

  • 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

  • Unwanted stack trace in weblogic.log for thrown JSP Exceptions

    We are throwing a JSP exception within a custom tag when data validation
              errors occur; the errorPage for the JSP page is then invoked to show the
              appropriate errors. However, in the weblogic.log, a stack trace is shown
              indicating the exception (example below). We do not want this stack track
              shown unless there is a real "error" in our system vs. invoking the
              errorPage to show "application" errors. Is there any way to supress this,
              as we are not explicitly causing this to happen. It appears to be a
              weblogic feature. This causes us problems in finding true system errors
              that might be occurring due to these non-problems showing up in the
              weblogic.log.
              Thanks for the help.
              John Bauer
              Wed Dec 20 15:34:49 EST 2000:<E> <ServletContext-General> exception raised
              on '/test/test.jsp'
              javax.servlet.ServletException: runtime failure in custom tag 'testtag'
              at jsp_servlet._test._test._jspService(_test.java:89)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :124)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:
              60)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:
              07)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              Manager
              java:251)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
              at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
              Code)
              

    The design of the data entry pages is such that the error page is the same
              page as the data entry page, and a validation JSP tag validates the data and
              if it finds a problem, it will set some variables and throw a JSP exception
              to redisplay the page. Unfortunately, we are forced to live with this
              design. Are you aware of any mechanism to suppress the automatic logging of
              thrown JSP exceptions in the weblogic log?
              Thanks,
              JDB
              Cameron Purdy <[email protected]> wrote in message
              news:[email protected]...
              > Exception handling for custom tags is very poorly handled right now. For
              > one thing, WL hides the actual exception.
              >
              > However, the way that you are doing this seems very odd. The error page
              is
              > for server errors, not user typos.
              >
              > Peace,
              >
              > --
              > Cameron Purdy
              > Tangosol, Inc.
              > http://www.tangosol.com
              > +1.617.623.5782
              > WebLogic Consulting Available
              >
              >
              > "John Bauer" <[email protected]> wrote in message
              > news:[email protected]...
              > > We are throwing a JSP exception within a custom tag when data validation
              > > errors occur; the errorPage for the JSP page is then invoked to show the
              > > appropriate errors. However, in the weblogic.log, a stack trace is
              shown
              > > indicating the exception (example below). We do not want this stack
              track
              > > shown unless there is a real "error" in our system vs. invoking the
              > > errorPage to show "application" errors. Is there any way to supress
              this,
              > > as we are not explicitly causing this to happen. It appears to be a
              > > weblogic feature. This causes us problems in finding true system errors
              > > that might be occurring due to these non-problems showing up in the
              > > weblogic.log.
              > >
              > > Thanks for the help.
              > > John Bauer
              > >
              > > Wed Dec 20 15:34:49 EST 2000:<E> <ServletContext-General> exception
              raised
              > > on '/test/test.jsp'
              > > javax.servlet.ServletException: runtime failure in custom tag 'testtag'
              > > at jsp_servlet._test._test._jspService(_test.java:89)
              > > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              > > at
              > >
              >
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > > :124)
              > > at
              > >
              >
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              > > l.java:
              > > 60)
              > > at
              > >
              >
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              > > l.java:
              > > 07)
              > > at
              > >
              >
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              > > Manager
              > > java:251)
              > > at
              > >
              >
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
              > > at
              > > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
              > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
              Compiled
              > > Code)
              > >
              > >
              >
              >
              

  • Weblogic.log formatting

    I have 2 weblogic servers running.
    one on my W2K laptop and an AS400
    When a nosuchmethod error is logged on my W2K webserver
    I get the method name.
    When the same error is generated on my AS400 webserver it does not.
    Is there a way to get it to show up in the AS400 weblogic.log
    thanks in advance
    Mickey

    "Beth" <[email protected]> wrote:
    Hi,
    I'm trying to find out some more info on the weblogic.log:
    1) I see that there is a weblogic.system.maxLogFileSize property
    in the weblogic.properties file which will rotate the log based on size.
    Are we limited to size only? Is there any way to rotate the log file
    based on a new day?This is available for access log...(for HTTP)
    not sure for weblogic.log
    >
    2) Is there any way to specify exactly how many rotations you want?
    For example if I only want to keep the last three weblogic.log files-
    if there are already three on the system, overwrite the oldest one.
    3) I am looking for more information on LogOutputStream, but haven't
    been able to locate the doc on the web site. Any idea where I might find
    it?
    4) I assume by using LogOutputStream and log() that the server is taking
    care of synchronizing multiple calls to the log file?I dont think logging is synchronised.
    for me it makes sense.
    >
    5) During development I will be using calls such as log.debug() but when
    I'm
    ready for production I don't want those log messages in the log file. Is
    there
    any kind of switch to tell the logging mechanism to ignore certains types of
    log
    messages? Or does one have to do something specific to the code to ignore
    those messages when the time comes?check out weblogic.system.discardOutAndErr=true
    but i am not sure this will help..
    >
    Thanks in advance,
    Beth

  • Advantages of Weblogic security framework over websphere security architecture

    Hi,
    Weblogic implement the security as a layer . And websphere, as far as I known
    implements security as plug ins.
    I'd like to known what are the advantages of weblogic security framework over
    Websphere security archirtecture ? performance point of view, features, reliability,
    robustness etc ...
    Thanks a lot !

    "walt" <[email protected]> wrote in message
    news:3fca2d60$[email protected]..
    >
    Hi,
    Weblogic implement the security as a layer . And websphere, as far as Iknown
    implements security as plug ins.
    I would consider the WLS security provider model to be a plugin model.
    I'd like to known what are the advantages of weblogic securityframework over
    Websphere security archirtecture ? performance point of view, features,reliability,
    robustness etc ...
    http://www.bea.com/content/news_events/white_papers/BEA_WLS_vs_Websphere_TCO_wp.pdf
    http://e-docs.bea.com/wls/docs81/secintro/archtect.html
    http://dev2dev.bea.com/products/wlserver/whitepapers/WLS_security_Framework.jsp
    http://dev2dev.bea.com/products/wlserver81/index.jsp

  • 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.

  • Weblogic.log questions

    Hi,
    I'm trying to find out some more info on the weblogic.log:
    1) I see that there is a weblogic.system.maxLogFileSize property
    in the weblogic.properties file which will rotate the log based on size.
    Are we limited to size only? Is there any way to rotate the log file
    based on a new day?
    2) Is there any way to specify exactly how many rotations you want?
    For example if I only want to keep the last three weblogic.log files-
    if there are already three on the system, overwrite the oldest one.
    3) I am looking for more information on LogOutputStream, but haven't
    been able to locate the doc on the web site. Any idea where I might find
    it?
    4) I assume by using LogOutputStream and log() that the server is taking
    care of synchronizing multiple calls to the log file?
    5) During development I will be using calls such as log.debug() but when
    I'm
    ready for production I don't want those log messages in the log file. Is
    there
    any kind of switch to tell the logging mechanism to ignore certains types of
    log
    messages? Or does one have to do something specific to the code to ignore
    those messages when the time comes?
    Thanks in advance,
    Beth

    "Beth" <[email protected]> wrote:
    Hi,
    I'm trying to find out some more info on the weblogic.log:
    1) I see that there is a weblogic.system.maxLogFileSize property
    in the weblogic.properties file which will rotate the log based on size.
    Are we limited to size only? Is there any way to rotate the log file
    based on a new day?This is available for access log...(for HTTP)
    not sure for weblogic.log
    >
    2) Is there any way to specify exactly how many rotations you want?
    For example if I only want to keep the last three weblogic.log files-
    if there are already three on the system, overwrite the oldest one.
    3) I am looking for more information on LogOutputStream, but haven't
    been able to locate the doc on the web site. Any idea where I might find
    it?
    4) I assume by using LogOutputStream and log() that the server is taking
    care of synchronizing multiple calls to the log file?I dont think logging is synchronised.
    for me it makes sense.
    >
    5) During development I will be using calls such as log.debug() but when
    I'm
    ready for production I don't want those log messages in the log file. Is
    there
    any kind of switch to tell the logging mechanism to ignore certains types of
    log
    messages? Or does one have to do something specific to the code to ignore
    those messages when the time comes?check out weblogic.system.discardOutAndErr=true
    but i am not sure this will help..
    >
    Thanks in advance,
    Beth

  • Pb with weblogic.log

    To debug our application, we inserted many System.out.println() in our
    servlets/jsp. The problem is that, whereas they appear in the
    weblogic-launch-window, they don't in the weblogic.log file. Is there a
    property to change in order to get these messages?

    I am also lookign which log file "System.out.println's" are going to. Please give details as to what we need to do to see these messages and which log file to go to.

  • 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?

  • Logging to different logging framework

    I was wondering if it is possible to log ALL messages from server, jms, rmi, web-access, etc. to a single logging framework, log4j/commons-logging/java logging. I eventually need to gather all the logs generated by the application server and log them to syslog, either by a handler or an appender. Does anyone know if this is possible?

    Did you get an answer to your message. I am in the same dilemma. I need to send log messages to one file however. If someone helped you with this, I would love to see how it was done.
    Thx,
    Pandorliza

Maybe you are looking for