Application server for Portal on LINUX

[Former Member]

Hello,

We have a problem starting application server for Portal on LINUX SLES11, installation went fine but while sapinst tried starting the instance it failed.

Central services instance run on AIX 6.1 along with Oracle DB 10.2.0.4.

While checking log we found below error.

Log from 'dev_bootstrap' file:

[Thr 140581733402384] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [bootstrap]

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

-> arg[  1]: ./bootstrap

-> arg[  2]: ID0012060

-> arg[  3]: ID0535086

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

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

[Thr 140581733402384] **********************************************************************

[Thr 140581733402384] *** ERROR => The Java VM terminated with a non-zero exit code.

[Thr 140581733402384] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'

[Thr 140581733402384] *** for additional information and trouble shooting.

[Thr 140581733402384] **********************************************************************

[Thr 140581733402384] SigISetIgnoreAction : SIG_IGN for signal SIGCHLD

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

Log from 'jvm_bootstrap.out' file:

[Bootstrap module]> Bootstrap must be called through the Startup Framework with the appropriate parameters!!!

Contents of instance.properties file:

bootstrap.JavaPath=/opt/IBMJava2-amd64-142

instance.install.dir=/usr/sap/CXX/J05/j2ee

bootstrap.Name=bootstrap

instance.ms.host=gXXXXXXX

bootstrap.JavaParameters=-Djco.jarm=1 -Xj9

bootstrap.RootPath=/usr/sap/CXX/J05/j2ee/cluster

instance.en.host=gXXXXXXX

bootstrap.MainClass=com.sap.engine.offline.OfflineToolStart

instance.ms.port=3901

bootstrap.ClassPath=./bootstrap/launcher.jar

instance.box.number=CXXJ05gXXXXXXX

instance.osLibsPath=/usr/sap/CXX/J05/j2ee/os_libs

bootstrap.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0012060 ID0535086

instance.en.port=3201

bootstrap.Type=bootstrap

bootstrap.MaxHeapSize=512

instance.system.id=5

Please check the above logs and let me know what could be wrong.

IBM JDK 1.4.2 is installed as recommended by SAP.

For installation we mounted /sapmnt/CXX/profile and global directory from central instance which is a normal procedure for a application server installation.

Thanks.

Regards,

Yoganand.V

[former_member191911]

Can you check for further details in log file jvm_bootstrap.out

Kr. Mark

[Former Member]

Hello Mark,

As I already posted there is nothing much in the jvm_bootstrap.out file.

Log from 'jvm_bootstrap.out' file:

[Bootstrap module]> Bootstrap must be called through the Startup Framework with the appropriate parameters!!!

Regards,

Yoganand.V

[former_member191911]

ah, missed that one..

and in the dev_server0? or is that not created yet?

according to this link you should modify the bootstrap parameters property:

http://help.sap.com/saphelp_nwpi71/helpdata/de/34/145641998e051de10000000a155106/content.htm

Kr. Mark

[Former Member]

Hello Mark,

Thanks for your time.

dev_server0 is not yet created, I checked bootstrap.properties file and found nothing wrong in it.

Below is the content, could you please check and see if you can find any thing wrong with it.

install.dir=/usr/sap/CXX/J05/j2ee

secstorefs.lib=/sapmnt/CXX/global/security/lib

rdbms.driverLocation=/oracle/client/10x_64/instantclient/ojdbc14.jar

rdbms.connection=jdbc/pool/CXX

instance.prefix=ID535086

rdbms.initial_connections=1

secstorefs.keyfile=/sapmnt/CXX/global/security/data/SecStore.key

secstorefs.secfile=/sapmnt/CXX/global/security/data/SecStore.properties

rdbms.maximum_connections=5

system.name=CXX

Regards,

Yoganand.V

[former_member191911]

Are you able to establish the connection to your database? Can you perform a tnsping?

Kr. Mark

[Former Member]

Hello Mark,

'tnsping' in not available on application server host since it is a part of DB software, but 'startsap' checks database on remote host successfully. So application server is able to communicate with remote database.

Regards,

Yoganand.V

[former_member191911]

In that case I'm almost running out of options..

Do you see anything on database side about the connection being successfully setup?

You don't have tcp.invited_nodes active in your sqlnet.ora?

Kr. Mark

[Former Member]

Hello Mark,

Even I do not have any idea.

jdbc.log under sidadm home directory says the connection to remote DB was successful.

tcp.invited_nodes is not active in sqlnet.ora, we have one more application server for SRM on the same host which starts and connects to CI without any issue.

J2EE engine framework directory os_libs is not even getting created, I have tried unistall and install many times, used SAPINST 51043618_8 media and also 51043619_7 media but both did not help.

JAVA component media used is 51039248_1 to 4.

Kernel level in CI is 720 SP 201 and when I try to upgrade the kernel in dialog instance to the same support pack level I get SP level as only 176 for 720, I used the SAR file SAPEXEDB_201-10007263.SAR and SAPEXE_201-10007264.SAR.

I guess I will have to create a OSS message and inform the situation.

I will keep this message open so some one can at least throw some light until I get some useful answer from SAP.

Thanks very much so far.

Regards,

Yoganand.V