xi monitor - trace error...file transfer failed but status is green light..

[Former Member]

Hi Friends,

<Trace level="1" type="T">Cache Content is up to date</Trace>

<Trace level="2" type="T">Start without given receiver</Trace>

<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>

<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>

<Trace level="2" type="T">...valid Receiver w/o Condition: - SRV_HR_TIMEVENT_UPLOAD_QUA</Trace>

<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>

<Trace level="2" type="T">Number of Receivers:1</Trace>

is that mean everything is fine...?

Thanks..

Maddy

[former_member238007]

Hi,

I think there is no error present in that..

and at the same time check with the log file which was created in the server and u may clearly see the additional information about the failure of the message ..

check once with the queue, using SMQ1 and reprocess the same message if every thing is fine with the queue..

regards,

Kishore.

[Former Member]

Hi

This is what the error status of message

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

- <!-- Request Message Mapping

-->

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

<SAP:Category>Application</SAP:Category>

<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>

<SAP:P1>com/sap/xi/tf/_timerecording_selectempno_to_empti~</SAP:P1>

<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>

<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_timerecording_selectempno_to_empti_{: RuntimeException in Message-Mapping transformatio}</SAP:Stack>

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

</SAP:Error>

What would be the reason ..

Thanks.

[former_member240483]

HI there ,

Seems some problem with your mapping..

do one thing test u r mapping in IR check whether it is working fine or not?

if it is then try to re process message again ...

if not u have to check u r mapping.

Regards

Rao

[former_member238007]

Hi,

Problem with your mapping yaar..

Just test the mapping in the IR .. and press F7 to check the basic errors,

then go to the Test tab in mapping, and give some sample values there and run it.

if runs fine there, then u may not get this error..

and activate the scenario and run..

regards,

Kishore

[Former Member]

Hi,

The messages are struck in the queue,please check the queue and try to clear and reprocess it.

Regards,

Nithiyanandam

[GabrielSagaya]

It seems your message is getting stuck in queue.Check transaction SMQ1.Is there any queue present.Delete the queue and process you message again

Also, go to SXI_CACHE and check the status of your Cache. is it green?

[Former Member]

Hi,

Your trace details have not indicated anything about failure...Please can you give the error details if you have from RWB or SXMB_MONI that have indicated about the failure of file transfer.

Thanks

Swarup

[prateek]

I dont think there is any problem. Are u facing any problem in ur scenario.

Regards,

Prateek

[Former Member]

Hi friends,

Still problem is existed... the below xml code message shows the reasons for failures ...i guess...

***********************************************************

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

- <SOAP:Header>

- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<sap:MessageClass>ApplicationMessage</sap:MessageClass>

<sap:ProcessingMode>asynchronous</sap:ProcessingMode>

<sap:MessageId>aa775670-f49e-11dc-8af5-001b787aa1c4</sap:MessageId>

<sap:TimeSent>2008-03-18T03:52:01Z</sap:TimeSent>

- <sap:Sender>

<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />

<sap:Service>SRV_HR_TIMEVENT_UPLOAD_QUA</sap:Service>

</sap:Sender>

- <sap:Receiver>

<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />

<sap:Service>SRV_HR_TIMEVENT_UPLOAD_QUA</sap:Service>

</sap:Receiver>

<sap:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZPF001_CC1_UPLOAD_TIMEEVENT</sap:Interface>

</sap:Main>

- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">

<sap:QualityOfService>ExactlyOnce</sap:QualityOfService>

</sap:ReliableMessaging>

- <sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">

<sap:Record namespace="http://sap.com/xi/XI/System/File" name="SourceFTPHost">10.10.40.146:21</sap:Record>

<sap:Record namespace="http://sap.com/xi/XI/System/File" name="Directory">/db2/MXP/arch_log/XI/PRODUCTION/HR</sap:Record>

<sap:Record namespace="http://sap.com/xi/XI/System/File" name="SourceFileTimestamp">-</sap:Record>

<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileType">bin</sap:Record>

<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">atnd217.TXT</sap:Record>

<sap:Record namespace="http://sap.com/xi/XI/System/File" name="SourceFileSize">-</sap:Record>

</sap:DynamicConfiguration>

- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">

- <sap:Hop timeStamp="2008-03-18T03:52:01Z" wasRead="false">

<sap:Engine type="AE">af.mxp.mxiprd</sap:Engine>

<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>

<sap:MessageId>aa775670-f49e-11dc-8af5-001b787aa1c4</sap:MessageId>

<sap:Info />

</sap:Hop>

- <sap:Hop timeStamp="2008-03-18T03:52:01Z" wasRead="false">

<sap:Engine type="IS">is.23.mxiprd</sap:Engine>

<sap:Adapter namespace="http://sap.com/xi/XI/System">XI</sap:Adapter>

<sap:MessageId>aa775670-f49e-11dc-8af5-001b787aa1c4</sap:MessageId>

<sap:Info>3.0</sap:Info>

</sap:Hop>

- <sap:Hop timeStamp="2008-03-18T03:52:04Z" wasRead="false">

<sap:Engine type="AE">af.mxp.mxiprd</sap:Engine>

<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>

<sap:MessageId>aa775670-f49e-11dc-8af5-001b787aa1c4</sap:MessageId>

</sap:Hop>

</sap:HopList>

- <sap:Diagnostic xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">

<sap:TraceLevel>Information</sap:TraceLevel>

<sap:Logging>Off</sap:Logging>

</sap:Diagnostic>

</SOAP:Header>

- <SOAP:Body>

- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">

- <sap:Payload xlink:type="simple" xlink:href="cid:payload-aa79ee80f49e11dc9f6f001b787aa1c4@sap.com">

<sap:Name>MainDocument</sap:Name>

<sap:Description />

<sap:Type>Application</sap:Type>

</sap:Payload>

</sap:Manifest>

</SOAP:Body>

</SOAP:Envelope>

******************************************************

Also

the below code

MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[EMPLOYEE_TIMEDATA_RECEIVER_RFC_CC_QUA]228a855a83613a828920fc7220b12fc6 is exhausted. The current pool size limit (max connections) is 1 connections.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: c

************************************************************

and also

when i see the adapter monitor - the status shows that "RFC Inactive LED component status is not defined."

We have restarted the XI SYSTEM even then there is no change in status....

What exactly the problem would be.....

Points will be rewarded for any help.... Thanks....