Error in Mail Sender communicational channel

Hello!
We have an XI scenario, which should take emails from the mail server and transfer them to SAP. For this purpose the configuration channel has been configured with the following params:
Transport protocol: IMAP:
Message protocol: XIPAYLOAD
Configure user authentification: checked.
This channel stopped working about two weeks ago after a kernal patch (notes 1436917, 1441654, 1424397 and 1443925). The error is the following:
exception caught during processing mail message [44]java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
Application log gives only this information:
1.5 #16F1003D6202007C00003680001470F4000484907936C6A6#1271655950632#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK##com.sap.aii.messaging.srt.xmb.XMBIMAPInitiatorServiceImpl.invoke()#J2EE_GUEST#0##bxp45ci_BXP_505494050##91fa4cf04b6e11dfae4616f1003d6202#XI Mail[Mail_Sender_MailFIBeleg/S36_SECURITAS/]_800280##0#0#Error#1#com.sap.aii.messaging.srt.xmb.XMBIMAPInitiatorServiceImpl#Plain###exception caught during processing mail message; java.io.IOException: unexpected list response;
I don't have an access to the Adminiatraion Viewr by now and can't activate any other traces. What is the most interesting - the error is occured only for definite sender, if the email is sent from another address, the processing works without errors.
Do you have any suppositions why could it be so and where should we search the reason of problem?
Your help will be very appreciated.

Dear Bond,
Please follow the below useful doc:
http://wiki.sdn.sap.com/wiki/display/XI/CombiningthreedifferentaspectsofPIinoneshot
http://wiki.sdn.sap.com/wiki/display/XI/StepbyStepMailToFileScenario
Thanks,
Satya Kumar

Similar Messages

Mail to File Integration(Mail Sender Communication channel status RED)

Hi all,
I am doing Email to File Integration Scenario, XI is reading mails from an particular exchange server mail id & putting it in to a file. now all IR & ID configuration is done.
But in RuntimeW Bench -> Adapter Monitreing The Sender Mail Communication Channel is RED with error occured: exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 00KC NO The requested item could not be found

We check the Exchange Server login Acess through TELNET ,as suggested from SAP Service marketplace
and login is successfull, with details available of Inbox
but in TENET when we try to execute the IMAP Status command error message comes
" expected space not found" .
Since XI is not able to read the inbox mail, so Sxmb_moni is blank.....
can any body suggest that this issus is related to that IMAP Status..........or some thing else..
our URL is correct.
Regards,
Ashutosh

the URL path was wrong...
it should end with .......exchange/Inbox/
the sender channel was having error RED ,but it was showing green status intially because delay update .....
Regards
Ashutosh

Mail Sender Communication channel not polling

Dear all,
In our PI 7.1 Sever, we have observed a issue.
Sender mail communication channel status is green in RWB-->Channel monitoring but the channel does not pick up any mails form the mailbox.
After we stop and then start the channel, it is picking up the mails.
Any pointers on the root casue for this issue and any resolution steps or any SAP Notes to implement will be of great help.
Regards,
Younus

Hi,
Is it like everytime you have to restart the mail channel again and again?
Sometimes it happens, a quick restart will refresh the adapter cache and the messages are processed.
So, its not a problem.
Regards,
Sushama

Error in SOAP Sender Communication Channel

Hello Gurus,
I am trying for a SOAP (Axis) -> PI -> IDOC scenario and getting an error while sending message to SOAP Channel.
Message structure used
<?xml version="1.0" encoding="UTF-8"?>
<MaterialData>
<field1>value</field1>
more fields
</MaterialData>
Basically a XML message.
I am getting below error message for Axis (channel monitoring):
MP: exception caught with cause org.xml.sax.SAXException: Bad envelope tag: MaterialData
Can you please let me know what should be the message format when testing Axis? I do not intend to use any SOAP envelope.
I have already referred: Re: SAP PI 7.0 Receiver SOAP Axis (Bad envelope tag: html)
Please help.
Thank you!

Hello,
Can you please let me know what should be the message format when testing Axis? I do not intend to use any SOAP envelope.
Correct me if I'm wrong, but I think you will only be able to plain message to the Axis sender when using REST. See SAP Note 1039369 FAQ XI Axis Adapter, under Sender Adapter General Question 35.
35. Can I post a plain no-soap request (REST) to the sender adapter servlet?
Yes. You need to include a query parameter rest in the request URL, as http://host:port/XIAxisAdapter/MessageServlet?...&rest. For the availability of this feature, refer to Note 1448849.
All the other messages require a SOAP Envelope.
Hope this helps,
Mark

Restrict E-mail sender in the Mail sender communication channel.

