Messages not processed

Hi all,
I have a problem regarding messages. There are some text files in the FTP folder that are not being processed by XI. They are not converted to XML messages. Some are processed while some are not. Please advise. Thanks!

Hi,
>>>There are some text files in the FTP folder that are not being processed by XI.
it can only mean 3 things:
- the file apdater is not configured to pick them up
- the file adpater is in error status - check communication channel monitor in RWB
- the file adapter is processing too many messages and it cannot pick up anymore - check it in messagingsystem/monitor - number of used queues
Regards,
Michal Krawczyk

Similar Messages

Proxy messages not processed in PI 7.1 pipeline coming from local client

Dear experts,
We have recently installed a PI7.1 system with two clients:
200 - Integration Server
250 - Local Integration Engine
Now, when we send proxy messages from the 250 client to the 200 client,
the messages are not processed in the integration server. The message
does arrive as we can see in SXMB_MONI, but there is no receiver determination
or what-so-ever executed. In SXMB_MONI we can see that only the SENDER
pipeline is executed.
Proxy messages from 6.20 and 7.0 systems to IS are properly processed.
Ofcourse the 250 client is defined as an application system in the integation engine
configuration (SXMB_ADM).
regards,
Jeroen

In SXMB_MONI we can see that only the SENDER pipeline is executed.
Yes. Even if no receivers are configured the data from sender to XI should be visible in sxmb_moni.
Check smq1 at XI. There could be some problem with the technical system for client 250.
Regards,
Prateek

Message not processed after technical routing

Hi ,
I have a SOAP ->ABAP Proxy (R/3) scenario that sometimes not processed completely. When checking the message in SXMB_MONI I notice a grey dot (which means log version) in the status column next to the message, Upon opening the message I can't see any errors.
The message has gone through the following steps.
Inbound Message
Receiver Identification
Interface Determination
Message Branch According to Receiver List
Request Message Mapping
Technical Routing
But final stage call adapter not executed so i came to know that response message not reached to XI.
This is occuring once or twice for every 25 to 30 messages.
Can any one provide some suggestions to rectify the above issue.
Thanks & Regards,
Arun.

Check out the below things,
1. Check for which input data it is giving. (Any specific data).
2. This may happen becaus of time out. (Huge data processing)
Also check out below link,
['Log Version' status in 'SXMB_MONI']
Resend the message from sender and it will work properly.
Log version means "Waiting for response" and liable to fail if response not received on time.
Edited by: Siddhesh Pathak on May 13, 2009 12:10 PM

XML messages not processed

Hi all,
I have a problem in my FTP folder. I have a text file to be processed as XML messages in XI. The problem is, it's not processing. The text file goes straight to the archive folder without processing it to an XML file. It's not in sxmb_moni and smq2. I'm not sure what happened. It was being processed before.
Thanks.
Regards,
IX

Check your sender file adapter status from the Communication channel monitoring on your Runtime Workbench.
Thanks,
Pooja Pandey

Print message not processed

I am able to take a print preview and print after attaching the custom message in purchase order but after saving it .
The message says that it is still in process and it is not processed.
Any idea where to check and where is the problem

check sp02 whether processing has been completed or not..also try this...
check the output immediately check box when pop up for print options are displayed..after that save it try again n see what happens

BPM :: Messages not processed at outbound side

Hi Experts,
We have 1000+ synchronous messages with BPM for only two days in July which havent processed fully. Now oncoming messages are getting processed fine, but the messages which were waiting for outbound processing from July are still waiting.
inbound side there is a success flag and outbound side it is showing a clock symbol(looks like scenario is collecting / waiting)... cant see any failed/waiting messages iin queues .. when I checked the workflow logs few are showing workflow manually edited and processed after exception.
The date messages were triggered are 10/Jun and seems one or more messages were edited on 17/jun later.
Now we would like to know which workflow thrown the exception and what they have done during manual operation.
And how to process the remaining holding messages.
Thanks in advance for you ideas and suggestions.

