Duplicate Message exception in sender JMS comm channel

Hi,
Can any one please tell me what is stored in MSG_ID1 and MSG_ID2 in table XI_AF_SVC_ID_MAP
I could only find the schema of XI_AF_SVC_ID_MAP table in SDN which is as follows,
MSG_ID1 (varchar),
MSG_ID2 (varchar),
PERSIST_UNTIL (timestamp).
We have an interface in where MQ daily sends 2 files to PI but sometimes one msg is getting discarded by sender JMS adapter giving warning -
A duplicate message was received, it was received earlier and processed with XI Message ID - "xyz". It will be ignored and discarded from the JMS queue.
Also I found that setting option Time Period for Duplicate Check for EO(IO) (secs) to 0 does not always work.
We are getting this problem after upgrading PI from 3.0 to 7.1.
So if any one has solution to this problem please help me.
Thanks & Regards,
Shweta

Hi Shweta
Usually this kind of issue happens when the msg ID in the MQ message header is not unique.
Ask the MQ team to ensure that MQ msg ID is always unique.
Regards,
Giuseppe

Similar Messages

How to set errorDelay parameter in sender JMS Communication Channel?

Dear XI/PI Experts,
Do you happen to have a documentation on how to implement the errorDelay parameter and other general parameters in the sender Sender JMS communication Channel? Do you happen to have a step by step guide or pdf that I can use?
I look forward to hearing from you.
Thanks a lot in advance.
Kind regards,
Grace

Hi Thanks for your replies.
What I need to do is to implement this bullet point:
¡ errorDelay
The default value for this parameter is 0.
This parameter determines how long the system waits before processing further messages if an error occurs. In transactional processing, it can make sense to specify a certain time period, for example, because messages with errors remain in the queue following a ROLLBACK.
In which part of the Sender JMS Comm Channel will I implement this?
Should I put this under tab /Parameters/Processing/Error Handling Settings or should this be under /Parameters/Advanced/Additional Paremeters?

Duplicate MessageID error in sender JMS

Hi,
could anyone provide some inputs in getting through the following error in sender JMS:
A duplicate JMS message was received. It was was received earlier and processed with the XI message ID 3fc663bf-c3ee-4eb8-179e-ad28e0ecde3a. It will be ignored and discarded from the JMS queue.
I have tried changing follwoign settings but still no use...
Under the PROCESSING tab, under XI SETTINGS
Time period for Duplicate Check for EO(IO) (secs) it was set to 86400
I have changed this to 300 seconds
Regards,
Chinna.

remove the duplicate entry from the java table XI_AF_SVC_ID_MAP

Sender file comm channel shows error status when no file is in source

Hello,
I have this sender file communication channel which is picking up files using ftp. Its working fine but if there is no file in the source directory during polling, it shows an error status in communication channel monitor. The error message is that directory/file does not exist and also * in file name is invalid character.
I have the same settings on our dev, QA and prod system but this strange thing is happening only on the dev and prod. Its not happening on QA whereas QA access the same directory as dev.
Any idea ???

Hi,
The error is strange one.
I suggest you to check Visual Admin to findout the exact trace/log file.
May be because of some connection problems etc..
Just go thru this SAP Note about File Adapter- 821267
Regards,
Moorthy

Sender File Comm Channel Fails after system refresh

Hi,
we did a system refresh of our PI system and since then the sender file communication channels donot work with the following exception:
Error: com.sap.aii.af.ra.ms.api.ConfigException: Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available.
I have seen many threads in this forum related to this issue but couldn't find a proper solution.
Any help is very much appreciated.
Thanks
MLS

You may do the following:
1. Perform SLDCHECK on XI.
2. Check if XIAFUSER is not locked or its password has been changed recently.
3. Goto SLD-> Business sytems-> Integration server, check Pipeline URL. It should be
http://hostname:8000/sap/xi/engine?type=entry
Regards,
Prateek

Sender File Comm Channel

Hi,
I have a unique problem. My file sender communication channel picks and process files only when the filename extension ends in .txt.
I had checked the configuration directory and made sure it is not *.txt type and had given star.star.
Still am not sure why this is happening.
When i dump a normal file without any .txt extension, it is not been picked up and the file remains in the same place, morever no errors are also coming.
Please share any light on this.
Regards,
Anandh
Edited by: Anandha Krishnan on Jun 9, 2008 6:37 PM

The other way to check if your changes are being correctly in the RWB, please deactivate the comm channel and then lookup RWB communication channel monitoring. check if the correct version is showing up out there. It could be the RWB is not getting the correct upated version. Activate the comm channel again and re-start the comm channel and then check.
You can also follow the path of using * in the filename instead of . as suggested by others.
Regards,
Indranil
Award points if appropriate

Sender RFC comm channel - program ID

