SAP Enterprise Portal Not Comming up after JDK upgrade

[Former Member]

Hi,

We've upgraded our Java version from j2sdk1.4.2_16 to j2sdk1.4.2_24,we've done upgrade as per the instructions given is SAP note.When we start the server after the upgrade this is not comming up the log says

Attempting to run an AutoProbe Connector with an incompatible JVM (expected checksum = 2315306221, actual checksum = 729510835)

[ERROR] To fix, re-generate the AutoProbe Connector with the current JVM.

Could some one guide me how to reslove this issue.

[Thr 1] Sun Jan 31 00:33:13 2010

[Thr 1] MtxInit: 10001 0 0

CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources

CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain

CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS

CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices

CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile

CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup

CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue

CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode

CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode

CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto

[ERROR] Attempting to run an AutoProbe Connector with an incompatible JVM (expected checksum = 2315306221, actual checksum = 729510835)

[ERROR] To fix, re-generate the AutoProbe Connector with the current JVM.

[sunny_pahuja2]

Hi,

Have you followed SAP Note 718901 - How to Change the JDK of the J2EE Engine to change JDK version ?

Thanks

Sunny

[Former Member]

Hi Sunny,

Thanks for your response.

We've raised message with SAP and Maite Gutiérrez from SAP Active Global Support helped us to resolve this issue.

The solution is after the JDK upgrade we need to execute the command

java -jar CreateAutoProbeConnector.jar -jvm -output

AutoProbeConnector.jar

If we are using wily to monitor the system.

Thanks & Regads,

Sreedhar

[Former Member]

Hello Sreedhar, Excelent response!!!

For complete your answer:

Note 856909 - Error after JDK upgrade on system with Wily Introscope.

-

---

SAP instances with servers with Willy Introscope installed -

---

Introscope Version 8 Installation Guide For SAP - Pag 24:

Creating an AutoProbe Connector

Use the CreateAutoProbeConnector.jar tool to create a connector specific to the JVM used to run the application server. There are two ways to specify the JVM:

u2022 use the JVM that is running the tool

u2022 pass the JVM directory on the command line to the tool

1. Change the working directory to wily\connectors.

2. Run the Create AutoProbe Connector tool using the following command:

u2022 Make sure to specify exactly the JVM that is used for launching the J2EE node by passing the JVM directory <java_home> on the command line:

java -jar CreateAutoProbeConnector.jar -jvm <java_home> -output connector.jar

Example:

java -jar CreateAutoProbeConnector.jar -jvm C:/soft/jdk14 -output connector.jar

3. The output is the <b>file connector.jar</b> in the same directory.

This error only is displayed in SAP instances with servers with Willy Introscope installed.

-

---

SAP instances with servers with Willy Agents Installed -

---

Creating an AutoProbe Connector

Use the CreateAutoProbeConnector.jar tool to create a connector specific to the JVM used to run the application server. There are two ways to specify the JVM:

u2022 use the JVM that is running the tool

u2022 pass the JVM directory on the command line to the tool

1. Change the working directory to wily\connectors. (Example: /usr/sap/DAA/<SID>/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.1.0.0-2009-06-05/wily/connectors)

2. Run the Create AutoProbe Connector tool using the following command:

u2022 Make sure to specify exactly the JVM that is used for launching the J2EE node by passing the JVM directory <java_home> on the command line:

java -jar CreateAutoProbeConnector.jar -jvm <java_home> -output AutoProbeConnector.jar

Example:

java -jar CreateAutoProbeConnector.jar -jvm C:/soft/jdk14 -output AutoProbeConnector.jar

3. The output is the <b>file AutoProbeConnector.jar</b> in the same directory.

-

---

[Former Member]

Hi,

Thank you very much for your detailed explanation.

Thanks & Regards,

Sreedhar