Adaptive RFC - Version problems?

[Former Member]

Hi,

I have one WebAS j2ee (6.40 sp11) system where my WebDynpro application connecting to RFC runs without any problem. But when I run it in my production WebAS (6.40 sp9), it runs into all kinds of problem. When I test the JCo connection, it throws:

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM

TYPE=B MSHOST=myserverxxx

GROUP=PUBLIC R3NAME=XXX MSSERV=sapmsXXX PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR partner not reached (host x.x.x.x, service sapmsXXX) TIME Thu Jan 27 17:27:08 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -10 MODULE nixxi_r_mt.cpp LINE 8579 DETAIL NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO 146 ERRNO TEXT Connection refused COUNTER 1

On this SP9 system, though I could create JCo connection for another R3 system (I mean Test Connection runs successfully), when I run the application, it throws this exception:

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for view com.sap.tut.wd.flightlist.SearchView. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)

at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:487)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:524)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

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:94)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Caused by: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:274)

at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)

... 33 more

Caused by: java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.gci.GCIContext.createMappedAttribute(Ljava/lang/String;Ljava/lang/String;Z)Lcom/sap/tc/webdynpro/progmodel/gci/IGCIAttributeInfo;

at com.sap.tut.wd.flightlist.wdp.InternalSearchView.<init>(InternalSearchView.java:43)

... 38 more

Can anyone help me with this? Thanks a million in advance!

Regards,

- Prashanth

[Former Member]

The usual problem: Web Dynpro runtime in NWDS and on Web AS have incompatible versions (SP numbers).

Armin

[Former Member]

Hi Armin,

Well, that IS the problem with the second part of my post But, the error (partner not reached) is very surprising, because when I created the connections for another R3 server, connections were tested successfully (and application threw runtime exceptions!). Moreover, when I compared the j2ee/os_libs folder, among the other things, my sp11 windows system had sapjco.jar and a couple of DLLs which my sp9 solaris system did not have. Does this mean that I donot have JCo installed on my SP9 system? How it is possible that test connection works for one R3 server and not for another?

I would be thankful for any help.