** Message being processed - Queue status green colour

Hi Friends,
Many messages in our SXMB_MONI  shows green color in the queue id column. It shows 'Message being processed'. All messages are in queue, still they are not delivered. Processing takes more hours. These messages are not EOIO queue. While we check this thru SMQ1 and SMQ2 it shows 'Running'. So, what could be the problem ...?
Kindly help friends, to solve this issue. (Points rewarded for helpful answer)
Kind Regards,
Jeg P.

HI,
QUEUE STATUS RUNNING BASICALLY MEANS THT
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
HOPE THIS WILL SOLVE THE PROBLEM
PLZ REWARDS POINTS
VIKAS

Similar Messages

  • Process Chain - Status Green but log says "Termination of chain "

    Hello Friends,
    One of the Steps in a Sub Chain of the Meta Chain shows the log as follows:
    30.10.2009 05:20:28 Job started
    30.10.2009 05:20:28 Step 001 started (program RSPROCESS, variant &0000000049485, user ID SCMREMOTE)
    30.10.2009 05:20:35 Spool request (number 0000017553) created without immediate output
    30.10.2009 05:20:35 Entire chain now has status 'G'
    30.10.2009 05:20:35 Termination of chain has been reported to meta chain D6SBR9M64EV91ZX911UJI7K36
    30.10.2009 05:20:35 Job finished
    and the Step has changed to Green. So we normally assume that it has executed succesfully. Recently, there came this data issue. This step loads Open Sales Order data from a Cube to APO DP Planning area. Now few Open Sales Order Qty for a material are missing in planning area.
    Does this step in the Process chain has executed Succefully or as the log says is it terminated? Though the step changes to green , were all the materials not loaded into planning area?
    Please advice and suggest.
    Thanks,
    Chandra.

    Hii
    This log shows that chain has been successfully terminated. This is a common log
    The missing of Open Sales Order Qty for a material  may be due to other reason .
    Try to get into more details for which Orders this has happened and check in the source system.
    Thanks
    Sonal...

  • Validation error : Business Partner  currently being processed

    Hi,
    Can anyone suggest a solution for the following error.
    Business Partner is created thru transaction BP in CRM.
    The newly created Business partner is saved and after coming out of
    transaction ,When we checked BDOC status in SMWO1 for BUPA_MAIN
    Object , it gives following errors:
    1) business partner xxxx is being processed by xxxx ( user )
    2) validation error occurred :Moodule CRM_BUPA_MAIN_VAL ,BDoc type
    BUPA_MAIN
    We found BP gets created successfully in R/3 side even though above
    error occurred.
    When we reprocessed the error message in SMWO1 , it is processed
    successfully ( status "green" )
    Pl. suggest a solution.
    Thanks in anticipation !
    regards,
    Prashant

    Hi Jashwanth,
    Tried the mentioned note but still problem persists.
    Pl. suggest !!
    regards ,

  • Putting message into send queue failed

    Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 8fd8ebf2-14dc-498c-26d4-fa83a612df8f(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: Violation of PRIMARY KEY constraint 'PK__BC_MSG_DUP_CHECK__0CB1C3F7'. Cannot insert duplicate key in object 'SAPPIQDB.BC_MSG_DUP_CHECK'..
    I get the above error for one of my interface.
    The scenario is simple lift and shift using integrated scenario.
    I am unable to figure out reason for the above error.
    Regards,
    Lalit Mohan Gupta.

    Hi Lalit Mohan Gupta,
    It seems like you have a problem with duplicate Message IDs (GUID). This can happen if you do not let SAP PI generate the message ID for the message being processed, but is relying on an external system to provide you with the message ID.
    In any case. I don't think you will succeed with getting the message processed, because of the duplicate message ID constraint in SAP PI. But you need to be aware that depending on how your SAP PI has been setup to handle archiving/deletion of messages in Java-stack, you could potentially run into the situation, where SAP PI removes the initial message from its database and by that enables processing of the duplicate message ID.
    Best regards,
    Jacob

  • Can't get rid of a TX - message keeps appearing and being processed by OSB

    I have some sort of a poison message or TX I can't flush. Every 10 seconds I get a log message like the second one below, and the number of pending messages in multiple places and OSB proxy service messages processed keep climbing - all without producing any new messages on my part. I've tried deleting the default server store on the OSB managed server and the filestore for the JMS server. No luck.
    When this first started happening, the error messages looked like the first one below. Something I did caused the change, I assume. However, it's the same TX ID throughout.
    So, first, how can I get rid of this thing? It's driving me nuts and keeping me from closing out a POC.
    Second, why is it happening? I have one suspicion - could it be because that somehow we configured mutiple domains with the same name for a distributed application? It's not my normal practice but it happened. These domains don't communicate directly, but there are domains that need to communicate with both. So I'm guessing the name ambiguity may be hurting us. Just a guess, though.
    In this case, the sgosb domain's proxy service (this domain name is unique) is receiving messages from a queue resident in the pega_domain in Singapore and another proxy service is putting a message to another queue in the pega_domain in the UK. This is not in a single TX; the first proxy service forwards the message to a queue in the sgosb_domain, the second proxy service gets that message and puts it into the other pega_domain. It's an XA TX for each proxy service.
    Just to make it more fun, the sgosb_domain has another proxy service reading from a different queue and forwarding it to a queue in the third pega_domain in the US.
    TIA for any help or insight.
    Oh yes, the OSB domain is WLS 10.3.4, while the pega_domains are WLS 10.3.2
    Original error message
    ####<Apr 13, 2011 4:32:13 AM GMT> <Error> <EJB> <sg01app510> <sgosb_1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'>
    <<anonymous>> <> <92f54a30d60e6302:-4b6d523c:12f4cfeaabc:-8000-0000000000000123> <1302669133597> <BEA-010026> <Exception occurred during commit of
    transaction Xid=BEA1-039B0B6D3D0E77C1B135(1898471720),Status=Rolled back. [Reason=Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
    begin=0,seconds left=600,XAServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=(ServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=
    (state=new,assigned=none),xar=null,re-Registered = false),SCInfo[sgosb_domain+sgosb_1]=(state=rolledback),SCInfo[pega_domain+pega_1]=(state=rolledback),properties=
    ({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+, XAResources={eis/tibjms/Topic,
    WLStore_sgosb_domain_FileStore_auto_1, eis/aqjms/Queue, eis/wls/Queue, eis/tibjms/Queue, WLStore_sgosb_domain__WLS_sgosb_1, eis/AQ/aqSample, eis/aqjms/Topic,
    eis/pramati/Queue, eis/sunmq/Queue, WLStore_sgosb_domain_WseeFileStore_auto_1, WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1,
    WSATGatewayRM_sgosb_1_sgosb_domain, eis/jbossmq/Queue, eis/activemq/Queue, eis/fioranomq/Topic, eis/tibjmsDirect/Topic, eis/wls/Topic,
    eis/tibjmsDirect/Queue, eis/Apps/Apps, eis/webspheremq/Queue},NonXAResources={})],CoordinatorURL=pega_1+nj09mhm5078:22111+pega_domain+t3+):
    javax.transaction.RollbackException: This transaction does not exist on the coordinating server.  It was probably rolled back and forgotten.
            at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
            at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
            at weblogic.transaction.internal.CoordinatorImpl_1032_WLStub.commit(Unknown Source)
            at weblogic.transaction.internal.TransactionImpl$1.run(TransactionImpl.java:331)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.transaction.internal.SecureAction.runAction(SecureAction.java:72)
            at weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:327)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:252)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
            at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:553)
            at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:424)
            at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:326)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
            at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
            at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
            at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: javax.transaction.RollbackException: This transaction does not exist on the coordinating server.  It was probably rolled back and forgotten.
            at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:94)
            at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
            at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
            at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    The error message I'm getting now
    ####<Apr 13, 2011 4:51:38 AM GMT> <Error> <EJB> <sg01app510> <sgosb_1> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <>
    <92f54a30d60e6302:-42808c28:12f4d3173cb:-8000-0000000000000032> <1302670298730> <BEA-010026> <Exception occurred during commit of transaction
    Xid=BEA1-0011D0679BA5074B8E12(1930603846),Status=Rolled back. [Reason=javax.transaction.xa.XAException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds
    left=60,XAServerResourceInfo[WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1]=(ServerResourceInfo[WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1]=
    (state=rolledback,assigned=sgosb_1),xar=WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1239571724,re-Registered =
    false),XAServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=(ServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=
    (state=rolledback,assigned=pega_1),xar=null,re-Registered = false),SCInfo[sgosb_domain+sgosb_1]=(state=rolledback),SCInfo[pega_domain+pega_1]=(state=rolledback),properties=
    ({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+, XAResources={eis/tibjms/Topic,
    WLStore_sgosb_domain_FileStore_auto_1, eis/aqjms/Queue, eis/wls/Queue, eis/tibjms/Queue, WLStore_sgosb_domain__WLS_sgosb_1, eis/AQ/aqSample, eis/aqjms/Topic, eis/pramati/Queue, eis/sunmq
    /Queue, WLStore_sgosb_domain_WseeFileStore_auto_1, WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1, WSATGatewayRM_sgosb_1_sgosb_domain, eis/jbossmq/Queue, eis/activemq
    /Queue, eis/fioranomq/Topic, eis/tibjmsDirect/Topic, eis/wls/Topic, eis/tibjmsDirect/Queue, eis/Apps/Apps, eis/webspheremq/Queue},NonXAResources=
    {})],CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+): weblogic.transaction.RollbackException: Unknown reason
            at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1881)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:345)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
            at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:553)
            at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:424)
            at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:326)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
            at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
            at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
            at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: javax.transaction.xa.XAException
            at weblogic.store.gxa.internal.GXAResourceImpl.prepare(GXAResourceImpl.java:1227)
            at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1295)
            at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:500)
            at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:380)
            at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:2593)
            at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:1321)
            at weblogic.transaction.internal.SubCoordinatorImpl.startPrepare(SubCoordinatorImpl.java:183)
            at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
            at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
            at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    .>Edited by: SteveElkind on Apr 13, 2011 5:50 AM

    Tom,
    Thanks! Succinct and easy to understand as ever.
    Yup, that covers it - I had also just seen this in the docs after looking at atheek1's earlier response (thanks to him/her as well). It's covered almost as clearly there as you state it here (http://download.oracle.com/docs/cd/E11035_01/wls100/jta/trxcon.html).
    While the ESB domains meet all of those requirements (except for cross-domain security configuration), each of the other two sets of domains (3 in each set) do not meet the naming uniqueness criteria for domain and server names; they do for JMS server names. I saw the store names in the TX identifier string as included resource, and assumed they might play a part - that's why I changed them. As you say, an unnecessary change. Oh well - it was an easy one.
    My normal practice has been for unique names in the past, due to problems I had years ago with cross-domain JMS traffic in an earlier WLS version. I guess it's the wrong time to have forgotten that lesson.
    Does anyone know of a quick way of changing a domain name quickly without rebuilding the domain? In the past WLST resulted in incomplete copies for me, is that still a problem? Server names are easy, just some global search-and-replace in the config.xml file (and in the management scripts, too)
    /Steve

  • BPM wait step : RWB"To Be Delivered status": SXMB_MONI"Message being sent"

    Hi All,
    I have a BPM interface running fine since 1 year.
    In this BPM I have wait step for 5 minutes.
    But yesterday message  is stopped on wait and not proceeding ahead.
    I checked XML is good as per mapping. and in runtime wirk bench message is still in "To Be Delivered status"
    and in SXMB_MONI message column Outbound Status still showing "Message being sent" even after 12 hours.(wait is only 5 minutes). And below is the trace of last message.
    Please guide how to handle or restart this message. in SMQ1 & SMQ2 there are no queues showing:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">--start determination of sender interface action</Trace>
      <Trace level="1" type="T">select interface Request_SI</Trace>
      <Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
      <Trace level="1" type="T">--start determination of receiver interface action</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface Request_SI</Trace>
      <Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
      <Trace level="1" type="T">--start determination of sender interface action</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      </SAP:Trace>
    Regards

    Solved, few BASIS jobs were inactive in transaction code "SWF_XI_CUSTOMIZING".

  • Messages in inbound queue in status-RUNNING and it is too slow

    Hi Experts,
    We have a issue there are tons of messages in inbound queue in status-RUNNING and it is too slow!, hence there are more messages getting in the queue every minute.
    This is Production enviorment.
    We have priority queues
    QIN is waiting status.
    De-register will not work due to loss of messages fear
    Please advice
    thanks and regards,
    krushi

    Hi,
    If the queues are hanging due to peak load at sometimes
    you can schedule following reports to restart them automatically
    (dont have to lock and unlock manually)
    RSQIWKEX - Inbound Queues
    RSQOWKEX- Outbound Queues
    Also you can save the first entry of the queue if its causing problems to process later- smq3
    thanks
    francis

  • 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;

  • Process Chain Status Red, DTP status yellow, DTP is green from inside

    Hello All,
    I have a problem where the  Process Chain  status is red, but the process(DTP) status is yellow.
    When I right click on the yellow process there is no error message and the DTP is green in Process Monitor.
    But the chain did not complete and the rest of the process steps are grey.
    After 20 minutes the Process Chain ran again(automatically after new data arrived) and this time without errors and it went green.
    My question is, how to proceed with the red Process chain and complete the further process and make it green.
    Regards
    Alex

    hi,
    There are scenarios where you need to change status of a process chain or a particular step in process chain.
    You might need to change the status in the cases where we need mark these steps successful so that dependent steps get processed. There are other scenarios where one needs to change the status of a single step in the process chain or status of whole process chain.
    Step by step instructions on change process chain status
    1. Right click on the failed step in the process chain monitor and go to displaying messages
    2. Go to u2018Chainu2019 tab and note down variant, instance and start date
    3. Go to SE16 and the table RSPCPROCESSLOG and enter variant, instance and start dates from step 2 and note down log_id, type, variant, instance.
    4. Go to SE37 transaction and execute the function module RSPC_PROCESS_FINISH and enter the values from step 3 and enter the new status u2018Gu2019 in status field and execute the FM
    5. This sets the status of the process chain (PC)
    After you set the status using the FM, go to the monitor screen of the process chain, you will notice the changed status. Now dependent steps in the process chain will start running
    Thanks

  • Message Status as "Scheduled" and Queue Status "Queue Stopped".

    Hi friends,
    My scenario is from Peoplesoft -> XI -> BI
    Message has reached BI, but in SXMB_MONI, its showing Message Status as "Scheduled" and Queue Status "Queue Stopped".
    How to proceed further ? How can I start that queue ?
    Thanks ain advance,
    Neena John

    Hi Neena,
    Go to SXMB_ADM -> Manage Queues -> Register Queues
    More on queues
    XI :  How to Re-Process failed XI Messages Automatically
    Run the report RSXMB_REGISTER_QUEUES and register the queues
    Run the report RSXMB_RESTART_MESSAGES for restarting ur messages
    Refer this:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
    Regards,
    Vinod.

  • Message Status "Scheduled", Queue Status "Queue Stopped"

    Hi friends,
    My scenario is from Peoplesoft -> XI -> BI
    Message has reached BI, but in SXMB_MONI, its showing Message Status as "Scheduled" and Queue Status "Queue Stopped".
    How to proceed further ? How can I start that queue ?
    Thanks ain advance,
    Neena John

    Hi Neena,
    Go to SXMB_ADM -> Manage Queues -> Register Queues
    More on queues
    XI :  How to Re-Process failed XI Messages Automatically
    Run the report RSXMB_REGISTER_QUEUES and register the queues
    Run the report RSXMB_RESTART_MESSAGES for restarting ur messages
    Refer this:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
    Regards,
    Vinod.

  • CcBPM: Message outbound status, Message being sent

    Hi
    I have a message with status flag message being sent at the outbound status PE since 30 days. Because of this message many messages got blocked with scheduled on outbound side status.
    I tried to delete work items related to the message in SWWL, but i am not able delete.
    Please suggest solution
    Regards
    Subba Rao

    Hi velidi subba rao,
    Please go to SMQ2 and right click on the entry and Select Save to LUW. It saves it to SMQ3. You will be able to reprocess it from there.
    Give it a try and let me know if it worked. Also just release the queues once you have saved the message that is stuck.
    Regards,
    Jannus Botha

  • Set process chain status to green despite an error

    Hi everybody,
    I've made a process chain with an ODS activation. If there's an error, an AND process comes with a message to users.
    When an error occurs on the ODS activation, the process chain ends like I want but his status is red.
    How can I do to set the status to green ? Is that possible ?
    Thanks

    Ok,
    In that case it can be simplier than that.
    You need after activation of ODS in your chain have two branches, one with error and another one with success.
    In the case of the success the branch is connected to the rest of the chain and the rest of the chain will continue and remain green status for that chain as the overall result of the chain.
    In the case of error the new branch is connected to a process that will always terminate with sucess. As an example you could create a variant for roll-up of aggregates of an Infocube. In these variant do not select any InfoCube and mark the option End Process Sucessfully if No Aggregates Exist. This will always force this process to OK, green status, and therefore will always end your chain as green status even when the ODS activation fails
    Hope this helps.
    Diogo.

  • Sales order remains on status being processed.

    I created a sales order and created pgi, Outbound delivery. When I tried to create a billing document it gave me a message, sales order is being processed. I opened the sales order and looked for the document flow, it says sales order is still being processed and delivery, pgi and transfer order are completed.
    Why it still shows this message.

    Hi Vijay,
    This can be the case of  other user logging into your order.  Please check in SM12 ( if you have authorization ) and for VBAK object  and your order number you can find a lock.  Please delete the lock and try to bill again.
    Hopefully this helps. 
    Even after invoice, if the status are " Being processed" ,, then you can think of SDVBUK00 to be run -- ( i dont think this is required )
    Reward if it helps.
    Thanks & Regards,
    CLN

  • Delivery status still 'Being Processed' although invoice had been created

    Dear all,
    I have a problem in production server.
    Delivery status still 'Being Processed' although invoice had been fully created and status is cleared.
    First, I get a problem when I tried to create invoice refer to this DN. Then I applied a message (execute report ZZBRE003: update table VBUK-WBSTK & VBUP-WBSTA = 'C'). Invoicing was created and status was cleared. But the delivery status still 'Being Processed'.
    Could you help me, how to make this delivery status: Completed?
    thanks,
    Fella

    Dear Fella,
    I think that you haven't posted GI (confirmation of service) for the full delivery qty. Please check GI status for each item in the delivery. If any item shows partial delivery, post GI for the balance qty.
    If any item has Partial Delivery Indicator 'D', the order can never have status 'fully delivered'. You must complete such items by entering a reason for rejection.
    If that is not the case, there is a chance that copying ctrl (Delivery->Invoice) is not configured correctly. Choose a right value for 'Update Document Flow' in the copying control for the Invoice type from the delivery type used.
    Please reward if helpful
    Regards,
    Noufel P

Maybe you are looking for

  • SSRS WebService ReportExecution2005.asmx raised an exception during creating pdf

    Hello, yesterday i created already a task regarding this problem, but i think it was not detailed enough. Since yesterday i tried a lot of things and came to the following result. If we call the WebService ReportExecution2005.asmx with format "PDF" l

  • Export/import character data conversion in NLS_LANG FAQ

    The [OTN NLS_LANG FAQ|http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm#_Toc110410566] says: > In Oracle9i the Export utility always exports user data, including Unicode data, in the character set of the database. The Impo

  • POS Interface

    Hi Friends I am working on Batch Valuation. Using Standard IDOC WPUUMS for sales posting from POS. The standard IDOC do not have Batch field and In have enhanced it to insert batch number in article and billing documents. But still batch number is no

  • Patch for developer6.0

    Hi can any one tell me the site address to download a patch for developer 6.0 thanks sanjay null

  • Question on Service Date on Debrief Form in Service Request

    Hello I have a requirement to fetch the Service Date on the Debrief form under Labor Section. The issue what i am seeing is the Service Date which was showing on the application is not the same what was stored in the CSF_DEBRIEF_LINES table. It is al