About ADF logging.xml

hello everyone, configure a loghandler in logging.xml like this:
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/owsm/msglogging/diagnostic.log'/>
where the ${domain.home} and ${weblogic.Name} set up, then can I set up other variable and how?

hello my jdev is 12c,
please look this url about ADF log
thanks

Similar Messages

About ADF log

hello every one ,how can I configure the ADF logging.xml to reach daily log ,and the log's name like xxx20131113.log？
<log_handler name='mylog-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' level='TRACE:32'>
   <property name='logreader:' value='off'/>
   <property name='path' value='D:\log\'/>
    <property name='rotationFrequency' value='daily'/>
   <property name='retentionPeriod' value='day'/>
   <property name='format' value='ODL-Text'/>
   <property name='useThreadName' value='true'/>
   <property name='locale' value='zh'/>
   <property name='maxFileSize' value='5242880'/>
   <property name='maxLogSize' value='52428800'/>
   <property name='encoding' value='UTF-8'/>
</log_handler>

Hi, I am able to create log file with date format. I did not have windows envt set up and I had to create envt in windows and tested the log. You will have to pass it as system variable using -D tag.   Ex : -Ddate.var=%datevar% where datevar is the one you are assigning date format. but ensure that you will not have space and special character in the extracted format.
thanks

Info about logging.xml in JDeveloper weblogic domains? JDK Logging Control

Is there any documentation on the file <DomainDir>/config/fmwconfig/servers/<ServerName>/logging.xml?
It seems to control JDK 1.4 logging for my weblogic server and overrides settings from the logging.properties file.
This is important new behaviour!
Is it documented somewhere?

I see some message about a proxy. Have you checked that you can use the proxy from you network?
If not you should turn the proxy off.
Timo

ADF Logger - logging.xml file

Hi,
We are building an ADF Application and created our logger, which is a wrapper around the ADFLogger. As expected logging etc works just fine for the ADF applications deployed in weblogic. However there are parts of the application which could be a standalone (pure java) based components deployed independently, which are leveraging this wrapper logger too. For these applications we added the ADF dependent libraries needed for the ADFLogger. Still these apps are not able to log anything, and I think the main reason being it is not able to get a handle to the logging.xml fine which defines the ODL handler. All other runtime parameters like
"-Djbo.debugoutput=adflogger -Djbo.adflogger.level=FINEST" are passed.
There is no error etc, however the logs are not coming.
Is there a way where we can specify the logging.xml to the ADFLogger, so that it doesn't looks for the default location under - '+/<domain>/config/fmwconfig/servers/DefaultServer+'?
In general also (for pure ADF based applications), is there a way we can define the path of our logging.xml file, instead of using the default one?
Would appreciate any help.
Thanks
Sachin

Hi,
While I appreciate your response, however the question I have is - 'can we have our own logging.xml?' If yes how do we pass the information of our logging.xml to ADFLogger, instead of using the default logging.xml.
I know we can have our own logger handler defined within the logging.xml, but that is not what we are looking for. The ask is to have the option of having the path of logging.xml defined for ADFLogger.
Thanks
Sachin

Issue Connecting from Oracle Business Component Browser - adf-config.xml

There are similar posts in the forum to this, but I wasn't able to glean from them what I should do.
Essentially, I tried Connecting by:
right clicking on a node under a Model project, and selected TEST.
When the Oracle Business Component Browser - Connect Dialog window opened, I clicked CONNECT.The Oracle Business Component Browser (Local) seems to have opened fine, but in the message log I see this:
"jar:file:/C:/JDeveloper/jdev/doc/studio_doc/ohj/bc4j_f1.jar!/bc4j_f1.hs"
Feb 10, 2007 10:16:30 AM oracle.adf.share.config.ADFConfigFactory findOrCreateADFConfig
INFO: oracle.adf.share.config.ADFConfigFactory No META-INF/adf-config.xml found
I'm not experienced enough to know whether this is significant or not, nor if so what I need to do about this.
Thank you to anyone who can help a newer person out with this.
Matt
Studio Edition Version 10.1.3.1.0.3984
Build JDEVADF_10.1.3.1.0_NT_061009.1404.3984
ADF Business     Components 10.1.3.39.84
BPEL Designer     10.1.3.1.0 (Build 061009.0802)
Java™ Platform     1.5.0_06
CVS Version     Internal to Oracle JDeveloper (client-only)
I found this release note, which mentions both adf-client.xml and JClient; I'm still too new to know whether this helps with this or not, but I'm hoping it does for someone out there.
Thanks again.
ON: http://www.oracle.com/technology/products/jdev/htdocs/10.1.3.0.3/readme.html
JClient Security Still Requires AM Property Setting (4889913)
JClient applications should continue to use application module configuration property jbo.security.enforce for enabling authentication and authorization.
The authorizationEnforce property in adf-config.xml new in 10.1.3 is not yet supported for JClient
Message was edited by: Matt
matt.tech

