Solution Manager Monitoring Table Size

Hi Gurus!
Question for you!
Is there a way to monitor the size of a table, or even the number of registers that it has, or anything like it?
The problem is that in several ocasions the size of tables gets too big that we end up having to delete old information or archive them, and I wanted to know about this before it becomes a problem.
Thanks in advance and BR,
Lucas

Hello,
Did you check this link http://help.sap.com/saphelp_nw70/helpdata/en/f0/02a63b9bb3e035e10000000a114084/frameset.htm on sap Help portal.
Hope this will help.
Regards,
Benjamin

Similar Messages

  • Display "system description" in Solution Manager monitoring info

    Hi,
    We have maintained the "system description" info for our satellite systems in SMSY:
    http://screencast.com/t/OTNmMjFiM
    Is there any way to display this info in the Solution Manager monitoring info?? Without this description text and only with system "SID" info it is very difficult for our IT Managers to identify each system...
    For example, in the monitoring Work Center (System Status tab), is there any way to add the "system description" as a column? We didn't find it any way to insert it...
    Example: http://screencast.com/t/ZGU0ZjJk
    Is there any way too in the SL Reports to include  the "system description" info in the system overview?
    Example: http://screencast.com/t/ZDg4MGIyYj
    Without this info it is really difficult for our IT Managers (from the NWBC) to manage the Solution Manager info and it is only useless for the IT Administrators...
    Thanks in advance,
    Jon

    Hello,
    You can run report RSMSY_REPORTING01 to get the details that you are looking for you will have to work with the selection criteria.
    Chad

  • Can Solution Manager monitor TIBCO system

    Hi there, can solution manager be configured to monitor TIBCO system - such as if certain services is running on TIBCO, check it's file system size, read files and check for Errors...etc?
    Cecilia

    Hi Craig:
    More questions. Would Solution Manager 3.2 or 4.0 be able to do it without the adapter?
    Regards
    Cecilia

  • Solution Manager monitoring of Standalone Gateway.

    I have been advised this is possible with the sapccmsr, which we have running on our java estate, I have registered the program, and seem to be having a problem getting it to recognise the fact there is anything to monitor?
    We have Aix 5.3
    SAP gateway is from the Netweaver 2004s kernel.
    SAPCCMSR is
    CCMS version  20040229, 64 bit, multithreaded, Unicode
          compiled at   Aug 24 2008
          systemid      324 (IBM RS/6000 with AIX)
          relno         7000
          patch text    patch collection 2008/3, OSS note 1129577
          patchno       175
    Solution manager is patch
    ST     400     0016     SAPKITL426     SAP Solution Manager Tool
    ST-PI     2005_1_700     0006     SAPKITLQI6     SAP Solution Tools Plug-In
    Not sure why, any ideas?

    Hi Paul,
    I would suggest to move this thread to the general SolMan forum, because it's not a VAR specific question.
    Do you agree?
    Best regards,
    Ruediger

  • Solution Manager Monitoring

    Hi Everyone,
    Please can anyone provide me some suggestions for how is solution manager being used to monitor the system?
    Like what all we can use early watch reports etc.
    Thanks in advance.
    Regards,
    Avneesh

    Hi Holger,
    You gave me the best response i was expecting for.
    Thanks for the help.
    Regards,
    Avneesh

  • Send Solution Manager monitor data to ITM (IBM Tivoli Manager)

    Hi all,
    I've recently installed a SAP Solution Manager 7.1 SP10 system in order to replace the old Solution Manager 7.0 system. The old system was (also) used for (CCMS) monitoring. A subset of the gathered data was sent to ITM (company policy and mandatory). With SolMan 7.1 SAP has drastically changed the way they monitor. CCMS/RZ20 (agent based) is no longer used (although it is still possible).
    In the TX /nSOLMAN_SETUP I've done the "System Preparation", "Basic Configuration", "Managed System Configuration" and "Technical monitoring", installed the CA Wily introscope EM, Bytecode agents etc. I can see monitoring data in my Solution Manager system.
    My question now is, how can I get (a subset of my) monitoring data from my Solution Manager system into ITM? How can I select only the for ITM relevant data, for instance file system full or failed database backup?
    Many thanks!
    /Marcel Kuijper

    Hi Marcel,
    Pelase check out the How-to guides at the following SAP link:
    http://wiki.scn.sap.com/wiki/display/TechOps/System+Monitoring+-+How-to+Guides
    and SAP note 1965064 - SolMan 7.10 SP10 - MAI OS/SNMP Adapters
    Regards,
    Roland

  • Solution Manager - Monitoring - Instance Status

    HI all, 
    I'm trying to configure in "setup system monitoring" the alert on "Instance Status" but  is always in staus "Alert is active but not accessible".  
    The others alerts work fine. 
    I have already configured the ccmsping in rz21 and in rz20 everything is ok. 
    Thanks in advance for any suggestions, 
    Andrea

    Hi,
    If you want to monitor the Availability status of the instance then check the below docs
    [http://help.sap.com/saphelp_nw70/helpdata/EN/38/9e100dd7980fffe10000009b3810a5/frameset.htm]
    [CCMSPING config|http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/d547f687-0901-0010-07a9-ce64cc044215]
    [CCMS Agent config|http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/40ef0688-814a-2a10-afb1-89b40d83d0e0]
    regards
    Naveen
    Edited by: Naveen Kumar on Dec 15, 2009 1:07 PM

  • Solution Manager System Monitoring of a CE 7.10

    Hi
    I am trying to setup a Solution Manager Monitoring Solution for a CE 7.10 Enviroment.
    I have already setup CEN in SOLMAN.
    I have registered CE Systems with a sapccmsr j2ee agent.
    I have setup the JCO RFC Connection in CE.
    I have created the TCP/IP Connection to the JCO Connection in Solman.
    I have set the TCP/IP Connection in RZ21 as the J2EE Customizing Destination.
    The solution involves only 1 Logical Component with 3 CE Systems.
    When I go to the solution manager setup and try to configure the MTE Nodes for my solution I cannot get the MTE context while clicking in Activate Monitoring for other Software Components
    I choose Java Application Server, choose my server, choose CEn but when i have to choose the context of the MTE i get an empty list.
    IF i go Activate Monitoring for Other Servers and choose the server I get the contexts of the remote server, but I can only choose one.
    So how can I see the context of the CE servers in the Software component part?
    Ty.

    Hi,
    Have you defined and added corresponding logical systems for the respective satellite systems?
    Here is the sequence of steps you've to do:
    in SMSY:
    1) Define server, DB, Systems
    2) Generate READ, TMW, TRUSTED RFCs to the satellite systems
    3) define logical systems and assign the satellite system to it
    in Solution_Manager:
    1) define new solution
    2) add the logical system into the solution
    If these steps are successful, you should be able to see the satellite system in SYSTEM MONITORING in Solution_Manager.
    Have you already done these steps?
    After performing these steps:
    Solution_Manager>choose relevant solution>operations setup>Solution Monitoring>System monitoring>Activate monitoring> choose the system and activate monitoring.
    Your system will then appear.
    Does this help any way?

  • SOLUTION MANAGER- alert doesn't exist or not accesible now

    I execute transaction solution_manager and I chose productive system in the User defined Alert I created alert "Erroneous Fax & e-Mail (client 300)" and I copy in the Alert long name MTE name which I obtained form rz20 source monitoring system and ... so on
    It sould work but in one system I received "alert doesn't exist or not accesible now"
    Can somebody help
    Thanks

    Hi,
    Can you provide me the solution for this issue. Even i am facing the same issue while configuring the solution manager monitoring set up.
    Thanks in Advance
    Suresh

  • Solution Manager generated link

    Hello,
    Solution Manager has a "generate" button that generates a URL for documents within the Solution Manager structure.
    Below is an example of a URL that are generated from Solution Manager.
    http://sapbsp02.weyer.com:08005/sap/bc/solman/SolmanDocuments/301?_CLASS=SOLARGEN&_LOIO=451472FAD7F04A44E10000000A52F3D5&LANGUAGE=EN&RELEASE=620&IWB_INDUSTRY=/KWCUST/&TMP_IWB_TRY_OTHER_IND=X&TMP_IWB_TASK=PREVIEW2&
    <b><i>Do you know where within Solution Manager the table is located?</i></b>
    Many Thanks,
    Jay

    Hi Jay,
    you are looking for the table where the document is
    stored? Well, i have not found it yet but in my opinion
    it has to be somewhere in the knowledge warehouse.
    The tables SA01PHIO (physical information object -
    document versions) and SA01LOIO (logical information
    object - document attributes within the structure e.g.
    SOLAR01/SOLAR02) contain the document attributes such as
    creation date and GUID etc.
    Hint: Look at the others SA01* tables.
    Best regards
    Danilo
    Message was edited by:
            Danilo Adam

  • Solution Manager Alerts

    Hi SAP Experts,
    I am working on SAP R/3 4.6C version. We have Solution Manager monitoring the systems. The Solutions Manager keeps sending the alert messages about the working status of the system. The Alerts are as follws:
    - Oracle Buffers Buffer cache
    - Dialog ResponseTime
    -  Dialog FrontendResponseTime
    -  Dialog DBRequestTime
    -  Dialog Dialog FrontEndNetTime
    -  Dialog LongRunners
    -  Paging Page_In
    -  Paging Page_Out
    -  CPU_Utilization
    Can anyone tell me the reason for these alerts and the solutions that need to implement to fine tune the system to avoid these Alerts.
    Your help will be greatly aprreciated.
    Regards
    Vanitha Dorcas

    Hi,
    Have you performed an EWA ? It should contain a brief suggestion about each issue.
    Br,
    Javier

  • System Monitoring with Solution Manager Ehp1

    Hi,
    I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
    Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
    Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
    when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
    <SID>_RZ20_COLLECT
    <SID>_RZ20_ANALYZE
    I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
    <SID>_RZ20_COLLECT_123539Error when opening an RFC connection
    Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
    Error during remote call of SALC function: Error when opening an RFC connection
    Error during remote call of RFC1 function: Error when opening an RFC connection
    I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
    Please, Could you help me?
    Thanks and regards,
    Tomas.

    Tomas,
    I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system).  I downloaded the lates ccmsagent file from the market place based my target system configurations.
    Herewith attaching the logs while I'm trying to check the profile parameter.
    tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    ================================================================================
    ==   Checking profile:     /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    ================================================================================
    ***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
    ***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
    ***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
    ***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
    ***WARNING: Unexpected parameter: dbs/io_buf_size =100000
    ***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
    ***WARNING: Unexpected parameter: rsau/selector1/class =35
    ***WARNING: Unexpected parameter: rsau/selector1/severity =2
    ***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
    ***ERROR: Size of shared memory pool 40 too small
    ================================================================
    SOLUTIONS: (1) Locate shared memory segments outside of pool 40
                   with parameters like: ipc/shm_psize_<key> =0
    SOLUTION: Increase size of shared memory pool 40
              with parameter: ipc/shm_psize_40 =1472000000
    Shared memory disposition overview
    ================================================================
    Shared memory pools
    Key:   10  Pool
                Size configured.....:   642000000 ( 612.3 MB)
                Size min. estimated.:   637597428 ( 608.1 MB)
                Advised Size........:   640000000 ( 610.4 MB)
    Key:   40  Pool for database buffers
                Size configured.....:  1048000000 ( 999.4 MB)
                Size min. estimated.:  1468229308 (1400.2 MB)
                Advised Size........:  1472000000 (1403.8 MB)
    Shared memories inside of pool 10
    Key:        1  Size:        2500 (   0.0 MB) System administration
    Key:        4  Size:      523648 (   0.5 MB) statistic area
    Key:        7  Size:       14838 (   0.0 MB) Update task administration
    Key:        8  Size:    67108964 (  64.0 MB) Paging buffer
    Key:        9  Size:   134217828 ( 128.0 MB) Roll buffer
    Key:       11  Size:      500000 (   0.5 MB) Factory calender buffer
    Key:       12  Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
    Key:       13  Size:   200500000 ( 191.2 MB) Alert Area
    Key:       16  Size:       22400 (   0.0 MB) Semaphore activity monitoring
    Key:       17  Size:     2672386 (   2.5 MB) Roll administration
    Key:       30  Size:       37888 (   0.0 MB) Taskhandler runtime admin.
    Key:       31  Size:     4806000 (   4.6 MB) Dispatcher request queue
    Key:       33  Size:    39936000 (  38.1 MB) Table buffer, part.buffering
    Key:       34  Size:    20480000 (  19.5 MB) Enqueue table
    Key:       51  Size:     3200000 (   3.1 MB) Extended memory admin.
    Key:       52  Size:       40000 (   0.0 MB) Message Server buffer
    Key:       54  Size:    20488192 (  19.5 MB) Export/Import buffer
    Key:       55  Size:        8192 (   0.0 MB) Spool local printer+joblist
    Key:       57  Size:     1048576 (   1.0 MB) Profilparameter in shared mem
    Key:       58  Size:        4096 (   0.0 MB) Enqueue ID for reset
    Key:       62  Size:    85983232 (  82.0 MB) Memory pipes
    Shared memories inside of pool 40
    Key:        2  Size:    31168040 (  29.7 MB) Disp. administration tables
    Key:        3  Size:   114048000 ( 108.8 MB) Disp. communication areas
    Key:        6  Size:  1064960000 (1015.6 MB) ABAP program buffer
    Key:       14  Size:    28600000 (  27.3 MB) Presentation buffer
    Key:       19  Size:    90000000 (  85.8 MB) Table-buffer
    Key:       42  Size:    13920992 (  13.3 MB) DB TTAB buffer
    Key:       43  Size:    43422392 (  41.4 MB) DB FTAB buffer
    Key:       44  Size:     8606392 (   8.2 MB) DB IREC buffer
    Key:       45  Size:     6558392 (   6.3 MB) DB short nametab buffer
    Key:       46  Size:       20480 (   0.0 MB) DB sync table
    Key:       47  Size:    13313024 (  12.7 MB) DB CUA buffer
    Key:       48  Size:      300000 (   0.3 MB) Number range buffer
    Key:       49  Size:     3309932 (   3.2 MB) Spool admin (SpoolWP+DiaWP)
    Shared memories outside of pools
    Key:       18  Size:     1792100 (   1.7 MB) Paging adminitration
    Key:       41  Size:    25010000 (  23.9 MB) DB statistics buffer
    Key:       63  Size:      409600 (   0.4 MB) ICMAN shared memory
    Key:       64  Size:     4202496 (   4.0 MB) Online Text Repository Buf.
    Key:       65  Size:     4202496 (   4.0 MB) Export/Import Shared Memory
    Key:     1002  Size:      400000 (   0.4 MB) Performance monitoring V01.0
    Key: 58900130  Size:        4096 (   0.0 MB) SCSA area
    Nr of operating system shared memory segments: 9
    Shared memory resource requirements estimated
    ================================================================
    Nr of shared memory descriptors required for
    Extended Memory Management (unnamed mapped file).: 64
    Total Nr of shared segments required.....:         73
    System-imposed number of shared memories.:       1000
    Shared memory segment size required min..: 1472000000 (1403.8 MB)
    System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
    Swap space requirements estimated
    ================================================
    Shared memory....................: 2050.4 MB
    ..in pool 10  608.1 MB,   99% used
    ..in pool 40  999.4 MB,  140% used !!
    ..not in pool:   34.4 MB
    Processes........................:  716.8 MB
    Extended Memory .................: 8192.0 MB
    Total, minimum requirement.......: 10959.2 MB
    Process local heaps, worst case..: 1907.3 MB
    Total, worst case requirement....: 12866.5 MB
    Errors detected..................:    1
    Warnings detected................:    9
    After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
    Pls have a look at these two and let me know what could I do to proceed further.
    tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
    INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
    INFO: Central Monitoring System is [SMP]. (found in config file)
          additional CENTRAL system y/[n] ?   :
    INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
    INFO:
          CCMS version  20040229, 64 bit, multithreaded, Non-Unicode
          compiled at   Jun 28 2010
          systemid      324 (IBM RS/6000 with AIX)
          relno         6400
          patch text    patch collection 2010/1, OSS note 1304480
          patchno       335
    INFO Runtime:
          running on    saptqa01 AIX 3 5 00069A8FD600
          running with profile   /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    INFO profile parameters:
          alert/MONI_SEGM_SIZE = 200000000
          alert/TRACE          = 1
          SAPSYSTEM            = 30
          SAPSYSTEMNAME        = TQA
          SAPLOCALHOST         = saptqa01
          DIR_CCMS             = /usr/sap/ccms
          DIR_LOGGING          = /usr/sap/TQA/DVEBMGS30/log
          DIR_PERF             = /usr/sap/tmp
    INFO:
          pid           4165682
    INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
    INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct  3 2008,  kernel 6400_20020600_254,  platform 324 (IBM RS/6000 with AIX)]
            segment status     ENABLED
            segment started at Tue Sep 14 09:35:56 2010
            segment version    20040229
    ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
           Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
           Please change configuration with profile parameters
               ipc/shm_psize_01 = -<different pool nr>
           xor
               ipc/shm_psize_13 = -<different pool nr>
    EXITING with code 1

  • Java process table empty after upgrade solution manager 7.1 Sp10

    Hi Experts,
    I have installed solution manager 7.1 SP3 and completed the SP10 patch upgrade using SUM tool. The upgrade was completed successfully. After upgrade igswd was red. Then i copied the Igs files in kernel files. Now ABAP instance and Igs is working now but JAVA is not coming up. JAVA process table also empty. Can any one help me to solve this issue. Attached the error for reference.
    trc file: "dev_disp", trc level: 1, release: "721"
    sysno      00
    sid        VSM
    systemid   562 (PC with Windows NT)
    relno      7210
    patchlevel 0
    patchno    201
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
    pid        5448
    kernel runs with dp version 138000(ext=120000) (@(#) DPLIB-INT-VERSION-138000-UC)
    length of sys_adm_ext is 592 bytes
    *** SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (00 5448) [dpxxdisp.c   1316]
      shared lib "dw_xml.dll" version 201 successfully loaded
      shared lib "dw_xtc.dll" version 201 successfully loaded
      shared lib "dw_stl.dll" version 201 successfully loaded
      shared lib "dw_gui.dll" version 201 successfully loaded
      shared lib "dw_mdm.dll" version 201 successfully loaded
      shared lib "dw_rndrt.dll" version 201 successfully loaded
      shared lib "dw_abp.dll" version 201 successfully loaded
      shared lib "dw_sym.dll" version 201 successfully loaded
      shared lib "dw_aci.dll" version 201 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    rdisp/dynamic_wp_check : 1
    rdisp/calculateLoadAverage : 1
    Tue Apr 01 19:02:09 2014
    *** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 6 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  6479]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    display_tcp_ip: 0
    DpIPCInit2: write dp-profile-values into sys_adm_ext
    DpIPCInit2: start server >VKCSOL_VSM_00                           <
    DpShMCreate: sizeof(wp_adm) 42864 (2256)
    DpShMCreate: sizeof(tm_adm) 5517056 (27448)
    DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
    DpShMCreate: sizeof(appc_ca_adm) 64000 (64)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080
    DpShMCreate: sizeof(comm_adm) 1384080 (2744)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm) 0 (296)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm) 0 (80)
    DpShMCreate: sizeof(vmc_adm) 0 (2160)
    DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
    DpShMCreate: sizeof(gw_adm) 48
    DpShMCreate: sizeof(j2ee_adm) 3952
    DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000DDE0050, size: 7174832)
    DpShMCreate: allocated sys_adm at 000000000DDE0060
    DpShMCreate: allocated wp_adm_list at 000000000DDE30B0
    DpShMCreate: allocated wp_adm at 000000000DDE32A0
    DpShMCreate: allocated tm_adm_list at 000000000DDEDA20
    DpShMCreate: allocated tm_adm at 000000000DDEDA70
    DpShMCreate: allocated wp_ca_adm at 000000000E330980
    DpShMCreate: allocated appc_ca_adm at 000000000E340390
    DpShMCreate: allocated comm_adm at 000000000E34FDA0
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 000000000E4A1C40
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated gw_adm at 000000000E4A1CF0
    DpShMCreate: allocated j2ee_adm at 000000000E4A1D30
    DpShMCreate: allocated ca_info at 000000000E4A2CB0
    DpShMCreate: allocated wall_adm at 000000000E4A2D40
    DpCommAttachTable: attached comm table (header=000000000E34FDA0/ft=000000000E34FDB0)
    DpSysAdmIntInit: initialize sys_adm
    rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
    dia token check not active (10 token)
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
    rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> EsILock: use spinlock for locking
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    <ES> Info: em/initial_size_MB( 16383MB) not multiple of em/blocksize_KB( 4096KB)
    <ES> Info: em/initial_size_MB rounded up to 16384MB
    Using implementation view
    <EsNT> Using memory model view.
    <EsNT> Memory Reset disabled as NT default
    <ES> 4095 blocks reserved for free list.
    ES initialized.
    mm.dump: set maximum dump mem to 192 MB
    mm.dump: set global maximum dump mem to 192 MB
    EsRegisterEmCheck: Register EmGetEsHandles at 000000013FC48640
    DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
    MPI: dynamic quotas disabled.
    MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 5824
      argv[0] = D:\usr\sap\VSM\DVEBMGS00\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\VSM\DVEBMGS00\exe\jcontrol.EXE
      argv[2] = pf=\\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=65000
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=VSM
      argv[7] = -DSAPMYNAME=VKCSOL_VSM_00
      argv[8] = -DSAPPROFILE=\\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 4.0.1 4.0.1 5.1) [dpxxdisp.c   1702]
    ***LOG Q0K=> DpMsAttach, mscon ( VKCSOL) [dpxxdisp.c   12707]
    MBUF state LOADING
    DpStartStopMsg: send start message (myname is >VKCSOL_VSM_00                           <)
    DpStartStopMsg: start msg sent
    CCMS: Initialized monitoring segment of size 60000000.
    CCMS: Initialized CCMS Headers in the shared monitoring segment.
    CCMS: Checking Downtime Configuration of Monitoring Segment.
    CCMS: AlMsUpload called by wp 1024.
    Tue Apr 01 19:02:10 2014
    01.04.2014 13:32:10.628 PID=5448, TID=5744 SapTimer info. QPC/Windows time mismatch. System suspended, busy, missing ticks. Mismatch QpcTime-WindowsTime:  -168 millisec (max +0). Slept 1000 millisec, Qpc elapsed: +1000 millisec, WindowsUtc elapsed +1168 millisec. SapTime-WindowsUtcTime=-1 seconds. TotalTimeCorrection=+0 millisec, QpcTime-WindowsUtcTime=-1028 millisec (*).
    Tue Apr 01 19:02:11 2014
    CCMS: AlMsUpload successful for D:\usr\sap\VSM\DVEBMGS00\log\ALMTTREE.DAT (2189 MTEs).
    Tue Apr 01 19:02:13 2014
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpJ2eeLogin: j2ee state = CONNECTED
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1296]
    MBUF state ACTIVE
    DpWpBlksLow: max wp blocks in queue is 800 (80 %)
    MBUF component UP
    DpMsgProcess: 1 server in MBUF
    DpAppcBlksLow: max appc blocks in queue is 500 (50 %)
    Tue Apr 01 19:02:21 2014
    DpModState: change server state from STARTING to ACTIVE
    Tue Apr 01 19:02:23 2014
    ***LOG Q0I=> NiIRead: P=127.0.0.1:61107; L=127.0.0.1:65000: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5086]
    *** ERROR => NiIRead: SiRecv failed for hdl 33/sock 1008
        (SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:61107; L=127.0.0.1:65000) [nixxi.cpp    5086]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5824)
    *** ERROR => DpProcKill: kill failed [dpntdisp.c   397]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Regards
    Jose H.

    Hi Ashutosh,
    Thanks for your immediate reply. Please find the log below.
    trc file: "dev_server0", trc level: 1, release: "721"
    node name   : ID3506750
    pid         : 8068
    system name : VSM
    system nr.  : 00
    started at  : Sat Mar 29 13:41:08 2014
    arguments  :
       arg[00] : D:\usr\sap\VSM\DVEBMGS00\exe\jlaunch.exe
       arg[01] : pf=D:\usr\sap\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
       arg[02] : -DSAPINFO=VSM_00_server
       arg[03] : pf=D:\usr\sap\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
       arg[04] : -DSAPSTART=1
    Used property files
    -> files [00] : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID3506700  : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID3506750  : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID3506700            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID3506750            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : VKCSOL
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    [Thr 19300] Sat Mar 29 13:41:08 2014
    [Thr 19300] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 19300] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 19300] JLaunchInitSignalHandling: signal handling is disabled
    [Thr 4928] WaitSyncSemThread: Thread 4928 started as semaphore monitor thread.
    [Thr 23444] JLaunchRequestFunc: Thread 23444 started as listener thread for np messages.
    [Thr 19300] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    [Thr 19300] MPI: dynamic quotas disabled.
    [Thr 19300] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    [Thr 19300] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
    [Thr 19300] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
    [Thr 19300] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
    [Thr 19300] CCMS: CCMS Monitoring Initialization finished, rc=0.
    [Thr 19300] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048m [jstartxx.c   2800]
    [Thr 19300] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID3506750]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4
    -> java parameters    : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee -XX:+JavaMonitorsInStackTrace -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/Agent.jar -Dcom.wily.introscope.agent.agentName=VSM_DVEBMGS00_server0 -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/IntroscopeAgent.profile -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 4.1.024 1.6-b04
    -> java vm vendor     : SAP Java Server VM (SAP AG)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> stack size         : 2M
    -> root path          : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\VSM\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120 sec.
    [Thr 19300] JLaunchISetDebugMode: set debug mode [no]
    [Thr 9092] JLaunchIStartFunc: Thread 9092 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 2097152 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -XX:MaxNewSize=600M
    -> arg[  4]: -XX:NewSize=600M
    -> arg[  5]: -XX:MaxPermSize=512M
    -> arg[  6]: -XX:PermSize=512M
    -> arg[  7]: -XX:+UseConcMarkSweepGC
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -XX:TargetSurvivorRatio=90
    -> arg[ 10]: -XX:SurvivorRatio=4
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -verbose:gc
    -> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 15]: -XX:HeapDumpPath=OOM.hprof
    -> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError
    -> arg[ 17]: -Djco.jarm=1
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Djava.security.policy=./java.policy
    -> arg[ 20]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 21]: -Dsun.io.useCanonCaches=false
    -> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee
    -> arg[ 27]: -XX:+JavaMonitorsInStackTrace
    -> arg[ 28]: -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/Agent.jar
    -> arg[ 29]: -Dcom.wily.introscope.agent.agentName=VSM_DVEBMGS00_server0
    -> arg[ 30]: -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/IntroscopeAgent.profile
    -> arg[ 31]: -Dstartup.mode=SAFE
    -> arg[ 32]: -Dstartup.action=UPGRADE
    -> arg[ 33]: -Dsys.global.dir=D:\usr\sap\VSM\SYS\global
    -> arg[ 34]: -Dapplication.home=D:\usr\sap\VSM\DVEBMGS00\exe
    -> arg[ 35]: -Djava.class.path=D:\usr\sap\VSM\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 36]: -Djava.library.path=D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\VSM\DVEBMGS00\exe;D:\usr\sap\VSM\SYS\exe\uc\NTAMD64
    -> arg[ 37]: -Dmemory.manager=2048M
    -> arg[ 38]: -Xmx2048M
    -> arg[ 39]: -Xms2048M
    -> arg[ 40]: -Xss2M
    -> arg[ 41]: -DLoadBalanceRestricted=no
    -> arg[ 42]: -Djstartup.mode=JCONTROL
    -> arg[ 43]: -Djstartup.ownProcessId=8068
    -> arg[ 44]: -Djstartup.ownHardwareId=I0649086862
    -> arg[ 45]: -Djstartup.whoami=server
    -> arg[ 46]: -Djstartup.debuggable=no
    -> arg[ 47]: -Xjvmx
    -> arg[ 48]: -XsapSystem=00
    -> arg[ 49]: -XmonGcCallback
    -> arg[ 50]: -DSAPINFO=VSM_00_server
    -> arg[ 51]: -DSAPSTART=1
    -> arg[ 52]: -DSAPSTARTUP=1
    -> arg[ 53]: -DSAPSYSTEM=00
    -> arg[ 54]: -DSAPSYSTEMNAME=VSM
    -> arg[ 55]: -DSAPMYNAME=VKCSOL_VSM_00
    -> arg[ 56]: -DSAPDBHOST=VKCSOL
    -> arg[ 57]: -Dj2ee.dbhost=VKCSOL
    (CompilerOracle read from file D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\.hotspot_compiler)
    [Thr 9092] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 20084] Sat Mar 29 13:41:10 2014
    [Thr 20084] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
    2.781: [GC 2.781: [ParNew: 409600K->2306K(512000K), 0.0126041 secs] 409600K->2306K(1994752K), 0.0127881 secs] [Times: user=0.05 sys=0.00, real=0.01 secs]
    [Thr 20084] Sat Mar 29 13:41:11 2014
    [Thr 20084] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 20084] JLaunchISetClusterId: set cluster id 3506750
    [Thr 20084] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 20084] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    Sat Mar 29 13:41:23 2014
    15.071: [GC 15.071: [ParNew: 411906K->16315K(512000K), 0.0306641 secs] 411906K->16315K(1994752K), 0.0309011 secs] [Times: user=0.13 sys=0.00, real=0.03 secs]
    Sat Mar 29 13:41:32 2014
    24.118: [GC 24.118: [ParNew: 425915K->29114K(512000K), 0.0363407 secs] 425915K->29114K(1994752K), 0.0365634 secs] [Times: user=0.11 sys=0.02, real=0.04 secs]
    [Thr 18736] Sat Mar 29 13:41:38 2014
    [Thr 18736] JHVM_RegisterNatives: com.sap.mona.api.JMonAPI
    [Thr 18736] CCMS: openMonitoringSegment(): inside static JMON Lib: already connected.
    [Thr 17644] JHVM_RegisterNatives: com.sap.mw.rfc.driver.CpicDriver
    [Thr 19340] JHVM_RegisterNatives: com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 7816] Sat Mar 29 13:41:39 2014
    [Thr 7816] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7816] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 25/sock 7884
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17936] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 7888
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    31.816: [GC 31.816: [ParNew[Thr 21936] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 21936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 7856
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 2800] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 2800] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 9/sock 7860
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    : 438714K->67978K(512000K), 0.0626636 secs] 438714K->67978K(1994752K), 0.0628963 secs] [Times: user=0.11 sys=0.08, real=0.06 secs]
    [Thr 7276] Sat Mar 29 13:41:40 2014
    [Thr 7276] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 7988
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 24572] Sat Mar 29 13:41:42 2014
    [Thr 24572] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24572] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 8132
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 5092] Sat Mar 29 13:41:43 2014
    [Thr 5092] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5092] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 8088
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 20084] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    [Thr 24276] Sat Mar 29 13:41:44 2014
    [Thr 24276] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 8480
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 1316] Sat Mar 29 13:41:45 2014
    [Thr 1316] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 1316] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 9292
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 13068] Sat Mar 29 13:41:46 2014
    [Thr 13068] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 13068] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 9736
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 19652] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
    [Thr 17680] Sat Mar 29 13:41:47 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 9736
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 23760] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 23760] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 10/sock 5976
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:41:48 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 9736
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:41:49 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 9736
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:41:50 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6272
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 5348] Sat Mar 29 13:41:51 2014
    [Thr 5348] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5348] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6336
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17548] Sat Mar 29 13:41:52 2014
    [Thr 17548] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17548] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6548
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 4216] Sat Mar 29 13:41:53 2014
    [Thr 4216] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 4216] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6424
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 23788] Sat Mar 29 13:41:54 2014
    [Thr 23788] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 23788] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6844
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6100] Sat Mar 29 13:41:55 2014
    [Thr 6100] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6100] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7448
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6828] Sat Mar 29 13:41:56 2014
    [Thr 6828] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6828] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6216
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 644] Sat Mar 29 13:41:57 2014
    [Thr 644] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 644] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 5992
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7376] Sat Mar 29 13:41:58 2014
    [Thr 7376] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7376] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6136
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24096] Sat Mar 29 13:41:59 2014
    [Thr 24096] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24096] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6004
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24460] Sat Mar 29 13:42:00 2014
    [Thr 24460] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24460] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6276
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 13452] Sat Mar 29 13:42:01 2014
    [Thr 13452] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 13452] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 7328
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17884] Sat Mar 29 13:42:03 2014
    [Thr 17884] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17884] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 7372
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6616] Sat Mar 29 13:42:04 2014
    [Thr 6616] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6616] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7200
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 3136] Sat Mar 29 13:42:05 2014
    [Thr 3136] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 3136] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6344
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 8284] Sat Mar 29 13:42:06 2014
    [Thr 8284] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 8284] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 7380
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 19240] Sat Mar 29 13:42:07 2014
    [Thr 19240] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 19240] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6940
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 21316] Sat Mar 29 13:42:08 2014
    [Thr 21316] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 21316] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 5988
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 22436] Sat Mar 29 13:42:09 2014
    [Thr 22436] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 22436] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 7368
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 20936] Sat Mar 29 13:42:10 2014
    [Thr 20936] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 20936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 7528
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 18784] Sat Mar 29 13:42:11 2014
    [Thr 18784] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 18784] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 4460
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 21320] Sat Mar 29 13:42:12 2014
    [Thr 21320] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 21320] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6148
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 19632] Sat Mar 29 13:42:13 2014
    [Thr 19632] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 19632] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 5948
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 8684] Sat Mar 29 13:42:14 2014
    [Thr 8684] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 8684] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6012
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 7468] Sat Mar 29 13:42:15 2014
    [Thr 7468] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7468] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6032
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 5588] Sat Mar 29 13:42:16 2014
    [Thr 5588] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5588] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 1032
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 2036] Sat Mar 29 13:42:17 2014
    [Thr 2036] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 2036] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6052
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 6692] Sat Mar 29 13:42:18 2014
    [Thr 6692] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6692] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6188
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 5184] Sat Mar 29 13:42:19 2014
    [Thr 5184] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5184] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6192
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 5604] Sat Mar 29 13:42:20 2014
    [Thr 5604] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5604] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6220
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 15996] Sat Mar 29 13:42:21 2014
    [Thr 15996] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 15996] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6236
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:22 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6236
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:23 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6236
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:24 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6236
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:26 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6064
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 19856] Sat Mar 29 13:42:27 2014
    [Thr 19856] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 19856] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6184
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24128] Sat Mar 29 13:42:28 2014
    [Thr 24128] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24128] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6248
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 13684] Sat Mar 29 13:42:29 2014
    [Thr 13684] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 13684] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6260
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7384] Sat Mar 29 13:42:30 2014
    [Thr 7384] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7384] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6264
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7432] Sat Mar 29 13:42:31 2014
    [Thr 7432] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7432] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6292
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6700] Sat Mar 29 13:42:32 2014
    [Thr 6700] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6700] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6304
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7272] Sat Mar 29 13:42:33 2014
    [Thr 7272] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7272] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6340
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 19864] Sat Mar 29 13:42:34 2014
    [Thr 19864] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 19864] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6392
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 5608] Sat Mar 29 13:42:35 2014
    [Thr 5608] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 5608] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6404
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 7160] Sat Mar 29 13:42:36 2014
    [Thr 7160] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7160] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6416
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 14536] Sat Mar 29 13:42:37 2014
    [Thr 14536] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 14536] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7340
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24404] Sat Mar 29 13:42:38 2014
    [Thr 24404] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24404] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6232
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 22756] Sat Mar 29 13:42:39 2014
    [Thr 22756] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 22756] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6076
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6284] Sat Mar 29 13:42:40 2014
    [Thr 6284] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6284] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 7472
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 12696] Sat Mar 29 13:42:41 2014
    [Thr 12696] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 12696] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6380
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 24180] Sat Mar 29 13:42:42 2014
    [Thr 24180] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 24180] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6420
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 23444] Sat Mar 29 13:42:43 2014
    [Thr 23444] JLaunchRequestFunc: receive command:17, argument:0 from pid:20668
    [Thr 23444] JLaunchIShutdownInvoke: set shutdown interval (stop:1396080763/end:1396080883/TO:120)
    [Thr 23444] JLaunchProcessCommand: Invoke VM Shutdown
    [Thr 23444] JHVM_FrameworkShutdownDirect: invoke direct shutdown
    [Thr 8780] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]
    [Thr 8780] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
    [Thr 5188] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.sadm.ShmCache
    [Thr 7240] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 7240] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6376
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 6536] Sat Mar 29 13:42:44 2014
    [Thr 6536] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 6536] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6852
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 18244] Sat Mar 29 13:42:46 2014
    [Thr 18244] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 18244] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6348
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:47 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6348
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    [Thr 17680] Sat Mar 29 13:42:48 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6348
        (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
    [Thr 22796] CCMS: closeMonitoringSegment(): inside static JMON Lib: nothing to do.
    [Thr 8780] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
    [Thr 17680] Sat Mar 29 13:42:49 2014
    [Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
    [Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6348
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
    Heap
    par new generation   reserved 614400K, committed 614400K, used 313963K [0x000000007fff0000, 0x00000000a57f0000, 0x00000000a57f0000)
      eden space 409600K,  60% used [0x000000007fff0000, 0x000000008f028658, 0x0000000098ff0000)
      from space 102400K,  66% used [0x0000000098ff0000, 0x000000009d2528e8, 0x000000009f3f0000)
      to   space 102400K,   0% used [0x000000009f3f0000, 0x000000009f3f0000, 0x00000000a57f0000)
    concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a57f0000, 0x00000000ffff0000, 0x00000000ffff0000)
    concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 70349K [0x00000000ffff0000, 0x000000011fff0000, 0x000000011fff0000)
    [Thr 18896] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 18896] JLaunchCloseProgram: good bye (exitcode = 0)
    Regards
    Jose H.

  • System Monitoring Setup in Solution Manager

    Hello Experts,
    We are going to implement and configure Solution Manager - System monitoring setup for pre testing purpose
    Currenly we have installed below SAP Systems
    1.Solution Manager Server
    2.ECC server (Without Ides) - Abap
    3.CRM Server (Without Ides) -Abap + Java
    We need to setup below tasks in Solution Manager
    1.Early watch alert
    2.System Monitoring
    3.Central System Administration
    4.Business Process Monitoring
    5.Service Level reporting
    1.Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
    Could you please someone give input reg this.
    Thanks
    Thirumal
    Edited by: Thiru Thirumal on Aug 6, 2008 4:56 AM
    Edited by: Thiru Thirumal on Aug 6, 2008 4:57 AM

    Hi,
    Q. Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
    A. Yes.
    Check with links for
    1.Early watch alert
    This process helps you to identify potential problems early, avoid bottlenecks, and monitor the performance of your ABAP and JAVA systems and your most important business processes, regularly, automatically and effectively. The data collection infrastructure comprises the ABAP Service Data Control Center and the JAVA function module Data Provider. The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.
    To be able to use it, you have:
    maintained the non-ABAP systems correctly in the system landscape maintenance (transaction SMSY)
    RFC u2013 Connections between: and an RFC u2013 Connections established.
    your satellite systems and the SAP Solution Manager system
    SAP Solution Manager and the SAP Service Marketplace
    Solution Manager system and Solution Manager Diagnostics
    Cf: Solution Manager IMG (transaction SPRO).
    checked the availability of the tools required for the SAP Service sessions (add-on ST-A/PI), with the report RTCCTOOL.
    activated Alert Monitoring and set-up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCCN) of your satellite systems, for all SAP satellite systems and the central SAP Solution Manager of your solution
    set-up your systems in a solution landscape in the SAP Solution Manager
    configured Solution Manager Diagnostics
    2.System Monitoring
    The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.
    The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.
    The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.
    3.Central System Administration
    You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, u201EBPMu201C of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.
    The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:
    ● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and u201EOther CCMSu201C and interface data, in the local CCMS of the satellite systems.
    ● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.
    The SAP Solution Manager system copies the data from the local CCMS.
    The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.
    The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.
    4.Business Process Monitoring
    The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.
    You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system
    5.Service Level reporting
    http://service.sap.com/solutionmanager for all solman tasks as given below.
    http://www.asap.net.cn/homepage_en/Solution%20Manager%20EN.pdf
    http://help.sap.com/saphelp_sm32/helpdata/en/1b/f02c41ab78f66fe10000000a1550b0/content.htm
    http://help.sap.com/saphelp_sm32/helpdata/en/9f/1f46570f8a4a268b3154e0e0f07280/content.htm
    Regards,
    Srini Nookala

  • Unified Job Monitoring -Share your experiences with SAP Solution Manager 7.1

    Dear Forum members,
    I woudl like to introduce myself as Raghav, S. I am in the development team responsible for building the unified job monitoring workcenter starting 7.1 SP10 (onwards).
    Please post your feedback, current status wrt to setup, commmon issues in this area.
    I will be more than glad to help you here.
    Regards, Raghav
    Development Manager
    CLM - Solution manager team, Labs India.

    Hello Raghev,
    we implemented unfied job monitoring on a larger scale by now, starting out with the monitoring of SAP Standard & Reorg Jobs.
    Everything seemed quiet OK at the beginning, but over time display performance of the Monitoring UI decreased drastically (exceeding 5 Min. "per click" in the UI).
    I pinned this down to the following (Oracle) SQL access:
      SELECT
      "CLIENT", "CONTEXT_ID", "TYPE_ID", "HASH_METRIC_PATH", "START_TIMESTAMP", "IS_CURRENT", "END_TIMESTAMP",
      "METRIC_PATH", "RATING_AGGREGATE", "VALUE_MIN", "VALUE_MAX", "VALUE_SUM", "VALUE_COUNT", "VALUE_LAST",
      "VALUE_DATA_TYPE", "VALUE_MAX_TIME", "LAST_TEXT"
    FROM
      "MES_DB_AGGREGATE"
    WHERE
      "CLIENT"=:A0 AND "CONTEXT_ID"=:A1 AND "TYPE_ID"=:A2 AND "IS_CURRENT"=:A3 OR "CLIENT"=:A4 AND
      "CONTEXT_ID"=:A5 AND "TYPE_ID"=:A6 AND "IS_CURRENT"=:A7 OR "CLIENT"=:A8 AND "CONTEXT_ID"=:A9 AND
      "TYPE_ID"=:A10 AND "IS_CURRENT"=:A11 OR "CLIENT"=:A12 AND "CONTEXT_ID"=:A13 AND "TYPE_ID"=:A14 AND
      "IS_CURRENT"=:A15 OR "CLIENT"=:A16 AND "CONTEXT_ID"=:A17 AND "TYPE_ID"=:A18 AND "IS_CURRENT"=:A19
    The execution plan used for this SQL is:
    0
    SELECT STATEMENT
    1
    INLIST ITERATOR      
    2  
    TABLE ACCESS BY INDEX ROWID MES_DB_AGGREGATE
    3    
    INDEX RANGE SCAN  MES_DB_AGGREGATECU
    MES_DB_AGGREGATE in our case has over 5 million entries.
    The parameterization of the DB incl. Memory and all should be OK.
    The index range scan simply takes that long.
    This might be, because the MES_DB_AGGREGATECU index has the lowest cardinality column (CLIENT) first.
    Header 1
    Header 2
    COLUMN_NAME
    NUM_DISTINCT
    CLIENT
    1
    CONTEXT_ID
    433
    TYPE_ID
    2192
    IS_CURRENT
    2
    Could you have your team check on this, because with the situation as is, the Job Monitoring application seemingly becomes non-usable, as soon, as you start to scale up.
    Best Regards,
    Thorsten