Hi,
As you pointed out in your post that
"inbound side there is a success flag and outbound side it is showing a clock symbol(looks like scenario is collecting / waiting)... "
Now you have not explained your scenario completely. Still from the problem statement I can say that The BPM is waiting for some messages. There are three possible scenarios where you can see the clock symbol.
You have the option of collecting multiple messages for an interface and bundling them into one message, for example, individual sales order items into one sales order. To do so, you need to define a receiver step within a loop. The loop can finish in a variety of ways.
Payload-Dependent => The loop finishes when the number of messages received matches the number specified in the payload of the messages.
Time-Dependent => The loop finishes at a specified point in time.
Message-Dependent => The loop finishes when a specific message is received.
Once all the messages have been received, a transformation step bundles the messages collected in the container element and from them creates a message in the container element .This message is then sent by a subsequent send step.
The processes use one of the abstract interfaces as an inbound interface, and the other as an outbound interface.
Your BPM cannot be time dependant, otherwise it would have completed processing by now.
Either your BPM is message dependant or payload dependant. You need to find this out.
Check out the correlation (if) used in BPM, and the condition in BPM which stops the message collection.
Plesae check SXMB_MONI and study the messages which have been succesfully processed by the BPM, so if your BPM is message dependant you have to find out what message it needs to stop collecting the message, this you can do by studying the successful message processed by the BPM. In this case your BPM will contain a FORK step. In one branch of FORK step there will be a receive step, this is the step where you can find the message required to complete waiting stage of the BPM.
Check if this message has arrived or not.
If your BPM is Payload dependant, find out whether number of messages received by the BPM matches the expected count or not. In this case the BPM must have a container operation to count the messages received. If the count is less than required value, the BPM will remain in waiting state.
regards
Anupam

Messages not processed from IP_OUT_QUEUE

Hi all,
I have enqueued the message to IP_OUT_QUEUE and consumer as B2BUSER. Still the message are not getting processed from the Queue. From the b2b.log, I see the following statements "***B2BListen turned off, will not listen on IP_OUT_QUEUE for messages***
What could be problem... It used to work before... Nothing has changed after that.... any clues??? I am using 10.1.2
2009.09.08 at 23:43:33:449: Thread-9: Repository - (DEBUG) Cache Purge Size = 3000
2009.09.08 at 23:43:33:449: Thread-9: Repository - (DEBUG) Cache Load Factor = 0.75
2009.09.08 at 23:43:33:452: Thread-9: Repository - (DEBUG) CatalogDriver manager == oracle.tip.model.metadata.CatalogMetaManager@8a0544
2009.09.08 at 23:43:33:453: Thread-9: Repository - (DEBUG) CatalogMetaManager getDriverjava.lang.InheritableThreadLocal@2f0df1 oracle.tip.repos.core.driver.CatalogDriver@2e323
2009.09.08 at 23:43:33:453: Thread-9: Repository - (DEBUG) CatalogDriver manager == oracle.tip.model.metadata.CatalogMetaManager@8a0544
2009.09.08 at 23:43:33:455: Thread-9: Repository - (DEBUG) CatalogMetaManager getDriverjava.lang.InheritableThreadLocal@2f0df1 oracle.tip.repos.core.driver.CatalogDriver@2e323
***2009.09.08 at 23:43:36:433: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize Enter***
***2009.09.08 at 23:43:37:016: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize B2BListen turned off, will not listen on IP_OUT_QUEUE for messages***
***2009.09.08 at 23:43:37:020: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run start listening on message***
2009.09.08 at 23:44:03:091: B2BStarter thread: Deployment - (DEBUG) Query Configurations null Lifecycle status Active exclude design true
2009.09.08 at 23:44:03:092: B2BStarter thread: Repository - (DEBUG) Persistency manager == oracle.tip.model.metadata.CatalogMetaManager@8a0544
2009.09.08 at 23:44:03:092: B2BStarter thread: Repository - (INFORMATION) Entering Use Case: queryConfiguration
2009.09.08 at 23:44:03:092: B2BStarter thread: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.09.08 at 23:44:03:093: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryConfiguration
2009.09.08 at 23:44:03:093: B2BStarter thread: Repository - (INFORMATION) CatalogDriver.runQuery() select ID , CLASSTYPE , NOTM , ISSEEDED , canreactivate , name , created , bilevel , LifeCycleState , description , description_clob , warningmessage , warningmessage_clob , status , type from TIP_Configuration_t t where ( LifeCycleState= ? )
2009.09.08 at 23:44:03:094: B2BStarter thread: Repository - (DEBUG) CatalogDriver.setBindVariables():
2009.09.08 at 23:44:03:094: B2BStarter thread: Repository - (DEBUG) Bind Variable : index = 2 value = Active
2009.09.08 at 23:44:03:097: B2BStarter thread: Repository - (DEBUG) CatalogDriver manager == oracle.tip.model.metadata.CatalogMetaManager@8a0544
2009.09.08 at 23:44:03:097: B2BStarter thread: Repository - (DEBUG) LargeStringImpl(InternalObject, String) - constructor
2009.09.08 at 23:44:03:098: B2BStarter thread: Repository - (DEBUG) Object OID - FE5E6FB76BBF25DDE030578C9515137B-22-1-1
2009.09.08 at 23:44:03:098: B2BStarter thread: Repository - (DEBUG) LargeStringImpl(InternalObject, BLOB) - constructor
2009.09.08 at 23:44:03:099: B2BStarter thread: Repository - (DEBUG) Object OID - FE5E6FB76BBF25DDE030578C9515137B-22-1-1
2009.09.08 at 23:44:03:099: B2BStarter thread: Repository - (DEBUG) LargeStringImpl.setBlob() - extracting blob contents to stringBuffer
2009.09.08 at 23:44:03:099: B2BStarter thread: Repository - (DEBUG) CatalogDriver.constructBaseObject()
20
Edited by: Praveen I on Sep 9, 2009 12:18 PM

