Sender communication channel - Polling delay?

Hi experts,
We have a sender CC with polling every 6 seconds (other parameters are: connect mode permanently, ftp.timeout 180).
Yesterday a file has been placed on source server at 00.18.00, but CC picked it up only at 00.19.18.
Anyone knows possible reasons for this delay in polling?
I have checked message monitoring there are no errors or connection problems, simply the start and end message date are 00.19.18 and 00.19.19.
Other info:
1) This source server is used also for other interfaces, and in that range of time there is no error, other files have been picked without problems.
2) I'm pretty sure that time of source server is the same respect to XI server, I've tested that.
Thanks
Fabio

Hi,
I have also faced this isses but failed to find any solid reason for the same.
Once i found a reason to the problem is that when the other system is trying to write the file they used temporary file names which goes from 0% completion to 100% completion and after 100% completion the exact file name is reflected. And XI only pick up the file with the exact match(after 100% completed). So, the XI system try to hit the file multiple times for picking up for processing while the file was written by other system. On multiple hit to the file with the cc, the cc cache refresh problem occurs.
When the cache get refreshed with some other file processing it immediatly try to hit the file and then the file is picked up.
Also, it sometimes happened that the other system tried to write the file with a previous timestamp, the problem might inbetween other system and xilandscape.
Cheers,
Jay

Similar Messages

2 JMS Sender Communication Channels polling 1 MQ Queue

Hi Experts,
I have a situation where 2 JMS sender communication channels are polling 2 different message type data (via content conversion in JMS) from 1 MQ queue. However adapters are having problem polling the right message from the queue.
Is this something that is not possible?
I know that we can possibly use 2 MQ queues - one for JMS 1 with message type 1 and the other for JMS 2 with message type 2
OR
1 JMS with 1 common message type with 1 MQ queue.
But I want to confirm whether my current situation is suppose to work or not.
Thanks,
Jay

>
Jung Sun Ko wrote:
> Hi Experts,
>
> I have a situation where 2 JMS sender communication channels are polling 2 different message type data (via content conversion in JMS) from 1 MQ queue. However adapters are having problem polling the right message from the queue.
> Is this something that is not possible?
Maintain different queues for different message types.
The adapters else will just pick the message that comes to the queue first based on the polling time irrespective of the message type. It is not intelligent enough
>
> I know that we can possibly use 2 MQ queues - one for JMS 1 with message type 1 and the other for JMS 2 with message type 2
> OR
> 1 JMS with 1 common message type with 1 MQ queue.
>
> But I want to confirm whether my current situation is suppose to work or not.
>
> Thanks,
>
> Jay
Hope the above replies answers your question

JMS (Sender Communication Channel) and MQ in Mainframe (Legacy) System

Hi All,
Can we use JMS Sender Communication Channel in XI that runs on Windows 2003 server to DIRECTLY poll messages from MQ in Mainframe (Legacy) system??
I understand that we can install MQ on XI server and have mainframe push the messages to XI MQ so that JMS can poll but wanted to see if there is a way to do this without having MQ on XI server.
If you know of any documentation regarding this, can you please post it?
Thanks,
Jay

Jung,
Are you looking for this help:
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
Also check this sap help:
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
---Satish

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

FILE SENDER COMMUNICATION CHANNEL DOESN'T GET FILE

Hi,
I have create a new sender communication channel with ftp file configuration. Server parameter and source directory are correct.
I have also checked file and directory permission (chmod 777)
Poll interval is 600 secs.
There is no error in communication channel monitor (returned log: CC is correctly configured and started).
Process started every poll interval, but no file is picked up.
Why?
Carme

Hi,
What type of file are you processing. Check whether the file type is binary or text mode.
Also check whether the file name you have specified in the CC and the exact file in the directory are the same.
Also check the file processing mode, whether it is read only, delete or in test mode.
If the file is in read only mode when the file first processed, then once the file was processed it would be in read only mode, so if you place the new file it should process, so try deleting the existing file in the directory and place a new file with exact file name along with the correct extension and try to process it.
Also I would suggest you check the exact file extension, by unchecking the radio button in the folder option under the menu tools> Folder options> view-->hide extension for file type.
Regards,
Nithiyanandam

XI-Multiple instance scenario -File & SQL sender communication channels

Hi
i have a basic question regarding how file sender communication channel ( where we poll for a particular file pattern either using file/ftp types in a particular subfolder ) or a sql sender communication channel - ( selecting records from a sql source ) would work in a scenario with two active XI instances and j2EE file and sql adapter services running on both of the J2EE servers ?
1. How would the file polling from both J2EE servers - avoid a conflict looking for the same file pattern ? Is there any inbuilt mechanism from SAP to make multiple instances work with the file polling - without a confict ?
2. Simlar question for SQL sender type communication channel ?
If SAP does have a mechanism to handle multiple instance scenarios for file and sql sender adapter based communication channels, is there a link/document on this ?

Hi Karthik,
Please see my comments.
I am just wondering aloud - what will happen if we use a select for update clause in the sql sender adapter communication channel -
Gouri: Yes you can use select + update. In fact that is the right way.
will this ensure that polling from one J2EE instance will lock the selected records so that the second instance does not select the same set of records from the sql server ? Or should we not use a select for update and use a simple select statement ?
Gouri: Yes. SQL DB will ensure that same data will not be picked by another node. As I mentioned earlier use serilizable option from advanced mode.
-Gouri