Hi,
the adf-config.xaml file is not created by default and not needed by default. you need this to define custom skins or ADF Security.
For an example of adfs-config.xml doe skins see SRDemo sample app
Frank

Logging using ADF Logging - how to ?

Dear all,
I have several web-applications developed with JDeveloper and deployed on a WLS.
Each application routes its System.out.println(whatever) command on the same weblogic.log file.
I would like to have a log file for each application instead.
So I've implemented the ADFLogging in my application, and I use this commands:
import oracle.adf.share.logging.ADFLogger;
private static ADFLogger _logger =
ADFLogger.createADFLogger(loggingBean.class);
_logger.warning("this is a warning msg");
_logger.severe("this is a severe msg");
Then I specify, in the WLS console, a file for logging for one application.
Fact is, the logging from the logger goes always in the Adminserver.log and in the basedomain.log, but not in the log file I've specified for the application.
How to get the _logger log messages in that specified file ?
Am I missing something obvious here ?
Thanks in advance,
Sergio.

Well, I guess that the relevant file is
./Middleware/user_projects/domains/base_domain/config/fmwconfig/servers/AdminServer/logging.xml
Here is the content:
<?xml version="2.0" encoding="UTF-8"?>
<logging_configuration>
<log_handlers>
<log_handler name='console-handler' class='oracle.core.ojdl.logging.ConsoleHandler' formatter='oracle.core.ojdl.weblogic.ConsoleFormatter' level='WARNING:32'/>
<log_handler name='odl-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-diagnostic.log'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='useThreadName' value='true'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name,composite_instance_id,component_instance_id,composite_name,component_name'/>
</log_handler>
<log_handler name='wls-domain' class='oracle.core.ojdl.weblogic.DomainLogHandler' level="WARNING"/>
<log_handler name='owsm-message-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/owsm/msglogging'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name'/>
</log_handler>
<log_handler name='em-log-handler' level='NOTIFICATION:32' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.log'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
<log_handler name='em-trc-handler' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='logreader:' value='off'/>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.trc'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='locale' value='en'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
</log_handlers>
<loggers>
<logger name="" level="WARNING:1">
<handler name="odl-handler"/>
<handler name="wls-domain"/>
<handler name="console-handler"/>
</logger>
<logger name="oracle" level="NOTIFICATION:1"/>
<logger name="oracle.adf"/>
<logger name="oracle.adf.desktopintegration"/>
<logger name="oracle.adf.faces"/>
<logger name="oracle.adf.controller"/>
<logger name="oracle.adfinternal"/>
<logger name="oracle.adfinternal.controller"/>
<logger name="oracle.jbo"/>
<logger name="oracle.adfdt"/>
<logger name="oracle.adfdtinternal"/>
<logger name="oracle.bam"/>
<logger name="oracle.bam.adapter"/>
<logger name="oracle.bam.common"/>
<logger name="oracle.bam.system"/>
<logger name="oracle.bam.middleware"/>
<logger name="oracle.bam.adc.security"/>
<logger name="oracle.bam.common.security"/>
<logger name="oracle.bam.adc.ejb.BamAdcServerBean"/>
<logger name="oracle.bam.reportcache.ejb.ReportCacheServerBean"/>
<logger name="oracle.bam.eventengine.ejb.EventEngineServerBean"/>
<logger name="oracle.bam.ems.ejb.EMSServerBean"/>
<logger name="oracle.bam.adc.api"/>
<logger name="oracle.bam.adc"/>
<logger name="oracle.bam.eventengine"/>
<logger name="oracle.bam.ems"/>
<logger name="oracle.bam.webservices"/>
<logger name="oracle.bam.web"/>
<logger name="oracle.bam.reportcache"/>
<logger name="oracle.bpm"/>
<logger name="oracle.bpm.analytics"/>
<logger name="oracle.integration"/>
<logger name="oracle.integration.platform.blocks.cluster"/>
<logger name="oracle.integration.platform.blocks.deploy.coordinator"/>
<logger name="oracle.integration.platform.blocks.event.saq"/>
<logger name="oracle.integration.platform.blocks.java"/>
<logger name="oracle.integration.platform.faultpolicy"/>
<logger name="oracle.integration.platform.testfwk"/>
<logger name="oracle.soa"/>
<logger name="oracle.soa.adapter"/>
<logger name="oracle.soa.b2b"/>
<logger name="oracle.soa.b2b.apptransport"/>
<logger name="oracle.soa.b2b.engine"/>
<logger name="oracle.soa.b2b.repository"/>
<logger name="oracle.soa.b2b.transport"/>
<logger name="oracle.soa.b2b.ui"/>
<logger name="oracle.soa.bpel"/>
<logger name="oracle.soa.bpel.console"/>
<logger name="oracle.soa.bpel.engine"/>
<logger name="oracle.soa.bpel.engine.activation"/>
<logger name="oracle.soa.bpel.engine.agents"/>
<logger name="oracle.soa.bpel.engine.bpel"/>
<logger name="oracle.soa.bpel.engine.compiler"/>
<logger name="oracle.soa.bpel.engine.data"/>
<logger name="oracle.soa.bpel.engine.delivery"/>
<logger name="oracle.soa.bpel.engine.deployment"/>
<logger name="oracle.soa.bpel.engine.dispatch"/>
<logger name="oracle.soa.bpel.engine.sensor"/>
<logger name="oracle.soa.bpel.engine.translation"/>
<logger name="oracle.soa.bpel.engine.ws"/>
<logger name="oracle.soa.bpel.engine.xml"/>
<logger name="oracle.soa.bpel.entity"/>
<logger name="oracle.soa.bpel.jpa"/>
<logger name="oracle.soa.bpel.system"/>
<logger name="oracle.soa.dvm"/>
<logger name="oracle.soa.management.facade.api"/>
<logger name="oracle.soa.mediator"/>
<logger name="oracle.soa.mediator.common"/>
<logger name="oracle.soa.mediator.common.cache"/>
<logger name="oracle.soa.mediator.common.error"/>
<logger name="oracle.soa.mediator.common.error.recovery"/>
<logger name="oracle.soa.mediator.common.message"/>
<logger name="oracle.soa.mediator.dispatch"/>
<logger name="oracle.soa.mediator.dispatch.resequencer.toplink"/>
<logger name="oracle.soa.mediator.filter"/>
<logger name="oracle.soa.mediator.instance"/>
<logger name="oracle.soa.mediator.management"/>
<logger name="oracle.soa.mediator.metadata"/>
<logger name="oracle.soa.mediator.monitor"/>
<logger name="oracle.soa.mediator.resequencer"/>
<logger name="oracle.soa.mediator.resequencer.besteffort"/>
<logger name="oracle.soa.mediator.resequencer.fifo"/>
<logger name="oracle.soa.mediator.resequencer.standard"/>
<logger name="oracle.soa.mediator.service"/>
<logger name="oracle.soa.mediator.serviceEngine"/>
<logger name="oracle.soa.mediator.transformation"/>
<logger name="oracle.soa.mediator.utils"/>
<logger name="oracle.soa.mediator.validation"/>
<logger name="oracle.soa.scheduler"/>
<logger name="oracle.soa.services.common"/>
<logger name="oracle.soa.services.identity"/>
<logger name="oracle.soa.services.notification"/>
<logger name="oracle.soa.services.rules"/>
<logger name="oracle.soa.services.rules.obrtrace"/>
<logger name="oracle.soa.services.workflow"/>
<logger name="oracle.soa.services.workflow.common"/>
<logger name="oracle.soa.services.workflow.evidence"/>
<logger name="oracle.soa.services.workflow.metadata"/>
<logger name="oracle.soa.services.workflow.persistency"/>
<logger name="oracle.soa.services.workflow.query"/>
<logger name="oracle.soa.services.workflow.report"/>
<logger name="oracle.soa.services.workflow.runtimeconfig"/>
<logger name="oracle.soa.services.workflow.soa"/>
<logger name="oracle.soa.services.workflow.task"/>
<logger name="oracle.soa.services.workflow.task.dispatch"/>
<logger name="oracle.soa.services.workflow.task.routing"/>
<logger name="oracle.soa.services.workflow.user"/>
<logger name="oracle.soa.services.workflow.verification"/>
<logger name="oracle.soa.services.workflow.worklist"/>
<logger name="oracle.soa.services.workflow.performance"/>
<logger name="oracle.soa.services.cmds"/>
<logger name="oracle.soa.wsif"/>
<logger name="oracle.soa.xref"/>
<logger name="oracle.ucs"/>
<logger name="oracle.sdp"/>
<logger name="oracle.sdpinternal"/>
<logger name="oracle.sdp.messaging"/>
<logger name="oracle.sdp.messaging.client"/>
<logger name="oracle.sdp.messaging.driver"/>
<logger name="oracle.sdp.messaging.engine"/>
<logger name="oracle.sdp.messaging.parlayx"/>
<logger name="oracle.sdp.messaging.server"/>
<logger name="oracle.wsm"/>
<logger name="oracle.wsm.msg.logging" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="owsm-message-handler"/>
<handler name="wls-domain"/>
</logger>
<logger name='oracle.sysman' level='NOTIFICATION:32' useParentHandlers='false'>
<handler name='em-log-handler'/>
<handler name='em-trc-handler'/>
</logger>
</loggers>
</logging_configuration>
--------------------------