Hi All,
 My scenerio customers want to Email with attachment to PI server. I've successfull tested this scenerio without one open issue. Right now anyone having email id can send mail to PI server.
I want to restrict the senders list. Is this possible in the sender Mail adapter configuration.
Thanks,

Hi,
Its possible.
You need to configure 2 receiver
1)MailA
2)MAILB
in receiver determination.
then you need to route it based on Subject using condition in receiver determination.
Use the below XSD to create your sender mail message type
<?xml version="1.0" encoding="utf-8" ?>

<xs:schema targetNamespace="http://sap.com/xi/XI/Mail/30"
xmlns:xi="http://sap.com/xi/XI/Mail/30"
xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xs:element name="Mail">
 <xs:annotation>
 <xs:documentation>Mail package for XI - Mail Adapter</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Subject" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="From" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="To" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="Reply_To" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="Content_Type" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="Date" type="xs:dateTime" minOccurs="0"></xs:element>
 <xs:element name="Message_ID" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="X_Mailer" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="Content" minOccurs="0">
 <xs:annotation>
 <xs:documentation>any type</xs:documentation>
 </xs:annotation>
 </xs:element>
 </xs:sequence>
 <xs:attribute name="encoding" type="xs:string"></xs:attribute>
 </xs:complexType>
</xs:element>
<xs:element name="MailReceipt">
 <xs:annotation>
 <xs:documentation>Mail Receipt for XI - Mail Adaper</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Server" type="xs:string"></xs:element>
 <xs:element name="Format" type="xs:string"></xs:element>
 <xs:element name="UseMailPackage" type="xs:boolean"></xs:element>
 <xs:element name="Encoding" type="xs:string"></xs:element>
 <xs:element name="Subject" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="From" type="xs:dateTime" minOccurs="0"></xs:element>
 <xs:element name="To" type="xs:string" minOccurs="0"></xs:element>
 <xs:element name="Date" type="xs:dateTime" minOccurs="0"></xs:element>
 </xs:sequence>
 </xs:complexType>
</xs:element>
</xs:schema>
and use mail package in sender mail adapter.
Then your mail will come in XI in the above format.
then based on subject field you can conditionaly determine the receiver.
Message Protocol
u25CF XIALL
In this mode, the content of the RF C822 e-mail matches the content of the XI message. The XI message is a multipart MIME message with a SOAP envelope as its first part. See also: Messages, under XI Message Protocol.
u25CF XIPAYLOAD
In this mode, the content of the e-mail is put in the payload of the XI message. If you do not set the Use Mail Package indicator, the information about the sender (From), receiver (To), and subject of the e-mail is lost.
http://help.sap.com/saphelp_nw70/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm

Error in AS2 sender communication channel

Hello,
We have a scenario where we are receving IDoc XML from our partner via AS2.
While doing so,we are receiving following error:
Error while parsing AS2 message: AUTHENTICATION_ERROR #
When we try to send a normal text file,it works,so this cannot be a certificate related issue.
XML header looks like:
<?xml version="1.0" encoding="windows-1250"?>
<ORDERS05 xmlns:abc="http://abc.xy.net/">
Kindly help.
Thanks.
Best Regards,
Shweta

Hello,
When I sent the same file from our dev to test system via AS2 ,the content type was application/octet-stream and the file was received successfully.
But when our partner sends it via AS2,content type is application/xml and we get the error I mentioned before.
Does content type has something to do with this problem?
Kindly help.
Thanks a lot.
Regards,
Shweta

XIProxy:PARSE_APPLICATION_DATA , error in soap sender communication channel

HI
I am having soap toABAP proxy synchronous interface , when i test from soap UI tool i am getting the below errro . can any body help me with this error
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
 at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1178)
regards
sandeep
Edited by: pendyalas on Jul 27, 2011 5:01 PM

Hello,
can you check the message format defined in repository.
Regards
Vivek

Sender Communication Channel Error

Hi all,
iam working on JDBC scenario.For this iam using party and business service.
iam getting following error at jdbc sender communication channel.
Error occurred while sending message: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.
Erlier it worked fine.But now iam getting this problem.
We are having some other channels which r working fine.
any ideas......?
Thanks,
Sreedhar Goud.

