WLS logging/statistics

Hi!
I wonder whether there is possible to gather the continous information
one can view in the WebLogic Console for statistical purposes.
E.g. it could be valuable to view curves for connection pool usage,
memory usage, bean cache usage and so on.
Thanks for any comments on this topic :-)
-jo
----- BEA signature --------------
Jo Torsmyr
Senior Consultant
Mobile: +47 92659288
Email: [email protected]
BEA Systems Oy
Strandveien 50, Godthaab
P.O. Box 344
N-1326 Lysaker
Norway
Telephone: +47 67838800
Fax: +47 67838801
WWW: www.bea.com

I did not set up the email messages within WLS 8.1. I have written my own emailer
class that I use.
"Sean C. Sullivan" <nospam@spamfree> wrote:
>
How did you setup error email messages with BEA Weblogic Server 8.1?
Can this be setup from the Admin console?
WD wrote:
Hi All,
My app is running on WLS 8.1. I am using WLS logging api to log themessages and
I also email those messages. I would like to configure the loggingso that I can
send a particular message once every x time interval.
e.g. If the same error message is thrown multiple times in an hour,currently
the app will send those many emails. I want to change it so that eventhough the
same error message is thrown multiple times in an hour, the app willsend only
one email.
Is there a way to do this using WLS api?

Similar Messages

Logging the Runtime Fault messages BPEL in WLS logs