Entries with oracle's IP in log.xml file.

This is about a couple of log entries I found in /dcm/logs/emd_logs/log.xml file.
while I have some Idea about the message itself what I don't understand is why the <HOST_NWADDR> points to 148.87.12.57
Can anyone shed some light on this.
Does R2 connect to oracle in some way each time it is brought up, 'cause the IP 148.87.12.58 is the IP of the PortalStudio and I figured its neighbour belongs to oracle too.
Do I need to keep the box connected to Internet all the time for it to work.
Could someone at oracle tell me what my box is trying to do by connecting to 148.87.12.57.
Please find the entries below.
Thanx
Vinodh R.
These are the entries I found
i)
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2002-07-08T03:56:36.721-04:00</TSTZ_ORIGINATING>
<COMPONENT_ID>OC4J</COMPONENT_ID>
<MSG_TYPE TYPE="ERROR"></MSG_TYPE>
<MSG_GROUP>n/a</MSG_GROUP>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>myportal</HOST_ID>
<HOST_NWADDR>148.87.12.57</HOST_NWADDR>
<MODULE_ID>iAS_dcm/oracle/defaultLogger/ExceptionLogger</MODULE_ID>
<PROCESS_ID>null-Thread[ApplicationServerThread,5,applicationServerThreadGroup]</PROCESS_ID>
<USER_ID>root</USER_ID>
</HEADER>
<PAYLOAD>
<MSG_TEXT>[ RM ] Exception in repository API new SchemaManager()</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[oracle.ias.repository.schema.SchemaException: Password could not be retrieved
     at oracle.ias.repository.IASSchema.init(IASSchema.java:152)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:243)
     at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
]]></SUPPL_DETAIL>
</PAYLOAD>
</MESSAGE>
ii)
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2002-07-08T06:41:27.339-04:00</TSTZ_ORIGINATING>
<COMPONENT_ID>OC4J</COMPONENT_ID>
<MSG_TYPE TYPE="ERROR"></MSG_TYPE>
<MSG_GROUP>n/a</MSG_GROUP>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>myportal</HOST_ID>
<HOST_NWADDR>148.87.12.57</HOST_NWADDR>
<MODULE_ID>iAS_dcm/oracle/defaultLogger/ExceptionLogger</MODULE_ID>
<PROCESS_ID>null-Thread[ApplicationServerThread,5,applicationServerThreadGroup]</PROCESS_ID>
<USER_ID>oracle</USER_ID>
</HEADER>
<PAYLOAD>
<MSG_TEXT>[ RM ] Exception in repository API getDBConnect()</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[oracle.ias.repository.schema.SchemaException: Unable to connect to Directory Server:javax.naming.CommunicationException: oracleportal.peesh.com:389 [Root exception is java.net.ConnectException: Connection refused]
     at oracle.ias.repository.directory.DirectoryReader.connect(DirectoryReader.java:104)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:243)
     at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
]]></SUPPL_DETAIL>
</PAYLOAD>
</MESSAGE>