Hi Pravin,
Check b2b_instancemesage view for related messages and make sure that payload is coming properly.
Also make sure that you have atleast one configuration in deployed state. Also make sure that transportServlet is up and running by accessing below url -
http://localhost:port/b2b/transportServlet
Also try by using the enqueue stubs which comes as part of tutorial (Ora_Home/ip/tutorial)
How are you enquing message to this queue? Please mail the b2b log in debug mode to my id (in my profile)/post the same here.
Regards,
Anuj

Messages not processed by integration server after SP09 to SP16

Operating System: Windows NT 2003 Standard edition Service Pack 1
Database: SQL_Server_8.00, DBSL:640.00 Patch Level: 100
ABAP Kernel: Non Unicode; Release: 640; Patch: 109;
XI: Version 3.0; Service Pack Stack:16
Host: PEARL; IPAddress: 10.1.1.13
We upgraded from service pack stack 09 to 16 and since then no messages
are getting routed to integration server. We tried a cache access
though TCODE: SXI_CACHE and it said "if_http_client receive
http_communication_failure". Then we went to ICM monitoring through
TCODE: SMICM and saw that the http service that runs on 8000 port is
inactive when we tried to activate it gave an error. Here is the
snapshot from the trace file.
[Thr 3492] *** ERROR => NiIBind: service '8000' (8000) in use
[nixxi_r.cpp 3845]
[Thr 3492] *** ERROR => NiIListen: NiBind (rc=-4) [nixxi_r.cpp
767]
[Thr 3492] *** ERROR => IcmBindService: NiBuf2Listen failed for host
PEARL:8000 (rc=-4): NIESERV_USED [icxxserv.c 1549]
When we tried to access runtime workbench through integration builder
webpage it says "page not found".
When we tried to login to the J2EE visual admin using the default
account(J2EE_admin) it gave the
error "http://pearl:8101/msgserver/text/logon returned empty list of
connection parameters."
In SAPMMC we looked at the system log and saw the error "SAP Basis
System: Operating system call gethostbyaddr failed (error no. 0 )".
We tried restarting the whole server but to no effect.

since your OS is Windows try following in command at prompt
C:>netstat -a
or
C:>netstat -an
one of the above will work in NT, the list shows the listening (Open) ports and ESTABLISHED (used)..check for the 8000 which is your HTTP port.
Also in SAP check the t-code "SMICM" and then goto services and see the HTTP services running without error or not?
Hint: Port names are defined in services file located at C:\WINDOWS\systemXX\drivers\etc\services file..

