cancel
Showing results for 
Search instead for 
Did you mean: 

xi 3.0: Mail adapter fails with "exception in method process"

Former Member
0 Kudos

Hi.

I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.

Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".

I tried both async and sync case with the same result. In the sync case, the response contains:


<!--  Call Adapter   --> 
<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: Exception in method process.</SAP:AdditionalText> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack /> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

Any idea???

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

sorry i attached a wrong stuff...

i attach know th detail log for the SYNC case, later i can do a check with ASYNC


Time Stamp Status Description 
2005-06-12 23:40:32 Success The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI 
2005-06-12 23:40:32 Success Using connection AFW. Trying to put the message into the receive queue. 
2005-06-12 23:40:32 Success The message was successfully retrieved from the receive queue. 
2005-06-12 23:40:32 Success The message status set to DLNG. 
2005-06-12 23:40:32 Success Delivering to channel: MAIL_RECV 
2005-06-12 23:40:32 Success Mail: message entering the adapter 
2005-06-12 23:40:33 Success Mail: response message received 9a9de870-db8a-11d9-bbc5-000c29cef774 
2005-06-12 23:40:33 Success Mail: sending a delivery ack ... 
2005-06-12 23:40:33 Success Mail: sent a delivery ack 
2005-06-12 23:40:33 Error Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback. 
2005-06-12 23:40:33 Error Delivery of the message to the application using connection AFW failed, due to: Exception thrown in method process. The transaction is marked for rollback.. 
2005-06-12 23:40:33 Success The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 23:45:33 CEST 2005. 
2005-06-12 23:40:33 Success The message status set to WAIT. 
2005-06-12 23:45:33 Success The message was successfully retrieved from the receive queue. 
2005-06-12 23:45:33 Success The message status set to DLNG. 
2005-06-12 23:45:33 Success Delivering to channel: MAIL_RECV 
2005-06-12 23:45:33 Success Mail: message entering the adapter 
2005-06-12 23:45:33 Success Mail: response message received 4d9b9800-db8b-11d9-a5cf-000c29cef774 
2005-06-12 23:45:33 Success Mail: sending a delivery ack ... 
2005-06-12 23:45:33 Success Mail: sent a delivery ack 
2005-06-12 23:45:33 Error Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback. 
2005-06-12 23:45:33 Error Delivery of the message to the application using connection AFW failed, due to: Exception thrown in method process. The transaction is marked for rollback.. 
2005-06-12 23:45:33 Success The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 23:50:33 CEST 2005. 
2005-06-12 23:45:33 Success The message status set to WAIT. 
2005-06-12 23:54:31 Success The message was successfully retrieved from the receive queue. 
2005-06-12 23:54:34 Success The message status set to DLNG. 
2005-06-12 23:54:34 Success Delivering to channel: MAIL_RECV 
2005-06-12 23:54:34 Success Mail: message entering the adapter 
2005-06-12 23:54:34 Success Mail: response message received 903a3b20-db8c-11d9-b572-000c29cef774 
2005-06-12 23:54:34 Success Mail: sending a delivery ack ... 
2005-06-12 23:54:34 Success Mail: sent a delivery ack 
2005-06-12 23:54:34 Error Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback. 
2005-06-12 23:54:34 Error Delivery of the message to the application using connection AFW failed, due to: Exception thrown in method process. The transaction is marked for rollback.. 
2005-06-12 23:54:34 Success The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 23:59:34 CEST 2005. 
2005-06-12 23:54:34 Success The message status set to WAIT. 
2005-06-12 23:59:35 Success The message was successfully retrieved from the receive queue. 
2005-06-12 23:59:35 Success The message status set to DLNG. 
2005-06-12 23:59:35 Success Delivering to channel: MAIL_RECV 
2005-06-12 23:59:35 Success Mail: message entering the adapter 
2005-06-12 23:59:35 Success Mail: response message received 439748c0-db8d-11d9-ce01-000c29cef774 
2005-06-12 23:59:35 Success Mail: sending a delivery ack ... 
2005-06-12 23:59:35 Success Mail: sent a delivery ack 
2005-06-12 23:59:35 Error Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback. 
2005-06-12 23:59:35 Error Delivery of the message to the application using connection AFW failed, due to: Exception thrown in method process. The transaction is marked for rollback.. 
2005-06-12 23:59:35 Error The message status set to NDLV.

MichalKrawczyk
Active Contributor
0 Kudos

Don't know what might be the cause but

just to check:

1.go to SLD

2. Business System: XI (your XI)

3. is the Pipeline URL value like:

http://CAPELAB010:httpport/sap/xi/engine?type=entry

?

you can check the HTTP port -> TCODE SMICM (goto ->services)

check it just to make sure

Regards,

michal

MichalKrawczyk
Active Contributor
0 Kudos

Hi Alessandro,

what do you mean sync?

sync mail ?

mail should be asyn I guess

try the async and give us the error from sxmb_moni

and also the error from http://server:port/mdt/amtServlet

and then choose your mail adapter to see if there an error over there too

>> the fantastic-as-always weblog

thx:))

Regards,

michal

Former Member
0 Kudos

Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.

Anyway, in my server i get a 404 for the link you suggested.

In the async case i don't get any error on the SXMB_MONI but only on the A.F.

I attach the audit log for the async case:

Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc 
 
Time Stamp Status Thread ID Sequence No. Description 
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI 
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue. 
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue. 
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG. 
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV 
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter 
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint 
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint. 
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005. 
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT. 
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue. 
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG. 
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV 
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter 
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint  
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint . 
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005. 
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT. 
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue. 
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG. 
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV 
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter 
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint  
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint . 
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005. 
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT. 
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue. 
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG. 
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV 
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter 
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint  
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint . 
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV. 
       Total: 33 Entries   1020304050 messages displayed per page; this is page 1 of  1 page(s)