SXMB_MONI shows error in Java Proxy (Inbound)

Hi All,
My scenario is FTP->XI->Java Proxy->FTP
I have configured the JPR Adapter and registered it correctly. But in SXMB_MONI, I am getting the error in JPR Adapter(Response) stating that,
Error when receiving by HTTP (error code: 108, error text:)
What could the problem?
Rgds,
-Prasad U

please change the time in the 'end of execution until' and check.Try giving it as 00:00:00 of the next day instead of 24:00:00 of the same day if you want to check the messages for that particular day.This might help.

Similar Messages

Sxmb_moni shows error

sxmb_moni shows error message when ever the transaction is processed.
SYSTEM ERROR OCCURED DURING PERSIST. this is the error message.This happens when i try to execute monitor for processed xml messages and it stops in that page.

please change the time in the 'end of execution until' and check.Try giving it as 00:00:00 of the next day instead of 24:00:00 of the same day if you want to check the messages for that particular day.This might help.

Error in java proxy generation due to xs:choice tag

Hi all,
I'm trying to generate a java proxy in the SAP XI design.
The message interface I'm using is based on an external definition which i imported from an xsd file.
The problem is that XI doesn't allow me to generate the java proxy because in the xsd schema the tag <xs:choice> is present and XI cannot handle it (just in this case, because the external definition works fine).
Does anybody know how to solve the problem or manage to generate the javaproxy anyhow?
Thanks in advance,
Daniele

> Replace <xs:choice> tag with <xsd:choice> tag
> 
> that should solve the prob.
I tried to change the tag (replacing also other <xs:...> tags in order to obtain a valid xsd) but the problem didnt change.
i'm almost convinced that tag is not supported in java proxy generation (but it is for external definitions...)

Sync inbound java proxy timeout

Hi all
my scenario abap proxy to java proxy sync.
but i had timeout error with some bulk data, but not too big...
does anyone know how to increase time for inbound java proxy?
regards;
dennis

Dear Ogawa,
Please if you have step by step document please send me .
i am getting this error in my scenario:
I am working on Java server proxy, In my scenario i am picking a file from sender File Adapter and in Receiver side i am using java proxy (Inbound). But in SXMB_MONI , it give me the Error and Error no is :110
See the Detailed Error in Call Adapter.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please help me .
Regards
Lateef

Inbound Java Proxy doesnu00B4t work

Hi
I have configured the following steps for an Inbound Java Proxy:
1.- Create a Business System (Web AS Java) where is located the Proxy.
2.- Create a XI receiver comm. channel with the respective configuration
3.- Create a Java Proxy and implemented in NWDS
4.- Generate a .jar archive
5.- Generate a .ear archive and deploy to the Integration Server.
6.- Register the Proxy.
The scenario is JDBC --> XI --> Java Proxy. In the SXMB_MONI TC show no errors but the java proxy doesn´t work, that is, it doesn't do anything. Somebody knows why?

thanks Krishna, I've look into the RWB and see an error in the Adapter Engine, I attach the Log in the Audit Log Tab of the message:
Success Message successfully received by messaging system. Profile: XI URL: http://myAppServer:50000/MessagingSystem/receive/JPR/XI Credential (User): XIAPPLUSER
Success Using connection JPR. Trying to put the message into the receive queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the receive queue.
Success The message status set to DLNG.
Success Java proxy runtime (JPR) accepted the message
Error Delivery of the message to the application using connection JPR failed, due to: Exception in method $messageSpecifier..
Success The asynchronous message was successfully scheduled to be delivered at Mon Sep 04 10:43:06 GMT-04:00 2006.
Success The message status set to WAIT.
Success Retrying to deliver message to the application. Retry: 1
I cannot see all the text in the error message, but it tell me that the error is in the JPR?

Java Proxy Runtime: failure to locate proxy bean on inbound call

