Messages not getting propagated?

I'm using CDC and streams - distributed async auto-log. Things have been working fine for a while. We had a DB crash due to a bad disk and I rebuilt the DB. We had a major gap in our data and getting streams to work again has been hell.
I'm seeing the most bizarre thing. I have one change set and one change source. I disable the change set for a while so I can do a manually load of data that is missing. I do a extend to see where the data is currently at - then I manually load the data up to that point. During the load I can see in the alert.log archive logs from production registering fine. Then, when I'm ready, I enable the change set. There's data in the change tables from before, so it begins to work, but as I watch the alert.log :
LOGMINER: Begin mining logfile: ...
LOGMINER: End mining logfile: ...
No rows are going into the change tables!!?!?!?!?! The CSCN$ is changing in the views and you can see messages coming in, but nothing in the change tables. This goes on for a while and finally 10 or 15 minutes later they start coming in. Now I have a gap again and I have to go back and manually fix things.
Why on earth would no rows be inserted into the change tables??? Any ideas? And, is there an easier way to fix this? I'd like to be able to go back in time and start over. I've tried DBMS_CAPTURE_ADM.ALTER_CAPTURE to change the start_scn, and this works, the older archive logs are mined, but the cscn$ in the veiws are not changed.
This CDC streams is not easy to manage change data when your app has errors and you need to be able to have fine grain control over the data coming in...

If there are no errors or session id's in DBA_QUEUE_SCHEDULES then perhaps the propogation was never started!
Use this to start propogation
DBMS_AQADM.SCHEDULE_PROPAGATION (queue_name         IN VARCHAR2,
                                  destination       IN VARCHAR2 DEFAULT NULL,
                                  start_time        IN DATE DEFAULT SYSDATE,
                                  duration          IN NUMBER DEFAULT NULL,
                                  next_time         IN VARCHAR2 DEFAULT NULL,
                                  latency           IN NUMBER DEFAULT 60,
                                  destination_queue IN VARCHAR2 DEFAULT NULL);If, for whatever reason it was unscheduled, for example a DB shutdown, then use this to re-start
DBMS_AQADM.ENABLE_PROPAGATION_SCHEDULE (queue_name        IN VARCHAR2,
                                        destination       IN VARCHAR2 DEFAULT NULL,
                                        destination_queue IN VARCHAR2 DEFAULT NULL);