Script Alert: "Sorry I could not process the following files" (Error Message using Image Processor)

I'm a seasoned Photoshop/Bridge CS5 user who recently upgraded to CS6. In Bridge I just ran my first Image Processor batch, trying to convert a set of RAW .NEF files to .PSD files with a basic editing action I created applied to them. Photoshop CS6 opens the files from Bridge and applies the actions, but then I get the "Script alert" error message "Sorry I could not process the following files" and a list of all of the files in the batch I was trying to run the script on. The files all remain open and are saved on my hard drive in a folder created by the Image Processor script, but do not close unless I manually close them. I never had this problem in CS5 where the image processor would apply the desired actions to the batch of photos one at a time, then save and close. Thoughts on how I can fix this bug?

Hey Jeff--
No specific action steps to make the image safe - no flattening, etc. Had problems narrowing down the specific action step causing the problem. So I ran the Image Processor script in the ExtendScript ToolKit and debugged in. (I'm using the version that shipped with CS4.)
Turns out what was happening is that the app.activeDocument.close() command on line 1490 was never getting called, because the this.SaveFile() above it was throwing an exception. More debugging got me to the problem - SaveFile() tries to restore the history state after making a doc safe for saving as a JPEG. This causes an exception. So I commented out line 1571:
// app.activeDocument.ativeHistoryState = historyState;
The script runs just fine after this. I commented out the close to see what history states got added to the doc, but no new states are recorded, so commenting out the restore line should not cause any problems.
Of course, my solution does not solve the problem and I may need to comment out all the saveFile() lines that does this. Not sure why some actions have this problem and others don't. The actions I am running have about 25 steps. Perhaps PS is not catching up quick enough. I added a $.sleep(2500) after the restore history but that didn't help.
So, not sure where this gets us. I will check about posting an action set with just one of the actions that cause the problem. But I may also have our customer comment out that line of the Image Processor script.
Hope this helps. May post more next week.

HT4623 I can not get connected to App Store , download or update any apps, EVEN I DID RESET ALL SETTING , STILL I RECIEVE A MESSAGE says: YOUR REQUEST IS NOT PROCESSED ,ERROR COD: 109 !! WHAT DOSE IT MEAN? HOW CAN I SOLVE THE PROBLEM??

I can not get connected to AppStore , DOWNLOAD OR UPDATE ANY OF MY APPS , WHEN I GO FOR INSTALLING , THE MESSAGE SAYS: YOIR REQUEST IS NOT PROCESSED , ERROR CODE, 1009!!! HOW CAN I SOLVE THIS PROBLEM??

Try contacting the iTunes support staff, they do the app store also, at: http://www.apple.com/emea/support/itunes/contact.html

BPE adapter : message not used by any process

hi frnds,
I've created 2 scenarios using BPM
1) merge scenario: 2 msgs ==> BPM ==> 1 msg
1st msg is going without any problem. but 2nd msg is giving error saying 'BPE ADAPTER ERROR: message not used by any process'. i checked in sxi_cache and found that return code for Intg'n process is 0 only. but still i tried reactivating. but no use
2) split scenario: 1 msg ==> BPM ==> 2 msgs
sender msg is going without any problem,but not receiving 2 rcvr msgs to the target directory. return code of IP is 0 and no other errors.
after installing PI on my system, for the first time i'm trying BPM scenarios. simple file to file working properly. BPE adapter has to be activated manually or i missed any initial configuration??? pls help me to resolve this.
thanks.

abhishek,
I have used the following steps in BPM for this scenario xml file ==> BPM ==>xml file
1) data types: a)send_dt
                        b) rcv_dt
2) msg types a) send_mt
                        b)rcv_mt
3) interfaces   : send_ob_im
                          send_abs_im
                          rcv_abs_im
                          rcv_ib_im
in integration process,
start ==> receive ==> send ==> stop
so in general its like,
send CC ==> send OB I/F ==> send ABS I/F ==> rcv ABS I/F ==> rcv IB I/F ==> rcv CC
when i'm not using BPM, outbound queue SMQ1 is empty and messages are not stickking up there. but if i use BPM, SMQ1 is having entry saying 'SYSFAIL'. for the first time i'm doing the BPM scenarios.
thanks.

