Java Proxy message in waiting status

Hi,
   Let me explain my case, In our Integration Scenario we have configured an Inbound Java Proxy as the How to guide (HOW TO WORK WITH JAVA PROXIES) expain, but the proxy doesn't hava code, that is, it have the code by default when its created, and when we register it and the scenario runs, in the message monitoring the status of the message to the JP Business Service is in WAITING status, and in the details it says sometimes that an old reference to another JNDI name of bean is doesn't locate or the message "MessageSpecifier could not be reset".
   Remember, the Imp. class has only the default code and the scenario is JDBC --> XI --> JavaProxy
   Any ideas?

Hi Hector,
Status: WAITING
The message had been sent and it is failed and is currently waiting for another attempt.
Solution :
When the fist attempt to deliver the message has failed (a recoverable exception arose), the message is usually rescheduled and the status is updated to WAITING. As long as the message is in this status, the Messaging System retries to deliver the message according to the configured retry settings (default 3 tries).
Regards
Agasthuri Doss

Similar Messages

Messages in HOLDING status in AE

Hi All,
We have an issue with JDBC receiver EOIO messages, with messages going into HOLD status in AE , its a DEV environment :
1) We have tried checking for failed messages before these messages we donot have any failed messages before these messages just messages in HOLD..
2) we are not able to delete or cancel these messages , we get a message cannot delete the message ,
3) The message is doing a INSERT update to JDBC , JDBC connection is fine.

Hi Kiran,
Please let me know if your problem is fixed.
I'm also facing the same problem in our Testing system where many messages are going to HOLD Status and also there are no messages in the System Error state.
We are trying to resend all the messages in every "Conversation ID". After this some messages gets successful and some will go into Waiting status. We then cancel the messages in waiting status and resend all the messages in HOLD status and the process continues till all the messages in HOLD status in every Coversation ID were cleared.
But this is a very very time consuming process.
So can you please let me know if there is any solution for this prolem.
Thanks,
Pruthvi

Execute Fault Message in Java Proxy

