Move to error queue after certain redelivery limit

Hi,
          I am newbie to Weblogic. I am currently using Weblogic8.1.4.
          I have written an MDB say mdbx which listens on a specific queue say QA, once it receives a message it will send this message to another queue QB. I have configured the queue QA such that it will try to redeliver the message 3 times to QB, if it fails in its first attempt. I have also configured an error queue to which the message should finally be placed when all the 3 attempts fails.
          My problem is, i find the redelivery limit and error queue i have configured for queue QA doesn't take effect. Please help me to resolve this.
          More Info:
          I am trying to send message from mdbx on the onMessage() method.
          Thanks and Regards
          A.SathishKumar

Please refer : http://www.javaoracleblog.com/java/How_to_set_minimumDelayBetweenMessages_for_delay_between_messages_for_JCA_adapters.jsf

Similar Messages

  • Roll back process after certain time limit

    Hi All,
      I am using Oracle 11g. I am calling one stored procedure (MainProc) from my application. Through this procedure I am calling internally three more procedure (Insert recordProc1, InsertRecordProc2 and DeleteRecProc).
    The third stored procedure (DeleteRecProc) is taking more than 5 minutes. But if these process crossings more than 5 minutes, have to stop the process and roll back all three stored procedures functions.
    I don’t have any commit statement inside of these stored procedures. But I have EXECUTE IMMEDIATE Inside of stored DeleteRecProc.
    Help required: Help me to make a counter / Timer. I have a parameter, which has the assigned time limit. How to check whether the process crossing the time limit? How to stop the process and call Rollback?
    Thanks in advance.
    Manian

    Don't know if this helps your situation.
    http://docs.info.apple.com/article.html?artnum=301579
    here is the entire thread
    http://discussions.apple.com/message.jspa?messageID=1237801#1237801

  • Best way to configure redelivery limit value for a Queue

    Hello,
    My doubt is related to configuring the JMS Redelivery Limit property from Weblogic 9.2 Server.
    We must support redelivery attempts in our queue, with a redelivery delay of 30s. So, we have set the queue's Redelivery Limit property to -1, via Console Configuration:
    Settings for My_DQueue -> Delivery Failure -> Redelivery Limit = -1
    The consumer of that queue is a MDBBean, which extends org.springframework.ejb.support.AbstractJmsMessageDrivenBean.
    The producers to that queue are weblogic.jms.extensions.WLMessageProducer.
    That queue has an error queue configured as Error Destination.
    Then, the WLMessageProducer is the one who specifies that value:
    WLMessageProducer messageProducer = (WLMessageProducer)queueSession.createProducer(queue);
    messageProducer.setRedeliveryLimit(5);However, we will not be able to ensure that all message producers pointing that queue will specifiy that redelivery limit. This may lead us to problems, as default queue Redelivery Limit is set to -1, and messages without specified redelivery limit would be redelivered indefinitely.
    I'd like to know if there is any way to specify a MAXIMUM redelivery limit value for a JMS queue. For example: fixing that limit to 10. If producers specify by themselves a redelivery limit lower than such value, that limit is applied to messages. Otherwise, the configured default limit value is used.
    Another option we have considered is to include, in the MDB's onMessage() method, a validation of the "JMS_BEA_RedeliveryLimit" message property:
    This validation would check whether no redelivery limit is configured in the Producer, and would forward such messages directly to the error queue, from the MDB, when the "JMSXDeliveryCount" outnumbers our fixed value:
    public void onMessage(Message message) {
       try {
          if(message.getIntProperty("JMS_BEA_RedeliveryLimit")<0){
             //MESSAGE FOUND WITHOUT REDELIVERY LIMIT SPECIFIED BY PRODUCER.
             //POTENTIAL DANGER OF BEING REDELIVERED INDEFINETELY
             int deliveryCount = message.getIntProperty("JMSXDeliveryCount");
             if(deliveryCount>10){
                 //CAN I FORWARD MESSAGE TO ERROR DESTINATION?But we were not able to found such examples to achieve this
    Thanks in advance!
    Joan Esteve

    Hi Joan,
    I just double-checked, and as far as I can tell the options for setting a redelivery limit include programmatically on the Producer or by configuring an override on the Destination. Unfortunately, you need the override to only take effect if the delivery limit hasn't already been set. (If we had a default deliverylimit configurable on our connection factory, this would have done the trick.)
    I think you've already hit upon the solution: your consumers can check each received message's JMSXDeliveryCount and act accordingly. It's fine for a consumer to use the JMS_BEA_RedeliveryLimit property see if the Limit has been set by a producer, and then check JMSXDeliveryCount to check the delivery count, but I'm not sure if the JMS_BEA_RedeliveryLimit property is set in older versions (8.1 may not have it for example).
    As a refinement, you may want to use the WLMessageProducer forward() API. This is an alternative to send() that preserves the message-id and timestamp of a consumed message. I don't think forward() allows any modification of the consumed message before it's forwarded.
    Hope this helps,
    Tom
    Edited by: Tom B on Feb 22, 2013 10:03 AM

  • Elements 11:  After selection tool defines move area, error message reads "No pixels are more than 50% selected".  How to remedy?

    Elements 11:  After selection tool defines move area, error message reads "No pixels are more than 50% selected".  How to remedy?

    Are you certain that you are on the correct layer?
    As a test, try this:
    Select the object with one of the selection tools, e.g. lasso, selection brush.tool. You should see "marching ants" once the selection is complete
    Place the selection on its own layer (Layer>new>layer via copy or CTRL+J). This will place the object on a separate layer.
    With this layer active, use the move tool to move/position it
    Does that work?

  • I'm getting an error -42110 after the download of the rental movie, anyone ??

    Hi there, i'm getting an error (-42110) after i finish the download of the rental movie on itunes.
    it won't let me play the movie.
    anyone would know?
    cheers

    i learned that if i buy the same movie again,after repairing that issue, then the movie plays just fine.
    pay pay pay...
    Ack. Check to see if you can get a refund for the first rental. Under "Video purchases" click "Rental" and click the "Email us" button:
    http://www.apple.com/support/itunes/

  • TS1702 I renteda movie (the last song) after 13 minutes it stopped and I recieved the following message "AN UNKNOWN ERROR OCCURRED (-50)". What can I do?

    I rented a movie (The last song) after 13 minutes it stopped and I recieved the following message "AN UNKNOWN ERROR OCURRED (-50)" .
    What can I do in this case?

    Perhaps try the "Error -50," "-5000," "8003," "8008," or "-42023" section in the Specific Conditions and Alert Messages: (Mac OS X / Windows) section of the following document:
    iTunes: Advanced iTunes Store troubleshooting

  • Was downlading a movie rental i purchsed after a while my internet got disconected and the download now has two errors and not succesfull download can you please help. :)

    WAS DOWNLOADING A MOVIE RENTAL I PURCHASED AFTER A WHILE MY INTERNET GOT DISCONNECTED AND I AM TRYING TO SEE IT AGAIN. CAN SOMEONE HELP ME?

    Erin I am sorry you are facing difficulty downloading the Creative Cloud software.  It can be frustrating when you do not have access to high speed stable Internet.
    You can attempt to download the base installers and updates by following the directions listed at:
    Adobe CC 2014 Direct Download Links: Creative Cloud 2014 Release | ProDesignTools
    All Adobe CC 2014 Updates: The Direct Download Links for Windows | ProDesignTools
    You may want to attempt to utilize some form of download management as the main issue seems to be the stability of your connection.
    There is not currently a method to resume downloads within the Creative Cloud Desktop application.  There is download management included though it may not be enough to compensate for the current Internet connection.  If you are curious you can find additional details on how to resolve download errors at Error downloading Creative Cloud applications - http://helpx.adobe.com/creative-cloud/kb/error-downloading-cc-apps.html.

  • Memory requirement is continiously increased when i am running my application program in an infinite loop,after certain time it shows an error called low virtual memory

    memory requirement is continiously increased when i am running my application program in an infinite loop,after certain time it shows an error called low virtual memory

    What are you doing with your program. Lots of improper programming techniques can cause this - building arrays, concantanating strings, opening but not closing refrences, etc. Need more details or post your VI. Also, have you looked at "LabVIEW Performance and Memory Management"? It's part of the shipping documentation and available from Help>Search the LabVIEW Bookshelf.

  • Error message after downloading and install rolled back (using up data limit)

    error message after completing install of trial. then program was rolled back. I do not appreciate using up data allotment unnecesarily, people.Thanks for any assistance.

    Rhumsike which Adobe software or service are you trying to install?  Also which operating system are you using?  Finally what is the error message which you are receiving?

  • Messages are not moving to Error Queue in OSB if Error is Raised

    Hi All,
    My OSB process is as below.
    Queue1-->OSB-->Queue2.
    OSB Proxy is listening to the Queue1.When messages comes to Queue1 Proxy will pick the message and after applying the business logic it will put the message to Queue2.
    If OSB is not able to deliver the message succesfully to Queue2 then it should retry for 2 times.If retry exhausted then the message should move to the error Queue.
    I have configured Queue 1 with delivery failure paramaters redelivery limit and redelivery delay.Also the Connection factory is XA enabled.Even if any error happens (i am not using reply activity in the error handler) its retrying infinitely and messages are not coming to the error Queue.If i use reply activity its not retrying its failing at first time and the message is moved out of the main Queue1.
    Can any one please help me on this?
    Thanks.
    Edited by: 892479 on Dec 21, 2011 6:31 AM

    Since the messages are getting retried, it means that messages are getting rolled back to Queue1 when any errors happen. So transactional behavior is configured correctly.
    Now the problem yu face is that the messages are not moving to error queue.
    Make sure that you have configured following in the delivery failure tab of the queue>
    Redelivery Delay Override - delay in miliseconds between retries
    Redelivery Limit - number of retries
    Expiration Policy - Redirect
    Error Destination - Choose the error queue here
    After that make sure that the Server is restarted, even though a server restart sign is not mentioned on the config page, some of these settings might not take effect without a restart.

  • How to configure a error queue for weblogic jms topic

    Hi guys.
    I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
    1. using jms transport configure proxy service:
    Retry Count :3
    Retry Interval:10
    Error Destination: ErrorTopic
    Expiration Policy: Redirect
    I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
    Any suggestions for this topic? Can anyone provide some helps or any useful links.
    Thanks in advance.
    Mingzhuang

    Mingzhuang
    I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
    1. using jms transport configure proxy service:
    Retry Count :3
    Retry Interval:10
    Error Destination: ErrorTopic
    Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
    http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
    http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
    I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
    Let me know if we are not on same page.
    Cheers
    Manoj

  • Redelivery limit not working for transaction timeout?

    hi,
              we have a redelivery limit on a queue that works, except for when there is a transaction timeout. in this case, the message seems to be redelivered infinitely. Is this a bug? a feature?
              we are using Weblogic Server 8.1 SP4. we don't have the source code, so i am not sure how the error handling is done or what exceptions are thrown.
              ------------------ejb-jar.xml------------
              <message-driven>
              <ejb-name>ImporFileReceiver</ejb-name>
              <ejb-class>au.com.auspost.pcms.common.integration.ejb.mdb.ImporFileReceiverMdb</ejb-class>
              <transaction-type>Container</transaction-type>
              <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
              <message-driven-destination>
              <destination-type>javax.jms.Queue</destination-type>
              <subscription-durability>NonDurable</subscription-durability>
              </message-driven-destination>
              </message-driven>
              <container-transaction>
              <method>
              <ejb-name>ImporFileReceiver</ejb-name>
              <method-intf>Local</method-intf>
              <method-name>onMessage</method-name>
              <method-params>
              <method-param>javax.jms.Message</method-param>
              </method-params>
              </method>
              <trans-attribute>NotSupported</trans-attribute>
              </container-transaction>
              <container-transaction>
              <method>
              <ejb-name>ImporFileReceiver</ejb-name>
              <method-intf>Remote</method-intf>
              <method-name>onMessage</method-name>
              <method-params>
              <method-param>javax.jms.Message</method-param>
              </method-params>
              </method>
              <trans-attribute>NotSupported</trans-attribute>
              </container-transaction>
              ------------------------ weblogic-ejb-jar.xml ---------
              <weblogic-enterprise-bean>
              <ejb-name>ImporFileReceiver</ejb-name>
              <message-driven-descriptor>
              <pool>
              <max-beans-in-free-pool>10</max-beans-in-free-pool>
              <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>jms/pcmsImportFileQueue</destination-jndi-name>
              <connection-factory-jndi-name>jms/pcmsConnectionFactory</connection-factory-jndi-name>
              </message-driven-descriptor>
              <transaction-descriptor>
              <trans-timeout-seconds>3600</trans-timeout-seconds>
              </transaction-descriptor>
              <reference-descriptor>
              </reference-descriptor>
              <dispatch-policy>pcms.execute.queue.mdb.internal</dispatch-policy>
              <remote-client-timeout>0</remote-client-timeout>
              </weblogic-enterprise-bean>
              ------------------------ config.xml -----------------
              <JMSServer Name="eParcel JMS server"
              Store="eParcel JMS Server File Store" Targets="wls_pcms_prod1">
              <JMSQueue CreationTime="1190981682976"
              ErrorDestination="PCMS Import File Error Queue"
              JNDIName="jms/pcmsImportFileQueue"
              Name="PCMS Import File Queue" RedeliveryLimit="2"/>
              <JMSQueue CreationTime="1208347415759"
              JNDIName="jms/pcmsImportFileErrorQueue" Name="PCMS Import File Error Queue"/>
              </JMSServer>
              <JMSConnectionFactory JNDIName="jms/pcmsConnectionFactory"
              Name="eParcel JMS Connection Factory" Targets="wlc_pcms_prod"/>
              <JMSConnectionFactory JNDIName="jms/pcmsXAConnectionFactory"
              Name="eParcel JMS XA Connection Factory" Targets="wlc_pcms_prod" XAConnectionFactoryEnabled="true"/>
              -------------- weblogic log ---------------
              ####<24/04/2008 01:53:58 PM EST> <Warning> <EJB> <HX415> <wls_pcms_prod1> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <project_admin> <> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
              javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 3599 seconds
              Name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)],Xid=BEA1-696C9947A48195BA18DC(68926234),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3599,seconds left=60,activeThread=Thread[ExecuteThread: '12' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@447373e,re-Registered = false),SCInfo[wlsd_auspost_prod+wls_pcms_prod1]=(state=active),properties=({weblogic.transaction.name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)], weblogic.jdbc=t3://10.3.2.35:7003}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+, XAResources={JMS_eParcel JMS Server File Store, weblogic, wlsd_auspost_prod, com},NonXAResources={})],CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+)
              at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(I)V(ServerTransactionImpl.java:1614)
              at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Ljava/util/List;I)V(ServerTransactionManagerImpl.java:1117)
              at weblogic.transaction.internal.TransactionManagerImpl.wakeUp()V(TransactionManagerImpl.java:1881)
              at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp()V(ServerTransactionManagerImpl.java:1034)
              at weblogic.transaction.internal.WLSTimer.trigger(Lweblogic/time/common/Schedulable;)V(WLSTimer.java:31)
              at weblogic.time.common.internal.ScheduledTrigger.run()Ljava/lang/Object;(Optimized Method)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(Optimized Method)
              at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
              at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
              at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:223)
              at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
              at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
              at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
              ; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 3599 seconds
              Name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)],Xid=BEA1-696C9947A48195BA18DC(68926234),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3599,seconds left=60,activeThread=Thread[ExecuteThread: '12' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@447373e,re-Registered = false),SCInfo[wlsd_auspost_prod+wls_pcms_prod1]=(state=active),properties=({weblogic.transaction.name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)], weblogic.jdbc=t3://10.3.2.35:7003}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+, XAResources={JMS_eParcel JMS Server File Store, weblogic, wlsd_auspost_prod, com},NonXAResources={})],CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+).

    Thanks Tom,
              Good point. The timeout exception is on ImportFileHandlerBean.handleMessage()....which is a session bean. The MDB must call this session bean, which also has a 3600 second timeout. It is confusing since the descriptor for the MDB has the transaction-timeout set, but i assume this is ignored for 'not-supported').
              I guess you would need to look at the code, but is there anyway a message go back on the queue, and not get the redelivery incremented?
              (I just had an evil thought...maybe the code could be physically sending the message onto the queue again when there is a timeout on the session bean.....hence would not get the redelivery incremented.....)
              -------------- ejb-jar.xml ----------------
              <session>
              <ejb-name>ImportFileHandler</ejb-name>
              <local-home>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocalHome</local-home>
              <local>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocal</local>
              <ejb-class>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean</ejb-class>
              <session-type>Stateless</session-type>
              <transaction-type>Container</transaction-type>
              </session>
              ----------- weblogic-ejb.jar.xml -----------
              <weblogic-enterprise-bean>
              <ejb-name>ImportFileHandler</ejb-name>
              <stateless-session-descriptor>
              </stateless-session-descriptor>
              <transaction-descriptor>
              <trans-timeout-seconds>3600</trans-timeout-seconds>
              </transaction-descriptor>
              <reference-descriptor>
              </reference-descriptor>
              <enable-call-by-reference>True</enable-call-by-reference>
              <local-jndi-name>ejb/ImportFileHandlerLocal</local-jndi-name>
              <remote-client-timeout>0</remote-client-timeout>
              </weblogic-enterprise-bean>

  • Distributed Destinations and Error Queues

              I have a distributed queue - distqueue which is configured with two queue members
              - srvr1q
              and srvr2q. srvr1q is a physical queue destination that is running on JMSServer1
              on one instance in a cluster. srvr2q is a physical queue destination that is running
              on JMSServer2 on another instance in the cluster. I have two errorqueues - srvr1errq
              and srvr2errq - deployed on JMSServer1 and JMSServer2 respectively. I have configured
              the srvr1q to the following:
              Redelivery Delay Override: 10000
              Redelivery Limit: 3
              Error Destination: srvr1errq
              Also the srvr2q is configured to the following:
              Redelivery Delay Override: 10000
              Redelivery Limit: 3
              Error Destination: srvr2errq
              There is an MDB listening to each one of these local queues. The MDB is programmed
              to throw a null pointer exception (to simulate business logic processing failures)
              My expectations are : the message goes to one of the local queues. Null Pointer
              exception is thrown. After 10 seconds the message is resent to the same queue
              with a similar fate. After the third attempt, the message is moved to the error
              queue of the corresponding local queue.
              What I see is the following:
              When I send a message I do see a Null Pointer Exception, but it occurs only once
              and I dont see the message going to the error queue. Since my Load Balancing policy
              is Round-Robin on the distqueue, the local queues receive the message every other
              time with the same result - Null Pointer Exception thrown only once.
              I also have JMSStores configured so the messages are persistent.
              Can someone explain to me what I am doing wrong?
              Thanks.
              

              "Prakash Muthukrishnan" <[email protected]> wrote:
              >
              >Hi Tom
              > Thanks again for the reply. I do use a tx MDB. I have set the transaction-type
              >to Container in the message-driven stanza in ejb-jar.xml. And also the
              >trans-attribute
              >for that EJB in the container-transaction stanza, I have used Required.
              >Do I need
              >to setup anything else ?
              I don't think so.
              > The transaction descriptor element in the weblogic-enterprise-bean
              >stanza in weblogic-ejb-jar.xml for that MDB is empty.
              Not sure what you mean?
              > Am I missing anything
              >else?
              Container & Required is all that is needed
              If you like, post your ejb descriptor xml file, and I'll take a quick
              look to double-check.
              >-Prakash
              >
              >Tom Barnes <[email protected]> wrote:
              >>Hi Prakash,
              >>
              >>A runtime exception should force a rollback for tx MDBs, and
              >>a recover for non-tx MDBs. If you are seeing different
              >>behavior there may be a bug in WL.
              >>
              >>Since MDBs do not log an exception when the app throws
              >>a Runtime exception, I often recommend wrapping the
              >>application code in a try catch anyhow
              >> try {
              >> } catch (Throwable t) {
              >> log
              >> force rollback
              >> }
              >>I think there are plans to provide a configurable that
              >>optionally does something similar in the next release (no guarantees).
              >>(The problem is that some apps throw a runtime on purpose, and
              >>could quickly flood the log if such runtimes were logged per message.)
              >>
              >>Tom
              >>
              >>Prakash Muthukrishnan wrote:
              >>> Tom
              >>> Thanks for the suggestion. Using the setRollbackOnly method did the
              >>trick. This
              >>> brings up
              >>> a related question: What if a run time exception was thrown during
              >>the processing
              >>> in an MDB?
              >>> Is it not retried and ultimately shoved into the error queue?
              >>> Thanks again.
              >>> -Prakash
              >>>
              >>>
              >>> Tom Barnes <[email protected]> wrote:
              >>>
              >>>>Hi Prakash,
              >>>>
              >>>>At first glance, it doesn't seem like your doing anything wrong.
              >>>>Could you post your release and SP level, as well as your config.xml?
              >>>>
              >>>>How many messages did you send through?
              >>>>
              >>>>Note that for transactional MDBs it is best to call "setRollbackOnly"
              >>>>on the EJB context rather than throwing an NPE. This is because
              >>>>throwing a runtime exception forces the MDB to destroy itself and
              >>>>get re-initialized (pretty high overhead). For non-transactional
              >>>>MDBs, throwing a runtime exception is your only option.
              >>>>
              >>>>Tom, BEA
              >>>>
              >>>>Prakash Muthukrishnan wrote:
              >>>>
              >>>>
              >>>>>I have a distributed queue - distqueue which is configured with two
              >>>>
              >>>>queue members
              >>>>
              >>>>>- srvr1q
              >>>>>and srvr2q. srvr1q is a physical queue destination that is running
              >>>>
              >>>>on JMSServer1
              >>>>
              >>>>>on one instance in a cluster. srvr2q is a physical queue destination
              >>>>
              >>>>that is running
              >>>>
              >>>>>on JMSServer2 on another instance in the cluster. I have two errorqueues
              >>>>
              >>>>- srvr1errq
              >>>>
              >>>>>and srvr2errq - deployed on JMSServer1 and JMSServer2 respectively.
              >>>>
              >>>>I have configured
              >>>>
              >>>>>the srvr1q to the following:
              >>>>>
              >>>>>Redelivery Delay Override: 10000
              >>>>>Redelivery Limit: 3
              >>>>>Error Destination: srvr1errq
              >>>>>
              >>>>>Also the srvr2q is configured to the following:
              >>>>>Redelivery Delay Override: 10000
              >>>>>Redelivery Limit: 3
              >>>>>Error Destination: srvr2errq
              >>>>>
              >>>>>There is an MDB listening to each one of these local queues. The
              >MDB
              >>>>
              >>>>is programmed
              >>>>
              >>>>>to throw a null pointer exception (to simulate business logic processing
              >>>>
              >>>>failures)
              >>>>
              >>>>>My expectations are : the message goes to one of the local queues.
              >>>>
              >>>>Null Pointer
              >>>>
              >>>>>exception is thrown. After 10 seconds the message is resent to the
              >>>>
              >>>>same queue
              >>>>
              >>>>>with a similar fate. After the third attempt, the message is moved
              >>>>
              >>>>to the error
              >>>>
              >>>>>queue of the corresponding local queue.
              >>>>>
              >>>>>What I see is the following:
              >>>>>When I send a message I do see a Null Pointer Exception, but it occurs
              >>>>
              >>>>only once
              >>>>
              >>>>>and I dont see the message going to the error queue. Since my Load
              >>>>
              >>>>Balancing policy
              >>>>
              >>>>>is Round-Robin on the distqueue, the local queues receive the message
              >>>>
              >>>>every other
              >>>>
              >>>>>time with the same result - Null Pointer Exception thrown only once.
              >>>>>
              >>>>>I also have JMSStores configured so the messages are persistent.
              >>>>>
              >>>>>Can someone explain to me what I am doing wrong?
              >>>>>Thanks.
              >>>>
              >>>
              >>
              >
              

  • Error Compiling Movie: Unknown Error - Simple Solution in Premiere

    ADOBE PREMIERE EDITORS: Be forewarned about the infamous "Error Compiling Movie: Unknown Error." It usually doesn't happen unless you're editing a big project like I am and then it screws with you because you've been editing fine until it's time to export and you can't even make your project into a movie, which defeats the purpose of all your hard work. I looked up forum after forum and finally there were a-few solutions that worked for some and not for others. (Adobe said they will get their team on this case right away.) Let's just say I do not have Final Cut Pro, so I cannot export to XML and then import into FCP to do the exporting like some people found helpful. Nor do I have the time to import my Premiere project into After Effects only to manually create all of my "dip to white" transitions. But I would have had to do that if nothing else I tried worked and thankfully, I was able to trick Premiere. It's so simple, it's stupid. Just open a new project in Premiere. Then "import" the project you wanted to export. For some odd reason, without changing anything of substance or in other words, doing practically nothing about the issue, it exports now. Just because I opened a "new" project and "imported" my old project. Of course, this may not work for others, but please try it and then reply your results. Me and I'm sure Adobe would find it very helpful to see if that worked for most people. It worked for me.
    [Profanity is not permitted.  Removed.  Please keep your language family-friendly.]

    I agree, Jim, but my train of thought was that a lot of people were changing and replacing and taking out effects and clips from their sequence to see if it was the components in the sequence that was causing the "unknown error." However, I had the same "unknown error" and was able to export in Premiere anyway by just practically "telling" Premiere that it's a new project, when I'm importing an old project to do the same task. Which makes me think that maybe Premiere doesn't have a problem exporting the specific files that most people thought were the problem, maybe it was just a glitch somewhere in Premiere that made the software think there was a problem after a certain amount of time, when there really wasn't. I don't know, I'm not a coder so that's just my layman guess. I did notice that Premiere was exporting/rendering fine when I was just beginning my project, but after it got to a certain length, that's when I couldn't render or export anymore. It honestly baffles me too. It would be useful to see what the results are if other people tried this simple switch-a-roo so possible issues can be narrowed down.

  • Have the problem to export media use the queue after the latest update of Premiere and Media encoder?

    After update the Premiere CC 2014 and Encoder CC 2014, I couldn't export the movie use the Queue function?
    There always had a unknown error stop the process. (Compile error?)

    You need to fix that first.
    Export and preview in the Media Encoder and watch when it stops.
    There you need to fix the timeline.
    Start a new project to see if you can use AME.

Maybe you are looking for

  • Searching artwork for only one song at a time

    When I use the "Get Artwork" feature in iTunes it searches my entire library for artwork that i'm missing (which i don't think it does a very good job at it anyway). this takes too long and just isn't what i want. Is there a way to have it only seach

  • Sender communication channel

    Hi..    We were doing File to File scenario. In that we have to give 2 physical files as input and one output. InputFile1---Name,Place InputFile2----Id,company Outputfile----Name,Place.Id,company. Can this scenario is possible without using bpm? And

  • Trading Partner Offline

    Sometimes Trading Parntners may go off-line during maintenance windows. Does B2B provide any feature where all the outbound messages for the Offline Trading parner can be parked aside . Finally when the Trading Parner goes online, parked outbound mes

  • PeView open large pdf File very slowly!

    I have a pdf file with 422M,On the OS 10.9 preview it very easy,very fast and no noise with fan. when updated OS 10.10,preview it very slowly, the fan more fast and more noise,why? it's back!

  • Handeling Null value using Essabse cube.

    Hi Gurus, I am new to OBIEE with Essabse cube. I have imported the cube and develop the report. I have flatened the measure. Everything is working fine. When i had a report request to have the Organisation and the Period Hierarchy along with the Meas