Class versions are incompatible (linkage error)

Hi All,
I New to SAP XI and i've been working on java mapping, i Used RAD 6.0 for generation of class files, i imported the generated files into Integration builder.
but when i execute the scenario i'm getting this error
"Class versions are incompatible (linkage error)"
in message monitoring with a red flag..
can anyone explain me why i'm getting this error....
Thanks & Regards,
Sai Kumar Madduri

Hi,
Our PI Details:
Runtime Environment
Java version: 1.5.0_14
Java vendor:Sun Microsystems Inc.
Version
Service pack:09
Release: 645_VAL_REL
NWDS IDE: 1.5.0_14
XI
Software component details
XI TOOLS 3.0
Support Package 11 of SAP_XITOOL, 3.0 SP011 011
XI TOOLS 7.0
No Entry for Support Packages.
Request to advise what is the best option for my JAVA Dom program to run
regards
shekar Chandra

Similar Messages

Java Mapping - Class versions are incompatible (linkage error)

Hi Friends,
While testing java mapping in Integration Repository i am getting an error - "Class versions are incompatible (linkage error)". Can anyone plz tell what might be the reason.
Regards,
Gowtham Kuchipudi.

hello
I have this message but my trace look like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
<Trace level="1" type="T">Set interface action INIT into *MAST*</Trace>
</Trace>
<Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- 
<Trace level="1" type="T">Interface Mapping http://Migdal.co.il/CRM/SAP-CRM/ProposalDeatailsService ProposalDeatailsService_WS2RFC_IM</Trace>
<Trace level="1" type="T">LinkageError at JavaMapping.load(): Could not load class: xmlpayload</Trace>
<Trace level="1" type="T">java.lang.UnsupportedClassVersionError: xmlpayload (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.lang.ClassLoader.defineClass(ClassLoader.java:448) at com.sap.aii.ibrun.server.mapping.MappingLoader.findClass(MappingLoader.java:158) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java:95) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:45) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor428.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</Trace>
<Trace level="1" type="T">Linkage error occurred when loading class xmlpayload (http://Migdal.co.il/CRM/SAP-CRM/ProposalDeatailsService, d7e31f30-53be-11dc-8fbd-ee09c0a8664d, -1)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Linkage error occurred when loading class xmlpayload (http://Migdal.co.il/CRM/SAP-CRM/ProposalDeatailsService, d7e31f30-53be-11dc-8fbd-ee09c0a8664d, -1) at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java:115) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:45) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor428.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: java.lang.UnsupportedClassVersionError: xmlpayload (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.lang.ClassLoader.defineClass(ClassLoader.java:448) at com.sap.aii.ibrun.server.mapping.MappingLoader.findClass(MappingLoader.java:158) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java:95) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:45) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor428.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
the error that I recieve in the SXMB is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
<SAP:P1>xmlpayload</SAP:P1>
<SAP:P2>http://Migdal.co.il/CRM/SAP-CRM/ProposalDeatailsS~</SAP:P2>
<SAP:P3>d7e31f30-53be-11dc-8fbd-ee09c0a8664d</SAP:P3>
<SAP:P4>-1</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Class versions are incompatible (linkage error)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
this is my XI information
Runtime Environment
Java version:1.4.2_12
Java vendor:Sun Microsystems Inc.
Version
Service pack:21
Release:30_VAL_REL
Latest change:409678
Sync time:200709211024
since I already have the SP required by the note, any other suggestions?
Thanks
Kfir

XI Mapping: Class versions are incompatible (linkage error)

Hi,
i have a simple File-to-File scenario, and I am getting the following error as observed in the XI Monitor:
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
<SAP:Stack>Class versions are incompatible (linkage error)</SAP:Stack>
To troubleshoot the mapping, I have removed all mappings, and put the target nodes to constant values. I am still getting the error in Mapping (linkage error).
I am using XI3.0SP0 (J2EE SP07, ABAP SP3). Is this a known problem / OSS notes available ? thanks.
Regards,
Manish Agarwal.

Hallo Agarwal,
have a look in OSS Message #755302
Regards Franz Forsthofer

ODM and ODM schema versions are incompatible please use ODM api version ver

Hi,
I am with a problem, I am with the version of Oracle 10g 10.1.0.3 EE in Linux As 3 and I am not getting to rotate Oracle it Dates Mining, when I am going login in the program him of the the following mistake,
ODM and ODM schema versions are incompatible please use ODM api version version 10.1.0.3
excuses for bad English!
tks,
Welvis Douglas
Msn : [email protected]

Hi,
When using Data Miner, the api that it uses to connect to the ODM database option must have the same version number as the db itself.
See the following page:
http://www.oracle.com/technology/products/bi/odm/odminer.html
And scroll down to the section on the 10.1.X apis:
"Data Miner requires that the version of odmapi.jar in the Data Miner lib directory be the same as the version of odmapi.jar installed with ODM. The version of odmapi.jar shipped with Data Miner is 10.1.0.2. Here are the additional patch versions of odmapi.jar for download:"
There are links there to get the .jar files required for the version you are using (10.1.0.3).
Thanks, Mark.

TNS:versions are incompatible

we have oracle Version 10.2.0.3.0 on hp-ux.
I can see the following alert in the listener log. can you please suggest what can be done to resolve this issue??
Trace level is currently 0
Started with pid=12844
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ss.pta.za.go2uti.com)(PORT=1521)))
Listener completed notification to CRS on start
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
21-APR-2009 06:48:47 * status * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 06:49:19 * status * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 06:57:31 * status * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 06:58:13 * ping * 0
21-APR-2009 07:06:56 * status * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 07:07:05 * ping * 0
21-APR-2009 07:07:12 * stop * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 09:31:36 * status * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 13:01:04 * status * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 13:01:15 * ping * 0
21-APR-2009 13:01:28 * stop * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 13:47:41 * status * 12618
TNS-12618: TNS:versions are incompatible
21-APR-2009 14:56:44 * status * 12618
TNS-12618: TNS:versions are incompatible
07-MAY-2009 04:12:21 * status * 12618
TNS-12618: TNS:versions are incompatible
07-MAY-2009 07:42:12 * status * 12618
TNS-12618: TNS:versions are incompatible
07-MAY-2009 07:42:24 * status * 12618

