Java server0 restaring authomatically

Hi All,
My java server0 is restating automatically.
I checked some notes and maintained the java parameters accordingly but it did not help.
Please find below the logs abd the parameters
I am on Windows 64 bit server
Java parameter setting
Djco.jarm=1
-XX:MaxPermSize=512M
-XX:PermSize=512M
-Xms2048M
-XX:NewSize=171M
-XX:MaxNewSize=171M
-XX:+DisableExplicitGC
-verbose:gc
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-Djava.awt.headless=true
-Dsun.io.useCanonCaches=false
-XX:SoftRefLRUPolicyMSPerMB=1
-XX:SurvivorRatio=2
-XX:TargetSurvivorRatio=90
-Djava.security.policy=./java.policy
-Djava.security.egd=file:/dev/urandom
-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
Developer trace
trc file: "H:\usr\sap\XID\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name   : ID7718850
pid         : 8428
system name : XID
system nr.  : 00
started at  : Wed Dec 02 16:18:16 2009
arguments       :
       arg[00] : H:\usr\sap\XID\DVEBMGS00\exe\jlaunch.exe
       arg[01] : pf=H:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_hkbxidev
       arg[02] : -DSAPINFO=XID_00_server
       arg[03] : pf=H:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_hkbxidev
       arg[04] : -DSAPSTART=1
       arg[05] : -DCONNECT_PORT=3593
       arg[06] : -DSAPSYSTEM=00
       arg[07] : -DSAPSYSTEMNAME=XID
       arg[08] : -DSAPMYNAME=hkbxidev_XID_00
       arg[09] : -DSAPPROFILE=H:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_hkbxidev
       arg[10] : -DFRFC_FALLBACK=ON
       arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 6488] Wed Dec 02 16:18:16 2009
[Thr 6488] *** WARNING => INFO: Unknown property [instance.box.number=XIDDVEBMGS00hkbxidev] [jstartxx.c   841]
[Thr 6488] *** WARNING => INFO: Unknown property [instance.en.host=hkbxidev] [jstartxx.c   841]
[Thr 6488] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
[Thr 6488] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
JStartupReadInstanceProperties: read instance properties [H:\usr\sap\XID\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host    : hkbxidev
-> ms port    : 3901
-> OS libs    : H:\usr\sap\XID\DVEBMGS00\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
**********ion=700.2006.09.13)
[Thr 6488] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_13-x64
[Thr 6488] JStartupICheckFrameworkPackage: can't find framework package H:\usr\sap\XID\DVEBMGS00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID7718850]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_13-x64
-> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=512M -XX:PermSize=512M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> java vm version    : 1.4.2_13-b06
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 4096M
-> init heap size     : 2048M
-> root path          : H:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : H:\usr\sap\XID\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     : H:\usr\sap\XID\DVEBMGS00\exe\jstartup.jar;H:\usr\sap\XID\DVEBMGS00\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
Best Regards
Tushar

Hi Sandeep,
This is general problem of portal.
This is due to heap memory.
For solving this issue you have to set the heap memory ( tune the system ) as per note :- 723909
====================================
-Xmx2048m
-Xms2048m
-XX:NewSize=320m
-XX:MaxNewSize=320m
-XX:PermSize=512m
-XX:MaxPermSize=512m
===========================
As well if you have much load on the application then you can increase more the heap meomry
i can see in your error the value of NEWSIZE is 170 increase NEWSIZE and MAXNEWZIXE to 320 and then restart the application
Thanks
Anil
Edited by: Anil Bhandary on Dec 2, 2009 1:18 PM