1. If you know the user, who having admin rights;
1.Open the VA tool; ex: C:\usr\sap\X67\JC01\j2ee\admin --> click on "go.bat"
2. Click on "New" button ( this is on Logon Dialog box)
3. Enter "Display name"; and select "Direct Connection To a Dispatcher Node".
4. Say "Next"
5. Enter "User Name","Host" and "Port" and Save the data.
6. Select User and click on "Connect"
2. Did you forget the J2EE_ADMIN password? Just follow below steps:
Just follow below steps:
1.Start the Config Tool C:\usr\sap\<SID>\<engine-instance>\j2ee\configtool\configtool.bat
Ex: D:\usr\sap\F02\JC00\j2ee\configtool --> configtool.bat
2. "Switch to configuration mode" for that Click on "Pencil" icon;
3. Click on "Pencil" icon means "Swith to Configuration Edit mode" then say "YES"
4. cluster_data --> server --> cfg --> services -->
click on "Propertysheet com.sap.security.core.ume.service
select properties:
ume.superadmin.activated = True
ume.superadmin.password = <enter password >
then say "OK"
Click on "Pencial ICON.
5. Save & restart Java Engine.
Login with "Administrator"
1. http://<host>:<Port>/useradmin/index.jsp
2. Enter userid / Password as "Administrator / <password>
3. it will ask change password just change it.
Please follow steps one by one. it should resolve your issue.

Error in Recever Mail Adapter (Communication Channel)

Hello Experts,
I am getting below error in recever Adapter Communication Channel. I have given SMTP, XIALL,PLAIN parameters, i have given proper: SMTP://compnay.com & correct user id and password, i browse throug all most all related links.
Exception caught by adapter framework: java.io.IOException: server does not support PLAIN or LOGIN authentication
Mail: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: server does not support PLAIN or LOGIN authentication
Delivery of the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: server does not support PLAIN or LOGIN authentication.
Thanks,
Siva

HI Siva
Are you trying to send Email from any file send by system or Read by PI and send as Email.
Please describe your Scenario.
If your email is generated from the content provided by Integraton engine use Message protocol XI PAYLOAD instead of XIALL.
Using Authentication you change from Plain to CRAM-MD5. then it might not give any error
Your URL should be SMTP://mailhost.company.com
For reference check Help URL
http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/frameset.htm
Thanks
Gaurav Bhargava

BIC Module Error in Sender Communication channel for EDI to File scenario.

Hi Experts,
We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
Thanks & Regards,
Abhishek

Hi Abhishek,
Is there any special character present in the EDI file?
the parser is not able to parse the data.
you can check the BIC conversion log for more information.
Regards,
Harish

Error in sender communication channel

Hi,
I am doing File to RFC scenario in which i am using Standard bapi to get the cost from the sap system
while sending the data in sender communication channel the processing mode is in delete mode but it is not deleting and throwing the error
Error: com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
this error is from sender communciation channel..
can any one give some inputs for this...
regards,
Kishore

K.P.N.,
i have checked it getting the same error. in moni also administrative cache clear error is coming
do we need to do any workaround...
regards
Kishore

Sender Communication Channel Monitoring Error

Hi....Experts,
i am doing rfc-soap scenario synchronous . this is B2B scenario, under party i created business services, under this created 2 communication channels. in RWB, Communication Channel monitoring i am getting this error at sender side..
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: only partyless services are supported but party : xxxxx is set for service sender business service name and sender CC name..
pls suggest me how can i rectify these errors..
for helpful answers i will give points*********
regards,
Pasi.
Edited by: pasi s on May 5, 2008 8:35 AM
Edited by: pasi s on May 5, 2008 8:40 AM

Hi Pasi,
Check if you are using the same business service (under which u have created the Channels) at sender side in configuration.
You have to use the same business serivce for sender under which your communication channels are created...................
Or
Create a sender communication channel in the service that u have used at sender side.............
So i think in your case there is a mismatch of using the diff sender service at diff stages.............
Hope this will solve your problem
Thanks
Sai
PS: kindly reward points if helpful

Sender communication channel stopped after error "Connection Timed Out"

Hi experts,
in our scenario we have an asyncronous sender communication channel with polling every 6 seconds to an external FTP server.
Yesterday evening a "Connection Timed Out" error came.
After this error the polling stopped but channel in communication channel monitoring still remains green.
So status green but no polling.
To solve this problem we stopped and then restarted channel from CC monitoring.
The channel is configured "manually".
The question is: Is it possible to avoid this problem? Maybe there's a parameter in configuration to set?
After a time out error the channel must go on polling, it should not stop. Or it must shows red status.
Thanks
Fabio Boni

HI,
I think PI level is "SAP J2EE Engine 7.00 PatchLevel 109886.44"
Thanks
Fabio

Adapter Module not working in Sender Communication Channel working in recie

Hi
I have written one adapter module. IF i give that Adapter Module in Sender Communication channel its not working. If i give that in Reciever Communication Channel its working. If i mention in both the channels then its working in sender communication channel also.But in only sender communication channel its not working in only reciever communication channel its working Can any one tell me why its happening
Thanks & Regards
Ravi Shankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B

