Server 0 and Dispatcher are in status Starting Framework

[Former Member]

Hi All,

This issue is mainly about Portal.

The Server 0 and Dispatcher are in status Starting Framework for a very long time..

The status does not change at all.

The dev_jrfc.trc under server 0 log does not get updated and the log directory also under server 0 does not get updated.

This is an issue in production system,so it would be of great help if some one could chip in soon.

P.S The ABAP part of the system is working fine.

Regards

Bharathwaj V

[Former Member]

Hello

Look at note 723909 for default Java memory settings.

Thanks

Fayzal

[Former Member]

Hello

Have a look at logs dev_jcontrol, std_server0. Are there any errors in these two logs? std_server0 will tell you at which stage during startup there is a problem & dev_jcontrol will tell you if there are memory problems.

Thank You

Fayzal

[Former Member]

Hello, are you check dev_server0 file? Your datasource is ABAP or AD, are connection user not locked in this datasource systems? try to check logs. Regards.

[Former Member]

Hi Bharathwaj,

Sometimes the amount of memory of java stack is insufficient or not correctly managed by the application server.

This is a common problem and I have to take a time upon this issue several times !!!

First of all take a time to check this link http://help.sap.com/saphelp_nw70/helpdata/EN/a2/bb0a412a06f023e10000000a155106/frameset.htm it could be handful about the problem you are proving there.

Sometimes thee Java VM, which executes the instance bootstrap, is started by using the following log file

<DIR_INSTANCE>/work/std_bootstrap.out

The following problems may have been logged:

You must verify there some invalid Java VM parameter

like unrecognized option: <some option>

The option supplied in the bootstrap.JavaParameters property is not valid for the Java VM. Correct the property value and try again.

Try to manage the amout of memory of your JVM

Error occurred during initialization of VM

Incompatible initial and maximum heap sizes specified

The memory settings supplied in the bootstrap.JavaParameters and bootstrap.MaxHeapSize properties do not fit together (for example, MaxHeapSize is smaller than the initial heap size specified with u2013Xms).

Correct the property values and try again.