Symptom
- Fatal: Critical shutdown was invoked. Reason is: Error getting confirmation reply during attach to cluster
- No db driver found for rdbms.driverLocation = <path>
- Java Server node and dispatcher does not start.
- dev_serverX/dev_dipatcher has the following error (path:/usr/sap/<SID>/<instance>/work)
[Thr 139938892457728] JLaunchIExitJava: exit hook is called (rc = -334)
[Thr 139938892457728] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 139938892457728] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 139938892457728] *** for additional information and trouble shooting.
- std_serverX/std_dispatcher has the following error (path:/usr/sap/<SID>/<instance>/work)
Loading: ClusterManager ... [Framework -> criticalShutdown] Error getting confirmation reply during attach to cluster.
com.sap.engine.core.Framework [Thread[Thread-1,5,main]] Fatal: Critical shutdown was invoked. Reason is: Error getting confirmation reply during attach to cluster.
- Server/dispatcher default trace has the following error (path:/usr/sap/<SID>/<instance>/j2ee/cluster/dispatcher/log ; usr/sap/<SID>/<instance>/j2ee/cluster/serverX/log)
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred: No db driver found for rdbms.driverLocation = <path>
at com.sap.engine.core.configuration.impl0.ConfigurationManagerImpl.initInternal(ConfigurationManagerImpl.java:99)
Read more...
Environment
Netweaver 7.0X
Product
Keywords
criticalShutdown,334,driverLocation,rdbms,ClusterManager,fatal,critical,dev_dispatcher,std_dispatcher,corrupt,path,JDBCDriver,dev_server0,std_server0,exitcode , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.