J2EE engine start problem

[Former Member]

Welcome

I encountered a problem with J2EE engine after installation. It is HA installation of Enterpise Portal (NW 2004s) runnig on Solaris 10/Oracle 10.2 under SunCluster 3.2 software, consisting of two phisical nodes. J2EE engine doesn't start completely on the one and only on this one particular node. The reason is:

less /export/home/<sid>adm/JdbcCon.log

Start: Wed Mar 11 17:03:42 CET 2009

Error: Couldn't connect to DB

com.sap.sql.log.OpenSQLException: Could not load class oracle.jdbc.driver.OracleDriver.

The database is up and runnig, I reviewed and checked all (I think so) configuration parameters regardind location of JDBC driver - no results. What is interesting - applications starts beyond sun cluster framework without problems. Please help if anyone encountered similar problems

Regards

[Former Member]

Hello,

You can also refere ro the note number 997510.

Regards,

Sangeetha

[former_member214355]

Hi

The cause of this error is usually detailed in the jvm_bootstrap.out file under the work directory.

Regarding;

com.sap.sql.log.OpenSQLException: Could not load class oracle.jdbc.driver.OracleDriver

please check the rdbms.driverLocation parameter in the

<j2ee_home>/cluster/bootstrap/bootstrap.properties file. If you have

indeed replaced the JDBC driver, so please update the neccessary

parameters at every place according to note #867976.

Thanks

Kenny

[Former Member]

Hi

Check the bootstrap log files

If the instance bootstrap was started, you need to analyze the following trace file:

<DIR_INSTANCE>/work/dev_bootstrap

Please check the following links

http://help.sap.com/saphelp_sm32/helpdata/de/c2/2f2c4142aef623e10000000a155106/content.htm

and

http://help.sap.com/saphelp_nw04/helpdata/en/e0/bf59416576031de10000000a155106/content.htm

I hope it helps

Regards

Chen

[Former Member]

Hi

what is the JDK version you are using ?

Note 716604 - Access to Sun J2SE and recommended J2SE options

Regards

Uday

[Former Member]

Hai,

Please check the log file under dev_jcontrol, dev_bookstrap, stdout*, etc for more details.

Also check the JDBC connection parameters using the config tool, you may get this errors if the DB instance is pointing to other node.

Regards,

Yoganand.V

[Former Member]

Hi Yoganand

Thanks for reply. I revised dev_jcontrol, dev_bootstrap etc files. What I found is below

dev_jcontrol

[Thr 1] JStartupICreateProcess: fork process (pid 29040)

[Thr 1] Wed Mar 11 11:55:09 2009

*[Thr 1] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx_mt. 1642]*

[Thr 1] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)

[Thr 1] JControlCloseProgram: started (exitcode = 66)

[Thr 1] JControlCloseProgram: good bye... (exitcode = 66)

dev_bootstrap

JHVM_BuildArgumentList: main method arguments of node [bootstrap]

-> arg[ 0]: com.sap.engine.bootstrap.Bootstrap

-> arg[ 1]: ./bootstrap

-> arg[ 2]: ID2053048

************************************************************************

[Thr 4] Wed Mar 11 11:54:59 2009

[Thr 4] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

[Thr 5] Wed Mar 11 11:55:08 2009

[Thr 5] JLaunchIExitJava: exit hook is called (rc = 66)

*[Thr 5] ***********************************************************************

• 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 5] SigISetIgnoreAction : SIG_IGN for signal 18

[Thr 5] JLaunchCloseProgram: good bye (exitcode = 66)

Configtool works fine from both nodes and JDBC connection parameters are correct, database is available through virtual hostname and all connection parameters point to this nodename. I checked this parameters according the note 867976 and everything looks good. As I mentioned before, J2EE starts outside the cluster framework, even started with script used by cluster agent....but uder cluster control it hangs and ONLY on this one particular node. This is realy strange. I've spent many hours looking for cause but still with no results

Regards

Rafal

[hofmann]

Hi,

maybe this can help you:

and

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/004e5f27-374b-2b10-4da9-894986fd...

stop/start Java Cluster (return code = 66) synchronization failed

􀂋cleanipc <nr> remove as <sid>adm

􀂋slibclean as root

Following SAP Note 940893, to analyze the exit code, you'll have to send the files to SAP Support ...

br,

Tobias