Similar Messages

  • WebCenter user role not getting propagated

    Hi,
    I am creating a WebCenter WSRP portlet application. I expected, after registering the application as a portlet, when I will consume it in WebCenter, the currently logged in user's name and role will be accessible. But in my case, when I am trying to check the logged in user's role using request.isUserInRole(...) method, it always return false. When I debugged the application, I saw that the user role is empty.
    Can someone please help me understand, if I have to do anything to successfully propagate the logged user's role to the custom portlet application.
    Just so you know, I could access the logged in user's name using request.getUserPrincipal().getName(). Please help.
    Thank you,
    Kanchan Upadhyay

    Hi,
    Yes, I am using LDAP and everything else in webcenter works fine. Just the user role is not getting propagated to my custom application developed using portlet. I have tried in taskflow also, seems like the user role is not accessible from there as well. Is there any specific way of accessing user information for custom application hosted in webcenter as portlets?
    Your help is appreciated!!
    Thank you,
    Kanchan

  • Problem in BADI, error message not getting displayed

    Hello Experts,
    I am facing a strange problem in BADI.
    The requirement is that the user should not be allowed to change the plant field
    on the screen of standard MM transctions for PO/PR amendment.
    I have written the code in separate BADIs for PO and PR.
    I am displaying an error message if the user tries to change the field.
    For PO, it is working fine.But for PR, the same code is not working.
    The control is going over to the BADI for PR and rest of the code is working fine.
    But the error message is not getting displayed for PR amendment.
    Can anybody please suggest the possible cause of problem and some solution to it.
    Thanks in advance.

    Hi
    See the sample BADI code for PR which raises an exceptions and do accordingly
    BAdI Name: ZPUR_RFQ (Implementation name) Purchase Requisitions
    Definition Name: ME_REQ_POSTED
    Interface Name : IF_EX_ME_REQ_POSTED
    Implementing Class: ZCL_IM_PUR_REQ
    Method :            POSTED
    METHOD if_ex_me_req_posted~posted .
      DATA : v_mtart TYPE mtart.
      DATA l_s_eban TYPE ueban.
      LOOP AT im_eban INTO l_s_eban.
        IF l_s_eban-estkz NE 'B'.
          CLEAR v_mtart.
          SELECT SINGLE  mtart INTO v_mtart FROM mara WHERE matnr = l_s_eban-matnr.
          IF v_mtart EQ 'ZERS' OR v_mtart EQ 'FHMI' OR v_mtart EQ 'UNBW'.
            MESSAGE e000(zm_msg) WITH 'You are not allowed' 'to create PR for stock items'.
          ENDIF.
        ENDIF.
        IF  l_s_eban-knttp NE 'F' OR l_s_eban-pstyp NE '9'.
          IF l_s_eban-knttp NE 'A'.
            IF ( l_s_eban-pstyp NE '9' AND l_s_eban-pstyp NE 'D' ) 
               AND l_s_eban-matnr EQ space.
              MESSAGE e000(zm_msg) WITH 'You cannot create'
                'a PR without material number'.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDMETHOD.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Messages not getting displayed in BADI

    Hi experts,
    I have implemented a BADI for automating FB50 in MIGO. Atlast i am using
    CALL FUNCTION 'MESSAGE_TEXT_BUILD'
      EXPORTING
        msgid                     = WA_MESSTAB-MSGID
        msgnr                     = WA_MESSTAB-MSGNR
       MSGV1                     = WA_MESSTAB-MSGV1
       MSGV2                     = WA_MESSTAB-MSGV2
       MSGV3                     = WA_MESSTAB-MSGV3
       MSGV4                     = WA_MESSTAB-MSGV4
    IMPORTING
       MESSAGE_TEXT_OUTPUT       = WA_TEXTOUT
    MESSAGE WA_TEXTOUT TYPE 'I'.
    But after this message is executed...the MIGO transaction's message is getting triggered immediately. So my message is not popping up.
    What to do?

    When i debug the program...
    I get the following things..
    wa_messtab-msgid = F5
    wa_messtab-msgnr = 312
    wa_messtab-msgv1 = 100128404
    wa_messtab-msgv2 = XYZ
    wa_textout = Document 100128404 was posted in company code XYZ
    and when i say
    message wa_textout type 'i'.
    at the output a popup window should display information in wa_textout.
    But this is not happening and message of type 'S' is getting displayed...that is standard msg of MIGO
    which is - Material document 5000115652 posted
    I want my custom msg in wa_textout to be displayed first. before the standard MIGO msg.

  • Message not getting displayed in BTE 1030

    I am displaying a message in functional module implemented for BTE 1030.
    The message is not getting diplayed. I have changed the message tyto 'S, I. W, E but still it does not display.  The sy-subrc is 0 after passing the messga statement.
    (The functional module is called normally and not in background)

    Just check your settings in transaction FIBF, and make sure you have choose the right Process Modules(Ususally we choose "of an SAP Application"), and if you have set some other limitation on Country ISO code or Application Indicator, pls make sure all of them have been satisfied.

  • Complete error message not getting displayed

    Hi All,
    I've built a custom webadi integrator which loads into a custom staging table.
    All fine with the webadi but the error messages are getting truncated to only 45 characters. The variable size is 4000 characters and a debug message before RAISE_APPLICATION_ERROR indicates there is no truncation of the message in the PL SQL package.
    Where and how is my message getting truncated?
    Any pointers highly appreciated !

    Hi
    See the sample BADI code for PR which raises an exceptions and do accordingly
    BAdI Name: ZPUR_RFQ (Implementation name) Purchase Requisitions
    Definition Name: ME_REQ_POSTED
    Interface Name : IF_EX_ME_REQ_POSTED
    Implementing Class: ZCL_IM_PUR_REQ
    Method :            POSTED
    METHOD if_ex_me_req_posted~posted .
      DATA : v_mtart TYPE mtart.
      DATA l_s_eban TYPE ueban.
      LOOP AT im_eban INTO l_s_eban.
        IF l_s_eban-estkz NE 'B'.
          CLEAR v_mtart.
          SELECT SINGLE  mtart INTO v_mtart FROM mara WHERE matnr = l_s_eban-matnr.
          IF v_mtart EQ 'ZERS' OR v_mtart EQ 'FHMI' OR v_mtart EQ 'UNBW'.
            MESSAGE e000(zm_msg) WITH 'You are not allowed' 'to create PR for stock items'.
          ENDIF.
        ENDIF.
        IF  l_s_eban-knttp NE 'F' OR l_s_eban-pstyp NE '9'.
          IF l_s_eban-knttp NE 'A'.
            IF ( l_s_eban-pstyp NE '9' AND l_s_eban-pstyp NE 'D' ) 
               AND l_s_eban-matnr EQ space.
              MESSAGE e000(zm_msg) WITH 'You cannot create'
                'a PR without material number'.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDMETHOD.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Message not getting refreshed in bsp pages.

    Hi experts,
    An error message which is getting displayed should be removed on leaving the page. I mean the meassage area is not getting refreshed on leaving the page. Everytime i need to refresh the page to remove it. Please help.
    Abhi.

    hello Friend,
    Please clear the internal table / work are used to show message in OnInitialization method of the BSP page.
    now It is not getting cleared at the time leaving the page and data stays in memory...
    Thanks
    K.

  • Support messages not getting displayed in Messages Tab - Solar01/02

    Hi,
    I am having an issue in displaying the support messages under the message tab of Solar01 and Solar02. If I try to create a new message, the notification pops up and also gets saved. But the message does not get displayed under the tab.
    I can find that the message is properly created through transaction monitor.Even if I try to manually assign the support message number in Messages tab it gives an error saying the number does not exist.We are using SOLMAN 4.0 SP 11.
    Please help. Points will be awarded for useful answers.
    Regards,
    J.Prabananth

    Dear Prabanath,
           I am not too sure you will be able to assign numbers to support messages. Run the report CRM_DNO_MONITOR and get the full number from the report and insert the ticket number in issue messages tab and click on save and go back one screen, it will ask you if you want to save, select yes.
       That worked for me. Recently I have strugged to resolve this. We are on Solman 4.0 SP12. Check if you have all necessary permissions for you and do you have any thing in sm21 or st22 by any chance if the issue is related to support pack ?
         Let me know if there are any issues. I might be able to help you.
    N

  • Support message not getting reflected in Solution manager system

    Hi,
    In satellite system support message is getting created, message number"...." successfully created in service desk.
    When i check in solution manager system in  crm_dno_monitor the message that i created in satellite system is not getting reflected in solution manager. I removed the varients and then executed . The result is still the same.
    Service desk was configured from our Development system (Client 320) to solution manager. I wanted the support desk to work from my another cleint in same system to Solution manager.
    What can be the possible problem.
    Thanks & Regards,
    Balaji.S

    Hi Gurus,
    Issue got resolved, the problem was with the variant which was assigned as default for the tcode.
    Thanks & Regards,
    Balaji.S

  • SMS messages not getting through

    using iOS 5.0.1 on a 3GS.  If I have iMessaging turned on and I text someone who has a phone other than an iPhone, they don't get the text.  I DO have the "Send as SMS when iMessage is unavailable" button checked.  I also DO select the person's mobile phone number, NOT their email, when I'm texting them.  I have experimented several times just now with a friend and they are NOT getting texts from me.  This seems like an awfully basic, awfully serious, awfully annoying bug. 
    I am now in the middle of experimenting to see if I can text at all if it's not iMessaging.  I have turned iMessaging off, and as far as I can tell my texts are STILL not getting through.  So, as far as I can tell, there is no way for me to text now.  What's the problem?
    Rich R.

    @Rich,
    I'm on Fido/Rogers (Canada) not AT&T, so my experience may not be applicable. But I have found in the past that older versions of SIM cards would not work properly in newer phones, and vice versa. Not just iPhones, but in general. SIM cards have different capabilities, varying amounts of internal memory, and different interface specs.  It's plausible that the vintage of SIM that shipped with your 3G (or whatever you had before) might be slightly incompatible with the 3GS.
    Another gotcha that I've encountered is the phone number (server address) of the SMSC that is programmed into the SIM. Large wireless carriers often (usually) have a number of different SMSCs distributed around their network. It's possible that they changed your designated SMSC. If your SIM still points at the old SMSC (and AT&T has moved you to a different one), that might explain your SMS problems. On the other hand, if the SIM you are using is the one that shipped from AT&T with your 3GS, then this is probably a red herring. Still, I think it would be useful to put the SIM into a non-iPhone and see if you can send/receive texts, just to verify that it's not a network problem.
    Programming of the proper SMSC into one's SIM card can be done over the air -- the carrier sends a specially-formatted SMS message to the phone, and the phone then updates the data in the SIM card. You might call AT&T and ask them to do so.
    I'm grasping at straws here. SIM vintage and/or SMSC configuration might have nothing to do with your problem.
    DRC

  • Updateable Snapshot changes not getting propagated

    Hi,
    I am using Oracle 8.1.7 with Updateable snapshot replication. When I do a dbms_snapshot.refresh as the repadmin user from the snapshot site, the changes I made to the table I am refreshing are not pushed to the master site. Also, the update is actually overwritten by the value that exists on the master site.
    Here is the actual refresh call sql:
    EXECUTE dbms_snapshot.refresh('scpa.dag', 'F', NULL, TRUE, TRUE, 1, 0, 0, TRUE);
    What table can I look in to see whether or not my update on the snapshot site is queued.
    I get no errors when I do the refresh.
    Thanks,
    Chris

    Try check deferror view on master site. When you call refresh procedure you set parameter refresh_after_errors to True, so there can be same unresolved replication conflict. In DBA studio it is tab Errors for node
    DB->Replication->Administration
    If there are no record in deferror on master site, check if you snapshot is a member of snapshot group. If not changes is not propagated.

  • JMS message not getting delivered

    I'm trying to create a simple MDB with JDeveloper 10.1.3.2.
    I've tried to configure the sender and receiver to use the embedded OC4J message service.
    The code compiles and runs without any errors but the message doesn't seem to get delivered to the MDB.
    How could I debug message delivery in this case?
    What could be causing the message delivery to fail?
    Here's the code from a session bean that sends the message:
    @Resource(mappedName="jms/Topic/testTCF") private ConnectionFactory connectionFactory;
    @Resource(mappedName="jms/Topic/testTopic") private Topic topic;
    public void sendMessage() {
    try {
    Connection con = connectionFactory.createConnection();
    Session session = con.createSession(true, 0);
    MessageProducer producer = session.createProducer(topic);
    TextMessage msg = session.createTextMessage();
    msg.setText("hello");
    producer.send(msg);
    con.close();
    } catch (JMSException e) { }
    MDB:
    @MessageDriven(activationConfig = {
    @ActivationConfigProperty(propertyName="connectionFactoryJndiName", propertyValue="jms/Topic/testTCF"),
    @ActivationConfigProperty(propertyName="destinationName", propertyValue="jms/Topic/testTopic"),
    @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic")
    public class MessageReceiver1Bean implements MessageListener {
    public void onMessage(Message message) {
    System.out.println("hello");
    Message service configuration:
    <jms-server port="9227">
    <queue location="jms/Queue/testQueue" name="queue"/>
    <queue-connection-factory location="jms/Queue/testQCF"/>
    <topic location="jms/Topic/testTopic" name="topic"/>
    <topic-connection-factory location="jms/Topic/testTCF"/>
    <log><file path="../log/jms.log"/></log>
    </jms-server>

              A few questions to better understand your case,
              1) are you using pub/sub (topics) or ptp (queues) ?
              2) are you producing inside a transaction (either use JTA or jms transacted session)
              3) do you use/set TimeToDeliver parameter ?
              4) when you monitor, do you see your messages under pending count ?
              "Rajiv Kadayam" <[email protected]> wrote:
              >
              >I'm having trouble with the 6.1sp5 version of weblogic specifically with
              >the JMS
              >server not quite notifying my message listeners whenever a new message
              >is received
              >in the queue. I can see the messages via the console by way of clicking
              >"monitor
              >all desitinations". I don't see any exceptions at all. This piece of
              >code does
              >work in Weblogic 7 and it did work on weblogic 6.1sp4. I'm not quite
              >using MDBs
              >and my publishers are CORBA services and there are no EJB components
              >involved.
              >
              >The trouble is there are no exceptions and my message listeners are just
              >waiting.
              >any tips or ideas would be greatly appreciated.
              >
              >thanks
              >rajiv
              

  • Message not getting delivered

    Hi,
    I have created a simple application which sends messages to the channel.
    Here is my channel :
    <?xml version="1.0"?>
    <!--
    A sample channel file
    Change "channelPrefix" and <channel/> elements to customize
    The following namespaces are used in this sample file. These
    namespaces refer to schemas that must be present in a schema
    directory.
    - xmlns:eg=http://www.bea.com/wli/eventGenerator" is used
    for event generator metadata references
    - xmlns:dp="http://www.bea.com/wli/control/dynamicProperties" is
    used by the file event generator to pass payload for pass-by-filename
    - xmlns:oagpo="http://www.openapplications.org/003_process_po_007" is
    used for a sample payload description
    -->
    <channels xmlns="http://www.bea.com/wli/broker/channelfile"
    channelPrefix="/test" >
    <channel name ="test" messageType="string">
    <!-- A simple channel passing XML -->
    <!--
    <channel name ="SampleXmlChannel" messageType="xml"/>
    -->
    <!-- A simple channel passing rawData -->
    <!--
    <channel name ="SampleRawDataChannel" messageType="rawData"/>
    -->
    <!-- A simple channel passing a string -->
    <!--
    <channel name ="SampleStringChannel" messageType="string"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in
    the oagpo namespace -->
    <!--
    <channel name ="SampleOAGPOChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"/>
    -->
    <!-- A channel passing rawData, the rawData is mapped by the
    StockQuotes.mfl file in the schema directory -->
    <!--
    <channel name ="SampleRawDataChannel" messageType="rawData"
    qualifiedRawDataMessageType="urn:StockQuotes.mfl"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element FileEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGFileChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:FileEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element dp:FileControlProperties
    in the po namespace, and the metadata is element FileEventGenerator
    in the eg namespace
    (this is the XML payload used for pass-by-filename in the
    file event generator) -->
    <!--
    <channel name ="SampleEGFileChannel" messageType="xml"
    qualifiedMessageType="dp:FileControlProperties"
    qualifiedMetadataType="eg:FileEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element JmsEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGJmsChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:JmsEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element EmailEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGEmailChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:EmailEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element TimerEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGTimerChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:TimerEventGenerator"/>
    -->
    </channel>
    </channels>
    Issue is whenever I run my application I get following excpetion , please
    let me know what I am missing . I am running weblogic 8.
    Thanks
    Veresh
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <Transaction Rolled
    back in response to exception occurred during async error processing
    javax.ejb.TransactionRolledbackLocalException: Exception in ejbLoad:; nested
    exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLExce
    ption: Lock time out; try later.
    javax.ejb.EJBException: nested exception is: java.sql.SQLException: Lock
    time out; try later.
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handleJDBCObjectResponse(Unknown Source)
    at com.pointbase.net.netJDBCPreparedStatement.executeQuery(Unknown
    Source)
    at
    weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:124)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean$GenericTableAccess.doLoad(BMPContainerBean.java:495)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbLoad(BMPContainerBean.java:1724)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.ejbLoad(ProcessContainerBean.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_Impl.ejbLoad(PersistentContainer_2ktjqj_Impl.java:136)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:324)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:228)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    javax.ejb.EJBException: nested exception is: java.sql.SQLException: Lock
    time out; try later.
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbLoad(BMPContainerBean.java:1776)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.ejbLoad(ProcessContainerBean.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_Impl.ejbLoad(PersistentContainer_2ktjqj_Impl.java:136)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:324)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:228)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    javax.ejb.TransactionRolledbackLocalException: Exception in ejbLoad:; nested
    exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLExce
    ption: Lock time out; try later.
    at
    weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledbackLocal(EJBRuntimeUtils.java:247)
    at
    weblogic.ejb20.internal.BaseEJBLocalHome.handleSystemException(BaseEJBLocalHome.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:233)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Error> <WLI-Core> <BEA-481028> <Failed to
    lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy16.publish(Unknown Source)
    at processes.event1.responsePublishPublish(event1.jpd:119)
    at processes.event1_wf$ImplControlSend4.invoke(event1_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event1_wf$_ProcessState.processMessage(event1_wf.java:177)
    at processes.event1_wf.event1Subscribe_onMessage(event1_wf.java:146)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy17.onMessage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event1BMPContImpl.event1Subscribe$callback(event1BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_4po8lm_ELOImpl.event1Subscribe$callback(PersistentContainer_4po8lm_ELOImpl.java:153)
    at
    com.bea.wlwgen.event1BMPContAdpt.invokeOnBean(event1BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Error> <WLI-Core> <BEA-481028> <Failed to
    lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000>
    <Id=responsePublishEvent; Method=processes.responsePublishEvent.publish();
    Failure=weblogic.jws.
    control.ControlException: [WLI-Core:489317]Failed to publish message to the
    Message Broker due to: com.bea.wli.broker.RepositoryException: [WLI-Core:481
    028]Failed to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    [[WLI-Core:481028]Failed to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    ]>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <Id=responsePublish;
    Method=processes.responsePublish.publish(); Failure=weblogic.jws.control.Co
    ntrolException: [WLI-Core:489317]Failed to publish message to the Message
    Broker due to: com.bea.wli.broker.RepositoryException:
    [WLI-Core:481028]Failed
    to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)

    Same problem here with and I've done everything shy of a total reset which I also find unacceptable. This problem exists on all iMessage platforms (iPhone, iPad, and Mac) so I don't see how restoring my iPhone would help the problem.

  • Message not getting displayed on page

    Hello,
    I have extended a controller and after some validation, i need to display message on top of Page. Please let me know.
    I am not able to display the Message on top of the page; I am able to find the error entry in the log as below
    [23]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Days ====>null
    [23]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Hours ====>18
    [25]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Entering processFormRequest
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:PersonId 13552
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:DurationHours 18
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:NetAccrual 6
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Sql select accrual from pto_bces
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Value true
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Value1 18
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Value2 6
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:ProjectedEndDate 2008-09-10
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Leaving processFormRequest
    [41]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Nextnull
    [42]:EXCEPTION:[kbv.oracle.apps.per.selfservice.loa.webui.MvnCreateAbsenceMainCO]:Hours.null
    [43]:ERROR:[fnd.common.Message.auto_log]:PERMVN_ABS_HOURS_MESSAGENOBJECT_CODE2008-09-10
    Code snippet
    /*try
    if (s!=null)
    if (i < Integer.parseInt(s))
    MessageToken[] tokens = { new MessageToken("OBJECT_CODE",l)};
    OAException message = new OAException("PER", "MVN_ABS_HOURS_MESSAGE", tokens,OAException.INFORMATION, null);
    // OAException message = new OAException("AK", "FWK_TBX_INVALID_EMP_NUMBER", tokens,OAException.INFORMATION, null);
    pageContext.putDialogMessage(message);
    // throw new OAException("PER","MVN_ABS_HOURS_MESSAGE",tokens);
    // OAException message = new OAException("AK", "FWK_TBX_INVALID_EMP_NUMBER", tokens,OAException.INFORMATION, null);
    // pageContext.putDialogMessage(message);
    }

    It displays on the log not on the page
    [174]:ERROR:[fnd.common.Message.auto_log]:PERMVN_ABS_HOURS_MESSAGENOBJECT_CODE2008-09-10
    [174]:ERROR:[fnd.framework.OAException]:Your request cannot be processed since you do not have enough accrued time as of the date you are requesting.
    Code
    if (s!=null)
    if (i < Integer.parseInt(s))
    MessageToken[] tokens = { new MessageToken("OBJECT_CODE",l)};
    OAException message = new OAException("PER", "MVN_ABS_HOURS_MESSAGE", tokens,OAException.INFORMATION, null);
    // OAException message = new OAException("AK", "FWK_TBX_INVALID_EMP_NUMBER", tokens,OAException.INFORMATION, null);
    // pageContext.putDialogMessage(message);
    throw new OAException("PER","MVN_ABS_HOURS_MESSAGE",tokens);
    // throw message;
    // OAException message = new OAException("AK", "FWK_TBX_INVALID_EMP_NUMBER", tokens,OAException.INFORMATION, null);
    // pageContext.putDialogMessage(message);
    }

  • Error Message not getting clear while creation of purchase order

    Hi All,
    I am facing one problem while creating purchasing order.
    I have written one user-exit for purchase order. User has to enter purchase requisition number for certain purchase order type. If he doesn’t enter PR number, we have to throw an error message.
    I have used the MM06E005 for the same. User exit is working fine, but the problem is, all error messages are collected in log and it will be displayed in a dialog screen when you check the document (Transaction ME21N).
    When I enter PR number and check the document, the error message is still there, system is not clearing the error log. I have created “Z” message class and have used in User exit.
    Do you guys have any solution for this? Am I using the right user exit? What should I do to clear the error message?
    If you don’t have answer, please pass it to your friends also….
    Thanks a lot in advance…

    Hi Rob,
    Your inforamtion was good enough to start. thanks a lot for that. I tried to implement the same but no luck this time also.
    FYI..
    The FM exit name is EXIT_SAPMM06E_012 and see the following code, i used.
    TYPES:  BEGIN OF type_my,
            subrc TYPE sysubrc,
            msgid TYPE symsgid,
            msgty TYPE symsgty,
            msgno TYPE symsgno,
            msgv1 TYPE symsgv,
            msgv2 TYPE symsgv,
            msgv3 TYPE symsgv,
            msgv4 TYPE symsgv,
            END   OF type_my.
    DATA:  my TYPE type_my.
    DATA : GV_PO(10) TYPE I.
      if I_EKKO-BSART = 'Z005'.
      GV_PO = I_EKKO-EBELN.
        loop at TEKPO.
          if TEKPO-BANFN is initial.
           message E000(ZBC_MESSAGES) with TEKPO-EBELP.
            my-subrc = sy-subrc.
           my-msgid = sy-msgid.
           my-msgty = sy-msgty.
           my-msgno = sy-msgno.
            my-msgid = 'ZBC_MESSAGES'.
            my-msgty = 'E'.
            my-msgno = '000'..
            my-msgv1 = sy-msgv1.
            my-msgv2 = sy-msgv2.
            my-msgv3 = sy-msgv3.
            my-msgv4 = sy-msgv4.
      Cleaning
            CLEAR:
            sy-subrc,
            sy-msgid,
            sy-msgty,
            sy-msgno,
            sy-msgv1,
            sy-msgv2,
            sy-msgv3,
            sy-msgv4.
      Generate message
            mmpur_message my-msgty my-msgid my-msgno
            my-msgv1 my-msgv2 my-msgv3 my-msgv4.
      Remove message from message list
            mmpur_remove_messages_by_id GV_PO.
          endif.
        endloop.
    It is still not working. Moreover i don't have PO number at run time.
    I hope this clarify the problem in more detail.
    Meanwhile i am searching for OSS as suggested by Michael Bennett.

Maybe you are looking for

  • Picture not showing up (although somehow present)

    Hello! Iphoto is behaving very strange on older fotos that were imported way long time ago: - Events aren't sorted by date: There's a first block of events with newer pictures which get sorted correctly, then things get messy: 2006 follows 2012, back

  • Ever since updating to Mountain Lion, I cannot watch live streams.

    Hey, since updating to ML, something seems to be interrupting how Flash is working. I am unable to see live video streams in the browser. When I try to use VOKLE, for example, it seems to load fine and then I get an error from Vokle telling me to mak

  • Regarding SAP integration modules

    Hi all, My client is interested to implement SAP for shipping project. The system should be able to cater jetty, container terminals, Finance, HR, Logistics, Warehouse etc. It should also be able to integrate with multiple legacy systems developed ea

  • Reference to all ApplicationModule

    Is there a way to get a reference to all ApplicationModules of the system used (by name maybe), so I can call rollback or commit on each one. I need away different than the following way: return (ApplicationModule)JSFUtils.resolveExpression("#{data."

  • Receive error messaage when loading pogo fb connect library is missing (all.js) but will load fine on chrome

    the website loads fine, but when loading the message [ fb connect library is missing (all.js) ] appears and i cannot select a room for play. i downloaded chrome and I no longer received the message, which led me to believe that the firefox browser mu