Similar Messages

  • Java Server0 stuck in starting apps state

    Dear All,
    My J2EE server was up and running, since last 2 days the Java stack [ more importantly the Server0 process] is down (showing yellow in the MMC), the SDM is running, the JAVA dispatcher is running , but the Server0 process is stuck in starting apps phase. I checked the Oracle tablespaces and found that Oracle SAPSR3DB was only 1%, so we increased the same.
    When we restarted the ABAP+JAVA stack we again found that our Java Server0 process is yellow phase , our SDM is running, the JAVA dispatcher is running , but the Server0 process starts and then moves to starting framework phase and then gets stuck in the starting apps phase.
    My ABAP part is running fine.
    On Checking the developer trace for this server 0 process , it says that JLaunchISetState is changing the state from starting application [2] to starting applications [10] where is gets stuck.Have also gone through the latest log files in the J2ee/cluster/server0/log, but could not find any error .
    I have tried waiting for long durations, but this has not resolved the issue.The RAM size is 3.5 GB and virtual memory is 12 GB.doesnt reveal any error.Also tried to increase the instance heap size via the config tool [ current value is 1024 , tried changing the value to 2048 , restarted cluster , but same issue again , so reverted back to old value].The OS is windows 2003 server , DB-Oracle 10g.This is a NW2004s stack on which PI 7.0 has been activated.
    Have also checked and found all J2EE users i.e. j2ee_admin, J2ee_guest, sapjsf, and all PI related super users unlocked.
    Also all DB schema users were found to be unlocked. Also tried increasing the number of threads in the thread manager in config tool.
    Also tried increasing the enque/table_space value to 4 times of RAM, but no change in problem.
    Checked values of VM parameters, everything seems to be fine.
    Please find the Dev_server0 trace file below :-
    trc file: "E:\usr\sap\PI7\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID9240450
    pid         : 5796
    system name : PI7
    system nr.  : 00
    started at  : Tue Dec 16 11:29:55 2008
    arguments       :
           arg[00] : E:\usr\sap\PI7\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
           arg[02] : -DSAPINFO=PI7_00_server
           arg[03] : pf=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=2168
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=PI7
           arg[08] : -DSAPMYNAME=hcl3SAP_PI7_00
           arg[09] : -DSAPPROFILE=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 5792] Tue Dec 16 11:29:55 2008
    [Thr 5792] *** WARNING => INFO: Unknown property [instance.box.number=PI7DVEBMGS00hcl3sap] [jstartxx.c   841]
    [Thr 5792] *** WARNING => INFO: Unknown property [instance.en.host=hcl3SAP] [jstartxx.c   841]
    [Thr 5792] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 5792] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : hcl3SAP
    -> ms port    : 3901
    -> OS libs    : E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : hcl3SAP
    -> ms port    : 3901
    -> os libs    : E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID9240400  : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID9240450  : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID9240400            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID9240450            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
    [Thr 5792] Tue Dec 16 11:29:56 2008
    [Thr 5792] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5792] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 5772] WaitSyncSemThread: Thread 5772 started as semaphore monitor thread.
    [Thr 5784] JLaunchRequestFunc: Thread 5784 started as listener thread for np messages.
    [Thr 5792] NiInit3: NI already initialized; param 'maxHandles' ignored (1;10002)
    [Thr 5792] CPIC (version=700.2006.09.13)
    [Thr 5792] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    [Thr 5792] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID9240450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_09
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> java vm version    : 1.4.2_09-b05
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : E:\usr\sap\PI7\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     : E:\usr\sap\PI7\DVEBMGS00\exe\jstartup.jar;E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 5792] JLaunchISetDebugMode: set debug mode [no]
    [Thr 5720] JLaunchIStartFunc: Thread 5720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -XX:MaxPermSize=256M
    -> arg[ 10]: -XX:PermSize=256M
    -> arg[ 11]: -XX:NewSize=171M
    -> arg[ 12]: -XX:MaxNewSize=171M
    -> arg[ 13]: -XX:+DisableExplicitGC
    -> arg[ 14]: -verbose:gc
    -> arg[ 15]: -Xloggc:GC.log
    -> arg[ 16]: -XX:+PrintGCDetails
    -> arg[ 17]: -XX:+PrintGCTimeStamps
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Dsun.io.useCanonCaches=false
    -> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 24]: -Dsys.global.dir=E:\usr\sap\PI7\SYS\global
    -> arg[ 25]: -Dapplication.home=E:\usr\sap\PI7\DVEBMGS00\exe
    -> arg[ 26]: -Djava.class.path=E:\usr\sap\PI7\DVEBMGS00\exe\jstartup.jar;E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 27]: -Djava.library.path=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;C:\j2sdk1.4.2_09\bin;E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs;E:\oracle\PI7\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_09\bin;C:\j2sdk1.4.2_09\jre\bin;E:\usr\sap\PI7\SYS\exe\uc\NTI386
    -> arg[ 28]: -Dmemory.manager=1024M
    -> arg[ 29]: -Xmx1024M
    -> arg[ 30]: -Xms1024M
    -> arg[ 31]: -DLoadBalanceRestricted=no
    -> arg[ 32]: -Djstartup.mode=JCONTROL
    -> arg[ 33]: -Djstartup.ownProcessId=5796
    -> arg[ 34]: -Djstartup.ownHardwareId=G1631462527
    -> arg[ 35]: -Djstartup.whoami=server
    -> arg[ 36]: -Djstartup.debuggable=no
    -> arg[ 37]: -DSAPINFO=PI7_00_server
    -> arg[ 38]: -DSAPSTART=1
    -> arg[ 39]: -DCONNECT_PORT=2168
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=PI7
    -> arg[ 42]: -DSAPMYNAME=hcl3SAP_PI7_00
    -> arg[ 43]: -DSAPPROFILE=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
    -> arg[ 44]: -DFRFC_FALLBACK=ON
    -> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 46]: -DSAPSTARTUP=1
    -> arg[ 47]: -DSAPSYSTEM=00
    -> arg[ 48]: -DSAPSYSTEMNAME=PI7
    -> arg[ 49]: -DSAPMYNAME=hcl3SAP_PI7_00
    -> arg[ 50]: -DSAPDBHOST=hcl3SAP
    -> arg[ 51]: -Dj2ee.dbhost=hcl3SAP
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 5720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 4072] Tue Dec 16 11:29:59 2008
    [Thr 4072] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 4072] Tue Dec 16 11:30:00 2008
    [Thr 4072] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 4072] JLaunchISetClusterId: set cluster id 9240450
    [Thr 4072] Tue Dec 16 11:30:01 2008
    [Thr 4072] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 4072] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 6392] Tue Dec 16 11:30:28 2008
    [Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 6392] Tue Dec 16 11:30:29 2008
    [Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.engine.Compress
    [Thr 6704] Tue Dec 16 11:30:36 2008
    [Thr 6704] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    [Thr 4072] Tue Dec 16 11:31:48 2008
    [Thr 4072] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    Thanks in advance for your time and patience.
    Prashant
    Edited by: Prashant Vijayadas on Dec 16, 2008 5:14 PM

    Hi Jazz,
    i cannot seem to find any errors in the default trace files either [ located in usr/sap/<SID>/DVEBMGS/j2ee/cluster/server0/log ]
    Please find the default trace files below:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!FILESET[4, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.3.trc]/>
    <!NEXTFILE[defaultTrace.5.trc]/>
    <!LOGHEADER[END]/>
    #1.5#0012793AE40C00440000000C0000121800045DD8487B974B#1229083417427#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)#
    #1.5#0012793AE40C00440000000D0000121800045DD8487D650D#1229083417552#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)#
    #1.5#0012793AE40C00440000000E0000121800045DD8487D65A5#1229083417552#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)#
    #1.5#0012793AE40C002F000000060000121800045DD848DD3380#1229083423878#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C0047000000000000121800045DD849291423#1229083428954#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://hcl3sap.hclt.corp.hcl.in:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.pi7.hcl3sap), due to: HTTP 503: Not Ready#
    #1.5#0012793AE40C0047000000010000121800045DD849298BB2#1229083428985#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Not Ready#
    #1.5#0012793AE40C0049000000000000121800045DD8492F4B02#1229083429407#com.sap.aii.af.service.alerting.Alert##com.sap.aii.af.service.alerting.Alert.getMDTUrl()#######SAPEngine_System_Thread[impl:5]_8##0#0#Error##Plain###HTTP response code: 503 (Not Ready)#
    #1.5#0012793AE40C004E000000000000121800045DD8496DB509#1229083433562#com.sap.aii.adapter.jdbc.XI2JDBC##com.sap.aii.adapter.jdbc.XI2JDBC.init(Channel, AdminAdapter, boolean)#######SAPEngine_System_Thread[impl:5]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Java###Configuration error in : #2#JDBC_Receiver_CC#<null>#
    #1.5#0012793AE40C002F000000090000121800045DD84973B644#1229083433968#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C0050000000020000121800045DD849746B3F#1229083433999#com.sap.engine.services.jndi##com.sap.engine.services.jndi#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)
         at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
         at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
         at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:318)
         at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:124)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:180)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:172)
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)
         ... 14 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)
         ... 17 more
    #1.5#0012793AE40C0050000000030000121800045DD849747B70#1229083434015#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Error getting the server-side naming service functionality during getInitialContext operation.#
    #1.5#0012793AE40C0051000000000000121800045DD849761D0C#1229083434124#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:JDBC2JDBC_Sender_BS:JDBC_Sender_CC]_1##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
    XI
    Sender
    RamaSurya.mdb' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
    XI
    Sender
    RamaSurya.mdb': SQLException: [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x1218 Thread 0x70c DBC 0x779cd6c Jet'.#
    #1.5#0012793AE40C0050000000040000121800045DD8497B42D4#1229083434452#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:243)
         at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
         at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
         at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:318)
         at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:124)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)
         ... 13 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:180)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:172)
         at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)
         ... 14 more
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)
         ... 17 more
    ') before. Reconfigure it or restart the JMS service!#1#VASAVI_RCR_JMS_HR#
    #1.5#0012793AE40C004E000000020000121800045DD84981BA8C#1229083434874#com.sap.aii.adapter.jdbc.XI2JDBC##com.sap.aii.adapter.jdbc.XI2JDBC.handleDBConnectException(Exception, AlertContextInformation)#######SAPEngine_System_Thread[impl:5]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE': SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153092352)(ERR=12500)(ERROR_STACK=(ERROR=(CODE=12500)(EMFI=4))(ERROR=(CODE=12560)(EMFI=4))(ERROR=(CODE=530)(EMFI=4))(ERROR=(BUF='32-bit Windows Error: 2: No such file or directory'))))#
    #1.5#0012793AE40C0053000000000000121800045DD8498DB60C#1229083435670#com.sap.aii.af.rfc.core.RfcRuntimeManager##com.sap.aii.af.rfc.core.RfcRuntimeManager.channelAdded(Channel channel)#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Java###can not instantiate RfcPool object - ignoring this channel '''' due to: #2#CC_send_RFC#com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts#
    #1.5#0012793AE40C0054000000000000121800045DD8498F2B21#1229083435764#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:BS_MWSOA_SDR:VSD_CC_JDBC]_2##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE': SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153092352)(ERR=12500)(ERROR_STACK=(ERROR=(CODE=12500)(EMFI=4))(ERROR=(CODE=12560)(EMFI=4))(ERROR=(CODE=530)(EMFI=4))(ERROR=(BUF='32-bit Windows Error: 2: No such file or directory'))))#
    #1.5#0012793AE40C0053000000010000121800045DD849987C48#1229083436373#com.sap.aii.af.rfc.core.RfcRuntimeManager##com.sap.aii.af.rfc.core.RfcRuntimeManager.channelAdded(Channel channel)#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Java###can not instantiate RfcPool object - ignoring this channel '''' due to: #2#CC_A_RFCSender#com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts#
    #1.5#0012793AE40C0055000000000000121800045DD8499BFF10#1229083436592#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_11##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C0056000000000000121800045DD849BF4E62#1229083438919#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C0057000000000000121800045DD849C87229#1229083439513#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_53##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C0058000000000000121800045DD849D0CAB8#1229083440060#com.sap.aii.adapter.file.XI2File##com.sap.aii.adapter.file.XI2File.init(Channel, AdminAdapter)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#FileReceiver_FCC#<null>#
    #1.5#0012793AE40C0058000000020000121800045DD849E48706#1229083441356#com.sap.aii.adapter.file.XI2File##com.sap.aii.adapter.file.XI2File.init(Channel, AdminAdapter)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#CC_Receiver1#<null>#
    #1.5#0012793AE40C0059000000000000121800045DD84A050EFF#1229083443480#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_119##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C002F0000000C0000121800045DD84A0DD554#1229083444058#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C0058000000040000121800045DD84A1C96B5#1229083445027#com.sap.aii.adapter.file.Conversion##com.sap.aii.adapter.file.Conversion.getTableParaWithErrorDescription(String)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/Conversion#Java###Parameter : not set#1#student.fieldNames#
    #1.5#0012793AE40C0058000000060000121800045DD84A3FEB97#1229083447338#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.init(Channel, AdminAdapter, boolean)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#stu_sender#<null>#
    #1.5#0012793AE40C0058000000080000121800045DD84A400FAA#1229083447354#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.start()#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###File adapter sender channel stu_sender not initalized - could not start#
    #1.5#0012793AE40C0054000000020000121800045DD84A48C532#1229083447916#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BS_TST:CC_F1_S]_185##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_F1_S: No suitable sender agreement found#
    #1.5#0012793AE40C005A000000000000121800045DD84A68B403#1229083450009#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_257##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C0059000000020000121800045DD84A68C418#1229083450009#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_258##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C005B000000000000121800045DD84A68F232#1229083450025#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_259##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C005C000000000000121800045DD84A68FDA1#1229083450025#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_260##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C005D000000000000121800045DD84A6BAA02#1229083450212#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRD]_263##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
    #1.5#0012793AE40C002F0000000F0000121800045DD84AA8C03D#1229083454211#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C005C000000020000121800045DD84B01421F#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_434##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C005E000000000000121800045DD84B01519A#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRD]_437##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
    #1.5#0012793AE40C005F000000000000121800045DD84B015B72#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_439##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C0059000000040000121800045DD84B015DEF#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_436##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C0060000000000000121800045DD84B01C588#1229083460037#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_440##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C0061000000000000121800045DD84B037ABA#1229083460146#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:JDBC2JDBC_Sender_BS:JDBC_Sender_CC]_438##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
    XI
    Sender
    RamaSurya.mdb' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
    XI
    Sender
    RamaSurya.mdb': SQLException: [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x1218 Thread 0x1988 DBC 0x78d1eac Jet'.#
    #1.5#0012793AE40C0062000000000000121800045DD84B282C7A#1229083462551#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_50##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
    #1.5#0012793AE40C0062000000010000121800045DD84B283F6D#1229083462567#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#CC_PO_RCR#
    #1.5#0012793AE40C0063000000000000121800045DD84B284C1A#1229083462567#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_57##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
    #1.5#0012793AE40C0064000000000000121800045DD84B28531A#1229083462567#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_56##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
    #1.5#0012793AE40C0065000000000000121800045DD84B289AAB#1229083462583#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_53##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
    #1.5#0012793AE40C0066000000000000121800045DD84B2AB132#1229083462723#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_49##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.66:7222#
    #1.5#0012793AE40C0064000000010000121800045DD84B397738#1229083463692#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_56##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#CC_PIP_TO_B2MML#
    #1.5#0012793AE40C0066000000010000121800045DD84B39B5F3#1229083463707#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_49##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.66:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.66:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#CC_B2MML_IB#
    #1.5#0012793AE40C0063000000010000121800045DD84B39C1BB#1229083463707#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_57##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#CC_S_GR#
    #1.5#0012793AE40C0065000000010000121800045DD84B39C67B#1229083463707#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_53##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
         at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         ...') before. Reconfigure it or restart the JMS service!#1#Sys_GoodsIssueFromStore_JMS_EMS#
    #1.5#0012793AE40C002F000000120000121800045DD84B420336#1229083464254#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C0067000000000000121800045DD84B4618D7#1229083464520#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Java###Unable to create the Queue due to #1#Name not found: 'Inbound_APC_Queue_Order'#
    #1.5#0012793AE40C0068000000000000121800045DD84B483E2D#1229083464660#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Java###Unable to create the Queue due to #1#Name not found: 'Inbound_APC_Queue_Order'#
    #1.5#0012793AE40C002F000000150000121800045DD84BDB73A2#1229083474297#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
    #1.5#0012793AE40C006A000000000000121800045DD84C0FEB63#1229083477734#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:BS_F2FBPM_SENDER:CM_SENDER]_3##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.178:1521:DEV' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.178:1521:DEV': SQLException: Io exception: The Network Adapter could not establish the connection#
    #1.5#0012793AE40C006B000000000000121800045DD851C45EB6#1229083573418#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820003]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#44a92fa0c84511dd92ad0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_A_flatefile]_13##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006B000000020000121800045DD851C46142#1229083573418#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#44a92fa0c84511dd92ad0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_A_flatefile]_13##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_A_flatefile: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006C000000000000121800045DD851DF9B17#1229083575199#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820005]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#45bb3be0c84511dd976d0012793ae40c#File2XI[:BService_MDM_SENDER:Outbound_From_MDM2]_12##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006C000000020000121800045DD851DF9DBA#1229083575199#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFtpList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#45bb3be0c84511dd976d0012793ae40c#File2XI[:BService_MDM_SENDER:Outbound_From_MDM2]_12##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel Outbound_From_MDM2: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006D000000000000121800045DD851F43711#1229083576557#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820007]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#467eb2f0c84511ddce9a0012793ae40c#File2XI[:BS_Sat:MsgMerge_Sender1_CC]_48##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006D000000020000121800045DD851F439AA#1229083576557#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#467eb2f0c84511ddce9a0012793ae40c#File2XI[:BS_Sat:MsgMerge_Sender1_CC]_48##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel MsgMerge_Sender1_CC: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006D000000040000121800045DD85210BEE6#1229083578416#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BSRDF:CC_BSRDF]_545##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C006C000000040000121800045DD852118EE5#1229083578479#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDG]_546##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C006C000000060000121800045DD8522A479D#1229083580087#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDE]_547##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C006D000000060000121800045DD8522AB3A6#1229083580119#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BSRD:CC_BSRD]_548##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
    #1.5#0012793AE40C006C000000080000121800045DD852509FDA#1229083582602#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDF]_549##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
    #1.5#0012793AE40C006E000000000000121800045DD852544076#1229083582836#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000a]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4982cb30c84511ddbd890012793ae40c#File2XI[:BS_Sat1:MsgMerge_Sender2_CC]_69##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006E000000020000121800045DD85254AFC8#1229083582868#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4982cb30c84511ddbd890012793ae40c#File2XI[:BS_Sat1:MsgMerge_Sender2_CC]_69##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel MsgMerge_Sender2_CC: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006F000000000000121800045DD852569148#1229083582993#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000b]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#499a98f0c84511ddb0c20012793ae40c#File2XI[:BS_PAUDV:CC_PAUDV_SEND]_134##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C006F000000020000121800045DD852569409#1229083582993#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#499a98f0c84511ddb0c20012793ae40c#File2XI[:BS_PAUDV:CC_PAUDV_SEND]_134##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_PAUDV_SEND: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006E000000040000121800045DD85256A507#1229083582993#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0####4b23f810c84511ddc7d30012793ae40c#File2XI[:BSRDE:CC_BSRDE]_558##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
    #1.5#0012793AE40C006F000000040000121800045DD85258BFEE#1229083583133#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0####4b3954d0c84511dd846c0012793ae40c#File2XI[:BSRDG:CC_BSRDG]_562##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
    #1.5#0012793AE40C0070000000000000121800045DD8527941A5#1229083585273#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000d]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4b370ae0c84511dd8e0c0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_Sending_file]_183##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0070000000020000121800045DD8527943FF#1229083585273#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4b370ae0c84511dd8e0c0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_Sending_file]_183##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_Sending_file: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0071000000000000121800045DD852A635CB#1229083588210#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000f]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4c8e3670c84511dd94bf0012793ae40c#File2XI[:BS_PAUD:CC_POAUDSEND]_240##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0071000000020000121800045DD852A63A01#1229083588210#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4c8e3670c84511dd94bf0012793ae40c#File2XI[:BS_PAUD:CC_POAUDSEND]_240##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_POAUDSEND: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0072000000000000121800045DD852AF7377#1229083588819#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200011]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cad3020c84511ddb7490012793ae40c#File2XI[:BS_SEND2:CC_MERVSEND2]_250##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0072000000020000121800045DD852AF7668#1229083588819#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cad3020c84511ddb7490012793ae40c#File2XI[:BS_SEND2:CC_MERVSEND2]_250##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_MERVSEND2: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0073000000000000121800045DD852BBB4AD#1229083589615#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200013]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cdf3ca0c84511dd8c190012793ae40c#File2XI[:BS_BLR:FileSender_BPM]_238##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0073000000020000121800045DD852BBB87F#1229083589615#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cdf3ca0c84511dd8c190012793ae40c#File2XI[:BS_BLR:FileSender_BPM]_238##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FileSender_BPM: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0056000000020000121800045DD852BC3912#1229083589647#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200016]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4d1abf00c84511dda6510012793ae40c#File2XI[:BS_BLR:FWS_SEND_CC]_268##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0056000000040000121800045DD852BC3B81#1229083589662#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4d1abf00c84511dda6510012793ae40c#File2XI[:BS_BLR:FWS_SEND_CC]_268##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FWS_SEND_CC: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C0074000000000000121800045DD852CD926F#1229083590787#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200017]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4e3d9420c84511ddc5950012793ae40c#File2XI[:BS_Sat:FileSender_FCC]_252##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
    #1.5#0012793AE40C0074000000020000121800045DD852CD94EB#1229083590787#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4e3d9420c84511ddc5950012793ae40c#File2XI[:BS_Sat:FileSender_FCC]_252##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FileSender_FCC: Sending file failed with java.lang.NullPointerException - continue processing#
    #1.5#0012793AE40C006D000000080000121800045DD853948DA4#1229083603829#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BS_DIPANKAR1_SENDER:Sender_CC]_553##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel Sender_CC: Directory
    192.168.91.1
    D:
    SAP_Data does not exist#
    #1.5#0012793AE40C0075000000010000121800045DD86BA73EED#1229084007463#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#RIJUA                           #4446C8DDBF70F1DAB51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_79##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
    #1.5#0012793AE40C0075000000030000121800045DD8861A181C#1229084450980#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#PI7BASIS                        #4F47C8DD65E5F12CB51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_79##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
    #1.5#0012793AE40C0076000000010000121800045DD88E669A80#1229084590160#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#SAPSYS                          #9D47C8DD4EE4F161B51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_95##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
    #1.5#0012793AE40C0076000000030000121800045DD899BD67E0#1229084780325#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#RIJUA                           #1448C8DDD335F1E5B51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_95##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
    #1.5#0012793AE40C0078000000010000121800045DD899EAE617#1229084783309#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##HE6#SAPSYS                          #81C1A9AA09F24B0894CFA72F264F2842#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/System/Server#Plain###bean SLDJAVA_ACCESSOR_REQUEST not found#
    #1.5#0012793AE40C0079000000010000121800045DD899EB397B#1229084783325#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##HE6#SAPSYS                          #81C1A9AA09F24B0894CFA72F264F2842#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Server#Plain###bean SLDJAVA_ACCESSOR_REQUEST not found#
    #1.5#0012793AE40C007B000000010000121800045DD8F60F3B22#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: received EOF, connection closed!#
    #1.5#0012793AE40C007B000000030000121800045DD8F60F4058#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: receive failed (Connection closed -1)#
    #1.5#0012793AE40C007B000000050000121800045DD8F60F425A#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: receive failed (Encomi: receive failed (Connection closed -1) -1), flush pending responses#
    #1.5#0012793AE40C007C000000000000121800045DD8F6115F52#1229086329505#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()######b0307110c84b11ddab1b0012793ae40c#SAP J2EE Engine|MS Socket Listener##0#0#Error##Plain###java.net.SocketException: Connection reset#
    #1.5#0012793AE40C007C000000010000121800045DD8F611603B#1229086329505#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()######b0307110c84b11ddab1b0012793ae40c#SAP J2EE Engine|MS Socket Listener##0#0#Error##Plain###java.net.SocketException: Connection reset
         at java.net.SocketInputStream.read(SocketInputStream.java:168)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
         at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
         at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.read(MSMessageHeader.java:440)
         at com.sap.engine.core.cluster.impl6.ms.MSMessageObjectImpl.readHeader(MSMessageObjectImpl.java:142)
         at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage(MSRawConnection.java:1660)
         at com.sap.engine.core.cluster.impl6.ms.MSListener.run(MSListener.java:86)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5#0012793AE40C007B000000070000121800045DD8F61E7D39#1229086330364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000090000121800045DD8F61E7F00#1229086330364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 1 times#
    #1.5#0012793AE40C007B0000000B0000121800045DD8F64AFC71#1229086333286#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000000D0000121800045DD8F6791AC5#1229086336302#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000000F0000121800045DD8F6A58D15#1229086339224#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000110000121800045DD8F6D20F7F#1229086342130#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000130000121800045DD8F6FE9326#1229086345052#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000150000121800045DD8F72CA0FC#1229086348067#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000170000121800045DD8F75795FA#1229086350880#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000190000121800045DD8F78418D5#1229086353802#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000001B0000121800045DD8F7B3C822#1229086356927#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000001D0000121800045DD8F7E02F82#1229086359833#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000001F0000121800045DD8F7E030C2#1229086359833#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 11 times#
    #1.5#0012793AE40C007B000000210000121800045DD8F80CB555#1229086362755#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000230000121800045DD8F83ABD55#1229086365770#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000250000121800045DD8F8674E72#1229086368692#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000270000121800045DD8F893C188#1229086371614#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000290000121800045DD8F8C1CD8A#1229086374630#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000002B0000121800045DD8F8EE5019#1229086377536#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000002D0000121800045DD8F91AD274#1229086380458#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000002F0000121800045DD8F947537E#1229086383379#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000310000121800045DD8F976E8A3#1229086386489#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000330000121800045DD8F9A36A4A#1229086389411#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000350000121800045DD8F9A36B62#1229086389411#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 21 times#
    #1.5#0012793AE40C007B000000370000121800045DD8F9D175D4#1229086392426#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000390000121800045DD8F9FDFF04#1229086395348#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000003B0000121800045DD8FA2A7A76#1229086398270#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007F000000010000121800045DD8FA49473F#1229086400285#com.sap.aii.utilxi.prop.impl.BasicPropertySource##com.sap.aii.utilxi.prop.impl.BasicPropertySource#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#158b1d00c84511dd9fed0012793ae40c#SAPEngine_Application_Thread[impl:3]_27##0#0#Error#1#/Applications/ExchangeInfrastructure#Plain###could not sync ExchangeProfile:
    Thrown:
    com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=HCL3SAP SYSNR=00 GWHOST=HCL3SAP GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner '10.112.132.211:sapgw00' not reached
    TIME        Fri Dec 12 18:23:20 2008
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     1
    Connect_PM  TYPE=A ASHOST=HCL3SAP SYSNR=00 GWHOST=HCL3SAP GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner '10.112.132.211:sapgw00' not reached
    TIME        Fri Dec 12 18:23:20 2008
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     1
         at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
         at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:989)
         at com.sap.mw.jco.JCO$Client.connect(JCO.java:3193)
         at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:101)
         at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1286)
         at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:193)
         at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.readProfile(ExchangeProfilePropertySource.java:177)
         at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.sync(ExchangeProfilePropertySource.java:165)
         at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:580)
         at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43)
         at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:52)
         at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:167)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#0012793AE40C007B0000003D0000121800045DD8FA56FC49#1229086401176#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B0000003F0000121800045DD8FA83A493#1229086404114#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000410000121800045DD8FAB189C5#1229086407113#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
    #1.5#0012793AE40C007B000000430000121800045DD8FADF9505#1229086410129#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engin

  • Java server0 is yellow

    hi i have installed nw2004s.abap level it is working fine.when i tried to log in portal ac j2ee_admin.i can login but if i click on any tabs .then error 503 is coming and java server0 and disp+work are turning green to yello.any one pls help me out..
    my disp+work trc file is
    trc file: "dev_disp", trc level: 1, release: "700"
    sysno      00
    sid        CRT
    systemid   562 (PC with Windows NT)
    relno      7000
    patchlevel 0
    patchno    75
    intno      20050900
    make:      multithreaded, Unicode, 64 bit, optimized
    pid        3508
    Mon Feb 25 17:04:41 2008
    kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)
    length of sys_adm_ext is 572 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (00 3508) [dpxxdisp.c   1237]
         shared lib "dw_xml.dll" version 75 successfully loaded
         shared lib "dw_xtc.dll" version 75 successfully loaded
         shared lib "dw_stl.dll" version 75 successfully loaded
         shared lib "dw_gui.dll" version 75 successfully loaded
         shared lib "dw_mdm.dll" version 75 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    Mon Feb 25 17:04:46 2008
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5273]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: start server >crmtest_CRT_00                          <
    DpShMCreate: sizeof(wp_adm)          18512     (1424)
    DpShMCreate: sizeof(tm_adm)          5258160     (26160)
    DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
    DpShMCreate: sizeof(comm_adm)          552080     (1088)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)          0     (72)
    DpShMCreate: sizeof(vmc_adm)          0     (1744)
    DpShMCreate: sizeof(wall_adm)          (41664/36752/64/192)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 000000000CFD0050, size: 5947376)
    DpShMCreate: allocated sys_adm at 000000000CFD0050
    DpShMCreate: allocated wp_adm at 000000000CFD1F00
    DpShMCreate: allocated tm_adm_list at 000000000CFD6750
    DpShMCreate: allocated tm_adm at 000000000CFD67B0
    DpShMCreate: allocated wp_ca_adm at 000000000D4DA360
    DpShMCreate: allocated appc_ca_adm at 000000000D4E0120
    DpShMCreate: allocated comm_adm at 000000000D4E2060
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 000000000D568CF0
    DpShMCreate: allocated gw_adm at 000000000D568D70
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 000000000D568DA0
    DpShMCreate: allocated wall_adm at 000000000D568DB0
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    Using implementation flat
    <EsNT> Memory Reset disabled as NT default
    <ES> 127 blocks reserved for free list.
    ES initialized.
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3992
      argv[0] = F:\usr\sap\CRT\DVEBMGS00\exe\jcontrol.EXE
      argv[1] = F:\usr\sap\CRT\DVEBMGS00\exe\jcontrol.EXE
      argv[2] = pf=F:\usr\sap\CRT\SYS\profile\CRT_DVEBMGS00_crmtest
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1105
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=CRT
      argv[7] = -DSAPMYNAME=crmtest_CRT_00
      argv[8] = -DSAPPROFILE=F:\usr\sap\CRT\SYS\profile\CRT_DVEBMGS00_crmtest
      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 ( 3.0 3.0 4.0.1) [dpxxdisp.c   1623]
    ***LOG Q0K=> DpMsAttach, mscon ( crmtest) [dpxxdisp.c   11586]
    DpStartStopMsg: send start message (myname is >crmtest_CRT_00                          <)
    DpStartStopMsg: start msg sent
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
    Mon Feb 25 17:04:47 2008
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpJ2eeLogin: j2ee state = CONNECTED
    DpMsgAdmin: Set release to 7000, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
    DpMsgAdmin: Set patchno for this platform to 75
    Release check o.K.
    Mon Feb 25 17:04:58 2008
    MBUF state ACTIVE
    DpModState: change server state from STARTING to ACTIVE
    Mon Feb 25 17:05:50 2008
    J2EE server info
      start = TRUE
      state = ACTIVE
      pid = 3992
      http = 50000
      https = 50001
      load balance = 1
      start_lazy = 0
      start_control = SAP J2EE startup framework
    Edited by: subba reddy on Feb 28, 2008 10:34 AM

    Hello subba reddy,
    To know better the cause of the problem, please post here the content of dev_server0 and std_dispatcher.out trace files.
    Best regards,
    Rafael Toshiaki
    PS: Please consider rewarding points for helpful answers on SDN.

  • Java Server0 failing - rc = -11113

    Hi
    We have installed SCM 5.0 with the ABAP+Java stack, i noticed that the java stack was not running, and when i checked the std_server0.out file, it was giving an error saying user/password was incorrect for user SAPJSF, I reset the password for user SAPJSF in SU01 and reset the password to match in the config tool global server :
    ume.r3.connection.master.passwd
    That appears to have cleared that error, now when I start Java, the server0 its erroring in dev_server0 :
    [Thr 5996] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 5996] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 5996] JLaunchCloseProgram: good bye (exitcode = -11113)
    Looking in the std_server0.out file, there are 2 errors :
      Service com.sap.security.core.ume.service started. (1250 ms).
    Jul 10, 2007 12:19:51... ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_16] Fatal: <b>Can not instantiate UserContext with given properties.</b>  service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: <b>No active userstore is set.</b>
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    Here is the full std_server0.out file :
    stdout/stderr redirect
    node name   : server0
    pid         : 3728
    system name : ***
    system nr.  : 00
    started at  : Tue Jul 10 12:19:42 2007
    [Thr 2760] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 313 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 47 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 15 ms.
    Loading: ClassLoaderManager ... 0 ms.
    Loading: ClusterManager ... 110 ms.
    Loading: LockingManager ... 47 ms.
    Loading: ConfigurationManager ... 1140 ms.
    Loading: LicensingManager ... 16 ms.
    Loading: CacheManager ... 78 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service cross started. (16 ms).
      Service memory started. (31 ms).
      Service runtimeinfo started. (16 ms).
      Service file started. (93 ms).
      Service timeout started. (31 ms).
      Service userstore started. (62 ms).
      Service trex.service started. (109 ms).
      Service jmx_notification started. (78 ms).
      Service p4 started. (172 ms).
      Service classpath_resolver started. (16 ms).
      Service deploy started. (2312 ms).
      Service MigrationService started. (32 ms).
      Service bimmrdeployer started. (16 ms).
      Service log_configurator started. (2578 ms).
      Service locking started. (0 ms).
      Service http started. (109 ms).
      Service naming started. (157 ms).
      Service failover started. (31 ms).
      Service appclient started. (31 ms).
      Service javamail started. (46 ms).
      Service ts started. (46 ms).
      Service jmsconnector started. (46 ms).
      Service licensing started. (0 ms).
      Service connector started. (94 ms).
      Service iiop started. (78 ms).
      Service configuration started. (16 ms).
      Service webservices started. (281 ms).
      Service dbpool started. (562 ms).
      Service com.sap.security.core.ume.service started. (1250 ms).
    Jul 10, 2007 12:19:51... ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_16] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more
    [Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
    Jul 10, 2007 12:19:51...            com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_16] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
    Anywhere else I can get more info on the error ?
    Any help appreciated.

    Hi Anand
    Java Instance is now up and running after creating the  users J2EE_ADMIN and J2EE_GUEST, so I set the post as answered.
    The only thing I am still not sure on is why the J2EE_ADMIN and J2EE_GUEST were not created as part of the install, I have reviewed the install document I created with the screen shots from SAPINST and it asked me to enter passwords for these users, which I did, so I presumed these users would be created in the install as with my previous NW04 installs, but this is my first SCM 5.0 on NW04S, so maybe its changed on NW04S ?
    I Patched ABAP to SP Stack 10 and used JSPM to patch from 9.2 to 10.1 straight after the install.
    Its only when I created users J2EE_ADMIN and J2EE_GUEST  with the correct roles assigned that Java started correctly.
    Looking at the SAP Help supplied above, it says that dependant on type of install, different JAVA users are created, but I installed ABAP + JAVA, so I think these users should be created.
    Paul.

  • Central Instance Java Server0/Server1 not starting

    We recently installed a new dialog instance for our CUA system (abap and java stacks). Now, whenever the Java stack fully initializes itself on the Dialong Instance first, the Server0 and Server1 on the Central Instance Java stack will not complete their startups. Both Server0 and Server1 get stuck on the "Starting Apps" status. Anybody see this before? Any suggestions on how to fix/reconfigure the java so that this does not happen?
    Currently, our work around is to always let the Central Instance finish its startup and then start the Dialong Instance. However, if the CI Java crashes and restarts on its own, it will not be able to complete its startup until we shut down the DI instance.
    Thanks.

    andreas,
    Here is a partial std_server0.out file. It seems that the dumping/memory/locking problem starts immediately after the Framework has started:
    ServiceManager started for 354203 ms.
    Framework started for 422687 ms.
    SAP J2EE Engine Version 7.00   PatchLevel 109886.44 is running!
    PatchLevel 109886.44 November 17, 2007 10:27 GMT
    Full thread dump Java HotSpot(TM) 64-Bit Server VM (1.4.2_13-b06 mixed mode):
    "DSR_Write_Rate_Monitor: DOWNEAVM249.dow_DGD_407398750" prio=5 tid=0x000000001a6b9860 nid=0x4864 runnable [0x0000000000000000..0x0000000000000000]
    "Thread-33" prio=5 tid=0x000000001a6b95d0 nid=0x4230 runnable [0x0000000000000000..0x0000000000000000]
    "Thread-32" daemon prio=10 tid=0x000000001a6b90b0 nid=0x5044 in Object.wait() [0x000000001de1f000..0x000000001de1fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008eff2080> (a java.util.TaskQueue)
         at java.util.TimerThread.mainLoop(Timer.java:429)
         - locked <0x000000008eff2080> (a java.util.TaskQueue)
         at java.util.TimerThread.run(Timer.java:382)
    "SAPEngine_CCMSCommandConsumer_0" prio=10 tid=0x000000001ac73d80 nid=0x1b1c in Object.wait() [0x000000001dc1f000..0x000000001dc1fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008eff0108> (a java.lang.Object)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.concurrent.LinkedQueue.take(LinkedQueue.java:104)
         - locked <0x000000008eff0108> (a java.lang.Object)
         at com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer.run(CCMSCommandConsumer.java:38)
         at java.lang.Thread.run(Thread.java:534)
    "Thread-29" prio=10 tid=0x000000001ac73860 nid=0x2a64 in Object.wait() [0x000000001da1f000..0x000000001da1fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008eff01d0> (a com.sap.jmx.provider.ProviderConnectionTimer)
         at com.sap.jmx.provider.ProviderConnectionTimer.run(ProviderConnectionTimer.java:31)
         - locked <0x000000008eff01d0> (a com.sap.jmx.provider.ProviderConnectionTimer)
         at java.lang.Thread.run(Thread.java:534)
    "Thread-28" prio=10 tid=0x0000000008d2dad0 nid=0x4bf4 in Object.wait() [0x000000001d81f000..0x000000001d81fb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008eff0268> (a com.sap.jmx.provider.LazyMBeanLoader)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.jmx.provider.LazyMBeanLoader.run(LazyMBeanLoader.java:133)
         - locked <0x000000008eff0268> (a com.sap.jmx.provider.LazyMBeanLoader)
         at java.lang.Thread.run(Thread.java:534)
    "SAPEngine_Application_Thread[impl:3]_1" prio=5 tid=0x00000000012e4920 nid=0x38b0 in Object.wait() [0x0000000007daf000..0x0000000007dafb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008fb8f078> (a com.sap.engine.lib.util.WaitQueue)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000008fb8f078> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:149)
    "SAPEngine_Application_Thread[impl:3]_0" prio=5 tid=0x00000000012e4690 nid=0xc20 in Object.wait() [0x00000000079af000..0x00000000079afb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008fb8f078> (a com.sap.engine.lib.util.WaitQueue)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)
         - locked <0x000000008fb8f078> (a com.sap.engine.lib.util.WaitQueue)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:149)
    "Thread-1" prio=5 tid=0x00000000012e4170 nid=0x3a68 in Object.wait() [0x0000000007baf000..0x0000000007bafb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008fbbf530> (a com.sap.engine.core.Framework)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.core.Framework.start(Framework.java:207)
         - locked <0x000000008fbbf530> (a com.sap.engine.core.Framework)
         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.boot.FrameThread.run(FrameThread.java:61)
         at java.lang.Thread.run(Thread.java:534)
    "Signal Dispatcher" daemon prio=10 tid=0x00000000012e34a0 nid=0x2334 waiting on condition [0x0000000000000000..0x0000000000000000]
    "Finalizer" daemon prio=9 tid=0x00000000012e3210 nid=0x23c8 in Object.wait() [0x0000000006baf000..0x0000000006bafb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x00000000909192e0> (a java.lang.ref.ReferenceQueue$Lock)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
         - locked <0x00000000909192e0> (a java.lang.ref.ReferenceQueue$Lock)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
         at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
    "Reference Handler" daemon prio=10 tid=0x00000000012e2f80 nid=0x1438 in Object.wait() [0x00000000069af000..0x00000000069afb80]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008f9a61d0> (a java.lang.ref.Reference$Lock)
         at java.lang.Object.wait(Object.java:429)
         at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
         - locked <0x000000008f9a61d0> (a java.lang.ref.Reference$Lock)
    "main" prio=5 tid=0x00000000012e2cf0 nid=0x3cb8 in Object.wait() [0x000000000222f000..0x000000000222fc68]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x000000008fbbf3e0> (a com.sap.engine.boot.StartFrame)
         at java.lang.Object.wait(Object.java:429)
         at com.sap.engine.boot.StartFrame.work(StartFrame.java:121)
         - locked <0x000000008fbbf3e0> (a com.sap.engine.boot.StartFrame)
         at com.sap.engine.boot.Start.main(Start.java:34)
    "VM Thread" prio=5 tid=0x000000000137a4a0 nid=0x3cac runnable
    "VM Periodic Task Thread" prio=10 tid=0x000000000137a6a0 nid=0xccc waiting on condition
    "Suspend Checker Thread" prio=10 tid=0x000000000137a5a0 nid=0x67c runnable
      Service tc.monitoring.logviewer started. (89484 ms).
    >
    Login :### Excluding compile:  com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
    Excluding compile:  com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType::_loadInto
    Thanks, Bruce

  • Java server0 its not starting  with error -11113

    Dear Experts team,
    When We are starting SAP Solution Manager 7.10, Its ABAP Instance is running file ,
    But Java Instance not running , In this Java Process table , SDM and dispatcher is working file (green)
    But in server0 its not starting  and -11113 (core service or addition service start fails)
    When check Developer Trace of dev_server0 , it show last few lines as given below,
    Thr 5464] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 5464] **********************************************************************
    [Thr 5464] *** ERROR => The Java VM terminated with a non-zero exit code.
    [Thr 5464] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    [Thr 5464] *** for additional information and trouble shooting.
    [Thr 5464] **********************************************************************
    [Thr 5464] JLaunchCloseProgram: good bye (exitcode = -11113)
    Please suggest ...
    Thanks
    Regards
    Sunil k

    Hi,
    Hope you are doing good.
    Please check the latest STD_SERVER0 and the default traces and attach the contents here. This should have the error details. Exit code 11113 means that some essential service fails to start so the server/dispatcher process fails.
    Thank you!
    Kind Regards,
    Hemanth
    SAP AGS

  • AS Java server0 Initial status - hangs if manually started

    Hi Experts,
    Would like to seek your help on my issue.
    I have a PI 7.10 server running on Windows & MS SQL db (with sapjvm version: 5.1.056,   sapjvm build: 51_REL-20100523)
    I recently performed a restore (DB & SAP) 
    Restore was successul, but when trying to start the instance the disp+work hangs at yellow status with "AS Java: Starting the Processes"
    I checked the AS Java Process Table and I see that the bootstrap is successful (green) but after that I immediately see the status of components as:
    debugproxy --> Status=Disabled
    icm --> Status=Initial
    server0 --> Status=Initial
    I then try to manually start the server0 but it hangs on yellow status with Status=Starting Framework
    I checked the std_server0.out and below is the entries:

    Then I checked the dev_w* and this is what I see:
    A Wed Feb 29 16:19:20 2012
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
    A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_ROLLBACK entered.
    A  ** RABAX: level LEV_RX_ROLLBACK completed.
    A  ** RABAX: level LEV_RX_DB_ALIVE entered.
    A  ** RABAX: level LEV_RX_DB_ALIVE completed.
    A  ** RABAX: level LEV_RX_HOOKS entered.
    A  ** RABAX: level LEV_RX_HOOKS completed.
    A  ** RABAX: level LEV_RX_STANDARD entered.
    A  ** RABAX: level LEV_RX_STANDARD completed.
    A  ** RABAX: level LEV_RX_STOR_VALUES entered.
    A  ** RABAX: level LEV_RX_STOR_VALUES completed.
    A  ** RABAX: level LEV_RX_C_STACK entered.
    A  ** RABAX: level LEV_RX_C_STACK completed.
    A  ** RABAX: level LEV_RX_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_INTERFACES entered.
    A  ** RABAX: level LEV_RX_INTERFACES completed.
    A  ** RABAX: level LEV_RX_GET_MESS entered.
    A  ** RABAX: level LEV_RX_GET_MESS completed.
    A  ** RABAX: level LEV_RX_INIT_SNAP entered.
    A  ** RABAX: level LEV_RX_INIT_SNAP completed.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.
    A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.
    A  ** RABAX: level LEV_SN_END completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP_END entered.
    A  ** RABAX: level LEV_RX_WRITE_SNAP_END completed.
    A  ** RABAX: level LEV_RX_SET_ALERT entered.
    A  ** RABAX: level LEV_RX_SET_ALERT completed.
    A  ** RABAX: level LEV_RX_COMMIT entered.
    A  ** RABAX: level LEV_RX_COMMIT completed.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
    A  ** RABAX: level LEV_RX_RESET_PROGS entered.
    A  ** RABAX: level LEV_RX_RESET_PROGS completed.
    A  ** RABAX: level LEV_RX_STDERR entered.
    A  Wed Feb 29 16:19:20 2012

    A  ABAP Program com.sap.vmc.bootstrap.Bootstrap         .
    A  Source                                          Line 0.
    A  Error Code VM_STACK_TRACE.
    A  Module  $Id: //bas/710_REL/src/krn/th/thxxvmc.c#29 $ SAP.
    A  Function ThVmcWriteStackTraceShortDump Line 8144.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    A  ** RABAX: end RX_RETURN
    A  A Java VM stack trace was created..
    above is seen also as Dumps in ST22
    Line: -
    M  ThVmcEndStackTrace: end stack trace of V1
    M  *** ERROR => ThJGetVmResp2: received resp VMC_J_VM_ABORT [thxxjava.c   5516]
    M  ThVmcCreateStackTrace: create stack trace >Java VM abort<, inProcess=0, fromSched=1
    M  *** ERROR => ThJDeleteVm: Tried 5 times to create vms but failed. Deactivate VMC [thxxjava.c   4895]
    M  ThVmcDeactivate: deactivate VMC
    M  DpVmcSetActive: set vmc state DP_VMC_ENABLED
    M  ThPlgSendErrTxt2: invalid tid/mode/plugin_info_hdl (22/0/0)
    M  in_ThErrHandle: 1
    M  *** ERROR => ThJHandleVmError: java vm returned after error (step 4, th_errno 5, action 1, level 1) [thxxhead.c   11080]
    M  DpVmcGetVmByTmAdm: no VM found for T22/M0/I0 (locked VMs ignored)
    M  ThResetEmMagic: reset em magic for T22/M0/I0
    Line: -
    Aside from this I checked on DB level and I see from the log:
    Error: 18456, Severity:14, state:16
    Login failed for user 'NT AUTHORITY\SYSTEM'.[CLIENT:<local machine>]
    I hope I've provided enough information above for anyone who can help me resolve this error.
    Thanks in advanced

  • Java server0 down

    Hi Expert,
    I have install SAP Solution Manager 7.0 EHP1 system with system copy method.
    My ABAP instance is up and running but JAVA down.
    Log as below, I have also refer the SAP Note 943602, but not help me to resolve the problem.
    Error occurred during initialization of VM
    Incompatible initial and maximum heap sizes specified
    JLaunchIAbortJava: abort hook is called
    ERROR => The Java VM aborted unexpectedly.
    Please see SAP Note 943602 , section 'Java VM crashes'
    for additional information and trouble shooting.
    JLaunchCloseProgram: good bye (exitcode = -2)
    Rgds,
    Ashok

    Thanks RB,
    Issue has been solve after changing the -Xms and -Xmx parameters values in config tool.
    Rgds,
    Ashok

  • Installing another Java server0

    Were having performance problems with running applications in Java.   Is there any good docs on installing a 2nd server or instance?

    This is covered in the normal Netweaver installation guides (http://service.sap.com/instguides).
    Are you sure that the performance problems are caused by too less resources? How did you find out?
    Markus

  • *** ERROR = The Java VM terminated with a non-zero exit code.

    DEAR MASTERS
              after configuring SLD on integerated ABAP+JAVA   server0 not starting   
    trc file: "D:\usr\sap\W55\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID9278150
    pid         : 4140
    system name : W55
    system nr.  : 00
    started at  : Sat Mar 21 08:45:23 2009
    arguments       :
           arg[00] : D:\usr\sap\W55\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
           arg[02] : -DSAPINFO=W55_00_server
           arg[03] : pf=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=1060
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=W55
           arg[08] : -DSAPMYNAME=wipro5_W55_00
           arg[09] : -DSAPPROFILE=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 4668] Sat Mar 21 08:58:30 2009
    [Thr 4668] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 4668] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 4668] JLaunchISetClusterId: set cluster id 9278150
    [Thr 4668] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 4668] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 4428] Sat Mar 21 08:59:58 2009
    [Thr 4428] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 4428] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 4616] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 4616] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.

    Hi,
    Please find the link below for J2EE start up problem.
    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d396d]
    Please refer to following note for VM settings.
    [https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=723909]
    Please also check the license validity on this server.
    Hope this helps.
    Manoj Chintawar

  • Server0 process in yellow and in status "starting apps" from many times

    Hi to all,
    platform windows/SQL
    I have a problem , I just made a system copy of my BI-Java (NW 7.0 SR3 ) using database independent system copy method.
    I make the export : all OK.
    I make the import ( system copy tool sapinst ) : All ok without errors.
    Now I'm tryng to start the Java ap server ( ABAP IS UP AND WORKS ) but it doesn't start : in MMC I see the java server0 process in yellow and in status "starting apps" from many times.
    Please help , what can I do ?

    I Eric ,
    I waited , but still yellow :
    here is the dev_server0 , it is very very  long file so i post most important parts of the log
    trc file: "F:\usr\sap\JBX\JC00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID5856350
    pid         : 2460
    system name : JBX
    system nr.  : 00
    started at  : Mon Nov 15 18:32:02 2010
    arguments       :
           arg[00] : F:\usr\sap\JBX\JC00\exe\jlaunch.exe
           arg[01] : pf=F:\usr\sap\JBX\SYS\profile\JBX_JC00_sappino
           arg[02] : -DSAPINFO=JBX_00_server
           arg[03] : pf=F:\usr\sap\JBX\SYS\profile\JBX_JC00_sappino
    [Thr 1676] Mon Nov 15 18:32:02 2010
    [Thr 1676] *** WARNING => INFO: Unknown property [instance.box.number=JBXJC00sappino] [jstartxx.c   841]
    [Thr 1676] *** WARNING => INFO: Unknown property [instance.en.host=sappino] [jstartxx.c   841]
    [Thr 1676] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 1676] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties]
    -> ms host    : sappino
    -> ms port    : 3901
    -> OS libs    : F:\usr\sap\JBX\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : sappino
    -> ms port    : 3901
    -> os libs    : F:\usr\sap\JBX\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID5856300  : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID5856350  : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID5856300            : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    -> [01] ID5856350            : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    [Thr 1676] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 1676] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 2796] JLaunchRequestFunc: Thread 2796 started as listener thread for np messages.
    [Thr 1116] WaitSyncSemThread: Thread 1116 started as semaphore monitor thread.
    [Thr 1676] Mon Nov 15 18:32:03 2010
    [Thr 1676] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 1676] CPIC (version=700.2006.09.13)
    [Thr 1676] [Node: server0] java home is set by profile parameter
         Java Home: C:\JAVA_SDK_64BIT
    [Thr 1676] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\JBX\JC00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID5856350]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\JAVA_SDK_64BIT
    -> java parameters    : -Djco.jarm=1 -verbose:gc -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -XX:NewSize=341m -XX:MaxNewSize=341m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:PrintGCDetails -XX:+PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version    : 1.4.2_26-b03
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> stack size         : 2M
    -> root path          : F:\usr\sap\JBX\JC00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\JBX\JC00\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     : F:\usr\sap\JBX\JC00\exe\jstartup.jar;F:\usr\sap\JBX\JC00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 1676] JLaunchISetDebugMode: set debug mode [no]
    [Thr 2372] JLaunchIStartFunc: Thread 2372 started as Java VM thread.
    [Thr 2372] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
         Java Parameters: -Xss2m
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -verbose:gc
    -> arg[  5]: -Djava.awt.headless=true
    -> arg[  6]: -Dsun.io.useCanonCaches=false
    -> arg[  7]: -Djava.security.policy=./java.policy
    -> arg[  8]: -Djava.security.egd=file:/dev/urandom
    -> arg[  9]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 10]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 11]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 12]: -XX:NewSize=341m
    -> arg[ 13]: -XX:MaxNewSize=341m
    -> arg[ 14]: -XX:MaxPermSize=192m
    -> arg[ 15]: -XX:PermSize=192m
    -> arg[ 16]: -XX:+DisableExplicitGC
    -> arg[ 17]: -XX:+PrintGCDetails
    -> arg[ 18]: -XX:+PrintGCTimeStamps
    -> arg[ 19]: -XX:SurvivorRatio=2
    -> arg[ 20]: -XX:TargetSurvivorRatio=90
    -> arg[ 21]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 22]: -verbose:gc
    -> arg[ 23]: -Dsys.global.dir=F:\usr\sap\JBX\SYS\global
    -> arg[ 24]: -Dapplication.home=F:\usr\sap\JBX\JC00\exe
    -> arg[ 25]: -Djava.class.path=F:\usr\sap\JBX\JC00\exe\jstartup.jar;F:\usr\sap\JBX\JC00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 26]: -Djava.library.path=C:\JAVA_SDK_64BIT\jre\bin\server;C:\JAVA_SDK_64BIT\jre\bin;C:\JAVA_SDK_64BIT\bin;F:\usr\sap\JBX\JC00\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;F:\usr\sap\JBX\SYS\exe\uc\NTAMD64
    -> arg[ 27]: -Dmemory.manager=2048M
    -> arg[ 28]: -Xmx2048M
    -> arg[ 29]: -Xms2048M
    -> arg[ 30]: -Xss2M
    -> arg[ 31]: -DLoadBalanceRestricted=no
    -> arg[ 32]: -Djstartup.mode=JCONTROL
    -> arg[ 33]: -Djstartup.ownProcessId=2460
    -> arg[ 34]: -Djstartup.ownHardwareId=M1883233260
    -> arg[ 35]: -Djstartup.whoami=server
    -> arg[ 36]: -Djstartup.debuggable=no
    -> arg[ 37]: -Xss2m
    -> arg[ 38]: -DSAPINFO=JBX_00_server
    -> arg[ 39]: -DSAPSTARTUP=1
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=JBX
    -> arg[ 42]: -DSAPMYNAME=sappino_JBX_00
    -> arg[ 43]: -DSAPDBHOST=SAPPINO
    -> arg[ 44]: -Dj2ee.dbhost=SAPPINO
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 2372] Mon Nov 15 18:32:04 2010
    [Thr 2372] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 3844] Mon Nov 15 18:32:07 2010
    [Thr 3844] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 3844] Mon Nov 15 18:32:08 2010
    [Thr 3844] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 3844] Mon Nov 15 18:32:09 2010
    [Thr 3844] JLaunchISetClusterId: set cluster id 5856350
    [Thr 3844] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 3844] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    Mon Nov 15 18:33:09 2010
    66.769: [GC 66.779: [DefNew
    Mon Nov 15 18:33:12 2010
    : 174592K->12719K(261888K), 2.4968787 secs] 174592K->12719K(2009856K), 2.5007114 secs]
    Mon Nov 15 18:33:28 2010
    85.012: [GC 85.019: [DefNew
    Mon Nov 15 18:33:31 2010
    : 187311K->15802K(261888K), 2.9950002 secs] 187311K->15802K(2009856K), 2.9962968 secs]
    Mon Nov 15 18:33:42 2010
    99.362: [GC 99.363: [DefNew
    Mon Nov 15 18:33:43 2010
    : 190394K->18114K(261888K), 1.3817075 secs] 190394K->18114K(2009856K), 1.3817727 secs]
    Mon Nov 15 18:34:04 2010
    121.270: [GC 121.270: [DefNew: 192706K->22709K(261888K), 0.4353252 secs] 192706K->22709K(2009856K), 0.4354424 secs]
    Mon Nov 15 18:34:14 2010
    131.077: [GC 131.079: [DefNew
    Mon Nov 15 18:34:15 2010
    : 197301K->29493K(261888K), 0.9813876 secs] 197301K->29493K(2009856K), 0.9823920 secs]
    [Thr 3344] Mon Nov 15 18:34:36 2010
    [Thr 3344] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    Mon Nov 15 18:34:44 2010
    160.965: [GC 160.966: [DefNew
    Mon Nov 15 18:34:47 2010
    : 204085K->40068K(261888K), 3.8189779 secs] 204085K->40068K(2009856K), 3.8194810 secs]
    [Thr 3532] Mon Nov 15 18:34:54 2010
    [Thr 3532] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 4932] Mon Nov 15 18:34:57 2010
    [Thr 4932] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    Mon Nov 15 18:35:09 2010
    186.312: [GC 186.315: [DefNew: 214660K->44513K(261888K), 0.4742509 secs] 214660K->44513K(2009856K), 0.4773469 secs]
    [Thr 3844] Mon Nov 15 18:38:32 2010
    [Thr 3844] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    Mon Nov 15 18:39:18 2010
    435.575: [GC 435.576: [DefNew: 219105K->48184K(261888K), 0.2394759 secs] 219105K->48184K(2009856K), 0.2397480 secs]
    Mon Nov 15 18:39:20 2010
    Excluding compile:  com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
    Mon Nov 15 18:39:23 2010
    440.506: [GC 440.506: [DefNew: 222776K->50686K(261888K), 0.1335379 secs] 222776K->50686K(2009856K), 0.1335965 secs]
    Mon Nov 15 19:42:07 2010
    [Unloading class sun.reflect.GeneratedMethodAccessor14]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor127]
    [Unloading class sun.reflect.GeneratedMethodAccessor13]
    [Unloading class sun.reflect.GeneratedMethodAccessor105]
    [Unloading class sun.reflect.GeneratedMethodAccessor99]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor135]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor4]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor96]
    [Unloading class sun.reflect.GeneratedMethodAccessor128]
    Mon Nov 15 19:42:08 2010
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor17]
    [Unloading class sun.reflect.GeneratedMethodAccessor119]
    [Unloading class sun.reflect.GeneratedMethodAccessor64]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor29]
    [Unloading class sun.reflect.GeneratedMethodAccessor47]
    [Unloading class sun.reflect.GeneratedMethodAccessor86]
    [Unloading class sun.reflect.GeneratedConstructorAccessor72]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor14]
    [Unloading class sun.reflect.GeneratedMethodAccessor109]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor82]
    [Unloading class sun.reflect.GeneratedMethodAccessor156]
    [Unloading class sun.reflect.GeneratedMethodAccessor147]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor94]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor65]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor93]
    Mon Nov 15 19:42:09 2010
    [Unloading class sun.reflect.GeneratedMethodAccessor107]
    [Unloading class sun.reflect.GeneratedMethodAccessor142]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor2]
    Mon Nov 15 20:19:06 2010
    : 1488916K->1046521K(1747968K), 3204.1629115 secs] 1749638K->1046521K(2009856K), 3204.1631834 secs]

  • Visual admin error on default trace on server0

    HI,
    We have a recurrent error log which occurs all 5 minutes in the default trace in our Was Java (server0 node).
    ACCESS.ERROR: Authorization check for caller assignment to J2EE security role [SAP-J2EE-Engine : administrators].
    The user that throw this error is PIRWBUSER.
    please, can you help us ?
    Thanks.

    Hi Stephane,
                     The following thread will help to resolve the problem.
    please check it.
    Error in SP13; Authorization check for caller assignment
    Re: Too many exception"ACCESS.ERROR: Authorization check"
    regards
    mahesh.

  • Java engine getting restarted

    Hi,
    We are using SAP Netweaver 2004s dual stack system which also includes Portal .when we try to access portal the java server0 is getting restarted frequently. When we checked relevant logs we came across the error OUT OF MEMORY .
    Even Some time we are not able to login to Portal as it comes back to same login page with out any error Msg.
    I am finding this error in Server0 Log --FATAL: Caught OutOfMemoryError! Node will exit with exit code 666
    System Configuration - Xenon 64 bit,RAM 8 GB, Paging memory 25 GB. wIDOWS 2003 Ent , Oracle 10.2 DB
    Current Java parameters Settings -
    servers general
    -Djava.security.policy=./java.policy
    -Djava.security.egd=file:/dev/urandom
    -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser
    -verbose:gc
    -Xmx1024m
    -Xms1024m
    -Djco.jarm=1
    -XX:PermSize=512m
    -XX:MaxPermSize=512m
    -XX:NewSize=320m
    -XX:MaxNewSize=320m
    -XX:SurvivorRatio=2
    -XX:TargetSurvivorRatio=90
    -XX:+PrintGCTimeStamps
    -XX:+UseTLAB
    -XX:SoftRefLRUPolicyMSPerMB=1
    -Dsun.io.useCanonCaches=false
    -Djava.awt.headless=true
    -Xss2m
    -XX:+UseParNewGC
    Server 0
    -Djco.jarm=1
    -XX:MaxPermSize=256M
    -XX:PermSize=256M
    -Xms1024M
    -XX:NewSize=171M
    -XX:MaxNewSize=171M
    -XX:+DisableExplicitGC
    -verbose:gc
    -XX:+PrintGCDetails
    -XX:+PrintGCTimeStamps
    -Djava.awt.headless=true
    -Dsun.io.useCanonCaches=false
    -XX:SoftRefLRUPolicyMSPerMB=1
    -XX:SurvivorRatio=2
    -XX:TargetSurvivorRatio=90
    -Djava.security.policy=./java.policy
    -Djava.security.egd=file:/dev/urandom
    -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    Help in this regard highly appreciated.

    Hi,
    Increase the value of heap size.
    -Xmx1024m
    -Xms1024m
    Make it as
    -Xmx2048m
    -Xms2048m
    after changing the parameter restart the application and test it , it should work.
    Follow the below note , which willl help you to solve the problem of OutOfMemory problem in JAVA
    723909 - Java VM settings for J2EE 6.40/7.0for more details
    Thanks
    Anil
    Edited by: Anil Bhandary on Oct 28, 2009 2:16 PM

  • APO Landscape

    Hi together,
    we plan to run an APO System.
    I want to use a iSeries Partition for all parts, which are running on System i  !!!
    How do the landscape looks like?
    For example:
    1.) SCM on IBM i with DB2 !
         Abap ?!
         Java (SERVER0) ?!
    2.) Live Cache on WIN64 2003 Server with what DB ?!
    Sizing:
    1.) How much Space for running only  APO-gATP?
    2.) 1 CPU or 2 CPU on IBM i
    3.) How much Disks Arms on IBM i ?
    Where is the MAINLOAD? On the SCM instanz or on the LIVECache Instanz???
    best regards,
    Carsten Schulz

    Hi Carsten,
    the LiveCache needs about 50% memory of the expected LiveCache Size !
    Otherwise, it will work, but perform poorly - as the name says already, it is a DB, that more or less holds all tables in RAM !
    For all ERP (or whatever the name in APO is) runs you needs pretty often access to the MaxDB -> it needs to be locally to your CI ...
    Regards
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

  • Exit code -333

    hi
    Is anyone familiar with the following exit code -333 for java engine restart, i could not find any reasons as why the java engine restared
    [Thr 23] Tue Sep 29 16:36:18 2009
    [Thr 23] JLaunchIExitJava: exit hook is called (rc = -333)
    [Thr 23] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 23] SigISetIgnoreAction : SIG_IGN for signal 18
    [Thr 23] JLaunchCloseProgram: good bye (exitcode = -333)
    Thank you
    Jonu Joy

    HI,
    We are having same issue, could you please confirm how did you solved this.
    ashish