Requirement: I need to capture the run time fault from BPEL processes in the WLS logs how to do this?
Solution: I have tried following I created the Java class ot initialise the Java logging.
Java snippet:
private static final Logger logger = Logger.getLogger("oracle.soa.Logger");
static {
LogFormatter.configFormatter(logger);
public static final void log(String message) {
logger.log(Level.INFO, message);
In my BPEL process I have the CatchAll activity
In the ‘AssignFault I’ have the assignments using ora: getFaultAsString() , but I’m not getting the expected fault in Assign Activity which we see in Audit Trail.
In Audit Trail i see the following message against the my Validate Activity
"Invalid data: The value for variable "ReceiveXML_Read_InputVariable", part "body" does not match the schema definition for this part Element 'TimeBandList' not expected.. The invalid xml document is shown below:"
The ora: getFaultAsString() is showing the "com.oracle.bpel.client.BPELFault: faultName: {{http://docs.oasis-open.org/wsbpel/2.0/process/executable}invalidVariables} messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}"

I had gone thru that documentation. I needed something more than that.
Well, I want to know what entries go into the access log & what into custom
log of ours.
Actually, the entries with 200 status only are going into our custom log ,
how can I make the entries with status 302 (redirection) to get into the
custom log?
Thanks.
priya
Robert Patrick wrote:
Yes. http://www.weblogic.com/docs51/admindocs/http.html#logs
Priya Bangara wrote:
Hi,
Our company has WebLogic Server 5.0 b2 running on our livesite. They
have been using WLS's access log and their own custom log. Now, they
have found some problem with the logs and I'm looking into it.
I don't find any documentation on 5.0b2 on BEASYS's site anymore. Are
all the features like 'extended log format', 'log rotation' of WLS 5.1
were there in 5.0 b2 ?
Please help. Issue is very critical. I would appreciate if you could
also send me some links where I can find more info on WL's logging
mechanism.
Thanks in advance,
Priya

WLS logging api

Hi All,
My app is running on WLS 8.1. I am using WLS logging api to log the messages and
I also email those messages. I would like to configure the logging so that I can
send a particular message once every x time interval.
e.g. If the same error message is thrown multiple times in an hour, currently
the app will send those many emails. I want to change it so that even though the
same error message is thrown multiple times in an hour, the app will send only
one email.
Is there a way to do this using WLS api?
Thanks,
WD

I did not set up the email messages within WLS 8.1. I have written my own emailer
class that I use.
"Sean C. Sullivan" <nospam@spamfree> wrote:
>
How did you setup error email messages with BEA Weblogic Server 8.1?
Can this be setup from the Admin console?
WD wrote:
Hi All,
My app is running on WLS 8.1. I am using WLS logging api to log themessages and
I also email those messages. I would like to configure the loggingso that I can
send a particular message once every x time interval.
e.g. If the same error message is thrown multiple times in an hour,currently
the app will send those many emails. I want to change it so that eventhough the
same error message is thrown multiple times in an hour, the app willsend only
one email.
Is there a way to do this using WLS api?

WLS Logs in a Cluster Environment

          We would like to have all WLS logs from the WLS server instances in the clluster
          to be written to the same file on a common file system, such as an NFS mounted
          partition. By default, WLS writes all logs to the local file system. In a distributed
          environment, this can make debugging pretty difficult.
          Has anyone had any experience with having all WLS logs written to the same file?
          Regards,
          Chet


Hi,
To uninstall you have to first run the Server tools and there you can uncheck the sbo mailer. There is not way you can uninstall SBO mailer service and you cannot find it under control panel its a service...not an applicaiton.
Run the server tools and then choose repair.
Regards,
Rakesh N

Where do I fine Logs & Statistics Data?

Good day, with the previous version of the firmware I was able (ubder the Advanced Tab) to view Logs and Statistics for my wireless network. Where can I find this same info with the newest version?
Thanks

Download and install AirPort Utility 5.6 for Mac OS X Lion , which offers much more functionality than AirPort Utility 6.0.
Keep both applications on your Mac (you cannot delete 6.0) and use the one that you want.

ADF: Cannot find reason for SEVERE error in WLS log

JDeveloper 11.1.1.1.0
When I deploy my ADF application to integrated WLS, I keep geting following log messages:
10.7.2009 9:09:17 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
10.7.2009 9:09:20 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
10.7.2009 9:11:04 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
10.7.2009 9:11:09 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
What is the problem?
Edited by: mskarabo on Jul 10, 2009 9:34 AM

Hi,
another situation when this could happen:
In my main jspx I have an af:panelTabbed with an af:region in each of the af:showDetailItems. The regions refer to bounded task flows consisting of only one view (a page fragment) using bindings. The jspx is below, with two additional showDetailItems for testing (sdi3, sdi4).
<f:view>
<af:document id="d1" title="TEST RichRenderKit isNavigating SEVERE error">
    <af:form id="f1">
      <af:panelTabbed id="pt1">
        <af:showDetailItem text="TaskFlow1" id="sdi1">
          <af:region value="#{bindings.MyTaskFlow1.regionModel}" id="r1"/>
        </af:showDetailItem>
        <af:showDetailItem text="TaskFlow2" id="sdi2">
          <af:region value="#{bindings.MyTaskFlow2.regionModel}" id="r2"/>
        </af:showDetailItem>
        <af:showDetailItem text="showDetailItem 1" id="sdi3">
          <af:outputText id="ot1" value="test"/>
        </af:showDetailItem>
        <af:showDetailItem text="showDetailItem 2" id="sdi4"/>
      </af:panelTabbed>
    </af:form>
</af:document>
</f:view>The error message appears in the log window only when navigating from a tab that uses a task flow as a region.
(E.g. the error shows when navigating from sdi1 or sdi2 to any other tab, but does not show when navigating from sdi3 or sdi4 to any other tab.)
Hope this helps to identify the problem.
Regards,
Patrik

WLS logging - quick questions

Hi
In JDeveloper, we could write our application logging to logs for debugging and viewable from JDeveloper.
When we deploy to Standalone weblogic server, we cant find our logging.
Of the 3 loggers (Msg Catalog, nonCatalog, Commons log API),
Which logging mechanism is the best practice used logging for development environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Which logging mechanism is the best practice used logging for production environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Thanks

Hi
In JDeveloper, we could write our application logging to logs for debugging and viewable from JDeveloper.
When we deploy to Standalone weblogic server, we cant find our logging.
Of the 3 loggers (Msg Catalog, nonCatalog, Commons log API),
Which logging mechanism is the best practice used logging for development environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Which logging mechanism is the best practice used logging for production environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Thanks

WLS http access logs not written to when starting WLS instance using nodemanager

When starting managed WLS instances using node manager the HTTP access logs are
not written to (the WLS log in the same directory is written to). All other functionality
of the WLS instances seem to operate just fine when started using node manager.
When we start the same managed WLS instances using a start-up script the HTTP
access logs are written to.
===
How can we get HTTP access logs to be written to when starting a WLS instance
using node manager?

I think I know the answer to this one!
I got bitten by the same bug (at least I think it is a bug). Check the location
specified for the HTTP-access log for your server instance. It is probably a relative
location, right?
According to the docs, relative paths should start from the Root Directory (see
your Remote Start config), but it seems like the BEA-programmers forgot to retrieve
the Root Directory and instead blindly writes to the process' current working
directory (CWD).
And when started by the Node Managet, the CWD = WL_HOME/common/nodemanager.
If you are as paronoid as I am (and you should be too), that directory should
not be writeable by anyone. Because my BEA installation was owned by 'bin', and
the processes run by 'beawls', I got an error message in my NM-logs pointing to
the problem. In your case, you are probably running NM as a user that has write-access
to your NM-home, and all your missing HTTP-access logs are deep, down there.
Jan Bruun Andersen

Jdeveloper, WLS and Log4j logging

All,
I want to route all the ADF application log messages to a log file using log4j.
I have created a log4j.properties and put in the ViewController/src folder. The application finds that config file, and produces the desired output - so far, so good.
Now I would like to route all the WLS logging using log4j.
To first try it, I've opened the integrated WLS console, and set, under server/logging, that the log implementation uses log4j instead of jdk. I have also checked the "redirect stdout", "redirect stderr", and "logging bridge" check boxes.
I've also:
- included the wllog4j.jar and log4j-1.2.16.jar in the classpath (by editing the /home/semar/Oracle/Middleware/wlserver_10.3/common/bin/commEnv.sh file).
- put a copy of log4j.properties also in the WLS path - which is, in my case: /home/semar/Oracle/Middleware/wlserver_10.3/server/bin
- put the path of the log4j.properties in the WLS CLASSPATH (by editing the /home/semar/Oracle/Middleware/wlserver_10.3/common/bin/commEnv.sh file)
I've then re-started the integrated wls, and now what happens is:
- the log appender for my application is no more found (log4j complains that the appender is not configured)
- no log file is produced/updated
Am I missing something obvious here ? Where should I put the log4j.properties then ? Are other extra tasks I should perform, in order to get all the ADF and WLS logging routed through log4j, and configured using a single log4j property file ?
I'm using WLS 10.3.5.0 and Jdeveloper 11g rel 2 11.1.2.1.0, running on a Linux OpenSuse 11.4
Sergio.

Still no joy.
I have put the two JARs + log4j.properties into domain_root/lib folder.
I have also modified the startWeblogic.sh by adding the following:
JAVA_VM="${JAVA_VM} -Dlog4j.configuration=${DOMAIN_HOME}/lib/log4j.properties"
export JAVA_VM
Both the .jar files and the log4j.properties are in the classpath and in the java options of the WLS starting log.
In my application I have:
package logging;
import org.apache.log4j.Logger;
import...
public class loggingBean {
/* Get actual class name to be printed on */
Logger log = Logger.getLogger(loggingBean.class.getName());
public loggingBean () {
System.out.println("hello from loggingBean constructor");
//_logger.info("Creating a new instance");
log.debug("Hello this is a debug message");
log.info("Hello this is an info message");
In the log4j.properties I have:
# Define the root logger with appender file
log = /tmp
log4j.rootLogger = DEBUG, FILE
# Define the file appender
log4j.appender.FILE=org.apache.log4j.FileAppender
log4j.appender.FILE.File=${log}/log.out
# Define the layout for file appender
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.layout.conversionPattern=%m%n
# end of the log4j.properties
And in the standard log file (nohup.out since I start the server with it):
<11.04.2012 14:56 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <hello from loggingBean constructor>
<11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN No appenders could be found for logger (logging.loggingBean).>
<11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN Please initialize the log4j system properly.>
<11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.>
The file /tmp/log.out does not exist.
Any thought ?
Sergio.

ADFBindingFilter error while deploying a war to WLS server using jdev 12c

I've a OSB Server setup using XBUS_MAIN_GENERIC_120131.1402.S which is using JDEVADF_MAIN_GENERIC_120102.0032.6211.
Launched the 12c Jdev and created a simple adfc web application with a test.jspx page and deployed in the OSB Server. The web app deployed and could launch the test page.
I have added the page definition for that test page by 'Go to Page Definition' option.
Now, If I try to deploy this web app war to the OSB Server, I'm getting the following exception in the jdev (Error1) and in the server log I could see the error (Error2).
Any Idea how to resolve this issue?
Error1 ( on Jdev )
[03:15:08 AM] ---- Deployment started. ----
[03:15:08 AM] Target platform is (Weblogic 10.3).
[03:15:09 AM] Retrieving existing application information
[03:15:09 AM] Running dependency analysis...
[03:15:09 AM] Building...
[03:15:15 AM] Deploying profile...
[03:15:16 AM] Wrote Web Application Module to /scratch/sansrini/OSB_DEV/OSBMgmtTestApp/OSBMgmtTaskflowsTestApp/deploy/newosb2.war
[03:15:16 AM] Deploying Application...
[03:15:18 AM] [Deployer:149193]Operation "deploy" on application "newosb2" has failed on "AdminServer".
[03:15:18 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application newosb2 on AdminServer.: [HTTP:101371]There was a failure when processing annotations for application /scratch/sansrini/view_storage/sansrini_xbus2/xbus/build/MW_HOME/user_projects/domains/base_domain/servers/AdminServer/upload/newosb2/app/newosb2.war. Ensure that the annotations are valid. The error is oracle.adf.model.servlet.ADFBindingFilter.
[03:15:18 AM] weblogic.application.ModuleException: [HTTP:101371]There was a failure when processing annotations for application /scratch/sansrini/view_storage/sansrini_xbus2/xbus/build/MW_HOME/user_projects/domains/base_domain/servers/AdminServer/upload/newosb2/app/newosb2.war. Ensure that the annotations are valid. The error is oracle.adf.model.servlet.ADFBindingFilter
[03:15:18 AM] Deployment cancelled.
[03:15:18 AM] ---- Deployment incomplete ----.
[03:15:18 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Error2 ( on wls log )
<Feb 3, 2012 3:15:18 AM PST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: [HTTP:101371]There was a failure when processing annotations for application /scratch/sansrini/view_storage/sansrini_xbus2/xbus/build/MW_HOME/user_projects/domains/base_domain/servers/AdminServer/upload/newosb2/app/newosb2.war. Ensure that the annotations are valid. The error is oracle.adf.model.servlet.ADFBindingFilter
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:732)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:93)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
Truncated. see log file for complete stacktrace

I guess you should be asking on an internal forum somewhere, because we, the unwashed masses, don't have access to JDev 12c.
John

Is there a way to automatically collect the log files from a AirPort or TimeCapsule base station?

Hi there,
the headline says basically all: Is there a way to collect the log files from a Time Capsule 7 AirPort from time to time? They are overwritten quite soon but I want a complete log of all activities to my access point.
The AirPort Utility says something about SNMP. Is this the way to go? Some kind of demon on my Mac that retrieves and saves the logs like every two days?
I want to copy the access logs, I am not interested in Time Machine backup logs.
Thanks.

There is a way to do this via Syslog. On the Logging & Statistics panel (within the AirPort Utility), you can point the AirPort's system logs to a Syslog "server."
This would require a "dedicated" network client to receive the logs.
Unfortunately, setting up a Syslog server is a bit intensive initially, but is simple to operate and maintain.
Please check out this Apple Support Communities thread: Directing Syslog message to a file
ref: Enable an Apple Mac OS machine as a syslog server

Can no longer access log files from EM(ECM11.1.1.6.0).

Full UI popup error is " Stream closed ADF_FACES-60097:For more information, please see the server's error log for an entry beginning with: ADF_FACES-60096:Server Exception during PPR, #4"
Of course, I can't see any further errors in the logs,so I'm really at a disadvantage. am currently asking client if he sees anything in the Console for errors.
This was working just fine, no issues accessing logs from EM. No configiration changes were made, there's almost 8gb RAM available on this box(SOA on different BOX). ECM set up is Admin, IPM, UCM on this box.
Is there special memory settings for logs?

log from Admin Console is this:
<Dec 11, 2012 12:03:32 PM PST> <Error> <oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator> <BEA-000000> <ADF_FACES-60096:Server Exception during PPR, #6
java.io.IOException: Stream closed
at java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:134)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:416)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:315)
at oracle.jsp.parse.XMLUtil.getDocument(XMLUtil.java:447)
at oracle.jsp.parse.OracleJsp2Java.transformImpl(OracleJsp2Java.java:402)
at oracle.jsp.parse.OracleJsp2Java.transform(OracleJsp2Java.java:593)
at oracle.jsp.runtimev2.JspPageCompiler.attemptCompilePage(JspPageCompiler.java:691)
at oracle.jsp.runtimev2.JspPageCompiler.compileBothModes(JspPageCompiler.java:490)
at oracle.jsp.runtimev2.JspPageCompiler.parseAndGetTreeNode(JspPageCompiler.java:457)
at oracle.jsp.runtimev2.JspPageInfo.compileAndLoad(JspPageInfo.java:624)
at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:645)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:387)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:810)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:734)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:180)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.sysman.eml.app.JSPFilter.doFilter(JSPFilter.java:93)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:527)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)
at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:45)
at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:45)
at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:45)
at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:45)
at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch(FacesContextFactoryImpl.java:268)
at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:471)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:140)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:191)
at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)
at oracle.sysman.emSDK.adfext.ctlr.EMViewHandlerImpl.renderView(EMViewHandlerImpl.java:158)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:911)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:367)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:222)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:102)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447)
Again, this is from me simply acessing any standard WLS log on the ECM Domain.
Lgin as weblogic, then Farm->logs>View Log Messages