JCBC Adapter and File adapter not processing messages

Hi
I noticed that messages are being delivered to Adapter engine and the same are visible in Runtime Workbench with status "to be delivered". But, JDBC Adapter and File Adapter not processing these messages.
Any idea where I can find the problem?
I was able to re-deliver successfully via the JDBC Adapter using the MessagingSystem GUI using XISUPER user.
Regards
Chandu

Hi,
1.Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Regards
Agasthuri Doss

Error: BPE_ADAPTER Message not used in any process

Please help me fix this error.
My scenario is i have a bpm process for merging three files.
and i configured in this way..
merge the three files into one and send into SAP
i have three communication channels (file adapter) for three files
one communication channel xi adapter for a proxy into sap.
using these files as input to BPM process
then using BPM process as sender to the proxy reciever
I am getting error from sxmb_moni in xi box
as error category:BPE_ADAPTER
error id: message_not_used.
it says message not used in any process.
please help me correct this problem..
thanks
jp

JP,
Are u sure there is nothing wrong in your design part? Also Are u using Fork to receive 3 files parallely, If yes then all the 3 files has been checked for start process? Can u confirm this.
Also in the Inerface determinations did u gave abstract interfaces that BPM is recieving?
Best regards,
raj.

Messages not being processed

Hi,
I experience an issue with 10g soa, about not having processed some messages sent to receive activities of my process.
I have my process deployed, I can initiate the instance of the process, I can move the flow of the process by calling some receive activities, but sometimes it seems it stucks on one of these receives. It happens randomly on various processes on various receive activities, like one day one receive operation doesn't proceed at all, and on another day it is another receive operation, and that is without any change to the process and redeployment.
I can see the message has been received by server, because I can query it from DLV_MESSAGE table from BPEL data source, and i see its STATE = 0, which is unprocessed. I am also sure that message has valid content and the correlation bits on the message are also correct, really there is no reason why such message should not be processed, it always worked until the moment it decides not to for unknown reason.
My question:
1. What causes messages to be not processed?
2. What are known options to deal with this situation?
Currently I am in a condition where I can spot unprocessed messages, which is fine, so I am aware of the problem, but I am not able to deal with the problem. Even if I tried to submit the message via BPEL Console, it was not processed either.
Thank you for any suggestions