Hi..
refer to Doc ID: 297781.1 on metalink.
Anand

Incompatible class versions :linkage error- JAVADOM

HI,
We have done Mapping using java DOm,created ZIp file & successfully imported in IR.
My NWDS is using java 1.4.2_15
we are using PI70/Sp09/Java Version 1.5.0_14
During Execution in IE we are getting this error.
error -
<SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
<SAP:Stack>Incompatible class versions (linkage error)</SAP:Stack>
<Trace level="1" type="T">Interface Mapping http://XI/Mapping/JavaDom/DOMMapping4 IM_ORDER1_ORDER</Trace>
<Trace level="1" type="T">LinkageError at JavaMapping.load(): Could not load class: CSJAVA/com/yash/xi/DOMMapping4</Trace>
<Trace level="1" type="T">java.lang.NoClassDefFoundError: JAVA/com/xi/DOMMapping4 (wrong name: com//xi/DOMMapping4) at java.lang.ClassLoader.defineClass0
Regards
shekar chandra

Hi,
Check the links they may help u out.
Event or DOM parsing?
http://discuss.joelonsoftware.com/default.asp?design.4.156750.12
XML Parsers: DOM and SAX Put to the Test
http://www.devx.com/xml/Article/16922/1954?pf=true
Regards,
Phani

JAVAMAP-Sax Parser ...............Linkage error when loading the class.

Dear all,
Do we have any extra things to execute the Java mapping using the Sax Parser?
When I am executing the interface mapping ,I am getting the" Linkage error when loading the class" error.
Kindly let me know your personnel maildId so that I can mail you the screen shots.
Thanks,
Srinivasa

Dear sunil,
Find the File.
Source:
<MTO_FTP_MAT_DETAILS>
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
TARGET
MTI_FTP_MAT_DETAILS
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
Source:
<MTO_FTP_MAT_DETAILS>
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
TARGET
MTI_FTP_MAT_DETAILS
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
import javax.xml.parsers.SAXParser;
import javax.xml.parsers.SAXParserFactory;
import org.xml.sax.Attributes;
import org.xml.sax.SAXException;
import org.xml.sax.helpers.DefaultHandler;
import com.sap.aii.mapping.api.StreamTransformation;
class Echo {
public static OutputStream out;
public class myEcho extends DefaultHandler implements StreamTransformation {
private Map map;
public void setParameter(Map param) {
map = param;
public void execute(InputStream in, OutputStream out) {
DefaultHandler handler = this;
SAXParserFactory factory = SAXParserFactory.newInstance();
try {
SAXParser saxParser = factory.newSAXParser();
Echo.out = out;
saxParser.parse(in, handler);
} catch (Throwable t) {
t.printStackTrace();
public void startDocument() throws SAXException {
try {
Echo.out.write("<?xml version='1.0' encoding='UTF-8'?>".getBytes());
} catch (IOException e) {
e.notify();
public void endDocument() throws SAXException {
try {
Echo.out.flush();
} catch (IOException e) {
throw new SAXException("I/O error", e);
public void startElement(String namespaceURI, String sName, // simple name
String qName, // qualified name
Attributes attrs) throws SAXException {
String eName = sName; // element name
if ("".equals(eName))
eName = qName; // not namespace-aware
if ("ns0:MTO_SAP_MAT_DETAILS".equals(qName)) {
try {
Echo.out.write(("<MTI_FTP_MAT_DETAILS>").getBytes());
} catch (Exception e) {
e.printStackTrace();
} else {
try {
Echo.out.write(("<" + qName + ">").getBytes());
} catch (Exception e) {
e.printStackTrace();
public void endElement(String namespaceURI, String sName, // simple name
String qName // qualified name
) throws SAXException {
String eName = sName; // element name
if ("".equals(eName))
eName = qName; // not namespace-aware
if ("ns0:MTO_SAP_MAT_DETAILS".equals(qName)) {
try {
Echo.out.write(("</MTI_FTP_MAT_DETAILS>").getBytes());
} catch (Exception e) {
e.printStackTrace();
} else {
try {
Echo.out.write(("</" + qName + ">").getBytes());
} catch (Exception e) {
e.printStackTrace();
public void characters(char buf[], int offset, int len)
throws SAXException {
String s = new String(buf, offset, len);
try {
Echo.out.write(s.getBytes());
} catch (Exception e) {
e.printStackTrace();

Problems with WL 9.2, Axis2 -- Linkage Error on XMLStreamReader class

When executing a test client against a web-service on our server we are getting this error back from our server.
We have the weblogic.xml fix in place to load the WEB-INF libraries first.
Any Ideas?
org.apache.axis2.AxisFault: java.lang.LinkageError: loader constraints violated when linking javax/xml/stream/XMLStreamReader class
at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:308)
at com.xxx.xxx.webservices.xxxServiceStub.retrievePaymentInfo(EPaymentServiceStub.java:183)
at com.xxx.xxx.TestClient.main(TestClient.java:78)

We found a work around....
you can deploy your application as an ear and at the ear level include an a weblogic-application.xml file that contains this information.
<?xml version="1.0"?>
<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http:
//www.w3.org/2001/XMLSchema-instance">
<prefer-application-packages>
<package-name>org.apache.*</package-name>
</prefer-application-packages>
</weblogic-application>

Linkage error occurred when loading class MyClass

Hi
I have written one simple class name MyClass and i have created jar file and i imported into import archive... but in interface mapping while i am testing i am getting the <b>"<b>Linkage error occurred when loading class MyClass"</b></b> error.... why i am getting this error
Thanks & Regards
Ravi Shankar B

Here it goes:
Symptom
The LINKAGE_ERROR error occurs during the mapping.
The trace contains "java.lang.NoClassDefFoundError: Illegal name":
Other terms
XI 30, Mapping, Linkage Error
Reason and Prerequisites
As of the jdk 1.4.2_05 from Sun, this program error occurs during the mapping in the runtime or during testing in the Repository. This error may also occur in conjunction with jdks of other vendors or other versions.
Solution
The error is corrected with Support Package 5 for Support Package 03 for the XI TOOLS 3.0 software component.
Import the corresponding archive SAPXITOOL03P_5.SCA for SAP Exchange Infrastructure XI 3.0 as described in the Netweaver 04 Support Package Stac Guide.
You will find the archive and the guide in the SAP Service Marketplace under the alias "SP stacks -> SAP NetWeaver -> SAP NetWeaver 04".
Regards
Vijaya

Linkage error occured when loading the class:Java Mapping

I AM GETTING THE ABOVE ERROR IN SUB WHEN TESTING THE MAPPING .
Source:
<MTO_FTP_MAT_DETAILS>
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
TARGET
MTI_FTP_MAT_DETAILS
<MATDETAILS>
<MAKTX>
<MATNR>
<WERKS>
<LABST>
<MEINS>
<PERCNT>
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
import javax.xml.parsers.SAXParser;
import javax.xml.parsers.SAXParserFactory;
import org.xml.sax.Attributes;
import org.xml.sax.SAXException;
import org.xml.sax.helpers.DefaultHandler;
import com.sap.aii.mapping.api.StreamTransformation;
class Echo {
     public static OutputStream out;
public class myEcho extends DefaultHandler implements StreamTransformation {
     private Map map;
     public void setParameter(Map param) {
          map = param;
     public void execute(InputStream in, OutputStream out) {
          DefaultHandler handler = this;
          SAXParserFactory factory = SAXParserFactory.newInstance();
          try {
               SAXParser saxParser = factory.newSAXParser();
               Echo.out = out;
               saxParser.parse(in, handler);
          } catch (Throwable t) {
               t.printStackTrace();
     public void startDocument() throws SAXException {
          try {
               Echo.out.write("<?xml version='1.0' encoding='UTF-8'?>".getBytes());
          } catch (IOException e) {
               e.notify();
     public void endDocument() throws SAXException {
          try {
               Echo.out.flush();
          } catch (IOException e) {
               throw new SAXException("I/O error", e);
     public void startElement(String namespaceURI, String sName, // simple name
     String qName, // qualified name
     Attributes attrs) throws SAXException {
          String eName = sName; // element name
          if ("".equals(eName))
               eName = qName; // not namespace-aware
          if ("ns0:MTO_SAP_MAT_DETAILS".equals(qName)) {
               try {
                    Echo.out.write(("<MTI_FTP_MAT_DETAILS>").getBytes());
               } catch (Exception e) {
                    e.printStackTrace();
          } else {
               try {
                    Echo.out.write(("<" + qName + ">").getBytes());
               } catch (Exception e) {
                    e.printStackTrace();
     public void endElement(String namespaceURI, String sName, // simple name
     String qName // qualified name
     ) throws SAXException {
          String eName = sName; // element name
          if ("".equals(eName))
               eName = qName; // not namespace-aware
          if ("ns0:MTO_SAP_MAT_DETAILS".equals(qName)) {
               try {
                    Echo.out.write(("</MTI_FTP_MAT_DETAILS>").getBytes());
               } catch (Exception e) {
                    e.printStackTrace();
          } else {
               try {
                    Echo.out.write(("</" + qName + ">").getBytes());
               } catch (Exception e) {
                    e.printStackTrace();
     public void characters(char buf[], int offset, int len)
          throws SAXException {
          String s = new String(buf, offset, len);
          try {
               Echo.out.write(s.getBytes());
          } catch (Exception e) {
               e.printStackTrace();

Hi,
When you make the jar to import to XI you must verify the two classes are generated at the same time. Later you can verify in Inteface Mapping that you are using the myEcho class to do the java mapping.
Plesae verify the java version are the same in you own machine and the xi machine.
Regards.

Cannot boot from Windows 8 notebook - Error: Operating system version is incompatible with Startup Repair

Hi all,
I have searched through forums, but could not find the solution to my problem:
I have a notebook ASUS with Windows 8 preinstalled.
Yesterday I was doing some housecleaning jobs with some freeware tool (don't remember the name).
Afterwards I have not been able to boot into Windows.
CURRENT SITUATION: When I switch the PC on, after the welcome screen of ASUS and Windows 8 the system goes to a blank screen (no cursor, no mouse, CTRL+ALT+DEL not working).
On next reboot, it does not start automatically the Recovery/Repair procedure and goes through the same steps again. It's not a loop, it just hangs.
Looking into c:\windows\system32\LogFiles\Srt\srttrail.txt I see the following error message at the bottom of the file on the time of my last boot attempt: "Operating system version is incompatible with Startup Repair"
I tried several things without success, so now I want to solve the problems one by one and first thing is to understand what might be causing the "Operating system version is incompatible with Startup Repair" error and how it can be solved.
Thanks for reading

Hi,
Any update here?
I agreed with the others. First, if we have any backup available to restore Windows 8.1, we may take use of that.
If we don't have any backup available, we'd better contact the manufacturer side for a deeper help.
Or as Janek Fehn suggested, make a clean install of Windows 8, then update to Windows 8.1 again.
Best regards
Michael Shao
TechNet Community Support

I am running Mac OS 10.6.7 I cannot run a java based program from the net when parental controls are set the error is The error is Load: class installer.CheckVersion 13. class not found Help!

I am running Mac OS 10.6.7 I cannot run a java based program from the net when parental controls are set the error is The error is Load: class installer.CheckVersion 13. class not found

Then, talk to the person running the lab.

Sudden hotsync "device database version is incompatible" error

I have a Sprint Treo 755p with software version 1.07. Desktop is 4.1.4.
Hotsync has been working fine for 6 months. Suddenly yesterday I started getting "The device database version is incompatible with this conduit. Doing nothing" in my hotsync log (see below for log result) . Contacts are synchronizing, memos have disappeared, and calendar is not synchronizing. After attempting to synchronize the 755p soft resets. It also soft resets when I do a string search and while it is searching the calendar. This may have all started yesterday when I sent a text message. The message went then the phone froze. I haven't had any freeze-ups with this phone so I was surprised. I popped the battery, but after restart my text message history was gone.
Did something get corrupted? I'd appreciate any advice.
OK Quick Install
VersaMail
- Sync configured to Do Nothing
-- Memos
- The device database version is incompatible with this conduit. Doing nothing.
OK Calendar
OK Contacts
OK Tasks
-- Backing up AddressingLibRecent-HsCh to C:\Program Files\palmOne\DJ\Backup\AddressingLibRecent-HsCh.PDB
Thanks
John

Never mind. I deleted the following files Memodb and MemoDB-Pmem, hot sync'd and now I am able to get Memos to open. Guess I had something in the database that didn't jive.
Post relates to: Treo 680 (Unlocked GSM)

LINKAGE ERROR in Java Mapping

Hi Friends,
I am getting LINKAGE ERROR when executing JAVA mapping as its not able to reference AbstractTransform class provided by SAP PI API.
This problem occurs in particular environment for this particular mapping. For other environments this is working fine.
I assume it has something to do with Java Library reference which is mis-configured during transport. Can anyone let me know how and where the library path is configured for Imported Achieves in SAP PI 7.1.
We are using java 1.5 for building and creating java achieves.
Many thanks,
SK

Hi Sumant,
This error occurs when the jdk version of XI server and the library version you used to develop the mapping are incompatible. Make sure you use the same version as of the server
have a look in SAP Note 755302
Regds,
Pinangshuk.

Java mapping - Linkage Error

Hello,
We are on PI 7.0 SP10.
Currently we are migrating the XI servers from Solaris to AIX IBM.
When I try to run Java mapping, I get following error:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
<SAP:P1>sapmarkets/marketconnect/xcbl/r3/OrderMapping</SAP:P1>
<SAP:P2>http://xi/SRM/ReceivePurchaseOrders</SAP:P2>
<SAP:P3>22150771-0ee7-11dc-c87a-fe330a306909</SAP:P3>
<SAP:P4>-1</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Incompatible class versions (linkage error)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.
Thanks in advance.
Beena.
Edited by: Beena Thekdi on Jan 22, 2008 8:05 PM

Thanks Raj.
But this note says
>> The error is corrected with Support Package 5 for Support Package 03 for the XI TOOLS 3.0 software component.
and I am already on PI 7.0.
Please tell me still I need to apply this?
Thanks,
Beena.

Class versions are incompatible (linkage error)

Similar Messages

Maybe you are looking for