Hello gurus of the SDN,
I have been trying to get an inbound Java Proxy scenario to work in XI 3.0 but have not been able to get the JPR to recognize my generated and deployed java code. My scenario is set up to call the java proxies generated from a message interface based on the MATMAS Idoc. I successfully deployed the generated java proxies on the same host box as is running the XI instance. The objects are named as follows
Message interface on XI = Inbound_MATMAS04
Generated proxy bean = Inbound_MATMAS04_PortTypeBean
Implementing class = InboundMATMAS04_PortTypeImpl
Implementing method = inboundMATMAS04
I used the JPR transport servlet to register the interface and implementing class but am not sure if I did this correctly. I used the following entry in my web browser:
http://nadcp786:50000/ProxyServer/register?
ns=urn:xiTrainingLabs:groupXX:SAP&
interface=InboundMATMAS04&
bean=InboundMATMAS04_PortTypeImpl&
method=inboundMATMAS04
I also tried using the localejb/ prefix for the bean name in the above step since the code is co-located. When I trigger the scenario, the Idoc info is passed into XI and the Java Proxy Runtime is called, but I get the following error response back in the SOAP header:
- <SAP:Error xmlns:SAP="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: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Finally, appended at the end of this post is the audit log of the messaging system showing that the JPR is called but without being able to locate the bean. I think I am missing a configuration step somewhere, but cant figure out what it is!! Can anyone help me?
Many thanks in advance.
Regards,
Nick Simon
Time Stamp Status Description
2004-10-25 19:47:32 Success The message was successfully received by the messaging system. Profile: XI URL: http://nadcp786.bcsdc.lexington.ibm.com:50000/MessagingSystem/receive/JPR/XI
2004-10-25 19:47:32 Success Using connection JPR. Trying to put the message into the receive queue.
2004-10-25 19:47:32 Success The message was successfully retrieved from the receive queue.
2004-10-25 19:47:32 Success The message status set to DLNG.
2004-10-25 19:47:32 Success Java proxy runtime (JPR) accepted the message
2004-10-25 19:47:34 Error JPR could not process the message. Reason: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl
2004-10-25 19:47:34 Error Delivery of the message to the application using connection JPR failed, due to: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl.
2004-10-25 19:47:34 Error The message status set to FAIL.
2004-10-25 19:47:34 Error Asynchronous error detected: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl. Trying to report it.
2004-10-25 19:47:34 Error Asynchronous error reported.
Message was edited by: Nicholas Simon

Hi
How do you determine the JNDI naming of the a EJB?
I have following entry in JNDI directory in the root
Object Name FlightQueryIn
Class Name javax.naming.Reference
Context Name
Object Value Reference Class Name:
Type: clientAppName
Content: sap.com/JavaProxyEAR
Type: interfaceType
Content: remote
Type: home
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4
Type: ejb-link
Content: FlightSeatAvailabilityQueryIn_PortTypeBean
Type: jndi-name
Content: FlightQueryIn
Type: remote
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4
I tried to register the bean with JPR using:
http://ctsapxid01:50100/ProxyServer/register?ns=http://sap.com/xi/XI/Demo/Airline&interface=FlightSeatAvailabilityQuery_In&bean=FlightQueryIn&method=flightSeatAvailabilityQueryIn
I followed the following blog
http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
Thanks,
Chris

XI 2.0 Java Proxy error

Hi All,
I am receiving the following error:
RFC_ADAPTER.JCO_RUNTIME_EXCEPTION:System error when calling the outbound RFC adapter (cannot deserialize JCo request from XML)
The message I'm sending is synchronous coming from a Java Webapp and requesting infomation from R/3.
There are two pieces to the interface I have created. The first is calling a function which validates a few fields then returns 'return codes'. The second will create a sales order and return a few numbers. They are built into the same interface and use message splitting based on an input field. The verification piece is working which tells me that this is not a problem with the actual RFC adapter but when I run the 'create sales order' function I receive the aforementioned error.
n e thoughts?

Hi Stefan, thx for the reply.
I am running the latest version of the function. I do have one date field in the RFC structure, the rest are strings. The data going into that date field is being mapped from a string field in the sent message. This shouldn't be a problem (I don't believe) I have done this in many other interfaces.
I noticed that in my xi monitor (SXMB_MONI) under the column labeled 'Outbound' the acronym 'RFC' shows up for my failing message. When I send a message through the other java proxy interface that works I get nothing in the column. I'm not sure if this means n e thing but I thought I would through that in.
I've also set up my scenario changing from synchronous to asynchronous and using the file adapter and it seems to make it through, minus the error on the return message.
.. I forgot to mention that there have not been any changes to the RFC adapter configuration. ... and I have restarted it to see if that would make a difference. It did not.
n e other ideas?
Message was edited by: Larry Chaput

Error with JPR(Java Proxy Runtime) in Adapter Monitor of RWB

Dear Experts,
             I am implementing scenario with Client Java Proxy(Outbound) and Server ABAP Proxy(Inbound). We have done all the designing in IR and configurations in ID. We have deployed the EAR successfully. But when we go to RWB(Runtime Work Bench) to monitor the inital status of JPR in RWB->Adapter Monitor. It shows the following error.
