Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

bd64 distribution model connection error

Former Member
0 Likes
1,555

hi friends

i have issue with idoc distribution model.i created one model view assinged RFC messgae type and all.i generated partner profile successfully,

but when i go to distribute the model .i am getting error:Target system RFC name and Communication error occurred .

one exception is thrown here

Exception thrown by application running in JCo Server

java.lang.ClassCastException: com.ibm.j2ca.sap.ext.SapJCoServerHandlerFactory$SapBapiHandlerContext incompatible with com.ibm.

i checked with Basis team as well as middleware team and ESB team (target system).everyone is saying RFC is working fine.

can anyone have idea what getting falied.here.i checked in program level using debug also and found FM:MODEL_VIEW_REPLICATE

this FM is throwing Exception      SYSTEM_FAILURE.

please  let me know if anyone has idea about this issue.

Regards

gaurav

hi friends

i have issue with idoc distribution model.i created one model view assinged RFC messgae type and all.i generated partner profile successfully,

but when i go to distribute the model .i am getting error:Target system RFC name and Communication error occurred .

one exception is thrown here

Exception thrown by application running in JCo Server

java.lang.ClassCastException: com.ibm.j2ca.sap.ext.SapJCoServerHandlerFactory$SapBapiHandlerContext incompatible with com.ibm.

i checked with Basis team as well as middleware team and ESB team (target system).everyone is saying RFC is working fine.

can anyone have idea what getting falied.here.i checked in program level using debug also and found FM:MODEL_VIEW_REPLICATE

this FM is throwing Exception      SYSTEM_FAILURE.

please  let me know if anyone has idea about this issue.

Regards

gaurav

4 REPLIES 4
Read only

MarkusTolksdorf
Product and Topic Expert
Product and Topic Expert
0 Likes
1,003

Hi Gaurav,

this means that in the implementation of the function module in the JCoServer either a cast is done of two classes that are not really fitting to each other or that the instance that shall be assigned to a variable has been loaded by a different class loader and therefore it does not fit. Even the same classes are considered different, when being loaded by different class loaders. Hence, check the function implementation, the issue is neither located in the ABAP system nor in the RFC communication nor in JCo.

Best regards,

Markus

Read only

0 Likes
1,003

hi markus

thanks for reply,can u please tell me where we can check Jco server.

regards

gaurav

Read only

0 Likes
1,003

Hi Gaurav,

hmm, as the class name starts with "com.ibm", it looks like the receiver program is an IBM product. So you will probably have to contact IBM support, if you don't have the source code of the program yourself.

(When googling for the above class name, I found 2-3 hits on the IBM WebSphere support pages, but unfortunately they were different problems.)

Best Regards, Ulrich

Read only

0 Likes
1,003

Hi Gaurav,

you had mentioned a middleware and an ESB team. I assume that one of them is rsponsible for the component hosting the JCoServer. And very probably, Ulrich is right and contacting IBM support makes sense to analyze the issue.

Best  regards,

Markus