The <url-pattern> tells the application server which requests are to be handled by the FacesServlet. If the requested URL matches, then the FacesServlet handles the request.
This parameter is not specific to JSF.

Oracle.adf.share.config.ADFConfigFactory No META-INF/adf-config.xml found

I just install jdeveloper10.1.3.3.0 4157, and test ,When I run test ,
display:"oracle.adf.share.config.ADFConfigFactory No META-INF/adf-config.xml found
Please help me how to solve this problem!

Just now I test jdeveloper 11g 4 preview
test project display log:
2008-6-15 22:38:14 oracle.security.jps.internal.config.xml.XmlConfigurationFactory handleLocation
警告: [XmlConfigurationFactory.handleLocation] Exception occurred when handling origLocation=/D:/jdevstudio11114949/j2ee/home/config/system-jazn-data.xml : no protocol: /D:/jdevstudio11114949/j2ee/home/config/system-jazn-data.xml
2008-6-15 22:38:14 oracle.security.jps.internal.config.xml.XmlConfigurationFactory handleLocation
警告: [XmlConfigurationFactory.handleLocation] Exception occurred when handling origLocation=/D:/jdevstudio11114949/j2ee/home/config/system-jazn-data.xml : no protocol: /D:/jdevstudio11114949/j2ee/home/config/system-jazn-data.xml
[JpsAuth] For permisson ( CredentialAccessPermission credstore.provider.credstore.ADF.anonymous#HR001 read), domain that failed: ProtectionDomain cs(file:/D:/jdevstudio11114949/BC4J/lib/adf-share-support.jar), []
BC4J Tester exit code(0)
Message was edited by:
user616170

High redo, log.xml and alert log generation with streams

Hi,
We have a setup where streams and messaging gateway is implemented on Oracle 11.1.0.7 to replicated the changes.
Until recently there was no issue with the setup but for last few days there is an excessive amount of redo and log.xml and alert log generation, which takes up about 50gb for archive log and 20 gb for the rest of the files.
For now we have disabled the streams.
Please suggest the possible reasons for this issue.
Regards,
Ankit

Obviously, as no one here has access to the two files with error messages, log.xml and alert log, the resolution starts with looking into those files
and you should have posted this question only after doing this.
Now no help is possible.
Sybrand Bakker
Senior Oracle DBA

Logging.xml

how could i specify the Custom formatter and handler at logging.xml?
While controlling programmatically, the logger works great and I am getting the perfect log as expected.
How can I do that at design time? I tried in one of the way, here even the file has not been creating it.
In a programmatic way i was able to do it, here i given the example
public static void log(final Level level, final Class obj, final String method, final String message, final Object... params)
FileHandler cfh;
try
cfh = new FileHandler("E:\\11.3\\Oracle\\jdev\\system11.1.1.3.37.56.60\\DefaultDomain\\servers\\DefaultServer\\logs\\mylog.txt");
cfh.setFormatter(new java.util.logging.SimpleFormatter());
cfh.setLevel(level);
ADFLogger aDFLogger = ADFLogger.createADFLogger(obj);
aDFLogger.addHandler(cfh);
aDFLogger.logp(level, obj.getName(), method, message);
aDFLogger.entering(obj.getClass().getName(), method, message);
catch (IOException e)
Here the sample ouput:
Aug 12, 2010 4:27:40 PM org.as.queries.OfficeEventVOImpl About to call service, AS0100F
FINE: Entering ...
Aug 12, 2010 4:27:40 PM org.as.queries.OfficeEventVOImpl About to call service, AS0100F
PERF: Entering ... About to call service, AS0100F
"54N " "SERVER ID " "USERID " "AS0100N " "Web: OfficeEventVOImpl.retArrayFromService():AS0100F " "Start Time : 08/12/2010 16:27:40"
My try with logging.xml which didn't even created a file.
<log_handler name='perf-handler' class='java.util.logging.FileHandler' formatter='java.util.logging.SimpleFormatter' level='ALL'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/perf.log'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
<logger name='org' level="ALL">
<handler name='perf-handler'/>
</logger>

Arun,
I played around a bit with your test case and it reproduces. I surmise the following:
logging.xml is the configuration file for the Oracle Diagnostic Logger, and as such, I infer (it doesn't seem to be documented anywhere) that you can only use the ODL handlers in there (I was able to use other formatters). The logging.properties file (in jre/lib) can use the standard handlers. What I did was to use the ADFLogger in my code - if I configure logging.properties with a file handler, the log message shows up in all of the ODL logging places as well as in the file specified in my FileHandler.
So, although it doesn't appear to be documented anywhere that I can find, if you want to use non-ODL handlers, you can configure them in the standard java.util.Logging configuration file, logging.properties.
John

Strange ADF Log: ACT COMP (QRY)!!!

Hi,
I have activated the ADF log in an ADF Faces application in order to analyse some performance problems it has. I have added the following options to the Java command line:
-Djbo.debugoutput=adflogger -Djbo.adflogger.level=FINE
Then I have seen messages like this one in the log output:
FacturasView3>#q computed SQLStmtBufLen: 2281, actual=2607, storing=2637 ACT > COMP (QRY)!!!
The phrase "ACT > COMP (QRY)!!!" in capital letters and with exclamation signs make me think that it's a warning to alert developers that something bad is happening. I have also seen messages like these one:
MovimientosCtbView4>#q old SQLStmtBufLen: 1170, actual=1079, storing=1109
similar to the first one but without the warning. What does the "ACT > COMP (QRY)!!!" phrase mean?
The performance problems that the we are experiencing with this application consist of high memory and CPU consumption when the application has been running about two hours in a production environment. Sometimes it happens when it has been running less than one hour.
The application was developed by other people, so I don't know if they used bad ADF practices.
Thanks,
Marc

So, the update from development on this is that in order to avoid creating a StringBuffer that we then need to resize numerous times while building up the various parts of a SQL statement, we estimate what the size of the stringbuffer will be and initially allocate it to be that size. If the actual SQL statement created ends up being bigger, then this diagnostic just tells us that our guestimate was under the actual number of characters required to store the whole statement, so in other words, the StringBuffer needed to be grown to accommodate the larger size.
It's not really something to worry about, but if you're interested in helping us improve our estimating algorithm, you can open a service request on Metalink with a simple testcase and ask for the support rep to file a bug for it so we can track down the situation where we've guessed too small for the size of the SQL string.

Error Stack in Expert Routine, Infos about Object Log

Hi all,
currently I try to find some information about using the error stack in combination with an expert routine. So far I know that I have to use the Object Log, which is already in place in my code for monitor messages.
LOOP AT itab_input INTO wa_input.
IF sy-subrc <> 0.
        CLEAR msg.
        msg-msgid = 'MY_CLASS'.
        msg-msgty = 'E'.
        msg-msgno = '002'.
        msg-msgv1 = v1.
        msg-msgv2 = v2.
        msg-msgv3 = v3.
        APPEND msg TO t_msg.
        " ??? Write wa_input to error stack???
        CONTINUE.
      ENDIF.
ENDLOOP.
Does somebody know how I could append wa_input to the error stack? Or does somebody have a good documentation about Object log?
Thanks a lot!
Nita

Good Morning,
thanks a lot for your input. I tried to implement this function, but I do not know where I could get the Segment Id from.
Do you know what i_use_crosstab is used for? I think i_with_message should be set to 'X' if I want to write wa_input-record it to the error stack.
CALL METHOD log->verify_record
          EXPORTING
            i_use_crosstab = ''
            i_segid         = lv_segid
            i_record        = wa_input-record
            i_with_message = 'X'
          RECEIVING
            r_skip          = lv_skip
          EXCEPTIONS
            too_many_errors = 1
            not_in_crosstab = 2
            OTHERS          = 3.
From semantic point of view the coding should do following:
- To avoid a second loop in my expert routine it should only check the current src record. If this is wrong, which I already determine in my coding, it should write the record in the error stack. If it is correct, it should check whether there are already records with the same semantic key in the error stack and if yes, add it also to it.
- I assume that I have to delete this record manually from my src. package than.
Cheers
Nita

Error in the log.xml

Dear oracles gurus,
cannot understand the log file which has been generate when I start the listener I start the listener doing this
[root@rac1 admin]# su - oracle
[oracle@rac1 ~]$ lsnrctl start
LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 07-OCT-2007 02:55:15
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Starting /u01/app/oracle/product/11.1.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 11.1.0.6.0 - Production
System parameter file is /u01/app/oracle/product/11.1.0/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/diag/tnslsnr/rac1/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=rac1.westernsolution.co.uk)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.1.0.6.0 - Production
Start Date 07-OCT-2007 02:55:17
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.1.0/db_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/rac1/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=rac1.westernsolution.co.uk)(PORT=1521)))
The listener supports no services
The command completed successfully
[oracle@rac1 ~]$
the show that the listener is connected but infact their are no listener because when I check my log.xml it says
<msg time='2007-10-07T02:41:05.792+01:00' org_id='oracle' comp_id='tnslsnr'
type= 'UNKNOWN' level='16' host_id='rac1.westernsolution.co.uk' <----------------
host_addr='192.168.122.1'>
<txt>07-OCT-2007 02:41:05 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=rac1.westernsolution.co.uk)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=listener)(VERSION=185599488)) * status * 0
</txt>
</msg>
I really do not understand why it says 'UNKOWN' . I think I have leave a mistake here.
to confirm that my listener is not working I have created a database link and the result are as follows
root@rac1 admin]# sqlplus
bash: sqlplus: command not found
[root@rac1 admin]# su - oracle
[oracle@rac1 ~]$ sqlplus
SQL*Plus: Release 11.1.0.6.0 - Production on Sun Oct 7 03:03:19 2007
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Enter user-name: system/manager
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from emp@local;
select * from emp@local
ERROR at line 1:
ORA-12541: TNS:no listener
SQL>
Please any body can help me to find out what done wrong with the listener by observing the out I have paste above
Regards
sallil chudoory