hi
if its problem with my code why its working if i give the adapter module in both the communication channels?If i give in only sender communication channel the module is not invoking. its not showing any auditlogs.Can any one please help me
OUTBOUND is for sender
INBOUND is for reciever right.?
the following code i have written
public ModuleData process(
          ModuleContext moduleContext,
          ModuleData inputModuleData)
          throws ModuleException {
          String SIGNATURE =
               "process(ModuleContext moduleContext, ModuleData inputModuleData)";
          Object obj = null;
          Message msg = null;
          String filename = null;
          AuditMessageKey amk = null;
          try {
               obj = inputModuleData.getPrincipalData();
               msg = (Message) obj;
               System.out.println("&&&&&&&&&&&&&&&&&" + msg);
               if (msg.getMessageDirection().equals(MessageDirection.OUTBOUND)){
                    amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.OUTBOUND);
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> etHostName: Module called"+ i++);
               }else{
                    File filename1 = new File("
10.7.1.43
XI
source","text.txt");
                    filename1.createNewFile();
                    amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> etHostName: Module called"+ i++);
               System.out.println("**************" + amk + "***********");
          } catch (Exception e) {
               Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> GetHostName: Error Module called");
               e.printStackTrace(System.err);
               ModuleException me = new ModuleException(e);
               throw me;
          // Read the channel ID, channel and the module configuration
          try {
               Hashtable mp = (Hashtable)inputModuleData.getSupplementalData("module.parameters");
               if(mp != null){
                    filename = (String)mp.get("FileName");
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,"Host >>> Element Name is set to {0}"+filename );
               }else{
                    Audit.addAuditLogEntry(amk,AuditLogStatus.WARNING,"HostElementName parameter is not set. Default used: HostName.");
                    filename = "FileName";
          } catch (Exception e) {
               e.printStackTrace(System.err);
               Audit.addAuditLogEntry(amk,AuditLogStatus.ERROR,"Cannot read the module context and configuration data");
               ModuleException me = new ModuleException(e);
               throw me;
          try {
               XMLPayload xmlpayload = msg.getDocument();
               DocumentBuilderFactory factory;
               factory = DocumentBuilderFactory.newInstance();
               DocumentBuilder builder = factory.newDocumentBuilder();
               Document document =
                    builder.parse((InputStream) xmlpayload.getInputStream());
               Element rootNode = document.getDocumentElement();
               if (rootNode != null) {
                    Element childElement = document.createElement("filename");
                    childElement.appendChild(document.createTextNode(filename));
                    rootNode.appendChild(childElement);
               // Transforming the DOM object to Stream object.
               TransformerFactory tfactory = TransformerFactory.newInstance();
               Transformer transformer = tfactory.newTransformer();
               Source src = new DOMSource(document);
               ByteArrayOutputStream myBytes = new ByteArrayOutputStream();
               Result dest = new StreamResult(myBytes);
               transformer.transform(src, dest);
               byte[] docContent = myBytes.toByteArray();
               if (docContent != null) {
                    xmlpayload.setContent(docContent);
                    inputModuleData.setPrincipalData(msg);
          } catch (Exception e) {
               e.printStackTrace(System.err);
               Audit.addAuditLogEntry(amk,AuditLogStatus.ERROR,"Cannot read the module context and configuration data");
               ModuleException me = new ModuleException(e);
               throw me;
          return inputModuleData;
Best Regards
Ravi Shankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B

JMS Sender Communication Channel problem

Hi XI gurus!!
I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
In defaultTrace.XX.trc I see the following information and errors:
#1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
#1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
{GenericConnectionProfileImpl
{Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
JmsMessageSelector=,
ConnectionFactoryConstructor=null,
ConnectionFactoryFactoryInvocation=null,
ConnectionFactoryInvocations=[],
DestinationConstructor=
{ConstructorInvocation
{className=null,
invokeParams=[]
DestinationInvocations=[],
MessageInvocations=[],
DestinationName=null,
User=,
Password=,
isJmsSessionTransacted=true,
InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
LookupConnectionFactory=QueueConnectionFactory,
LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
SerializedConnectionFactoryPath=null,
SerializedDestinationPath=null,
Flags=0000000000000000000000000000000000000000000000000000100000000010
#1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
#1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
#1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
Thanks

HI,
As per the trace details given please consider few of the below options....
What do u see in adapter monitoring tool for JMS adapter?
http://hostname:5XX00/mdt/amtServlet
Did you follow the document on correlation of JMS messages?
In communication channel You have to set
Correlation ID -> XI conversationID
XI message ID->GUID
XI Conversation ID -> JMS correlation ID.
Now in the custom J2EE application you should set
jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
This thread deals with the issue..
JMS Queue monitoring
Check if the JMS Sender adapter EOIO is with serialized messages
Thanks
Swarup

Error in Mail Sender communicational channel

Similar Messages

Maybe you are looking for