Skip to Content

After Java stack drop, SAP Management Console still show yellow because Java is down.

In our test environment we successfully removed the Java stack from our central system following the instructions given in section 7.3 of the Stack Split Guide and the Software Provisioning Manager. When we restarted the system it appeared yellow in the SAP Management Console because Java was not running.

We would expect that, since the system no longer has Java, it should appear all green in the SAP Management Console. We monitor the SAP Management Console and would tend to review any system that is not appearing to be all green. So it is not good to be showing a false positive error.

We will continue trying all the normal things that one would to resolve this but if someone has had the exact same issue and resolved it I would love to hear from you as this will save us some time.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    May 18 at 01:06 PM

    Solution: The Java stack drop functionality in SPM removes many of the Java related parameters including

    rdisp/j2ee_start

    One would think that this should not matter since its value should be 0 after removing the Java stack anyway and since the default value for this parameter is 0 one would think that it is not necessary for the profile to contain this setting. This is where the problem lies. Even though the default value of this parameter is 0 it is still necessary for the profile to contain this parameter set to 0 as follows:

    rdisp/j2ee_start = 0

    If the profile does not contain this parameter set to 0, then the system will show as yellow in the SAP Management Console. It should not work this way but unfortunately it does. The documentation in the guide does say to set this profile parameter to 0 before starting the stack drop as follows:

    "Before you start the removal procedure, perform the following:
    Shut down the J2EE cluster using transaction SMICM
    Set rdisp/j2ee_start = 0 in the central and all dialog instance profiles
    Restart the instance services ..."

    However, because the stack drop removes the parameter it should say to add this parameter set to 0 back into the profile after the stack drop.

    Aside from this problem take a look at the order of the steps above. It says to shut down SMICM then set profile parameter to 0 restart the system. Since the profile parameter is set to 0, when you restart the system Java will not start so what is the purpose of the first step where we are told to shut it down first?

    Add comment
    10|10000 characters needed characters exceeded

  • May 17 at 12:33 PM

    Hello Thomas,

    Can you provide the START (if present), instance and "DEFAULT.PFL" profiles?

    If the Java was removed from all instances of the system, then the parameter "system/type" should be ABAP.

    The Java related parameters should be removed as well ("rdisp/j2ee*", "j2ee/*", "jstartup/*", ...).

    Regards,

    Isaías

    Add comment
    10|10000 characters needed characters exceeded