Java Instance is sychnronising binaries for a long time and is not working

[Former Member]

Hello experts,

I have recently configunre a Guided Procedure after testing it the JAVA instance is broken. After restarting the System I am not able to Start the Instance, The Icon is still yellow and the status is "synchonizing binaries".

log_bootstrap:

[Sep 3, 2008 9:33:57 AM ] * Properties used for initialization: {element.resynch=detect, Logging properties = {log[defaultTrace]=FileLog, .logs=log[defaultTrace],log[consoleLog], log[defaultTrace].pattern=..\..\work\log_bootstrap.log, /.severity=Info, log[consoleLog].formatter=formatter[ConsoleFormatter], formatter[ConsoleFormatter]=TraceFormatter, log[consoleLog]=com.sap.engine.bootstrap.logging.BootstrapConsoleLog, log[defaultTrace].cnt=3, formatter[BootstrapFormatter]=TraceFormatter, log[defaultTrace].formatter=formatter[BootstrapFormatter], formatter[ConsoleFormatter].pattern=%m, log[defaultTrace].limit=5242880, .severity=Info, formatter[BootstrapFormatter].pattern=[%24d] %m}}, debugoff

[Sep 3, 2008 9:33:57 AM ] * Bootstrap initialized for 625 ms.

[Sep 3, 2008 9:33:57 AM ] * Initializing DB connection...

[Sep 3, 2008 9:33:59 AM ] SecStoreFS object initialized.

[Sep 3, 2008 9:33:59 AM ] setDefaultFilenames () called, filename = "D:\usr\sap\MJ3\SYS\global/security/data/SecStore.properties".

[Sep 3, 2008 9:33:59 AM ] File version = "7.00.000.001", software version = "7.00.000.001".

[Sep 3, 2008 9:33:59 AM ] File version = "7.00.000.001", software version = "7.00.000.001".

[Sep 3, 2008 9:33:59 AM ] setDefaultKeyFilename () called, filename = "D:\usr\sap\MJ3\SYS\global/security/data/SecStore.key".

[Sep 3, 2008 9:33:59 AM ] Check record okay.

[Sep 3, 2008 9:33:59 AM ] Existing store opened.

[Sep 3, 2008 9:33:59 AM ] File version = "7.00.000.001", software version = "7.00.000.001".

[Sep 3, 2008 9:33:59 AM ] Entering setDefaultsFromProperties()

[Sep 3, 2008 9:33:59 AM ] com.sap.sql.trace.j2ee.cnt is 10

[Sep 3, 2008 9:33:59 AM ] com.sap.sql.trace.j2ee.limit is 10000000

[Sep 3, 2008 9:33:59 AM ] Exiting setDefaultsFromProperties()

[Sep 3, 2008 9:34:04 AM ] SecStoreFS object initialized.

[Sep 3, 2008 9:34:04 AM ] * DB connection initialized for 6985 ms.

[Sep 3, 2008 9:34:04 AM ] * Launching external modules...

[Sep 3, 2008 9:34:04 AM ] Calling the Configuration Manager's persistInstanceProfile()...

Any ideas???

Regards

Marco

Edited by: Marco Gennari on Sep 3, 2008 10:13 AM

[TomCenens · Accepted solution]

Dear Marco

Please check your defaulttrace trace of your J2EE engine for more information on the reason why it is not starting up.

Kind regards

Tom

[Former Member · Accepted solution]

Ther is no default_trace with the present date. So there aren't any information.

Regards

Marco

[TomCenens · Accepted solution]

Dear Marco

Check log files in and /usr/sap/<SID>/<DVE* or J_instance_no>/j2ee/cluster/server0/log/system

in that case.

There should be log files with timestamp around/after startup.

Please put content online if you cannot resolve problem.

Kind regards

Tom

[Former Member · Accepted solution]

Hi Tom,

unfortunately there are not logs with a date after/aroung startup in that folder:

D:\usr\sap\MJ3\J01\j2ee\cluster\server0\log\system.

But I have following logs in the folder D:\usr\sap\MJ3\J01\work

- log_bootstrap

- jvm_bootstrap

- std_bootstrap

- dev_bootstrap

- std_deployment

- jvm-deployment etc.

Helpful??

Regards

Marco

[TomCenens · Accepted solution]

Dear Marco

Perhaps check sapcpe.log might be issue there

[http://help.sap.com/saphelp_nw04s/helpdata/en/4f/37782d21fc11d288cd0000e83539c3/content.htm|http://help.sap.com/saphelp_nw04s/helpdata/en/4f/37782d21fc11d288cd0000e83539c3/content.htm]

Log file location:

/usr/sap/<SAPSID>/<INSTANCE NAME>/work/sapcpe.log

Kind regards

Tom

[Former Member · Accepted solution]

Hey,

the sapcpe.log says that there are no errors. Any other ideas? Any other log files which could be helpful for us.

Many thanks

Marco

[TomCenens · Accepted solution]

Dear Marco

You could try to just stop/start the J2EE engine using SMICM (hard restart) in abap or using the stopsap SCS<instance number> or stopsap JC<instance number> according to if it's dual stack installation or java only.

There should be some kind of information on the reason why it hangs though. You can also check your work folder of the abap side for log files such as dev_server0 and std_server0.out, dev_dispatcher, dev_dispatcher0.out for more clues.

Perhaps take a look at which processes are running (jcontrol,jlaunch and how many of them).

I can derive from above you have a java only instance so the work folder log files are not of use here, ill just let the comment hang for other people.

In case of java only check for more info in your J<instance no>/work folder if you can find more information

Kind regards

Tom

Edited by: Tom on Sep 3, 2008 10:47 AM

[Former Member · Accepted solution]

I restarted the Java engine and checked the sapstartsrv:

-

---

trc file: "sapstartsrv.log", trc level: 0, release: "710"

-

---

pid 1968

[Thr 1988] Wed Sep 03 09:29:04 2008

SAP HA Trace: SAP Microsoft Cluster library '710, patch 88, changelist 957810' initialized

CCMS agent initialization: return code 0.

Initializing SAPControl Webservice

SapSSLInit failed => https support disabled

Starting WebService Named Pipe thread

Starting WebService thread

Webservice named pipe thread started, listening on port
.\pipe\sapcontrol_01

Webservice thread started, listening on port 50113

MHPSAP52\mgennari is starting SAP System at 2008/09/03 9:33:13

SAP HA Trace: FindClusterResource: OpenCluster failed: 1753 [sapwinha.cpp, line 213]

SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 908]

MHPSAP52\mgennari is stopping SAP System at 2008/09/03 11:54:53

It seems that something is wrong with a Cluster.

Hope that helps to find the Problem

Marco

[TomCenens · Accepted solution]

Dear Marco

No I don't really think the cluster message is relevant, will rather be an effect of something else that goes wrong.

You can also take a look at /usr/sap/<SID>/J<instance no>/cluster/dispatcher/log perhaps those log files have more information

Kind regards

Tom