Status     Name                                Text
Error        SLD Access                     SLD host:port = yhsapi01.yashsap.com:50000
Error getting JPR configuration from SLD. Exception: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=yhsapi01 SYSNR=00 GWHOST=yhsapi01 GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR max no of 100 conversations exceeded
TIME Wed Jun 03 19:42:45 200
RELEASE 700
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 466
MODULE r3cpic.c
LINE 10713
COUNTER 5521
No access to get JPR configuration

Hi!
Obviously there are more than 100 connections opened in your system.
ERROR max no of 100 conversations exceeded
Please check your gateway settings (in ABAP you can check the parameters using transaction SMGW).
Regards,
Volker

Error while running java proxy in PI 7.1

Hi All,
I had created a java proxy using nwds 7.1. This java proxy is called by XI channel and its synchronous.
WHen i run my scenario in PI i am getting a error "Error while sending message: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: No remote bean found for reference of class $Proxy2919
Kindly help me finding what can be the issue.
Regards,
Rajesh

Go to the JNDI Browser (Nwa -> Problem Management), and check if the proxy was deployed correctly with the exact name "Proxy2919".
Also, check the OSS note below.
#1292633 - JPR: Throwing "No remote bean found for reference of class"

Error with receiver java proxy

for a XI type communication channel for receiver Java proxy I see following error in SXMB_MONI.
Unable to read user password from communication channel of type Error when accessing the secure store (access ID = 3650CAFA1FBAA04E8F260C6C4C1923FA) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023).
I have specified the correct credentials for the non sap system in authentication data i.e. XIAPPLUSER and its password.
Any pointers?

Hi Amol
Did you solved this problem? I am also getting the same error when calling receiver java proxy with Adapter type XI.
If you have solved the problem pl let me know.
Regards
Prahllad

Java Proxy error

Hi,
I have generated and deployed Java server proxy successfully in PI 7.1.
The problem is I am getting a error as follows
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean sap.com/HTTPEAR/DeliveryInImp
I have regiered the bean using the URL already.
Should i add any jar references to my EAR explicitly and redeploy.
Regards,
Sudharshan N A

Hello,
You need to add the references of the proxy libraries (jars) in application-j2ee-engine.xml. Once you build the .ear file, you need to delete the libraries by unziping the .ear. Because, the proxy libraries (jar) should not be deployed as there are already existed in J2EE engine. Refer the following blog
/people/thorsten.nordholmsbirk/blog/2006/08/06/use-a-java-proxy-instead-of-a-jca-adapter
Regards,
Prasanna

Java Proxy error: Exception in method methodExists