Maybe you are looking for

  • Send button is very wide in IE (fine in FF)

    Hello All I am trying this guys code for submitting a form without page refresh using jQuery - things are going well except for (in) IE. The send button is really wide in IE but perfect in FF - I truly dont remember ever seeing this and cant find a s

  • Title Default Font Question

    The default font for the "Centered" title option appears to be Gils Sans. Does anyone know how to set a different default font, perhaps either for that title option alone or for all title options? Not a big deal, but since I always use Arial for my t

  • LMS 4.0.1 - inventory does not provide details about ports on T1/E1 HWIC

    Hi, I'm running LMS 4.0.1 on Windows Server 2008 Standard SP2 In the management system I have Cisco ISR 2921 and Cisco ISR 3945 devices with Cisco 4-Port Clear Channel T1/E1 High-Speed WAN Interface Card. The issue is that for some of those devices,

  • Associated helper application does not exist

    Please bear with me as I'm computer illiterate.... I'm a new Mac user and I don't even know if my problem is Mac related, Adobe Reader (the application) related or Firefox related.... It appears I've been opening PDF files with Preview ever since I g

  • I have a Canon Pixma MX 880 and when I try to change or delete photos on my SD card,

    I have a Canon Pixma MX 880 and when I try to change or delete photos on my SD card, I get the following error: "You need permission to perform this action" and below that: "You require permission from the computer's administrator to make changes to