Hi all,
Short question:
I have RFC to FTP scenario.
Sender RFC channel needs a program ID.
I created a TCP/IP RFC Destination in source SAP system and specified in there the program ID i will use. However, when i try to test this connection, it throws folllowing error:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program SAD_TO_DXI not registered
Error Details LOCATION: SAP-Gateway on host xxxxxx / sapgw05
Error Details DETAIL: TP SAD_TO_DXI not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 6852
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Wed Sep 26 17:21:55 2007
Error Details VERSION: 2
Could you please tell me how can i solve this?? and confirm this is the parameter i have to specify in the Sender CC??
Thanks in advance and kind regards,
David

hi David,
I guess the connection between R/3 and XI is not proper......
Connection between XI and R/3
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Also check the program ID
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Also check discussion
Re: Why Program ID
regards
biplab
Use a Good Subject Line, One Question Per Posting - Award Points

UNIX Script Not running - Sender File Comm Channel

I have written a script to split a large file into smaller files . It works great when I log into the server via putty, and run it from the command prompt .
However, when I run it from the Sender File Channel "Run OS command before/after processing", nothing happens . I put in some code to write a log file after every line , but it never gets generated if I run the channel , so im assuming its never called by PI .
However, the channel monitoring says "Success" for "Execute OS command "/home/Int001/Inbound/File_Split.sh" . So if it is successfully called, how come i dont get my expected results?
1. What is the credentials used by PI to run scripts ?
2. Does PI need some special permissions to run the script ?

Hi Johannd,
To change Password for Sap System User, you can follow this help:
http://help.sap.com/saphelp_nwmobile71/helpdata/en/aa/1dc94af0fa11d3a6510000e835363f/content.htm

SELECT query in a sender jdbc comm channel

Hi experts,
I would like to access a table in a database and select some rows from there but from a specific date onwards. I mean, i want to retrieve only the rows from, lets say, table.date = 2008-04-05 on.
So i specified somthing like:
*SELECT * FROM table WHERE date >= to_date(2008-04-05) and status ='0'*
UPDATE table SET status='1' WHERE date >= to_date(2008-04-05) and status ='0'
BUT this is throwing following error message:
The JDBC driver returned the following error message: 'java.sql.SQLException: ORA-00911: invalid character '. For details, contact your database server vendor.
Could you please provide some support in order to achieve this?
Thanks in advance and best regards,
David

Hi there,
I tried again without using the 'to_date' function but still doesnt work.
I have no access to the database so i asked the DB team to make some testing there. They say the date format in the DB is 'dd-mm-YYYY' but XI receives 'YYYY-mm-dd' via jdbc adapter!!!!
So, at first i typed 'YYYY-mm-dd' in the query and this was the result:
Database-level error reported by JDBC driver while executing statement 'SELECT * FROM albaranes,lineas WHERE albaranes.albaran = lineas.albaran and albaranes.fecha_albaran >= 2004-06-19 and albaranes.sap_status ='3''. The JDBC driver returned the following error message: 'java.sql.SQLException: ORA-00911: invalid character '. For details, contact your database server vendor.
and shortly afterwards i used 'dd-mm-YYYY' and this is what i got:
Database-level error reported by JDBC driver while executing statement 'SELECT * FROM albaranes,lineas WHERE albaranes.albaran = lineas.albaran and albaranes.fecha_albaran >= '19-06-2004' and albaranes.sap_status ='3''. The JDBC driver returned the following error message: 'java.sql.SQLException: ORA-01843: not a valid month '. For details, contact your database server vendor.
sap_status field is of string type so this is not the point, i think.
Could you please advice?
Best regards,
David
Edited by: Domingo Jimenez Navarrete on May 5, 2008 12:18 PM

Inactive Sender WS Comm Channels PI 7.1

Hello everybody,
can anyone tell me if there's a way to set to inactive de WS communication channels in PI 7.1, specificly Senders????, I don't want to mess with the URL's and stuff, only need a temporal inactive status, thanks in advance.
Regards,
Julio Cesar

hi
in runtime worbench go to> Component Monitoring(first tab)>select All and play Display>select Adapter Engine>press Communication Channel Monitoring-->leave all the field black and press use filter buttom.
thats all
Hope Helps

Erro in JMS receiver Comm Channel