Hello all!
We are doing the following synchronous scenario: CRM->XI->JavaProxy--->Third party....
Here is the process we are following to deploy our Proxy:
1.Created EJB Module Project in NWDS
2.Import the files generated by XI into ejbModule folder from ZIP file.
3.Renamed *PortTypeImpl.template to *PortTypeImpl.java
4.Compiled all code (no errors)
5.Added all the references to the SAP libraries required (taken from our XI server):
com.sap.aii.proxy.xiruntime
com.sap.xi.util.misc
com.sap.aii.messaging.runtime
com.sap.guid
6.Codified Java Proxy codified the method <interfacename> in the <intefacename>_PortTypeImpl class.
7.Edited ejb_jar.xml to add EJBs.
8.Provided a JNDI name in the file ejb-j2ee-engine.xml.
9.Built EJB archive (no errors).
10.Created a new Enterprise Application Project and pointed build path to our EJB Project.
11.Added our EJB to the Enterprise Application project.
12.Created the references to the SAP libraries in the Enterprise Application Project in the application-j2ee-engine.xml file:
com.sap.aii.proxy.xiruntime
com.sap.xi.util.misc
com.sap.aii.messaging.runtime
com.sap.guid
13.Within the Enterprise Application Project we built an EAR file.
14.We deployed our .ear file to the J2EE Engine via Visual Admin (no errors).
15.We registered our Java Proxy on the ProxyServer, using
/register?ns=<interface_namespace>&interface=<XI_Interface_Name>&bean=<EJB_JNDI_name> &method=<name of the method implemented by you on the _PortTypeImpl>
Actually, we did the following:
url for registering the EJB:
http://ithpsrq0:50200/ProxyServer/register?ns=http://banco.popular.com.pr/xi/crm&interface=mi_AccountInfo_is&bean=popularinc.com/MiAccountInfoIs_Default&method=miAccountInfoIs
Message displayed when listing interfaces (http://ithpsrq0:50200/ProxyServer/listAll)
http://banco.popular.com.pr/xi/crm#mi_AccountInfo_is = popularinc.com/MiAccountInfoIs_Default:miAccountInfoIs
1 interfaces found
When running the interface we get the following error:
com.sap.aii.af.ra.ms.api.DeliveryException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.
Does anyone have any suggestions?
What causes a "methodExists" Exception?
Please help us,
Thanks a lot!!!

Hi,
Is this a runtime of "com.sap.aii.proxy.xiruntime.core"
please check the jars used, adding this jars will solve this i guess.
aii_utilxi_misc.jar
ejb20.jar
exception.jar
jARM.jar
sapj2eeclient.jar
sapxmltoolkit.jar
aii_msg_runtime.jar
aii_proxy_xirt.jar
Also check, application-j2ee-engine.xml and see if,
com.sap.aii.proxy.xiruntime
com.sap.aii.messaging.runtime
com.sap.xi.util.misc
com.sap.guid
You wil get the jars in XI servers, you can ftp and get the jars, but you may need to search them.
Anotherthing, always take the jars from the xi servers to be sure you are compatible with the upgrades .
Hope this solves your problem.
Anirban.

Getting Inbound Java Proxy Exception in method "onMessage"

I have built an Inbound Java proxy, deployed the EJB, viewed it in the J2EE admin tool, registered the JPR settings (also listAll, reviewed results, looks OK), configure the XI scenario. When I run the XI scenario using the Runtime workbench I get the following error in the BPM Synchronous Send step (calling the Java Proxy)
"com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method onMessage".
Does anyone have any suggestions?
What causes an "onMessage" Exception?

Thanks Sudhir Here is the process I am following to deploy my Proxy, would you please validate it. Created EJB Project in NWDS, unziped XI gened proxies into ejbModule folder, renamed *PortTypeImpl.template to *PortTypeImpl.java (will add real code later), compiled all code (no errors), edited ejb_jar.xml to match your suggested format, can view EJB Candidates (and see my Proxy Bean), built EJB.JAR file (via Wizard), created new Enterprise Application Project and pointed build path to my EJB Project, within the Enterprise Application Project I built an EAR file (which includes the "EJB Project JAR File", Deployed Enterprise Application Project to the XI J2EE Engine. I can log into XI J2EE Admin and see my EJB Project and the Proxy Bean I am trying to execute. Is this the process you used to deploy the proxy bean?
Also you you turn on JPR Tracing to see what parameters are passed into the JPR engine?

[urgent]inbound java proxy

Hi
how can i know if receiver XI adapter touch inbound EJB by registering url?
my scenario is ABAP Proxy to Java proxy Sync.
i can see mapping error on moni because payload inbound adapter has empty ,
my issue, XI seems not to call inbound EJB?
on adapter monitoring, JPR green
what missing ?
XI receiver
HTTP 1.0
XI3.0
integration server
URL Address
Target Host : XI IP
service number : 50000
path : /MessagingSystem/receive/JPR/XI
authentication Type : Use Logon Data for Non-SAP System
UserName : XIAPPLUSER
password : password
thanks
ogawa

Hi,
Please can you put here what the error is:...check if the mapping is working properly...
Also can you check if the registering is done correctly.
Please check on this thread
Java Proxy Runtime: failure to locate proxy bean on inbound call
Regards
Vijaya

Inbound Async Java Proxy

I am using an Inbound Async Java Proxy to send via socket three strings, via SXMB_MONI and RWB->MM->MDT I can see message was successfully delivered to JP System that for me is the XI J2EE engine, the JP is not sending anything (the logic is very simple) much worse I hardcoded the strings that is to supose to send and still nothing happens, I think the JPR is not calling the EJB, this is the body of my ejb-jar.xml, I have doubts on the values of the local, home, remote... tags
<ejb-jar>
 <description>EJB JAR description</description>
 <display-name>EJB JAR</display-name>
 <enterprise-beans>
 <session>
 <ejb-name>MiIaAlertaDMS_PortTypeBean</ejb-name>
 <home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4</home>
 <remote>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4</remote>
 <local-home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocalHome4</local-home>
 <local>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4</local>
 <ejb-class>sapPegDmsPEGBPM00.MiIaAlertaDMS_PortTypeBean</ejb-class>
 <session-type>Stateless</session-type>
 <transaction-type>Container</transaction-type>
 </session>
 </enterprise-beans>
</ejb-jar>
Any ideas on this problem?
Thanks in advance.

HI,
Can you just cross check with the help of this blog-
/people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
Also as I told, you can write a file from payload in Java Proxy- to debug
Regards,
Moorthy

SXMB_MONI shows error in Java Proxy (Inbound)

Similar Messages

Maybe you are looking for