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

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (5)

Prashanth-

Have you performed any Kernel upgrade we had a similar problem when we performed the sp's and kernel upgrade.

Regards,

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi All,

This was due a sizing problem, there was simply not enough java memory available for the stack to come up. We had later increased the physical memory and revised our memory parameters and that had fixed this.

Sorry my old id was no longer functional and I couldnt post a closure to this issue.

cheers

Prashant

Hi,

Can you check the idle CPU % in the server? It can be that the process is not able to get the enough CPU resource to come up.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Please check the startup mode to "always" in com.sap.security.core.ume.service and also bind value in configtool.

Regards,

Sureshram.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi, after what your server0 is down? Are you doing any change in the datasource configuration or other changes ? You have 32 bit or 64 bit installation? Are you trying to set up youe VM settings per

Note 723909 - Java VM settings for J2EE 6.40/7.0 ?

Your datasource are ABAP or AD? Any other information ...

Regards.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Sergo,

Our WAS ABAP+JAVA [ PI 7.0 ] stack was running smoothly when this error occurred.

No we were not changing the datasources in UME. The server has been operational for over 8 months.

I checked the note 723909 and checked the parameters XXpermsize and XXmaxpermsize but find them to be correct. Also checked that the parameters like JAVA_HOME , j2ee/vm/home are correctly set. The java version is 1.4.2.09. Also tried increasing the heap size to 2048, but then the server process ended and reason mentioned in the log was unable to allocate sufficient memory [ so i reverted back to the old value of heap size].

This is a 32 bit installation,and my Datasource is ABAP.

Any suggestions about how we can resolve this error.

Thanks for your efforts,

Regards,

Prashant

> Can you check if there is any error in the default trace file in usr/sap/<SID>/DVEBMGS/j2ee/cluster/server0/log ??

Did you check this?

Regards,

Jazz

> Thr 4072 JLaunchISetState: change state from Starting (2) to Starting applications (10)

I cannot find any noticeable error in the log you pasted.

Can you check if there is any error in the default trace file in usr/sap/<SID>/DVEBMGS<>/j2ee/cluster/server0/log ??

Regards,

Jazz

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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)