please close this tar I got the solutionLOL -
This was not a TAR. This was a discussion with the volunteers (mostly non-Oracle employees at that) who use Oracle and are willing to help others.
If this was a TAR, you would have been paying someone for the solution.

How to create adf-settings.xml

hi
The blog post "How to configure an ADF Phase Listener and where to put the file " by Frank Nimphius
at http://blogs.oracle.com/jdevotnharvest/entry/how_to_configure_an_adf_phase_listener_and_where_to_put_the_file
says "... To configure the adf-settings.xml file, create the file as shown below in the .adf\META-INF directory of your application ..."
But how to create a file in the .adf\META-INF directory using JDeveloper seems to have some confusing documentation:
- section "A.5.1 How to Configure for ADF Faces in adf-settings.xml"
at http://docs.oracle.com/cd/E21764_01/web.1111/b31973/ap_config.htm#ADFUI9840
in "Oracle® Fusion Middleware Web User Interface Developer's Guide for Oracle Application Development Framework 11g Release 1 (11.1.1.5.0) Part Number B31973-09 "
says
"To create and edit adf-settings.xml:
1. If not already created, create a META-INF directory for your project.
2. Right-click the META-INF directory, and choose New from the context menu. ..."
Using JDeveloper 11.1.1.5.0 creating a Fusion Web Application (ADF) the .adf\META-INF directory seems to exist, but there does not seem to be a way to "Right-click the META-INF directory, and choose New from the context menu." as documented.
- section "A.5.1 How to Configure for ADF Faces in adf-settings.xml "
at http://docs.oracle.com/cd/E24382_01/web.1112/e16181/ap_config.htm#ADFUI9840
in "Oracle® Fusion Middleware Web User Interface Developer's Guide for Oracle Application Development Framework 11g Release 2 (11.1.2.1.0) Part Number E16181-02 "
says
"To create and edit adf-settings.xml:
1. If not already created, create a META-INF directory for your project in the Application Sources folder (.adf\META-INF).
2. Right-click the META-INF directory, and choose New from the context menu. "
Using JDeveloper 11.1.2.1.0 creating a Fusion Web Application (ADF) there seems to be a ViewController\src\META-INF\adf-settings.xml file created by default. Note that it is not in .adf\META-INF but in ViewController\src\META-INF .
- (q1) What are the specific steps to create adf-settings.xml in the correct location using JDeveloper?
many thanks
Jan Vervecken

