SAP AS Java Administration · Starting & Stopping the AS Java

A start command reaches only one instance's sapstartsrv. How does it end up starting every instance, in priority order?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Starting & Stopping the AS Java

On a Java-only AS (no ABAP stack), what drives the start and stop, and how is that different from a dual-stack AS ABAP+Java?

Why does a running SAP system with a Java stack always have at least two instances, not one?

When starting an SAP system, which instance must come up first, and what property decides that ordering?

During a soft shutdown of an AS Java, what determines when each server process actually stops?

What is sapstartsrv, and how many of them are involved when you start a multi-instance SAP system?

With per-priority start timeouts, what has to happen before the next-highest priority tier of instances is started?

Start learning today

Free to start — download the app or use it in your browser.