How to view logs in case of stand alone deployment

Hi,
I have deployed my UI app on a WLS server (A standalone deployment). And my UI has an LOV and i want to find out the exact query that it is firing when i click on the LOV (They query has some bind variables too).
So for this i need to see the wls logs (sql query especially) from UI. But since its a standalone deployment, i am not able to sucessfully see the logs.
I tried following
1. put the "-Djbo.debugOutput=console" as the java_property in setDomain.env file.
And then i bounced my container. I never see any sqls in any of the logs under AdminServer or in the terminal where i start my container.
2. Tried putting the same option in WLS console ..as mentioned in this thread - Where to put "jbo.debugoutput=console" in WLS?
With this option, when i set it in environment->servers->your_server_name click on the 'Start Server' tab and put it to the 'Argument' text field, i dont know where is it creating the log file.
Should i be giving it as "-Djbo.debugoutput=file' " or a <filename> in "'-Djbo.debugoutput=<filename>' " ... i tried both anyway but it doesnt create any file.
Could you please let me know what is the proper way to see the logs in such case and also if there is a way out, could you please list the steps to implement or point to a document on it ?
Thanks,
Suman

Hi Suman,
You could try setting -Djbo.debugoutput=ADFLogger and then either editing logging.xml or using the Oracle Diagnostic Logging screen in OEM Fusion Middleware Control to ensure that the oracle.jbo logger is set at a low enough level.
John