Jan,
I am actually testing this with 11g R2 PS2 (upcoming) and for me the adf-settings.xml file is not created, which I am confused of. The 11.1.1.6 documentation has been updated with
*"By default, there is an adf-settings.xml file created for you in the view_project/src/META-INF directory."*
This leaves room for interpretation
i) adf-settings.xml are created in th eproject directory for the reason mentioned in an older thread that this is better for workspaces that contain two projects with controller settings
ii) where there is a "by-default" there must be a non-default, which could indicate the location I used in the blog
The documentation then goes:
To create and edit adf-settings.xml:
If one does not already exist, create a META-INF directory in the src directory of your view project (you will need to do this outside of JDeveloper).
Note:*
If you are using ADF Model in your application, then the directory will already exist in the application_name/.adf directory.*
Which seems odd. Though it confirms the application wide configuration I used, why would you have the default created for the View Layer project and the manual one you create in the application wide configuration. So it seems that there indeed is a missing guidance on where this file should go into.
So it seems you still will have to wait for a final answer on this. Note that adf-settings.xml is not only used by the controller, which may mean you can have multiple locations (and multiple files?). I'll try and do a bit more research on this. For now, as you say the listeners work for you, I suggest you leave them with the ViewLayer project. I am wondering if the adf-settings.xml file gets deployed with an Adf Library (will check this) in which case the right answer would be to save it in the view project.
Frank

