cancel
Showing results for 
Search instead for 
Did you mean: 

Dump in WD Java Application when using sap-wd-arfc-useSys Parameter

Former Member
0 Kudos

Hi Experts,

Our scenario is that we have a webdynpro application which will connect to 2 ECC systems for fetching data. I have created 4 JCos (1 model and 1 metadata for each ECC system) like this:

<CommonName>MODEL_DEST

<CommonName>META_DEST

<CommonName>MODEL_DESTEPQ

<CommonName>META_DESTEPQ

The first two JCos pointing to one system and the next two to some other system.

I created one WD Java application with a model for which I used the first 2 JCos for importing BAPIs. Now when I run the application without any URL parameters, application is perfectly fine connecting to the first system and fetching data.

When I add parameter to the application and run the url as below:

http://<server>:<port>/webdynpro/dispatcher/<vendor>/<dcname>/<appname>?sap-wd-arfc-useSys=<CommonNa...

my application is throwing dump as shown here:


com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:107)<vendor>.multisys.comp.mutibackend.VcMultiBackendComp.executeCustomerF4Bapi(VcMultiBackendComp.java:268)

<vendor>.multisys.comp.mutibackend.wdp.InternalVcMultiBackendComp.executeCustomerF4Bapi(InternalVcMultiBackendComp.java:290)<vendor>.multisys.comp.mutibackend.VcMultiBackendComp.getCustomerList(VcMultiBackendComp.java:227)

<vendor>.multisys.comp.mutibackend.wdp.InternalVcMultiBackendComp.getCustomerList(InternalVcMultiBackendComp.java:286)<vendor>.multisys.comp.mutibackend.VcMultiBackendView.onActionGetCustomerList(VcMultiBackendView.java:145)

<vendor>.multisys.comp.mutibackend.wdp.InternalVcMultiBackendView.wdInvokeEventHandler(InternalVcMultiBackendView.java:211)com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)

com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)

com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

javax.servlet.http.HttpServlet.service(HttpServlet.java:853)com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)com.sap.engine.services.httpserver.server.Client.handle

(Client.java:95)com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)java.security.AccessController.doPrivileged(Native Method)

com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

The line of code which shows is nothing but execute statement written in WD Java for the BAPI and the places where I call the BAPI

I followed these below links to achieve what I am trying

http://help.sap.com/saphelp_nw70/helpdata/en/2a/7a754297fdd142e10000000a1550b0/content.htm

Mapping Logical Systems - Using Java - SAP Library

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/526bd490-0201-0010-038e-d3ff7eb1d...

Correct me if I did anything wrong.

Edit: The EP version we are using is 7.0

Accepted Solutions (1)

Accepted Solutions (1)

govardan_raj
Contributor
0 Kudos

hi sujai ,

since it is showing the point where we execute the rfc in wdjava code , can you please check wheather the mandatory inputs are getting passed , i.e print the success messages and check the inputs passed , for both types of jcos , and also check st22 if any dump you are getting at abap side ,

if you are not able to find any then in the second jcos where this dump is occuring check wheather the user name given as sufficient authorizations , check logs at nwa , it will give exact problem you are facing.

log the exceptions at NWA , that will help you to trace the error and you can solve the same.

Regards

Govardan Raj S

Former Member
0 Kudos

Thanks for the reply Govardan. The issue is not with rfc or errors from abap side though I have found out the solution. I just used another parameter which solved my problem.

The parameter that I have used is:

sap.wdarfc.useSys

Now the application works as expected

Answers (0)