Skip to Content
author's profile photo Former Member
Former Member

Error Invoking Method on Inbound Java Proxy

Hi all!

I have a problem regarding an Inbound Java Proxy. The Bean is deployed and everything configured so far

here is the entry in the JPR:

http://plecto.com/ago/javaserver#JavaServerInterface = sap.com/PlectoProxies/JavaServerInterface_PortTypeBean:javaServerInterface

I can't see any mistake, also comparing it to a working inbound java proxy bean.

When I call the Bean, the XI monitor tells me:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<!-- Aufruf eines Adapters -->

http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="PARSING">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method javaServerInterface of proxy bean $Proxy210: null: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method javaServerInterface of proxy bean $Proxy210: null</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

I can only guess that the Bean cannot be located. I don't think the problem is that JPR can't invoke the method, even if I keep the stub generated by the Integration Builder it tells me this invokation errors.

What might be the reason of this error, where can I find log files, which show me the steps to the exception...

I appreciate any hint

thanks in advance

sincerely

Stefan B.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 08, 2004 at 12:10 PM

    I have soled the problem:

    You must not fill in the faultDeatil!

    I created a fault detail List and tried to fill the first item with text, that made the method somehow corrupt and the XI Monitoring told me "error invoking method".

    You may only fill in the standard-->faultText with a String, and the Url of course.

    to test wether the method is wrong or the interface has been wrongly implemented I left the generated Proxy Class (out of the designer) unchanged which still told me "error invoking method"

    IMHO, I think that the last two days I realised that the developers on SAP side could have done better work, once again.

    Message was edited by: Werner Scholze

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.