Some blog information to support this case
http://soacrux.blogspot.com/2010/08/automatic-recovery-program-for-pending.html
Content repaste:
Automatic recovery program for pending BPEL call back messages
BPEL engine maintains all async call back messages into database table called dlv_message. You can see such all messages in BPEL console call-back manual recovery area.The query being used by bpel console is joined on dlv_message and work_item tables.This query simply picks up all call back messages which are undelivered and have not been modified with in certain threshold time.
Call-back messages are processed in following steps
BPEL engine assigns the call-back message to delivery service
Delivery service saves the message into dlv_message table with state 'UNDELIVERED-0'
Delivery service schedules a dispatcher thread to process message asynchronously
Dispatcher thread enqueues message into JMS queue
Message is picked up by MDB
MDB delivers the message to actual BPEL process waiting for call-back and changes state to 'HANDLED=2'
So given above steps, there is always possibility that message is available in dlv_message table but MDB is failed in delivering it to BPEL process which keeps message always in state= 0.
Following program can be tailored to suite one's own requirements to recover from such state-0 messages.
Note:- This program contains logic to recover from invocation and call-back messages. Please comment out appropriately.
package bpelrecovery;
import com.oracle.bpel.client.*;
import com.oracle.bpel.client.util.SQLDefs;
import com.oracle.bpel.client.util.WhereCondition;
import java.util.ArrayList;
import java.util.Hashtable;
import java.util.List;
import javax.naming.Context;
public class bpelrecovery {
public bpelrecovery() {
public static void main(String[] args) {
bpelrecovery recover = new bpelrecovery();
String rtc = "";
try{
rtc = recover.doRecover();
catch (Exception e){
e.printStackTrace();
rivate void recoverCallbackMessages(List messages)
throws Exception
String messageGuids[] = new String[messages.size()];
for(int i = 0; i < messages.size(); i++)
ICallbackMetaData callbackMetadata = (ICallbackMetaData)messages.get(i);
String messageGuid = callbackMetadata.getMessageGUID();
messageGuids[i] = messageGuid;
System.err.println((new StringBuilder()).append("recovering callback message =
").append(messageGuids).append(" process
[").append(callbackMetadata.getProcessId()).append("(").append(callbackMetadata.getRevisionTag()).ap
pend(")] domain [").append(callbackMetadata.getDomainId()).append("]").toString());
Locator locator = getLocator();
IBPELDomainHandle domainHandle = locator.lookupDomain();
domainHandle.recoverCallbackMessages(messageGuids);
public String doRecover() throws Exception{
// Connect to domain "default"
try{
System.out.println("doRecover() instantiating locator...");
Locator locator = getLocator();
System.out.println("doRecover() instantiated locator for domain " +
locator.lookupDomain().getDomainId());
// look for Invoke messages in need of recovery
StringBuffer buf1 = new StringBuffer();
WhereCondition where = new WhereCondition(buf1.append(SQLDefs.IM_state).append( " = "
).append(IDeliveryConstants.STATE_UNRESOLVED ).toString() );
System.out.println("doRecover() instantiating IInvokeMetaData... with where = "+ where.getClause());
IInvokeMetaData imd1[] = locator.listInvokeMessages(where);
System.out.println("doRecover() instantiated IInvokeMetaData");
// iterate thru the list
List l1 = new ArrayList();
for (Object o:imd1){
l1.add(o);
// See how many INVOKES are in the recovery zone
System.out.println("doRecover() instantiated IInvokeMetaData size = " +l1.size());
// look for Callback messages in need of recovery
StringBuffer buf = new StringBuffer();
where = new WhereCondition(buf.append(SQLDefs.DM_state).append( " = "
).append(IDeliveryConstants.TYPE_callback_soap ).toString() );
System.out.println("doRecover() instantiating ICallbackMetaData... with where = "+
where.getClause());
ICallbackMetaData imd[] = locator.listCallbackMessages(where);
System.out.println("doRecover() instantiated ICallbackMetaData");
// recover
List l = new ArrayList();
for (Object o:imd){
l.add(o);
recoverCallbackMessages(l);
catch (Exception e){
e.printStackTrace();
return "done";
public Locator getLocator(){
System.out.println("getLocator() start");
Locator locator = null;
// set JNDI properties for BPEL lookup
String jndiProviderUrl = "opmn:ormi://localhost:6003:oc4j_soa/orabpel";
String jndiFactory = "com.evermind.server.rmi.RMIInitialContextFactory";
String jndiUsername = "oc4jadmin";
String jndiPassword = "welcome1";
Hashtable jndi = new Hashtable();
jndi.put(Context.PROVIDER_URL, jndiProviderUrl);
jndi.put(Context.INITIAL_CONTEXT_FACTORY, jndiFactory);
jndi.put(Context.SECURITY_PRINCIPAL, jndiUsername);
jndi.put(Context.SECURITY_CREDENTIALS, jndiPassword);
jndi.put("dedicated.connection", "true");
try{
System.out.println("getLocator() instantiating locator...");
locator = new Locator("default", "welcome1", jndi);
System.out.println("getLocator() instantiated locator");
catch (Exception e){
System.out.println("getLocator() error");
e.printStackTrace();
return locator;

My outbound messages are not processing in XI

Hi All,
When i try to test my scenario i.e sending message from SRM to MDM , all my messages are struck in the Queue in XI. Even i deleted queues in SMQ2 , my messages are not processing and in sceduled for outbound processing stage. Even i restard also its on pending status. Please help me How to process my messages which is pending in XI.
Thanks in advance
Regards,
KK

Hi..
go to sxmb_moni->monitor processed messages
select ur message.. scroll towards right..
click on ur message queue ID.
check if there is any errored out message in that queue.
if yes .. delete that message,
and release the queue by unlocking that.
Regards
Pushkar

Messages not processed

Similar Messages

Maybe you are looking for