Updating defaultTimeout in adf-config.xml through WLST

Hello,
I hope i have this in the right area. I'm cross posting because I think I put it in the wrong place originally. If I get an answer, I'll cross link the two.
I'm trying to change the default, min and maximum timeouts for portlets that come from our WSRP portlet producing application. The documentation I found on the time outs says to edit adf-config.xml 1 and when editing the adf-config.xml do that via WLST ^2^.
1) portlet time out: [http://docs.oracle.com/cd/E17904_01/core.1111/e10108/webcenter.htm#BABIGHDC|http://docs.oracle.com/cd/E17904_01/core.1111/e10108/webcenter.htm#BABIGHDC]
<adf-portlet-config>
<defaultTimeout>5</defaultTimeout>
<minimumTimeout>2</minimumTimeout>
<maximumTimeout>100</maximumTimeout>
<adf-portlet-config>
2) editing adf-config.xml: [http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#WCADM5019|http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#WCADM5019]
I can not find the MBean in the bean browser that seems to hold this setting.
There is a bit of a conflicting message in the docs though. "If you must modify these properties, post deployment, you must edit adf-config.xml manually." But the doc that describes editing adf-config.xml says that using WLST are
So... Questions:
1) Are these three elements (defaultTimeout, minimumTimeout, and maximumTimeout) some exception to being set from WLST?
2) If not, what is the MBean I should find this setting in?
Thank you very much,
Marc
Edited by: MarcDavenport on Jun 26, 2012 12:37 PM

