Debug mesages not logged in log file

Hi,
I have a situatuion where a CP invokes a stored procedure. Within it, I have a few debug messages to log scenarios. Using FND_FIL.put_line(Fnd_file.log,...........
I have checked that the system Profile values at site level are as under
FND: Debug Log Enabled = No
FND: Debug Log Level = Statement
FND: Debug Log Mode = Asynchronous with Cross-Tier Sequencing
FND: Debug log Module = %
These values are NOT set at Application, Responsibility or User Level. Meaning they are all blank for these options.
Should we be setting the Debug Log Enabled to 'Yes' at User Level. I am unable to set it even with System Administrator responsibility.
How do I get to see the debug messages in the View Log window after completion of CP?
Thanks
uds

Hi,
I had also faced similar issue.
Try giving this way.
Give this inside the doperform
     IsaLocation log =IsaLocation.getInstance(com.sap.isa.core.BaseAction.class.getName());
Hope this helps
Regards
Antony

Similar Messages

  • Debug info to log file

    G'day,
              I have jsp which I am attempting to write some debug info to the log
              using out.println(...) java statement.
              My question is how do I make it go to the weblogic log file as opposed
              to my html page ?
              Any help would be appreciated.
              Cheers
              Glenn Torepe
              

    Why can't you use ServletContext.log()? I've been using that all the
              time.
              John Salvo
              Nils Winkler wrote:
              >
              > That will not work. System.out.println will only go to the console
              > window, but not to the log file.
              >
              > You have to use the class weblogic.logging.LogOutputStream. AFAIK this
              > class is not documented, but you can use "javap" to get an overview.
              > Here's a quick example:
              >
              > ---
              > import weblogic.logging.LogOutputStream;
              >
              > // in some method
              > LogOutputStream los = new LogOutputStream("Test");
              >
              > los.error("Error in method");
              >
              > los.close();
              > ---
              >
              > This will log the text "Error in method" to the log file as an error,
              > "Test" is used as an additional identifier, like this:
              >
              > Fri Oct 06 12:17:38 EDT 2000:<E> <Test> Error in method
              >
              > Hope that helps,
              >
              > Nils
              >
              > On 9 Oct 2000 14:29:16 -0800, Dimitri Rakitine <[email protected]>
              > wrote:
              >
              > >Use System.out.println(...);
              > >
              > >Ian Grosvenor <[email protected]> wrote:
              > >> G'day,
              > >
              > >> I have jsp which I am attempting to write some debug info to the log
              > >> using out.println(...) java statement.
              > >
              > >> My question is how do I make it go to the weblogic log file as opposed
              > >> to my html page ?
              > >
              > >> Any help would be appreciated.
              > >
              > >> Cheers
              > >
              > >> Glenn Torepe
              > >
              > >Dimitri
              >
              > Nils Winkler
              > iXL, Inc.
              > [email protected]
              

  • Server crash due to lot of debug statements in log file during deployment

    I am facing problem while deployment of my application
    I am using log4j api and its in debug mode as following
    log4j.rootCategory=DEBUG, A2
    log4j.appender.A2=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.A2.file=D:/logs/directory.log
    log4j.appender.A2.datePattern='.'yyyy-MM-dd'.txt'
    log4j.appender.A2.append=true
    log4j.appender.A2.layout=org.apache.log4j.PatternLayout
    log4j.appender.A2.layout.ConversionPattern=%d %-5p [%t] - %m%n
    I am getting lot of debug statements when i am deploying the application and result is server crash
    can anyone help me?
    some of the debug statements are :
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - ignorableWhitespace()
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - ignorableWhitespace(
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - ignorableWhitespace( )
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - endElement(,field,field)
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - match='form-validation/formset/form/field'
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - bodyText=''
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire body() for ObjectCreateRule[className=org.apache.commons.validator.Field, attributeName=className]
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire body() for SetPropertiesRule[]
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire body() for SetNextRule[methodName=addField, paramType=org.apache.commons.validator.Field]
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Popping body text ''
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire end() for SetNextRule[methodName=addField, paramType=org.apache.commons.validator.Field]
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - [SetNextRule]{form-validation/formset/form/field} Call org.apache.commons.validator.Form.addField(          key= null
              property= pct_other_project_3_last_yr
              indexedProperty= null
              indexedListProperty= null
              depends= required
              page= 0
              fieldOrder= 0
              Vars:
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Matching name=addField on class org.apache.commons.validator.Form
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Found straight match: public void org.apache.commons.validator.Form.addField(org.apache.commons.validator.Field)
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - isPublic:true
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire end() for SetPropertiesRule[]
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire end() for ObjectCreateRule[className=org.apache.commons.validator.Field, attributeName=className]
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - [ObjectCreateRule]{form-validation/formset/form/field} Pop org.apache.commons.validator.Field
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - ignorableWhitespace()
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - ignorableWhitespace(
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - ignorableWhitespace()
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - ignorableWhitespace(
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - ignorableWhitespace( )
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - startElement(,field,field)
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Pushing body text ''
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - New match='form-validation/formset/form/field'
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire begin() for ObjectCreateRule[className=org.apache.commons.validator.Field, attributeName=className]
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - [ObjectCreateRule]{form-validation/formset/form/field}New org.apache.commons.validator.Field
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire begin() for SetPropertiesRule[]
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - [SetPropertiesRule]{form-validation/formset/form/field} Setting property 'property' to 'pct_se_prev_yr_2'
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - [SetPropertiesRule]{form-validation/formset/form/field} Setting property 'depends' to 'required'
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - [SetPropertiesRule]{form-validation/formset/form/field} Set org.apache.commons.validator.Field properties
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - BeanUtils.populate(          key= null
              property= null
              indexedProperty= null
              indexedListProperty= null
              depends= null
              page= 0
              fieldOrder= 0
              Vars:
    , {property=pct_se_prev_yr_2, depends=required})
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - setProperty(          key= null
              property= null
              indexedProperty= null
              indexedListProperty= null
              depends= null
              page= 0
              fieldOrder= 0
              Vars:
    , property, pct_se_prev_yr_2)
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Convert string 'pct_se_prev_yr_2' to class 'java.lang.String'
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Using converter org.apache.commons.beanutils.converters.StringConverter@1d86a73
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - setProperty(          key= null
              property= pct_se_prev_yr_2
              indexedProperty= null
              indexedListProperty= null
              depends= null
              page= 0
              fieldOrder= 0
              Vars:
    , depends, required)
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Convert string 'required' to class 'java.lang.String'
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Using converter org.apache.commons.beanutils.converters.StringConverter@1d86a73
    2005-09-16 09:36:19,000 DEBUG [scheduler-1] - Fire begin() for SetNextRule[methodName=addField, paramType=org.apache.commons.validator.Field]

    The only suggestions I have off the top of my head are:
    * Ensure (1) the host system has at least 2GB (file store size) of free physical memory in addition to the memory used by current processes, and (2) the host system is not rebooted between each WebLogic restart. If you make sure of these two items, then the operating system will implicitly cache the store's file contents in memory even between boots -- when WebLogic subsequently boots the file store, the O/S should serve the file contents up much more quickly.
    * Consider moving to a JDBC store. JDBC store runtime performance is lower, but since you have a typically only have a small amount of records to recover, boot performance should be higher in this case.
    * Not that it helps your particular case, but it happens that we have boot performance enhancements in process for a future release (hopefully a near future release).
    Tom

  • OPM과 OM ISSUE 해결을 위해 LOG FILE을 생성 및 검색하는 방법

    제품 : MFG_OM
    작성날짜 : 2005-11-09
    OPM과 OM ISSUE 해결을 위해 LOG FILE을 생성 및 검색하는 방법
    ===========================================================
    PURPOSE
    Customer에게 Oralce Processing Manufacturing(OPM)/Order Management(OM)
    issue 해결을 위해 Log file을 생성하고 검색하는 방법을 알고 이를 고객에게
    전달할 수 있다.
    Explanation
    OPM 고객이 Order process 중 fail이 발생 했을 경우,fails 된 Order process
    에 따라 우리는 관련된 log file을 받기를 원한다.
    예를 들면;
    a) Order pad에 문제가 있다면 사용자는 Tools > Debug을 'On'으로 setting
    함으로써 log file을 생성할 수 있다.
    이는 Order pad 자체에서 행할수 있고 좀 더 자세한 사항은 아래의 step2 에
    설명되어져 있다.
    b) 만약 pick release가 fails 된다면 OPM support는 'pick release
    generation' concurrent manager log file을 요구하게 된다.
    좀 더 자세한 사항은 아래 step4 에 설명되어져 있다.
    c) 만약 Transact process move order form(manual allocation screen)의
    allocation 작업이나 pick confirm이 fails 이라면 support는 생성되는
    OPMLOG***를 받기를 원할 것이다.
    좀 더 자세한 사항은 아래 step5 에 설명되어져 있다.
    d) 만약 Order Management/Inventory Interface가 fail 이라면 support는
    'Interface Trip Stop' concurrent 실행중에 생성된 log file을 받기를 원할
    것이다. 자세한 사항은 step5 에 설명되어져 있다.
    OM/OPM issues를 위한 Log files의 생성 및 검색 방법
    1. utl_file_dir parameter 값을 얻기 위해 아래의 sql을 실행한다.
    select value
    from v$parameter
    where name like 'utl_file_dir';
    2. OM: Debug Directory profile option 값으로 step1의 결과값이 setting
    되어져 있는지 확인한다.
    3. Order pad에서 log file 생성:
    1) OM: Debug level profile을 '5'로 setting
    2) Order pad에서 Tools > Debug를 ON, lof file name을 적어 놓는다.
    3) Issue를 재현하고 step1 결과로 나온 경로에서 log file을 검색한다.
    4. Pick release concurrent log file을 생성하기 위해서는 profile option
    OM: Debug level을 '5' setting 후 pick release를 concurrent manager
    mode로 수행한다.
    Application의 view requests 화면에서 log file을 검색할 수 있다.
    5. Transact move order form에서 'manual allocation' 진행시의 log file을
    생성하기 위해서 아래의 steps을 따른다.
    1) Step2에서 지정한 경로에서 'OPMLOG****' file을 remove 한다.
    2) Manual allocation을 수행한다.
    3) 'OPMLOG***' log file이 생성될 것이며, '****'는 session id 값이다.
    Session id 값은 application 화면의 Help > Tools > Examine의
    $Profiles/db_session_id 위에서 찾을 수 있다.
    4) Pick confirm에 관련된 log는 2)번 step을 제외하고, pick confirm을
    수행하여 생성할 수 있다.
    6. Interface Trip Stop(ITS)가 실행되는 중의 log file을 생성하기 위해서는
    OM: Debug level profile option 값을 Interface Trip Stop을 실행하기
    전에 '5'로 setting 한다.
    Interface Trip Stop을 실행하기전에 'Defer' checkbox가 uncheck 되어
    있는지 확인해야 하며, 이 log file은 Application의 view requests 화면
    에서 검색할 수 있다.
    Reference Documents
    Note 290069.1

  • ORA-00316 in the alert log file

    Thu Aug 21 17:23:05 2008
    Errors in file /ora_dump/CONCILIA/bdump/concilia_arc1_205172.trc:
    ORA-00316: log 3 of thread 1, type 0 in header is not log file
    ORA-00312: online log 3 thread 1: '/ora_data04/CONCILIA/redo01.log'
    Thu Aug 21 17:23:05 2008
    Errors in file /ora_dump/CONCILIA/bdump/concilia_arc1_205172.trc:
    ORA-00316: log 3 of thread 1, type 0 in header is not log file
    ORA-00312: online log 3 thread 1: '/ora_data04/CONCILIA/redo01.log'
    $

    It looks like your redo log might be corrupted.
    Check the content of trc file and work with Oracle support.
    00316, 00000, "log %s of thread %s, type %s in header is not log file"
    // *Cause:  The online log is corrupted or is an old version.
    // *Action: Find and install correct version of log or reset logs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • How to know the history of shrinking log files in mssql

    hello,
    In my SAP system some one shrinked the log file to 100 GB to 5 GB.How we would check when this
    was shrinked recently .
    Regards,
    ARNS.

    hi,
    Did u check the logfile in sapdirectory.There will be entry of who changed the size and the time.
    Also,
    Goto the screen where we usually change the logfile size.In that particular field press f1 and goto technical setting screen. Get the program name , table name  and field name.
    Now using se11 try to open the table and check whether the changed by value is there for that table.
    Also open the program and debug at change log file process block.use can see in which table it update the changes.
    There is a case of caution in this case.
    The size of the application server's System Log is determined by the
    following SAP profile parameters. Once the current System Log reaches
    the maximum file size, it gets moved to the old_file and and a new
    System Log file gets created. The number of past days messages in the
    System Log depends on the amount/activity of System Log messages and the
    max file size. Once messages get rolled off the current and old files,
    they are no longer retrievable.
    rslg/local/file /usr/sap/<SID>/D*/log/SLOG<SYSNO>
    rslg/local/old_file /usr/sap/<SID>/D*/log/SLOGO<SYSNO>
    rslg/max_diskspace/local 1000000
    rslg/central/file /usr/sap/<SID>/SYS/global/SLOGJ
    rslg/central/old_file /usr/sap/<SID>/SYS/global/SLOGJO
    rslg/max_diskspace/central 4000000  .

  • AFP log file - how to log file moving

    Hi all,
    I am trying to find out who moved file from one folder to another on share point. I've noticed that AFP service do not log file moving/copying.
    It is not a big deal, but will be nice to find this information.
    Any ideas?
    Thanks!

    Sure you can do that or, if you want
    without stopping, only do this in the command line
    *>oc4j_default_island...whatever...1.log*
    and it will put the file size in 0.
    the *>* will sent input of nothing into the file, deleting all existing data, witout lossing the file lock.
    And like 20 post earlier we have discuss about the rotation of oc4j log files under opmn.
    Regards.

  • Finding virusscan log files

    I'm running McAfee VirusScan for Mac. Yesterday it would not update, saying "could not write to ini file". I believe there's a log file somewhere that's full, but I cannot find where it's storing the log files. Any ideas? Thanks in advance.

    There are two standard locations for log files: /Home/Library/Logs/ and /Library/Logs/. You should open the Console application in the Utilities folder to see if the log files are available there.
    .ini files are not log files but rather initialization files. They may be stored elsewhere such as the /Home/Library/Preferences/ folder or a folder in /Home/Library/Application Support/. Also check for a folder in /Library/Application Support/ and /Library/Preferences/.

  • Debug info from ZAction not visible in log file

    Hi,
    i am trying to see debug info from my Z ActionClass in the log file. Debug messages from the standard actions from crm~avw applicaiton are visible. My ZAction is in the package com.customer and i have maintained this entry in VisualManager\LogManager in property SingleTraceFile_UnrestrictedLcoations. Part of the code is pasted below. Pls help.
    public class ZAction extends BaseAction {
          private static final IsaLocation log = IsaLocation.getInstance(ZAction.class.getName());
             public ZAction()
              public ActionForward doPerform(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response)
                  throws ServletException, IOException
                log.debug("Entered ZAction");

    Hi,
    I had also faced similar issue.
    Try giving this way.
    Give this inside the doperform
         IsaLocation log =IsaLocation.getInstance(com.sap.isa.core.BaseAction.class.getName());
    Hope this helps
    Regards
    Antony

  • Log file not generated

    i follow the steps
    1.In Application Set profile FND: Debug Log Level to "Statement"
    2.restart apache
    3.Run debug from help-->diagnostics-->debug
    4.Secure debug log file which should be in
    select value from v$parameter where name like 'utl_file%'
    but the is no log file created i dont know why (these steps are provided by an SR)
    thnx

    What about "FND: Debug Log Filename for Middle-Tier" and "FND: Diagnostics" profile options?
    Note: 372209.1 - How to Collect an FND Diagnostics Trace (aka FND:Debug)
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=372209.1
    If the above does not help, set the debug log at the user level and check then.
    Note: 390881.1 - How To Set The Debug Log At User Level?
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=390881.1

  • Unable to debug the Data Template Error in the Log file

    Hi,
    I am unable to debug the log file error message Please can anybody explain me in detail where the error lies and how to solve the error.The log file shows the following message.
    XDO Data Engine ver 1.0
    Resp: 50554
    Org ID : 204
    Request ID: 2865643
    All Parameters: USER_ID=1318:REPORT_TYPE=Report Only:P_SET_OF_BOOKS_ID=1:TRNS_STATUS=Posted:P_APPROVED=Not Approved:PERIOD=Sep-05
    Data Template Code: ILDVAPDN
    Data Template Application Short Name: CLE
    Debug Flag: Y
    {TRNS_STATUS=Posted, REPORT_TYPE=Report Only, PERIOD=Sep-05, USER_ID=1318, P_SET_OF_BOOKS_ID=1, P_APPROVED=Not Approved}
    Calling XDO Data Engine...
    java.lang.NullPointerException
         at oracle.apps.xdo.dataengine.DataTemplateParser.getObjectVlaue(DataTemplateParser.java:1424)
         at oracle.apps.xdo.dataengine.DataTemplateParser.replaceSubstituteVariables(DataTemplateParser.java:1226)
         at oracle.apps.xdo.dataengine.XMLPGEN.writeData(XMLPGEN.java:398)
         at oracle.apps.xdo.dataengine.XMLPGEN.writeGroupStructure(XMLPGEN.java:281)
         at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:251)
         at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:192)
         at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:222)
         at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:334)
         at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:236)
         at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:272)
         at oracle.apps.fnd.cp.request.Run.main(Run.java:148)
    Start of log messages from FND_FILE
    Start of After parameter Report Trigger Execution..
    Gl Set of Books.....P
    Organization NameVision Operations
    Entering TRNS STATUS POSTED****** 648Posted
    end of the trns status..687 Posted
    currency_code 20USD
    P_PRECISION 272
    precision 332
    GL NAME 40Vision Operations (USA)
    Executing the procedure get format ..
    ExecutED the procedure get format and the Result..
    End of Before Report Execution..
    End of log messages from FND_FILE
    Executing request completion options...
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 2865643 on node AP615CMR at 28-SEP-2006 07:58:26.
    Post-processing of request 2865643 failed at 28-SEP-2006 07:58:38 with the error message:
    One or more post-processing actions failed. Consult the OPP service log for details.
    Finished executing request completion options.
    Concurrent request completed
    Current system time is 28-SEP-2006 07:58:38
    Thanks & Regards
    Suresh Singh

    Generally the DBAs are aware of the OPP service log. They can tell you the cause of the problem.
    Anyway, how did you resolve the issue?

  • Error/Warning Messages in Agent Debug Log Files

    I have noticed the following error message in the Agent Debug Log Files and was wondering if anybody could shed any light on their meaning or what might be causing them.
    Warning 1855:####### ServiceEngine: Service::getPolicyResult():No passwd value in session response.
    Warning 1855:####### PolicyAgent: Access Manager Cookie not found.
    Error 1855:####### AM_SSO_SERVICE: SSOTokenService::getSessionInfo(): Error 18 for sso token ID <SSO_TOKEN_ID>

    hi
    Looks like the message numbers you are processing in the function module CRM_MESSAGE_COLLECT are only for 'errors'.
    Please go to Transaction: CRMC_MSGS
    Look at the following Application Areas
    CRM_ORDER
    CRM_ORDERADM_H
    CRM_ORDERADM_I
    CRM_ORDER_MISC
    CRM_ORDER_OUTPUT
    Select one of the above and double click 'Single Messages' towards your left side on the screen. Select the relavant message number from the list and check the 'S' flag. Press 'F1' (help) on this box and you will see the following.
    Only error messages are saved in the processing log. If a message definitely should be saved - contrary to this rule - then the indicator needs to be set.
    You need to make sure that a message marked like this can be deleted again - by calling up the function module CRM_MESSAGES_DELETE in the appropriate place in the program.
    When you do these steps, please note the message 'Do not make any changes (SAP data)'. This is not tested and used from my side. Please see if this impacts other functions. I am not sure. Do necessary R&D before you proceed further. Please explore tables CRMC_MESSAGES_S and CRMC_MESSAGES and see if this helps.
    Reward if helps
    Regards
    Manohar

  • How to easily export/download "Debugging & Logging Log Files" data?

    In the Debugging & Logging > Log Files screen/page, are there workarounds for easily export/download the data that's listed in that screen? I do not want to download the log. Basically, all I want is the table that shows the File Name, Type Size, and Last Modified information.
    Thank you,
    Charlie

    Not really, but if you copy and paste the table and stick it in ms word or something it will retain its layout, you can then just save it, or just take a screenshot. It all depends on what you planning on using the export for. Why do you need that information specifically, this will depend on the way to do it. If its something you want often and automatically then you can just generate the information yourself using some Coldfusion and the logs directory.

  • How best to manipulate a log file that is not well-formed

    I have a text file that look something like this:
    [21/06/07] System DEBUG * BA_LOG_OUTPUT
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text <?xml version=�1.0� encoding=�UFT-8�?>
    <note>
    <to>Tove</to>
    <from>Jani</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </note>
    [21/06/07] System DEBUG * BA_LOG_OUTPUT
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text <?xml version=�1.0� encoding=�UFT-8�?>
    <note>
    <to>Tony</to>
    <from>James</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </note>
    [21/06/07] System DEBUG * BA_LOG_OUTPUT
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text <?xml version=�1.0� encoding=�UFT-8�?>
    <note>
    <to>Amy</to>
    <from>Tobi</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </note>I am trying to read the file so that it picks the welled formed XML and put it through a SAX parser. For example, it should pick out the following before putting into a SAX parser: <?xml version=�1.0� encoding=�UFT-8�?>
    <note>
    <to>Tove</to>
    <from>Jani</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </note>
    <?xml version=�1.0� encoding=�UFT-8�?>
    <note>
    <to>Tony</to>
    <from>James</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </note>
    <?xml version="1.0" encoding="UTF-8"?>
    <note>
    <to>Amy</to>
    <from>Tobi</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </note>There is a pattern in the file, the line
    <?xml version=�1.0� encoding=�UFT-8�?>Always start on the 4th line after BA_LOG_OUTPUT line
         public void readFile(){
              String line = null;
              Pattern p = Pattern.compile( "BA_LOG_OUTPUT" );
              Pattern p1 = Pattern.compile( "[" );
              try{
                   while( ( line = br.readLine() ) != null ){
                        Matcher m = p.matcher(line);
                        while( m.find() ){
                             for(int i = 0; i < 5; i++ ){
                                  line = br.readLine();
                             System.out.println(line);     
              }catch( Exception e ){
                   System.err.println( e.getMessage() );
         }In the code above, I can find where I want to read from, but how do I make the code so that it read the rest of the xml save them in stack (which would eventually be passed to SAX parser) and stop when it find the pattern [.
    Find the next pattern in the file (BA_LOG_OUTPUT), read the whole xml which start 4 line after the pattern, save it on the stack, stop reading when it find the pattern [.  and so on.
    It should continue to do the same throughout the file.

    The solution may work but the problem is a bit more complicated than that. The example I gave above is just an example. In the real log file, the tags are never the same, so you may have something that look like this:
    [21/06/07] System DEBUG * BA_LOG_OUTPUT
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text <?xml version=�1.0� encoding=�UFT-8�?>
    <note>
    <to>Tove</to>
    <from>Jani</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </note>
    [21/06/07] System DEBUG * BA_LOG_OUTPUT
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text <?xml version=�1.0� encoding=�UFT-8�?>
    <partone>
    <todiff>Tony</todiff>
    <from>James</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </partone>
    [21/06/07] System DEBUG * BA_LOG_OUTPUT
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text
    System DEBUG Random text  Random text <?xml version=�1.0� encoding=�UFT-8�?>
    <anothertag>
    <anothername>Amy</anothername>
    <from>Tobi</from>
    <heading>Reminder</heading>
    <body>Don't forget me this weekend!</body>
    </anothertag >In this case, I cannot use the loop
                while(!(line = in.readLine()).equals("</note>")) {
                    System.out.println(line);
                }How can i make this work?

  • Log file does not exist

    I have recently installed p6.8 and when I try to view my log after I have scheduled the project I get a message that my "SCHEDLOG.TXT does not exist", I've hit the elliptical button and created the file path that I want the file stored in but, when I try to view the log that is the message I get.

    Before clicking on the Log tab, be sure that you have the process diagram selected in the panel above it. Inside the Log tab there is a refresh button inside the tab - be sure to click this button to refresh the view of the log file entries.
    Your log file is stored where your project is stored. Not to be confused with the end user "Workspace", Eclipse (the IDE Studio uses) stores it's project is a folder also called the workspace. This is determined by the dialog box with the name of the file folder you select when Studio first initializes. You'll be able to find the log files for your project in this directory:
    C:\<your Workspace folder>\<your project's name>\system
    Finally, once you find your log file you'll notice hundreds of Engine DEBUG statements are stored in it that make diagnosing what is happening almost impossible. Take a look at this link to see how to resolve this problem.
    Re: How to create a new instance of a global activity
    Hope this helps,
    Dan

Maybe you are looking for