Invalid layout of preloaded class when starting SAP JVM

Most admins would have set up the SAP systems to get it monitored or analyzed by Solution Manager systems. Therefore the SAP JVMs are enabled with a connector to Wily Introscope. The AutoProbe Connector is compiled using the current JVM and can only be started if the JVM remains unchanged.

You cant start JVM without compiling connector and you cant compile connector without JVM


When you patch the JVM or switch from third party JVM to SAP JVM, the connector class does not load. The JVM startup fails with one of the following errors:
  • Invalid layout of java.lang.ClassLoader at uniqueId
  • fatal error: Invalid layout of preloaded class
  • Attempting to run an AutoProbe Connector with an incompatible JVM
  • Attempting to run an AutoProbe Connector with an different JVM

To get the JVM to start, remove the following VM parameters using Config Tool:

-Dcom.wily.introscope.agent.agentName=<SID>_<Instance>_server<x>

 -Dcom.wily.introscope.agentProfile=D:/usr/sap/<SID>/.../applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.006-26/wily/IntroscopeAgent.profile

 -Xbootclasspath/p:D:/usr/sap/<SID>/.../applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.4.0-201226/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/<SID>/.../applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.2012-06-26/wily/Agent.jar

In order to get the AutoProbe Connector working again, you have to recompile the connector using the JVM you intend to use.

You can do this using SOLMAN_SETUP > "Managed Systems Setup" > "Configure Automatically"  > "Byte Code Adpater Installation"

or compile the AutoProbe connector manually by executing the following example commands

cd /usr/sap/<SID>/SMDA<Instance-ID>/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT*/wily/connectors

 java -jar CreateAutoProbeConnector.jar -jvm /sapmnt/<SID>/exe/sapjvm_5 -output connector.jar

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more