Hi,
I am working on a scenario File(Sender) JMS (Receiver).The input is a text file The file sender polls this input file and the file sender CC does the content conversion and puts the XML message into the JMS Queue. But in the receiver JMS comm channel i get the error saying
Error sending message in sending to destination ABCF, the message message: TextMessage[null, <?xml version="1.0" encoding="...]: weblogic.jms.common.JMSException: Error sending mess
Please help me on this

Hi,
Please have a look at your message in SXMB_MONI and see if the payload is correct.
Also have a look at the MDT (http://<server>:<port>/MDT) and see what errors occur for your message.
Regards,
Yaghya

XAException during sending JMS message

I'am having following exception during sending JMS message using JMSService to remote OC4J queue:
04/09/15 16:35:02 XAException in errorRollback rollback(c0:a7:9:14:cd:2d:0:0:2a:
0:0:0:0:0:0:0:0:2b:0:ff:2:84:8c:1):
04/09/15 16:35:02 XAException in errorRollback null
04/09/15 16:35:02 XAException in errorRollback rollback(c0:a7:9:14:cd:2d:0:0:2a:
0:0:0:0:0:0:0:0:2b:0:ff:2:84:8c:1):
04/09/15 16:35:02 XAException in errorRollback null
<2004-09-15 16:35:02,717> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseSc
heduledWorker::process> Failed to handle dispatch message ... exception Message
handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.
engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transac
tion was rolled back: TwoPhase Commit failed; nested exception is: javax.transac
tion.xa.XAException: rollback(c0:a7:9:14:cd:2d:0:0:2a:0:0:0:0:0:0:0:0:2b:0:ff:2:
84:8c:1):
Regards
Jarek

Hi Jarek,
Is it possible to send us a reproducible bpel package or steps to reproduce? you can send the test case to [email protected]
when you send the zip file could you please rename to .zap extension. I haven't seen this problem before. I want to reproduce this on my development env.
-muruga

Mapping Error - Dump source message to file adapter comm channel

Hi
Does anyone know of a way to dump the source message to a file adapter comm channel if - and only if - the message fails during mapping. For example, we receive a message from a trading partner that lacks an element that is mandatory during the mapping. When the mapping fails, the source message is sent - as is - to a file adapter comm channel.
I don't need anything more than the source message i.e. no need for any errors etc... to be included.
The kicker.. I would like to do this without using BPM if at all possible.
Any ideas greatly appreciated. Thx, Duncan

Hey Ram,
Go to Integration Directory and open the Receiver Determination for your scenario.
Check the configured receiver services. They are in a table-like area in the middle of the screen.
In this table of configured receiver services for that particular Sender Service/Interface, you should have the system that normally receives that message (your ERP or any other application system) and the service that contains the receiver file comm channel that will receive the message in case of error.
Check help.sap.com for help on condition editor on receiver determinations.
Now, the issue. You can only check whether a field exists, you can't check whether it doesn't exist (There's only a "EXIST" operator, and no negative operator). Thus, you can only do the following: always send messages to File, but you can avoid messages that dont have field from being sent to App System. Yeah, that sucks...
But don't fear, young padawan! There is a possible workaround. =D
In your message mapping, do the following for that particular field:
If field exists (check with Exist and IF standard functions) just bypass the field. Else, map the field with an impossible value (like string "$CREATED$"). Then, in your receiver determination, you will do the following conditions:
for App System: If field =/= $CREATED$
for File Receiver: If field = $CREATED$
Now, if the field doesnt exist, it will have value $CREATED$, thus the message will be sent to File and not to App System. If the field exists, the message will be sent to App and not to File.
Try that out.
Regards,
Henrique.

Sync/Async - JMS receiver comm. channel not processing

I have a Sync/Async scenario (without bpm) in PI 7.11:
RFC -> PI -> JMS
whereby the JMS receiver comm. channel does not fully process the message.
More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
- Message processing started
The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
- Message processing started
(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
14.02.2011 12:50:19 Information Transform: transforming the payload ...
14.02.2011 12:50:19 Information Transform: successfully transformed
14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
14.02.2011 12:50:19 Information ROB: forwarding the request message
14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
wheras the non-success msg shows only:
14.02.2011 12:55:30 Information Transform: transforming the payload ...
14.02.2011 12:55:30 Information Transform: successfully transformed
14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
14.02.2011 12:55:30 Information ROB: forwarding the request message
14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
And also the sxi_monitor shows these messages with a status of "Log version".
Keith

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

File adapter in comm.channel green, but no message collecting

Hello,
looks like this is something really at the roots.
Ok, we are in NW2004s PI 7.0.
One IDOC process is successfully implemented.
Now we started with a file to file communication!
File sender adapter is configured and shown in status green in comm.channel monitoring which would bring me to the idea that the comm.channel is configured well (To be sure we changed the directory path in the comm.channel to a wrong one which results in an error. Ok, corrected. Now all lamps are green). Comm channel is activated and polling.
But... nothing happens. The Adapter is not collecting the file in the source directory (existing) and there is no entry in monitoring on RWB or SXMB_MONI.
In Adapter monitoring all adapters except the JPR (red) are with a GREY lamp!
As we had an issue with activating the adapters (adapter monitoring before did not show any adapter (except JPR) ) two days ago we are not sure if the current issue belongs to a mistake in the configuration or in basis environment.
From XI 3.0 side we would expect that the adapter monitoring should show adapters used in green.
Do you have experience with such a behaviour?
Any help is welcome!
regards
Dirk

Hi Bhavesh,
we are near to bumping our heads against the server.
In comm.channel:
directory is : / (as simple as possible)
file name is : *.001
The file in the directory is named it_test.001 so it should be catched.
What can we do wrong?
By the way: If we change the directory to /out which is existing we have an (file is in this directory too) error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 /out: The system cannot find the file specified. '.
Cache is fine!
regards
Dirk

Duplicate Message exception in sender JMS comm channel

Similar Messages

Maybe you are looking for