Hello,
I Call my Java Inbound Proxy and catch an exception.
How can i send now a Faul Message back to XI ?
} catch (Exception ex4) {
               ExchangeFaultData_Type faultData = new ExchangeFaultData_Type();
               faultData.setFaultText(ex4.getMessage());
               ErrorReturn_Type errorReturn = new ErrorReturn_Type();
               errorReturn.setStandard(faultData);
What should i do ?
Regards,
Robin

Hi Robin:
Without knowing your complete code, I think what your are missing is "gluining" everything together, something like this:
Somewhere in your code, define some variables:
      ExchangeFaultData_Type      faultData                   = null;
      FmJpAviso_Type              fmJpAviso_Type              = null;
      FmJpAviso_Message           fmJpAviso_Message           = null;
      FmJpAviso_Message_Exception fmJpAviso_Message_Exception = null;
      catch( HibernateException ehibernate )
       mensajeError = new StringBuffer();
       mensajeError.append(DataComercial.PED_XI_BDI_DMS_DC_001).append("\n\n")
                            .append(ehibernate.toString());
       catAPPL.fatalT(logger,mensajeError.toString());
          // Default Integration Scenario ExchangeFault Message
       faultData = new ExchangeFaultData_Type();
       faultData.setFaultText(mensajeError.toString());
           // My Fault Message Type for the inbound Message Interface
       fmJpAviso_Type = new FmJpAviso_Type();
       fmJpAviso_Type.setStandard(faultData);
           // My Fault Message
       fmJpAviso_Message = new FmJpAviso_Message();
       fmJpAviso_Message.setFmJpAviso(fmJpAviso_Type);
          // My Fault Message Exception
       fmJpAviso_Message_Exception = new FmJpAviso_Message_Exception();
       fmJpAviso_Message_Exception.setFmJpAviso_Message(fmJpAviso_Message);
       ehibernate = null;
       mensajeError = null;
          // Inform XI about this situation in the Java Proxy
       throw fmJpAviso_Message_Exception;
Hope this helps,
Regards, Pedro

Does Java Proxy guarantee the delivery of message?

Hi All ,
I would like to know, if java client proxy guarantees the delivery of messages similar to ABAP client proxies.
I am asking this question with reference to a situation where the XI system is down and the client proxy messages are invoked to the Integration Server.
Can anyone share more thoughts on this?
Thanks
Narendra

Narendra,
Refer to the url http://help.sap.com/saphelp_nw04/helpdata/en/e3/c809c2fde0af4098e1ae126d06866c/frameset.htm
From the menu on the LHS of this page you can navigate down to Acknowledgements
An acknowledgement can be set which will enable you to confirm that an asynchronous message has been received
Hope this helps,
Mike

Messages stuck with status "WAITING"

Hi Everyone,
We have implemented PI interface a year ago with JDBC sender (ORACLE) and RFC receiver (SAP) to transfer the goods movements from legacy to SAP and give back the current stock after the goods movement is posted back to ORACLE system.
The interface has been working fine for over an year now but suddenly since 15days we are experiencing the issue of delays in message transmission where-in in SXMB_MONI we see a time difference of 60-90mins between start message start time and end time...
Nothing has been changed from development/design perspective and am unable to understand the reasons for this delay.
Also for the above scenario the message status in MESSAGE MONITORING shows waiting status and i have cross verified for any errors and could not find any errors in given time.
also MDT Screen shot for your reference
I am struggling to figure out the reasons and this is causing stock mismatch between Oracle system and SAP and has become show stopper.
Please guide me in identifying the root cause and fixing this...
Thanking you all in anticipation of help...
Lakshmi

hi Claudia,
I have cross verified both and as you can see there are no errors
a
and finally the XML
couldn't figure out why this delay happening... One thing after an hour or so... the things get cleared as one in executing state finishes leading to others to finish.. but by then they are getting accumulated
Appreciate any guidance to figure out the root cause...
Thanks in advance
lakshmi

Message Inbound with Java Proxy

Hi all,
I try looking for java proxy example code to write a whole inbound message into file. But I can't to find it. I try with these blogs but still confuse.
/people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
/people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
Could you please to help and give me a example code?
Thanks and Regards
Park

Hi,
Refer this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702
I hope this would help you

How to cancel processed messages with acknowledgement waiting status

Hi All,
Messages processed successfully in Integration Server but messages still waiting for acknowledgement. I want to cancel these messages.Will u please let me know how to do delete these messages.I already canceled messages with status to be delivered in Integration Engine and Adapter Engine. But in SXMB_MONI, messages are processed successfully with waiting status.Please suggest how we need to cancel them.
Please Suggest some possible solution.
Regards,
Kanisha Sharma
Edited by: kanisha on Jul 2, 2010 8:28 AM

Hi,
Thanks for your reply.Yes it is an IDOC based scenario. But Idoc is in outbound side. Idoc processed successfully in ERP as well as PI processed successfully to MDM.Messages processed successfully in SXMB_MONI but once imported in MDM IS, then acknowledgement will be send to PI.My issue is:- MDM server is down and i want to cancel these messages.
Please suggest
Regards,
Kanisha Sharma

Synchronous Java Proxy Server template - filling reponse message elements

Hi !
I'm writing a java proxy server for a synchronous interface. I'm somehow new in java...and I don't know how should I create elements for my response message inside the java method used to process the request message.
The response message format is something like this:
<field1>abc</field1>
<field2>
....<field2a>
........<fields2a1>
........</fields2a1>
....</field2a>
....<field2a>
....</field2a>
</field2>
according to the type "DT_Output_Type" type of the public class MyMethod defined in the java template generated by XI repository..
I think I should do something like this:
DT_Output_Type response = new DT_Output_Type();
DT_Output_Type.field2_List field2values = new DT_Output_Type.field2_List();
field2values.setfield2a(0,"1234");
response.setfield1 = "abc";
response.setfield2(field2values);
return response;
But I receive "Error invoking method". If I comment out the code where I assign values to sub-elements, everything works ok.
Thanks !
Matias

Hi Matias,
>>DT_Output_Type.field2_List field2values = new DT_Output_Type.field2_List();
This will create instance for field2 only.
Before setting field2a using field2values.setfield2a(0,"1234"); you must creat instance of field2a and also for field2a1.
I guess field2a will be an array.
so the order of creating instance and setting values can be ...
1. create instance of field2
2. create instance of field2a array
3. create instance of first array element of field2a
4. create instance of field2a1
5. set value for field2a1
6. set field2a1 in first array element of field2a
repeat steps 3-6 for next elements of field2a
7. set field2a array object (created in step 2) in field2
8. response.setfield2(field2values);
Also,
as mentioned by Amol, set value for filed1 should be
response.setfield1("abc");
Regards,
Uma

Java Proxy Fault Message

Hello,
I have a async Java Inbound Proxy.
When i send a message to this Interface i call a java class how connect to a jdbc database.
When the Database is not online i catch an exception.
This exception i want to send with a fault message to XI.
What i have to do ?
At the moment i do the following but it doesn't work:
} catch (SQLException e) {
ExchangeFaultData_Type faultData = new ExchangeFaultData_Type();
faultData.setFaultText(e.getMessage());
ErrorReturn_Type errorReturn = new ErrorReturn_Type();
errorReturn.setStandard(faultData);
throw new ErrorReturn_Message_Exception();
Any Idea?

Hi Robin:
Without knowing your complete code, I think what your are missing is "gluining" everything together, something like this:
Somewhere in your code, define some variables:
      ExchangeFaultData_Type      faultData                   = null;
      FmJpAviso_Type              fmJpAviso_Type              = null;
      FmJpAviso_Message           fmJpAviso_Message           = null;
      FmJpAviso_Message_Exception fmJpAviso_Message_Exception = null;
      catch( HibernateException ehibernate )
       mensajeError = new StringBuffer();
       mensajeError.append(DataComercial.PED_XI_BDI_DMS_DC_001).append("\n\n")
                            .append(ehibernate.toString());
       catAPPL.fatalT(logger,mensajeError.toString());
          // Default Integration Scenario ExchangeFault Message
       faultData = new ExchangeFaultData_Type();
       faultData.setFaultText(mensajeError.toString());
           // My Fault Message Type for the inbound Message Interface
       fmJpAviso_Type = new FmJpAviso_Type();
       fmJpAviso_Type.setStandard(faultData);
           // My Fault Message
       fmJpAviso_Message = new FmJpAviso_Message();
       fmJpAviso_Message.setFmJpAviso(fmJpAviso_Type);
          // My Fault Message Exception
       fmJpAviso_Message_Exception = new FmJpAviso_Message_Exception();
       fmJpAviso_Message_Exception.setFmJpAviso_Message(fmJpAviso_Message);
       ehibernate = null;
       mensajeError = null;
          // Inform XI about this situation in the Java Proxy
       throw fmJpAviso_Message_Exception;
Hope this helps,
Regards, Pedro

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?

Problem with Java Proxy and Socket Connection

Hi Gurus!!
I have developed a Java Proxy that connects via socket with a Server Socket application. This Server Socket application accepts more than one connection at the same time.
When I connect the first time from my Java Proxy, the connection is correctly established. When the first connection opened, if a try a second connection, this is not established.
I use "new Socket(SocketServer,SocketPort);" to open the connection.
I think that all time the Java Proxy is trying to open the same connection, and this is a problem.
Is there a way to indicate to the server that is a new connection and that the existing connections remain?
Anybody could help me, please?
Thanks and regards,
Manuel Míguez.

Sorry!!!!i must give you more information.
The error which i have when i push the submit button is
HTTP Status 404 -
type Status report
message
descriptionThe requested resource () is not available.
GlassFish Server Open Source Edition 3.0.1
My thought is that the error is in this line
String connectionURL = "jdbc:mysql://localhost/mybooking";in mysql when i write this code then the table opens with no problems:
mysql>show databases;
mysql>usebooking;
mysql>showtables;
mysql>describe booking;Furthermore i have added in my web application the library mysql JDBC driver my-sql-connector-java-5.1.6.bin.jar
Edited by: 813355 on Nov 22, 2010 1:50 AM
Edited by: 813355 on Nov 22, 2010 2:00 AM

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

Error in scenario for client Java Proxy

2006-04-28 15:30:49 Success Java proxy runtime (JPR) is transferring the request message to the messaging System
2006-04-28 15:30:49 Success Application attempting to send an XI message synchronously using connection JPR.
2006-04-28 15:30:49 Success Trying to put the message into the call queue.
2006-04-28 15:30:49 Success Message successfully put into the queue.
2006-04-28 15:30:49 Success The message was successfully retrieved from the call queue.
2006-04-28 15:30:49 Success The message status set to DLNG.
2006-04-28 15:30:50 Error Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: No receiver could be determined
2006-04-28 15:30:50 Error Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:.
2006-04-28 15:30:50 Error Transmitting the message using connection http://<SERVER>:<PORT>/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:.
2006-04-28 15:30:50 Error The message status set to FAIL.
2006-04-28 15:30:50 Error Returning to application. Exception: XIServer:NO_RECEIVER_CASE_BE:
2006-04-28 15:30:50 Error JPR failed to transfer the request message to the messaging system. Reason: XIServer:NO_RECEIVER_CASE_BE:
I am getting this in the audit log for a Java Proxy <> XI <> RFC scenario. What could be the problem?
the configuration in integration directory seems to be perfectly fine however the message flow fails giving this error NO_RECEIVER_CASE_BE
Regards,
Amol

HI Amol,
Did you check the Message type/Message Inetrface names in the Java Proxy ?
Also check for Receiever Determinations in the configuration.
I assume that , you have created the Communication Channel under the Business System created as Standalone Java System.. If not check this.
Go to SXI_CACHE and check for the Receiever Determination created in the Configuration...
Hope this helps,
regards,
Moorthy

Java Proxy Registration

Hi All,
Just tell me whether this is the correct way of registering the Java Proxy or not....
I am using Inbound Proxy...
http://sapntwr.wipro.com:50000/ProxyServer/register?ns=urn://wipro.com/proxytest&interface=MIDataTarget&bean=com.wipro.proxytest/JProxEAR/MIDataTarget_PortTypeBean&method=mIDataTarget
where
sapntwr.wipro.com is the host
50000 is the port
urn://wipro.com/proxytest is the namespace I have created my objects
MIDataTarget is the Message Interface for Target message
com.wipro.proxytest/JProxyEAR/MIDataTarget_PortTypeBean is the JNDI Name
and
mIDataTarget is the method used in Implementation class to access the data.
If this is the correct way to register, then I am puzzled why I am getting error in SXMB_MONI....
Messages are stopped in the queue.
Can anyone help me out to solve this......
Thanks & Regards,
Prasad U

Hi Sudhir,
Thank you for the response. Now I am getting the following error in "Error" xml in SOAP Header.
Please tell me wheather this is coz of some authentication problem or some problem with my Proxy.
<?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">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> 403 &nbsp Forbidden</td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23">SAP J2EE Engine/6.40 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> You are not authorized to view the requested resource. <table><tr><td valign="top"> Details:</td><td valign="top"><PRE>No details available</PRE></td></tr></table> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 403 with the description Forbidden XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Prasad U

Business system for java proxy

i use xi system as java AS for java proxy. in receiver communication channel i use URL ADDRESS or HTTP destination?????

please help me its showing following error
<Trace level="2" type="T">Switch back to normalized party (HTTP response)</Trace>
<Trace level="1" type="T">Sender scheme external =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="2" type="T">Undo header mapping (HTTP response)</Trace>
<Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party =</Trace>
<Trace level="1" type="T">Agency =</Trace>
<Trace level="1" type="T">Scheme =</Trace>
<Trace level="1" type="T">Service = BS_Debashish</Trace>
<Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party =</Trace>
<Trace level="1" type="T">Agency =</Trace>
<Trace level="1" type="T">Scheme =</Trace>
<Trace level="1" type="T">Service = XIT4Java</Trace>
<Trace level="2" type="T">Sender: Header after undo of mapping</Trace>
<Trace level="2" type="T">Party =</Trace>
<Trace level="2" type="T">Agency =</Trace>
<Trace level="2" type="T">Scheme =</Trace>
<Trace level="2" type="T">Service = BS_Debashish</Trace>
<Trace level="2" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="2" type="T">Party =</Trace>
<Trace level="2" type="T">Agency =</Trace>
<Trace level="2" type="T">Scheme =</Trace>
<Trace level="2" type="T">Service = XIT4Java</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>

Java Proxy message in waiting status

Similar Messages

Maybe you are looking for