Steve Muenchs "Dynamic JDBC" on WLS 11g (10.3.1)?

Hi,
I try to run Steves Example "11g Dynamic JDBC Credentials for Model 1, Struts, Trinidad, and ADF Faces Rich Client" on Standalone WLS 11g (10.3.1) but it doesn't works... on integrated WLS it runs without problems. The WLS-Log shows:
Modul: oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack
Message: Failed to create config mbean.
details: java.lang.Exception: oracle.mds.core.MetadataNotFoundException: MDS-00013: No Metadate for Metaobject "/META-INF/adf-config.xml" found.
Does somebody have the example to run brought? Or if new settings are necessary for the example on WLS 11g?
Kind regards
Martin

Hi,
since Steve's solution has nothing to do with the adf-config, I suggest you create a simple testcase that reproduces the problem. It appears as if the ADF binding is not set up properly
Frank

How do I turn off base station logging?

Airport Extreme seems to have started logging events two days ago with no input from me. Have been using for about two months. I wonder what's going on and how I can turn off base station logging.

There are basically two types of logs that the AirPorts provide: 1) The "real-time" logs under the Logs tab of Logs and Statistics within the AirPort Utility, and 2) Syslogs which require that you provide a destination device that is set up to collect these types of logs.
Which are you referring to? If it is the former, there is no "off" option. With the latter, you would just need to remove the IP address from the Syslog Destination Address window on the Logging & Statistics tab of the AirPort Utility.

WLS logging/statistics

Similar Messages

Maybe you are looking for