Marc,
This is just a guess(have'nt done this), but I think the settings are not an exception, and you should be able to find the MBean here:
http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_intro.htm#BHCCJJED
This section of the doc seems to walk through an example setting properties in adf-config.xml
I would interpret those instructions in the official doc to mean :
1. If you don't mind changing this at deploy time and re-deploying(like we do when we're in deep development), you can change this and redeploy.
2. If you have a deployed application, you can make changes through WLST. But keep in mind that the changes you make through WLST will not be overwritten later when you change the adf-config in Jdev and redeploy.
(This lets you fine tune the timeouts for specific environments. ex: bigger timeouts for dev envs hosted with smaller resources/unstable un-optimized code, rather than guess a timeout that works for all environments )
Now comes the conflicting parts :
"If you must modify these properties, post deployment, you must edit adf-config.xml manually."
I think,they mean "manually using WLST". This can probabaly be done with both WLST commands and the MBeans.
Now once you make these changes to a deployed application, the changes you made are stored in MDS. This means that this "tuning" will survive a re-deployment.
So if we :
set the timeout to 1 minute initially at design time,
then change that to 5 minutes through WLST,
and then edit adf-config again in Jdev to a 10 minute value and redeploy,
the MDS still has the 5 minute value, and it will overwrite the 10 minute value we set later at design time and redeployed.
MDS documents are always applied on top of the deployed stuff.
The doc you refered to : http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#CHDGEDGJ
does make a good explanation of how the changes persisted in MDS affects the final configuration.
Hop that helps !

About ADF logging.xml

Similar Messages

Maybe you are looking for