Web service consumer (proxy) and "commit work" statement (short dump)

[Former Member]

Hi all,

I'm dealing with a short dump after the development of a web service consumer (ABAP proxy). My ABAP is invoked as a print routine for an output message handled by RSNAST00 standard program. The goal is to transmit some data to an external web service during the output handling.

I did  se80, proxy generation and SOA manager configuration so far. It seems everything is looking fine. Nevertheless I have a real trouble.

When the proxy is called  no error happened. By then RSNAST00 usually perform a "COMMIT WORK AND WAIT" statement at the end of his processing in order to commit all NAST message updating and more.

My concern is that this "commit" command and the SOAP are not compatible.

After the RSNAST has finished, I have a short dump "CX_BGRFC_INVALID_DESTINATION".

Doing some research on the internet I found this exception has some relationship with a kind of SOAP scheduler. No clue about what is it or how can I configure it.

So now I'm in two minds if I'm doing something wrong in my ABAP proxy (SOA MANAGER,SE80) configuration or maybe some SOAP layers are not configured properly on SAP.

I will enclose the short dump and the dump picture I got.

Thanks in advance for any suggestion.

Fabrizio

[nabheetscn]

This message was moderated.

[Former Member]

Thanks for the answer, but I still have problem.

First of all transaction SBGRFCMAINIDST seems not been present on ECC system.

Browsing notes I have also found some transactions like SBGRFCCONF and RK12.

But now I'm wondering if I sttarted from a wrong wntry point.

Is this background RFC queing and setup compulsory in order to consume a web servica via ABAP proxy? I never had this dump before.

I started from SE80 and then I went to my package and choosed CREATE->ENTERPRISE_SERVICE. Then I have followed the wizard.

Is it the right way to start developing a web service (without XI/PI) ????

Is there any difference from enterpeise services and web services in SE80?

Thanks

Fabrizio

[Former Member]

Hi Fabrizio

I've had this issue 2 times in 3 days.

First the regular call to proxy was giving dump.

Then I test executed the proxy with dummy data, the call was successful, but if i do Extras > Trigger Commit Work, it gave same dump.

Then I tried trigger commit work for some other proxy, just to see whether issue is global or specific to my proxy. Dump was coming only for my proxy on trigger commit work.

After hit and trial, it was resolved after recreating the logical port in SOAMANAGER.

While creating logical port, system asks for WSDL url.

In my case, either the URL had changed, or contents of WSDL had changed.

[Former Member]

Hi Kumar,

I have solved the issue by applying sap note 1059303.

Now a commit work doesn't cause a short dump anymore.

It seems EHP5 or higher patch levels don't suffer from the same problem.

BR

Fabrizio

[Former Member]

Well I am on a higher release and still faced same dumps.

[Former Member]

I regret to hear this.

Anyway I did not say anything about the release, but I was talking about the enhancement package.

Even though I was working on a real rubbish server, I've just followed the note and solved this issue.