Trace Messages

I am investigating issue with authenticating with WinRM (CredSSP) and I've followed the procedure described in this blog:
http://blogs.technet.com/b/jonjor/archive/2009/01/05/how-to-capture-a-winrm-trace.aspx
However, I do not get any meaningful information in the records, the only thing I can see is "No Format Information found"
Stoimen

Hi Stoimen,
Based on your description, I understand that you follow the method in
the article to capture a WinRM trace. However, it seems that don’t provide any helpful information.
Would you please let me know whether that both two methods in that article didn’t help you? Both just show
"No Format Information found"?
Meanwhile, would you please let me confirm whether have repeated the process of
creating WinRM trace session for both client and server? When start the trace sessions, have you reproduced the issue which you want to
investigate? Just for confirmation, thanks for your understanding.
In addition, you can find the Windows Remote Management events were logged in Event Viewer. Please follow the
path:
Application and Services Logs-> Microsoft-> Windows-> Windows Remote Management. Check if can find some related events.
If anything I misunderstand or any update, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

Similar Messages

  • Unable to see custom Trace messages in Log Viewer which were defined in UDF

    Hello Experts, I am not able to see my trace messages in Log Viewer. I have a small user defined fuction which takes a variable and returns its uppercase and while do that it writes few warning level trace messages in the trace file. I've tried changing the levels from Warning to Info but I still don't see anything in my Log Viewer. At this point I am not even sure if I am looking at right place. When I test my mapping in Message Mapping's Test tab it works fine and shows me all my trace messages. But when I do end to end it is not writing anything to the trace file. I've tried to use instructions from following blogs:
    1. /people/michal.krawczyk2/blog/2007/04/30/xipi-personalized-logging-tracing(logging and tracing)
    2. /people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni (logging and tracing)
    3. /people/michal.krawczyk2/blog/2005/02/25/simple-java-code-in-graphical-mapping--xi(for my UDF)
    but I still don't see traces in my Log Viewer. Please let me know if I am doing anything wrong here.
    Thanks in advance!!
    ==============================================================
    public String TraceVar(String var1, Container container) throws StreamTransformationException{
    AbstractTrace importanttrace; //create an instace of AbstractTrace
    importanttrace = container.getTrace(); //get trace
    importanttrace.addWarning("FiletoFileMP:MyUdflibrary: " + var1); //write first message to the trace
    // fix the naming conventions later
    String SenderName; // declare multiple vars to store infos
    String ReceiverName;
    String interface_name;
    String message_ID;
    String time_Sent;
    java.util.Map map;
    map = container.getTransformationParameters();
    //get interface info into the variables
    time_Sent = (String) map.get(StreamTransformationConstants.TIME_SENT);
    message_ID = (String) map.get(StreamTransformationConstants.MESSAGE_ID);
    interface_name = (String) map.get(StreamTransformationConstants.INTERFACE);
    SenderName = (String) map.get(StreamTransformationConstants.SENDER_NAME);
    ReceiverName = (String) map.get(StreamTransformationConstants.RECEIVER_NAME);
    //post interface info to the trace
    importanttrace.addWarning("Time Sent: " + time_Sent);
    importanttrace.addWarning("Message ID: " + message_ID);
    importanttrace.addWarning("Interface Name: " + interface_name);
    importanttrace.addWarning("Sender Name: " + SenderName);
    importanttrace.addWarning("Receiver Name: " + ReceiverName);
    //convert var1 to uppercase to make sure this function has be executed
    return var1.toUpperCase();
    Edited by: Mayur Patel on May 5, 2009 11:03 PM

    Thank you Prateek for a quick response.
    Yes I was able to see my trace messages in SXMB_MONI. Below is my the info... This is great. I am still not sure why this info is not showing up in Log Veiwer's (default trace) window. Any ideas? Since this XML file contains lots of other information I was wondering how to put my trace messages into the log viewer.
    Thanks!!
      <Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
      <Trace level="2" type="T">FiletoFileMP:MyUdfLibrary: Honda</Trace>
      <Trace level="1" type="T">FiletoFileMP:MyUdfLibrary: Honda</Trace>
      <Trace level="1" type="T">Time Sent: 2009-05-05T16:16:39Z</Trace>
      <Trace level="1" type="T">Message ID: 366CEAF14D3B410033AFDDB71CD2AF73</Trace>
      <Trace level="1" type="T">Interface Name: SIC_Car_Outbound</Trace>
      <Trace level="1" type="T">Sender Name: SIC_Car_Outbound</Trace>
      <Trace level="1" type="T">Receiver Name: SI_Car_Inbound</Trace>
      <Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>

  • How to put the trace messages in JSP DynPage

    Hi,
    How to put the trace messages in JSP DynPage components. What settings I need to do and where do I see the trace log.
    Can I also print the values of some variables in trace. If yes, how to achieve this?
    Thanks in advance,
    Regards,
    Madhu

    Hi Madhu,
    for NW04 see http://help.sap.com/saphelp_nw04/helpdata/en/e2/75a74046033913e10000000a155106/frameset.htm
    as well as
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/using logging and tracing on the sap web as java.pdf
    Hope it helps
    Detlev

  • [svn:fx-4.x] 14570: Using method in AutomationManager to trace messages

    Revision: 14570
    Revision: 14570
    Author:   [email protected]
    Date:     2010-03-03 22:02:16 -0800 (Wed, 03 Mar 2010)
    Log Message:
    Using method in AutomationManager to trace messages
    QE notes: All trace messages in delegates that showed up while debugging should show class and method name in addition to actual message
    Doc notes:
    Bugs:
    Reviewer:
    Tests run: checkintests
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/branches/4.x/frameworks/projects/automation/src/mx/automation/codec/AutomationOb jectPropertyCodec.as
        flex/sdk/branches/4.x/frameworks/projects/automation/src/mx/automation/codec/RendererProp ertyCodec.as
        flex/sdk/branches/4.x/frameworks/projects/automation/src/mx/automation/delegates/TextFiel dAutomationHelper.as
        flex/sdk/branches/4.x/frameworks/projects/automation/src/mx/automation/delegates/controls /SWFLoaderAutomationImpl.as
        flex/sdk/branches/4.x/frameworks/projects/automation/src/mx/automation/delegates/core/UIC omponentAutomationImpl.as
        flex/sdk/branches/4.x/frameworks/projects/automation/src/mx/automation/delegates/core/UIT extFieldAutomationImpl.as
        flex/sdk/branches/4.x/frameworks/projects/automation/src/mx/automation/tabularData/OLAPDa taGridTabularData.as
        flex/sdk/branches/4.x/frameworks/projects/automation_air/src/mx/automation/delegates/cont rols/FlexNativeMenuAutomationImpl.as
        flex/sdk/branches/4.x/frameworks/projects/automation_dmv/src/mx/automation/delegates/adva ncedDataGrid/AdvancedDataGridAutomationImpl.as
        flex/sdk/branches/4.x/frameworks/projects/automation_spark/src/mx/automation/delegates/co re/UIFTETextFieldAutomationImpl.as
        flex/sdk/branches/4.x/frameworks/projects/automation_spark/src/spark/automation/delegates /components/supportClasses/SparkDropDownListBaseAutomationImpl.as
        flex/sdk/branches/4.x/frameworks/projects/automation_spark/src/spark/automation/delegates /components/supportClasses/SparkListBaseAutomationImpl.as
        flex/sdk/branches/4.x/frameworks/projects/automation_spark/src/spark/automation/tabularDa ta/SparkListBaseTabularData.as

    Thanks Balusc!!
    I have made use of your code to display PDF files in an IFRAME tag too!!! I just dint believe that this would be possible. Please just take a look at my JSP page.
    <h:form id="CaseLookUp">
         <%
         String path = request.getContextPath()+"";
         out.print(path);
         %>
    <iframe scrolling="auto" src="<%=path%>/imageServlet?file=D:\70-229 V5.pdf" width="80%" height="600" ></iframe>
         </h:form>

  • Can anyone help how to print stack trace messages using log4j?

    Can anyone help how to print stack trace messages using log4j?

    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
    <log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>
    <appender name="STDOUT" class="org.apache.log4j.ConsoleAppender">
    <layout class="org.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="%d %-5p %m%n"/>
    </layout>
    </appender>
    <appender name="DEBUG" class="org.apache.log4j.RollingFileAppender">
    <param name="File" value="/usr/local/dice/d2jbin/cmdToNetJobs/app-debug.log"/>
    <param name="Append" value="true"/>
    <param name="MaxFileSize" value="1000KB"/>
    <param name="MaxBackupIndex" value="5"/>
    <layout class="org.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="%d %-5p %m%n"/>
    </layout>
    <filter class="org.apache.log4j.varia.LevelRangeFilter">
    <param name="LevelMin" value="DEBUG" />
    <param name="LevelMax" value="DEBUG" />
    </filter>
    </appender>
    <appender name="INFO" class="org.apache.log4j.RollingFileAppender">
    <param name="File" value="/usr/local/dice/d2jbin/cmdToNetJobs/app-info.log"/>
    <param name="Append" value="true"/>
    <param name="MaxFileSize" value="1000KB"/>
    <param name="MaxBackupIndex" value="5"/>
    <layout class="org.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="%d %-5p %m%n"/>
    </layout>
    <filter class="org.apache.log4j.varia.LevelRangeFilter">
    <param name="LevelMin" value="INFO" />
    <param name="LevelMax" value="INFO" />
    </filter>
    </appender>
    <appender name="WARN" class="org.apache.log4j.RollingFileAppender">
    <param name="File" value="/usr/local/dice/d2jbin/cmdToNetJobs/app-warn.log"/>
    <param name="Append" value="true"/>
    <param name="MaxFileSize" value="1000KB"/>
    <param name="MaxBackupIndex" value="5"/>
    <layout class="org.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="%d %-5p %m%n"/>
    </layout>
    <filter class="org.apache.log4j.varia.LevelRangeFilter">
    <param name="LevelMin" value="WARN" />
    <param name="LevelMax" value="WARN" />
    </filter>
    </appender>
    <appender name="ERROR" class="org.apache.log4j.RollingFileAppender">
    <param name="File" value="/usr/local/dice/d2jbin/cmdToNetJobs/app-error.log"/>
    <param name="Append" value="true"/>
    <param name="MaxFileSize" value="1000KB"/>
    <param name="MaxBackupIndex" value="5"/>
    <layout class="org.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="%d %-5p %m%n"/>
    </layout>
    <filter class="org.apache.log4j.varia.LevelRangeFilter">
    <param name="LevelMin" value="ERROR" />
    <param name="LevelMax" value="ERROR" />
    </filter>
    </appender>
    <root>
    <priority value="debug"/>
    <!--<appender-ref ref="STDOUT"/>
    --><appender-ref ref="DEBUG"/>
    <appender-ref ref="INFO"/>
    <appender-ref ref="WARN"/>
    <appender-ref ref="ERROR"/>
    </root>
    </log4j:configuration>
    I ve written like this
    and to print stack trace I used
    log.error(Throwable(e))
    but does nt display printstacktrace how to do it

  • Disabling Trace Message

    Is there any way to disable the BI-BEANS trace/debuging message? I have clear the option "Show Message" from BI Designer Run-Setting, but I still have the TRACE message appear ...
    tx,
    sjarif

    Hi,
    Not sure which trace messages you are referring to? The only messages I have seen are:
    1) Running jdev.exe creates a background window that records a lot of diagnostic and feedback information. In Windows environments this can be removed by runing jdevw.exe program.
    2) Within JDev there is a Messeage Log window. When you run/debug a BIBeans application from within JDeveloper disgnostic and any stack trace information is writted to this window. This information is very useful as it allows you to monitor your application. This can be removed by closing the Message Log window.
    Both these are only available via JDevloper and will not be visible when the application is deployed to your user community.
    Keith Laker
    Product Manager
    Oracle Business Intelligence Beans

  • Dispalaying Trace message in sxmb_moni from UDF

    Dear Experts,
    This is regarding displaying the Trace produced by  User Defined Function in SXMB_MONI.
    I ve used a UDF in my scenario and am quite able to see the Warning Message(Trace) in the Test Environment for Message mapping.For that I ve used method trace.addWarning(" Warning Message ").
    The TRACE_LEVEL  parameter has been set to 3 in SXMB_ADM->Integration Engine Configuration->Edit->Change Specific Configuration Data.
    But I'm not getting any Warning Message any where under SXMB_MONI.
    Please suggest in this regard.
    Regards,
    Navneet

    Hi Navneet,
    You may try using Message Bar:
    More is here: http://help.sap.com/saphelp_nw04s/helpdata/en/c0/9e0e41a346ef6fe10000000a1550b0/frameset.htm
    Plz don forget points, if it helped
    Regards,
    Pragathi.

  • JCO3 How to set trace path or catch trace message

    In old Jco can setTracePath
    http://help.sap.com/javadocs/NW04/current/jc/com/sap/mw/jco/JCO.html#setTracePath(java.lang.String)
    but in JCO 3 how can do that ?
    I found http://help.sap.com/saphelp_nw70ehp1/helpdata/en/f6/daea401675752ae10000000a155106/content.htm
    JCO trace
    name
    JCO*.trc
    location
    directory j2ee/cluster/server* or defined path
    how to switch on and off
    set JVM options for the server via the Config Tool and restart server: -Djco.trace_level=[0-10],-Djco.trace_path=[defined_path]
    any other methods?

    Hey Jacky,
    Please browse the API of class com.sap.conn.jco.JCo. There is a method call setTrace.
    public static void setTrace(int level,  java.lang.String path)
    Turns on the JCo trace. Allowed levels are [0 .. 10]. The common used are:
    0 - nothing
    1 - errors and warnings
    2 - execution path, errors and warnings
    3 - full execution path, errors and warnings
    4 - execution path, info messages, errors and warnings
    6 - full execution path, info messages, errors and warnings
    7 - debug messages, full execution path, info messages, errors and warnings
    8 - verbose debug messages, full execution path, info messages, errors and warnings
    As path value null, stdout, stderr or an existing path are allowed. If path is equals null or stdout or stderr JCo will trace out to the standard output (error) stream. If at least one JCoTraceListener is registered, the trace output will be sent to the listener only. To redirect the JCo trace into a file, the path value has to be set to an existing directory.
    Parameters:
    level - [0 .. 10]
    path - null, stdout, stderr or an existing path

  • Ocssd trace messages 11g/linux

    2 node 11g rac on OEL 5.3 , all seems ok but there is a lot of weird messages in
    ocssd.log (about 500000 lines per day). They repeat every second or so.
    Is this normal 11g crs behaviour ?
    [    CSSD]2009-05-11 00:53:35.030 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:35.116 [1219053888] >TRACE: clssgmDeadProc: proc 0x23d1470
    [    CSSD]2009-05-11 00:53:35.116 [1219053888] >TRACE: clssgmDestroyProc: cleaning up proc(0x23d1470) con(0x23cd140) skgpid ospid 14057 with 0 c
    lients, refcount 0
    [    CSSD]2009-05-11 00:53:35.686 [1219053888] >TRACE: clssgmGroupState: requested group state of group DBPROD, member count 2
    [    CSSD]2009-05-11 00:53:36.579 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:37.131 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:37.132 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:38.590 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:39.228 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:39.228 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:39.269 [1177094464] >TRACE: clssnmSendingThread: sending status msg to all nodes
    [    CSSD]2009-05-11 00:53:39.269 [1177094464] >TRACE: clssnmSendingThread: sent 5 status msgs to all nodes
    [    CSSD]2009-05-11 00:53:40.594 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:41.248 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:41.248 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:42.682 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:43.345 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:43.345 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:43.497 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(3) src(1) dest(2) size(420) tag(0085004c) incarnation(13224
    5734)
    [    CSSD]2009-05-11 00:53:43.497 [1124645184] >TRACE: clssgmHandleMasterAdd(): src(1) dest(2) size(420)
    [    CSSD]2009-05-11 00:53:43.497 [1124645184] >TRACE: clssgmHandleMasterAdd(): grock(SRVM.DATABASE.NODEAPPS.cylon1) memberNo(-1) node(1) type(3)
    [    CSSD]2009-05-11 00:53:43.497 [1124645184] >TRACE: clssgmAddMember: granted member(0) flags(0x1) node(1) grock (0x2aaaac328920/SRVM.DATABASE.
    NODEAPPS.cylon1)
    [    CSSD]2009-05-11 00:53:43.497 [1124645184] >TRACE: clssgmCommonAddMember: global lock grock SRVM.DATABASE.NODEAPPS.cylon1 member(0/Remote) no
    de(1) flags 0x1 0x1
    [    CSSD]2009-05-11 00:53:43.511 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(4) src(1) dest(2) size(352) tag(0086004c) incarnation(13224
    5734)
    [    CSSD]2009-05-11 00:53:43.511 [1124645184] >TRACE: clssgmHandleMasterExit(): src(1) dest(2) size(352)
    [    CSSD]2009-05-11 00:53:43.511 [1124645184] >TRACE: clssgmRemoveMember: grock SRVM.DATABASE.NODEAPPS.cylon1, member number 0 (0x2aaaac107060)
    node number 1 state 0x0 member refcnt 1 grock type 3
    [    CSSD]2009-05-11 00:53:44.279 [1177094464] >TRACE: clssnmSendingThread: sending status msg to all nodes
    [    CSSD]2009-05-11 00:53:44.279 [1177094464] >TRACE: clssnmSendingThread: sent 5 status msgs to all nodes
    [    CSSD]2009-05-11 00:53:44.686 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:45.446 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:45.446 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:45.727 [1219053888] >TRACE: clssgmGroupState: requested group state of group DBPROD, member count 2
    [    CSSD]2009-05-11 00:53:46.684 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:47.534 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:47.534 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:48.702 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:49.279 [1177094464] >TRACE: clssnmSendingThread: sending status msg to all nodes
    [    CSSD]2009-05-11 00:53:49.279 [1177094464] >TRACE: clssnmSendingThread: sent 5 status msgs to all nodes
    [    CSSD]2009-05-11 00:53:49.647 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:49.647 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:50.198 [1219053888] >TRACE: clssgmAllocProc: (0x23d1470) allocated
    [    CSSD]2009-05-11 00:53:50.199 [1240033600] >TRACE: Connect request from user root
    [    CSSD]2009-05-11 00:53:50.200 [1219053888] >TRACE: clssgmClientConnectMsg: properties of cmProc 0x23d1470 - 1,2,3
    [    CSSD]2009-05-11 00:53:50.200 [1219053888] >TRACE: clssgmClientConnectMsg: Connect from con(0x23cef30) proc(0x23d1470) pid(14217) version 11:
    1:1:4
    [    CSSD]2009-05-11 00:53:50.212 [1219053888] >TRACE: clssgmRegisterClient: proc(70/0x23d1470), client(1/0x23d1c00)
    [    CSSD]2009-05-11 00:53:50.213 [1219053888] >TRACE: clssgmExecuteClientRequest: GRKJOIN recvd from client 1 (0x23d1c00)
    [    CSSD]2009-05-11 00:53:50.213 [1219053888] >TRACE: clssgmJoinGrock: global grock SRVM.DATABASE.NODEAPPS.cylon2 new client 0x23d1c00 with con
    0x23caab0, requested num -1
    [    CSSD]2009-05-11 00:53:50.213 [1219053888] >TRACE: clssgmAddGrockMember: adding member to grock SRVM.DATABASE.NODEAPPS.cylon2
    [    CSSD]2009-05-11 00:53:50.213 [1219053888] >TRACE: clssgmAddMember: granted member(0) flags(0x1) node(2) grock (0x23d1d70/SRVM.DATABASE.NODEA
    PPS.cylon2)
    [    CSSD]2009-05-11 00:53:50.213 [1219053888] >TRACE: clssgmQueueGrockEvent: lockName(SRVM.DATABASE.NODEAPPS.cylon2) type(2) count (1/1) xwaiter
    s(0) event(1) to memberNo(0)
    [    CSSD]2009-05-11 00:53:50.213 [1219053888] >TRACE: clssgmCommonAddMember: global lock grock SRVM.DATABASE.NODEAPPS.cylon2 member(0/Local) nod
    e(2) flags 0x1 0x1
    [    CSSD]2009-05-11 00:53:50.223 [1219053888] >TRACE: clssgmExecuteClientRequest: GRKEXIT recvd from client 1 (0x23d1c00)
    [    CSSD]2009-05-11 00:53:50.223 [1219053888] >TRACE: clssgmExitGrock: client 1 (0x23d1c00), grock SRVM.DATABASE.NODEAPPS.cylon2, member 0
    [    CSSD]2009-05-11 00:53:50.223 [1219053888] >TRACE: clssgmUnregisterPrimary: Unregistering member 0 (0x23d2070) in global grock SRVM.DATABASE.
    NODEAPPS.cylon2
    [    CSSD]2009-05-11 00:53:50.223 [1219053888] >TRACE: clssgmRemoveMember: grock SRVM.DATABASE.NODEAPPS.cylon2, member number 0 (0x23d2070) node
    number 2 state 0x14 member refcnt 0 grock type 3
    [    CSSD]2009-05-11 00:53:50.430 [1219053888] >TRACE: clssgmDeadProc: proc 0x23d1470
    [    CSSD]2009-05-11 00:53:50.430 [1219053888] >TRACE: clssgmDestroyProc: cleaning up proc(0x23d1470) con(0x23cef30) skgpid ospid 14217 with 0 c
    lients, refcount 0
    [    CSSD]2009-05-11 00:53:50.699 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:51.666 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:51.666 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:52.796 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1
    [    CSSD]2009-05-11 00:53:53.666 [1124645184] >TRACE: clssgmDispatchCMXMSG: msg type(13) src(1) dest(2) size(123) tag(00000000) incarnation(1322
    45734)
    [    CSSD]2009-05-11 00:53:53.666 [1124645184] >TRACE: clssgmHandleDataInvalid: grock HB+ASM, member 1 node 1, birth 3
    [    CSSD]2009-05-11 00:53:54.279 [1177094464] >TRACE: clssnmSendingThread: sending status msg to all nodes
    [    CSSD]2009-05-11 00:53:54.279 [1177094464] >TRACE: clssnmSendingThread: sent 5 status msgs to all nodes
    [    CSSD]2009-05-11 00:53:54.889 [1219053888] >TRACE: clssgmExecuteClientRequest: Received data update request from client (0x2aaaac0c68a0), typ
    e 1

    Yes. It is normal. By default cssd logging is enabled at level 2 in 11g.
    Thanks,
    Jomon

  • Event trace message

    hi,experts
    In swel,  the message  says:"The OPEN_DI of BTE 00002214 could not determine any function module."
    so ,how to solve the problem ?

    Open SWE2 and check whether can you find your workflow under the Receiver Type and beside to that you will se a column with name Type Linkage see whether that check box is enabled or not if it is not enabled then double clcik on it and a new screen will appear in that you check the chekc box Linkage Activated

  • How to trace the message in which line of program used?

    Dear fellows,
           Many times when we run a t-code (especially standard t-code), it will return many message log. but when we debug the t-code to trace the error message, it is difficult to find why raise this error message. Even we can not find in which line of program. We can not use the where-to-used list in SE91 to trace, because it is not written like this:       message 033(FD) TYPE E.
           For example in validation(GGB0)  we use some message, but when this message come out, we didn't know this message in which program raise.  And it also can not be traced using message at in debug mode.
           In many case, the way of using message is not easy to be trace , but if we can find which line of program to raise this message, would help a lot for finding the cause problem.
           Is there any tool for us to trace message ?
           Thanks for your sincerely answer!

    Hello All,
    If the message log is filled like this
      L_S_MSG-MSGTY     = 'E'.
      L_S_MSG-MSGID     = 'BL'.
      L_S_MSG-MSGNO     = '303'.
      L_S_MSG-MSGV1     = '007'.
    Can you trace this message by putting a watch-point/break point? I guess no! If some has YES as answer, please feel free to correct me.
    That is why whenever filling a message log/return table it is important that we ensure that the message can be traced back using "where-used". Hence the usage of MESSAGE...INTO (or the pre-historic, IF 1 = 2 ... MESSAGE ... ENDIF) construct.
    BR,
    Suhas

  • Format message while using idocscript trace method

    could anyone please tell me how to format text (new lines, tab, bold) while using
    <$trace("<message>""#log")$>
    is this even supported?

    Can't help you with bold... think of this as really plain text output.  If you try to put in HTML tags, they just get escaped.
    You can use "\t" for tabs, and "\n" for a new line.
    <$trace("This is \t a tab. \n This is a new line.", "#log")$>

  • 'System Error' status at Message Monitoring( HTTP to FILE )

    I have created a scenario HTTP to FTP. I sent message to XI server using the HTTP Client.
    After sending the message I am getting the response at browser.
    Result:
    http-Status:  200 Message accepted
    Payload:
    But when I look in to the Message monitoring at RWB, I am getting the message status as
    System error. while going to the details i can see below error category.
    Error Category       MAPPING
    Error Code      EXCEPTION_DURING_EXECUTE
    (Is the password different for port 50000 and 8000)
    Please help me to solve this issue.
    Thanks in Advance,
    John

    This is the trace message that I got for this error
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46)</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:72) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>

  • Outputting error messages in a browser?

    Is there a way to output all error messages to some sort of
    window when viewing a SWF in a browser? I'm working on a game and
    I'm about to beta test with a few dozen people. They will do this
    by playing the game in a browser. Sometimes the game crashes and it
    would be great if the error message that accompanies the crash
    could be shown, so they can copy and paste it to me in an email.
    This way i dont have to play the game over and over in the flash
    IDE to try and re-create the problem.
    I know you can output trace messages to a javascript window,
    but what i need to do is output ALL error messages to a window of
    some sort. Any ideas or advice would be appreciated.
    -Miles Tilmann, Programmer, Pixeljam Games
    (pixeljam.com)

    Okay i answered my own question. For anyone who is looking to
    beta test their SWF with other people, this might be helpful..
    everything in the program is controlled by one mainLoop
    function. so i just enclosed that mainLoop function within a try {}
    statement. then right after that i did:
    catch (e:Error) {
    //some code that puts the String (e.getStackTrace()) on the
    screen
    e.getStackTrace() will create a string that gives you the
    detailed error message. HOWEVER... this will not work within a
    browser. it will only work within the standalone flash player. so
    i'm just going to have people download that stand alone player and
    beta test the game outside the browser. or create a
    self-executable.
    if you need to have it within a browser, i think the most you
    can get back for an error message is the type of error (example:
    ReferenceError 1069). you can get that by showing e.message or
    e.toString(). i cant seem to get it to pass any more information
    about it. and when the program is huge, those errors arent very
    helpful.

  • Message lost during Message Send in weblogic 9.2 JMS

    I am using Weblogic Server 9.2 in a clustered environment (2 nodes in separate machines). The application deployed has ejb timers which picks up data from DB, and sends text messages (very small size as its just an ID) to a Queue (using the JMS APIs - QueueSender.send(message)). There is an MDB (with max-beans-in-free-pool) configured to be 20 listenting to this message. There might be 1-20 records picked up from the DB and the id of those records will be sent to the JMS Queue as separate JMS messages. i.e. QueueSender.send will be called as many times as there are record ids to send. The timer after sending the message to the queue sets the status of all the data it picked up to "Busy" in the same transaction as the message send. We are using XA driver and the JMS Connection factory is also XA enabled. We had problems with this XA transaction as weblogic sometimes sends the messages and before db commit happened to set the status to "Busy". We had a workaround to this problem by setting the JMS Connection factory setting "time to Deliver" to 300 so that the messages are visible to the MDB only after 300 ms thereby giving time for db commit to be over as per the suggestion in the following link. http://jayesh-patel.blogspot.com/. We had done this 2 months back and to date we find no problem.
    Now we are facing another strange problem. The JMS sometime misses delivering the messages. This is evident from the logs we had printed from the MDB. The logs indicate some messages has reached the MDB and some did not. This problem occurs occasionally. Also what I see is that this had occured under normal load conditions only though this application operates under high loads (number of messages being processed per day may go up to 5000). In the last one month this had occured 3 times. The JMS messaging is becoming unreliable.
    This seems to be a bug in Weblogic 9.2 JMS. Is there any workaround to prevent this problem. ?

    It is doubtful that JMS is losing messages. Suggestions:
    * Try increasing your sheduled message delay. 300 millis is a short delay -- any small network glitch, disk hardware issue, or even a single JVM GC in the JDBC driver can cause the database to take longer than 300 millis to complete its part of the transaction.
    * Try "WebLogic JMS Message Lifecycle Logging" if you want to trace message activity.
    * Instead of the delay, consider using WebLogic's Datasource "LLR" option, a commonly used solution to your use case. This is an optimization option that yields fully ACID (safe) transactions, and has the very nice side effect of deterministically forcing the TM to always commit the database portion of a transaction before committing any other resources participating in the same transaction.
    Links:
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jms_admin/troubleshoot.html
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jta/llr.html#LLRfailover
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jdbc_admin/jdbc_datasources.html#llr
    Tom
    Edited by: TomB on May 7, 2010 5:20 PM

Maybe you are looking for