Files not getting picked up using Sender Communication Channel frm MDM sy

Hi Experts,
XI sender communication channel is configured to pick up any files coming from MDM system from the following path
/XXX/XXX/mdm/mds/XXX/XXX/Material_Master/Outbound/P33/P33_R3_PORT/Ready
Earlier we had the scenario working properly that created idocs in R3 system.(MDM>XI>R3)
Currently i tried to test the scenario again but i don't see an entry in the sxmb_moni or tried checking whether the sender communication channel is working properly it showed polling correctly in RWB.The files are already sitting in the the above path.XI should be picking it up but don't know what the problem is?
I also tried a test in RWB>Integration Engine>Test Message put the payload and it was able to create idocs in R3.So i concluded there is an error in picking up message from MDM.
Is there any log available for the commmunication channel where i can see error info of whether any files picked up or not.
Please suggest me what all can be done to to ensure the CC is picking up the files.
Earlier responses highly appreciated.
B'Rgds,
Sudhansu

Hi,
In addition to the RWB channel check suggested by Aamir, you should also check if the channel is
1) Active in ID
2) Channel is not locked in VA, if it is locked then your status in RWB will show processing started but the files wont be picked up...for more details check the unlocking procedure mentioned in this thread:
JDBC Sender Adapter - NOT FETCHING RECORDS -PROCESSING STARTED
The unlocking procedure is the same for FILE and JDBC....
Regards,
Abhishek.

Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

Hello All,
One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
Is the (IDoc) Communication Channel from Sending system to XI required to configured?
Many thanks in advanced!
Jochen

Hi Jochen,
for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
Thanks,
Rajeev Gupta

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

File Structure - Sender Communication Channel

Hi All,
My Sender flat file structure is below like this
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
I did the Sender Communication Channel configuration - Content Conversion
Document Name : XXX
Document NameSpace: XXXX
Recordset Structure: MT_Test,*
Recordset Sequence: Ascending
Key field Type: String Case-Sensitvie
MT_Test.fieldNames: Filed1,Field2,Field3,Field4,Field5,Field6
MT_Test.fieldSeparator: '|'
MT_Test.additionalLastFileds: ignore
MT_Test.endSeparator : 'nl'
ignoreRecordsetName: true.
But its pick the file, In SXMB_Moni show Currect...
But in Runtime workbench, in Communication Channel moni, it show below like this,
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_Test xmlns:ns0="http://XXXXX">
<JOBS />
</ns0:MT_Test>
What is the Issue, where i missed some thing, In message mapping, its correct..
Thanks.
SR

SR,
I am still little confused with your below statement.
But its pick the file, In SXMB_Moni show Currect...
But in Runtime workbench, in Communication Channel moni, it show below like this,
>
> <?xml version="1.0" encoding="UTF-8" ?>
> - <ns0:MT_Test xmlns:ns0="http://XXXXX">
> <JOBS />
> </ns0:MT_Test>
You mean to say that in MONI, the mapping output is fine, but when you check the output at RWB -> CC Monitoring for the Sender Channel, then you get the above mentioned XML?
This means that there is nothing wrong with your source CC settings. If the entry in RWB -> Sender CC is wrong, your MONI entry will never be right. So, this is really weird.
What is the source structure that you have defined in DT?
Regards,
Neetesh
Edited by: Neetesh Raj on Sep 29, 2009 2:31 PM

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

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

JMS sender communication channel content conversion

Hi,
I struck with the content conversion in the JMS Sender communication channel.
I have configured the communication channel with the filed fixed lengths. (Simple type)
The field fixed lengths i have given are 10,2,3,11
The contents in the file 1000000072 230 111
but, in the input xml after conversion iam getting 100000007 in the first field and 2 in the second field 23 in the third field.
I have configured the sender communication channel as in the document in SDN.
Even, i configured several communication channels. I didn't get this strange error any time.
I have gone through SDN to fix this issue, but i didn't get solution.
If anyone got rectified this kind of error, please answer your solution to me
Thanking you,
Regards,
Krishnaraju.

Hi,
Thanks for all your support. The issue got resolved.
The issue is due to the file, In the file the special characters are appearing. We are not able to see these characters in the notepad, wordpad, text editor.
But, these characters are appearing in th syn text editor. So, we removed those characters and processessed the file. Now, it is successfull.
Regards,
Krishnaraju.

JDBC Sender Communication Channel Problem

Hello everybody,
I have a sender communication channel, it is with green Functioning status in channel monitor in runtime workbench, and the log says "Process started" for every pool as configured, but it doesn't return any data to XI, and there's data to be taken, the problem started a few hours cause it was working fine, I've already executed a Complete refresh cache in SXI_CACHE, and changed the channel from Active to Inactive in ID, and Stopped and Started it again in RW, it doesn't give any errors, but it doesn't bring back any data that should be, any suggestions or maybe any information on how to refresh totally those channels????, thanks in advance.
Regard's
Paul

Hi Paul
Check for JDBC adapter locks. cpa cache locks are not relevant to your problem.
Moreover check with the visual admin logs as well. if you can get info about the issue you have
Thanks
Gaurav

Sender communication channel - Polling delay?

Similar Messages

Maybe you are looking for