cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE instance not comming up

Former Member
0 Kudos

Hi

We have done a system copy and after that the J2EE instance is not comming up. We are on NW2004 with SP20 and running on HP-UX (64). The database is oracle 9.2 and its is running. The listener as well is running.

My jvm_bootstrap.out say its somthing to do with a property "element.clusterID" not set in properties file. I have checked that in the configtool and its correct over there.

The log jvm_bootstrap.out

-


Bootstrap MODE:

<BETA2>

determined by parameter [ID436605].

-


Exception occurred:

com.sap.engine.bootstrap.SynchronizationException: Property " element.clusterID " not set in the properties file.

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:124)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)

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.offline.OfflineToolStart.main(OfflineToolStart.java:81)

[Bootstrap module]> Problem occurred while performing synchronization.

-


Is there somthing i am missing out. I ve checked the instance.properties and also the vmbootstrap.properties as well but didnt not find and entry for element.clusterID.

Help much appreciated.

Thanks

Sheril

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Mine solved by adding element.clusterID=27050400 (without ID) into bootstrap.properties under /usr/sap/QAS/DVEBMGS01/j2ee/cluster/bootstrap

Former Member
0 Kudos

The problem was with the instance.properties file wherein you have to edit the cluster ID to match with the one in configtool, ie the refreshed parameters.

Fixed that and my portal refresh is completed.

Former Member
0 Kudos

Do you have the same JVM at the new system/server?

Former Member
0 Kudos

hi Brian,

We have the same version of JVM in the target server as well.

Thanks

Sheril