Maybe you are looking for

  • Help needed in Agent Inbox SORTBY - Drop down field

    Hi All, I am trying to add a new drop down value in SORT BY Field in Agent INBOX Search screen. Can some one give me little guidance on this as i am stuck with it. My approach till now : Tried enhancing the view ICCMP_INBOX/Inboxsearch.it is creating

  • How to bring SOLMAN Systemmonitoring on mobile devices

    Dear all, looking for a possibility to bring Solution Monitoring and/or Systemmonitoring on an iOS or android mobile device. Has anyone experienced this? looking for tools or describtion how to realize it. Thank you very much I´m grateful for every h

  • Importing AVCHD 720p30 makes 60fps

    I'm using a Panasonic HMC40 to shoot 720p30 video clips. When I log and transfer, the clips import fine but they play at twice the speed. When I right-click on a clip in the browser and select item properties it states the video is 60fps. I have Easy

  • Thumbnail size when uploading pics to Websites

    Ok, I've asked this question on several sites with no luck and getting a little frustrated. When attempting to load photos from file on my local harddrive to facebook, 500px, flickr, email, etc. the the thumbnails are fixed in size. The option to enl

  • Oracle revoke issue

    Hi ALL, When we revoke a user permission say: REVOKE CREATE TABLE,      ALTER TABLESPACE,      UNLIMITED TABLESPACE,      FORCE TRANSACTION      FROM temp_user;/ Its sets the tablespace value to zero for the all the tablespace for which the temp_user