Publish directly on an error destination

Hi,
          is it possible to publish directly on an error destintation ?
          my test fails so i was wondering if it was possible
          Thanks for any help,

Sure, no problem. An error destination is just a regular JMS destination, so you can send to it directly or receive from it directly.

Similar Messages

  • Messages in JMS Topic Error destination

    Hi,
    I have a JMS Topic with an error destination queue configured. Now, In our scenario , there are two subscribers of topic for the same message. Suppose for a message published to topic, subscriber1 is able to processes message successfully but subscriber2 throws errors when processing the same message.
    1. Once the redelivery limit is reached and subscriber2 continues to throw exception, Will the message get en queued to Error Destination (in spite of the fact that subscriber 1 has processed the same message successfully) ?
    2. For a consumer (e.g MDB) listening to Error destination and consuming error messages, Is it possible to determine which topic subscriber was unable to process the message ?
    Please let me know
    Regards,
    Arif

    Here it depends on the state of the message, if the message is visible then the message would be available for consumption, else it is not. In case the subscriber 2 failed to consume the message and the message is still visible then a retry would be made, else the message would not be retried.
    In case the message is visible then the message would be move to the error queue based on the configured redelivery attempts.
    Additionally, an MDB can find the destination using the getJMSDestination() call. But as per my understanding we will only be able to get the name of the last destination which in this case would be error queue:
    http://docs.oracle.com/javaee/1.4/api/javax/jms/Message.html#getJMSDestination%28%29

  • Error destination for durable subscribers

    We want to use the publish/subscribe mechanism for application
              integration purposes. We have one application publishing a message on
              a topic and multiple application that have a durable subscription on
              that topic.
              We want to control the redelivery process for an individual
              subscriber. When the number of retries is exceeded for a particular
              message it is sent to the error destination for that application. This
              allows us to fix the problem in the application (whatever it was) and
              resubmit the message to the application.
              We can set the Error Destination and control the redelivery process
              for both Topics and Queue. But is it also possible to define an error
              destination and redelivery process for individual durable
              subscriptions?
              Cheers,
              Mark van Holsteijn
              PS: My reference material is MQ en TUXEDO/Q. In both MQ and TUXEDO/Q
              you subscribe a specific Queue to a topic giving you both an error
              destination and redelivery control.
              

              Mark van Holsteijn wrote:
              > Tom,
              >
              > Thanks for the swift confirmation. Would it not be a handy enhancement
              > to the WebLogic JMS provider?
              >
              > About TUXEDO: tpsubscribe() lets you subscribe a queue in a queue space
              > to an event using the option TPEVQUEUE. See
              > http://edocs.bea.com/tuxedo/tux81/rf3c/rf3c81.htm#1045667
              >
              That isn't really the same animal as pub/sub - the above call redirects
              an event subscription to a particular Q, where each Q has to be manually
              configured. If my understanding is correct,
              you could emulate the same thing in WebLogic with just a little
              bit of work: configure multiple queues, and write an EJB
              method that redirects information to a particular Q based on the value
              of one of its parameters (or write an MDB that does a similar
              thing.)
              > Cheers,
              >
              > Mark
              >
              >
              > Tom Barnes wrote:
              >
              >> Mark van Holsteijn wrote:
              >>
              >>> We want to use the publish/subscribe mechanism for application
              >>> integration purposes. We have one application publishing a message on
              >>> a topic and multiple application that have a durable subscription on
              >>> that topic.
              >>>
              >>> We want to control the redelivery process for an individual
              >>> subscriber. When the number of retries is exceeded for a particular
              >>> message it is sent to the error destination for that application. This
              >>> allows us to fix the problem in the application (whatever it was) and
              >>> resubmit the message to the application.
              >>>
              >>> We can set the Error Destination and control the redelivery process
              >>> for both Topics and Queue. But is it also possible to define an error
              >>> destination and redelivery process for individual durable
              >>> subscriptions?
              >>
              >>
              >>
              >> No.
              >>
              > Thanks for the confirmation.
              >
              >>>
              >>>
              >>> Cheers,
              >>>
              >>> Mark van Holsteijn
              >>>
              >>> PS: My reference material is MQ en TUXEDO/Q. In both MQ and TUXEDO/Q
              >>> you subscribe a specific Queue to a topic giving you both an error
              >>> destination and redelivery control.
              >>>
              >>
              >> I think I know what you are referring to in MQ,
              >> but Tux/Q has no pub/sub capability.
              >>
              >
              > Chec
              >
              >> Tom, BEA
              >>
              >
              

  • Problem creating JMS Error Destination via Ant in WLS 8.1

    We've got several JMS queues in our application. We create the server via Ant (using the wlconfig task).
    All is well, the queues have been working fine, until we try to add an error destination queue (after several attempts to handle the message, it'll be sent to the error queue for later troubleshooting).
    Here's an example of what we've got now:
    <create type="JMSQueue" name="batchQueue" property="jmsqueue">
        <set attribute="JNDIName" value="net.nike.cdm.batchQueue"/>
        <set attribute="RedeliveryLimit" value="5"/>
    </create>We create another queue to handle the errors, and then add an attribute to the first to point to the second:
    <create type="JMSQueue" name="batchErrorQueue" property="batchErrorQueue">
        <set attribute="JNDIName" value="net.nike.cdm.batchErrorQueue"/>
        <set attribute="RedeliveryLimit" value="5"/>
    </create>
    <create type="JMSQueue" name="batchQueue" property="jmsqueue">
        <set attribute="JNDIName" value="net.nike.cdm.batchQueue"/>
        <set attribute="RedeliveryLimit" value="5"/>
        <set attribute="ErrorDestination" value="${batchErrorQueue}"/>
    </create>This seems logical, because if we do this same exact operation via the console, the config.xml goes from this:
    <JMSQueue JNDIName="net.nike.cdm.batchQueue"
                Name="batchQueue" RedeliveryLimit="5"/>to this:
    <JMSQueue ErrorDestination="batchErrorQueue"
                JNDIName="net.nike.cdm.batchQueue"
                Name="batchQueue" RedeliveryLimit="5"/>
    <JMSQueue JNDIName="net.nike.cdm.batchErrorQueue" Name="batchErrorQueue"/>The error we get when trying to do this via Ant is:
    [wlconfig] A destination and its ErrorDestination must both be on the same JMS server. (The problematic destination is "batchQueue" on JMS server "cdmdomain"). Also, an ErrorDestination can not be null if the ExpirationPolicy for a destination is "redirect" and a destination can not specify itself as its ErrorDestination.Flipping on -verbose in Ant, the actual exception is:
    [wlconfig] SET -mbean cdmdomain:Name=batchQueue,Type=JMSQueue -property ErrorDestination cdmdomain:Name=batchErrorQueue,Type=JMSQue
    [wlconfig] A destination and its ErrorDestination must both be on the same JMS server. (The problematic destination is "batchQueue"
    s its ErrorDestination.
          [if] Error in class net.sf.antcontrib.logic.IfTask
    BUILD FAILED
    file:C:/viewstore/CDM_R6.5_Development/B2B_CDM/dev/build.xml:1399: Error invoking MBean command: java.lang.NullPointerException
           at weblogic.ant.taskdefs.management.WLConfig.handleException(WLConfig.java:567)
           at weblogic.ant.taskdefs.management.WLConfig.invokeCommand(WLConfig.java:381)
           at weblogic.ant.taskdefs.management.WLConfig.invokeSetCommand(WLConfig.java:235)
           at weblogic.ant.taskdefs.management.WLConfig.invokeCreateCommand(WLConfig.java:163)
           at weblogic.ant.taskdefs.management.WLConfig.executeCommands(WLConfig.java:106)
           at weblogic.ant.taskdefs.management.WLConfig.invokeCreateCommand(WLConfig.java:167)
           at weblogic.ant.taskdefs.management.WLConfig.executeCommands(WLConfig.java:106)
           at weblogic.ant.taskdefs.management.WLConfig.execute(WLConfig.java:89)
           at org.apache.tools.ant.Task.perform(Task.java:341)
           at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:117)
           at org.apache.tools.ant.Task.perform(Task.java:341)
           at net.sf.antcontrib.logic.IfTask.execute(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 org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:147)
           at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
           at org.apache.tools.ant.Task.perform(Task.java:341)
           at org.apache.tools.ant.Target.execute(Target.java:309)
           at org.apache.tools.ant.Target.performTasks(Target.java:336)
           at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
           at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
           at org.apache.tools.ant.Main.runBuild(Main.java:609)
           at org.apache.tools.ant.Main.start(Main.java:196)
           at org.apache.tools.ant.Main.main(Main.java:235)So, my question is, what are we doing wrong? What IS the syntax to set an error destination for a JMS queue via Ant for WLS 8.1?
    Any help would be greatly appreciated
    Thanks,
    Douglas Bullard

    I get exactly the same problem - was a resolution to this issue found?
    Thanks,
    Richard Marriott
    [email protected]

  • Direction Not Available Error -ios6

    Maps are not working on my iphone4 after ios6 upgrade I am getting "Direction Not Available" error even though it is able to search the place if I just give search. I was using maps successfully with ios5. Please let me know what is the solution.

    I am also facing the same prob..in UAE. is there any solution?

  • Error Destination in JMS Transport Configuration page (Proxy Services)

    Hi, Can anybody provides me the sample of Error Destination in JMS Transport Configuration page (Proxy Services) .I need to know the format. I am using "jms://<host:port[,host:port]*/factoryJndiName/destJndiName>", but it does not work.
    From Oracle webstie, http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html, the detail description of Error Destination is " In this field you can configure the name of the target destination for the messages, which have reached the maximum number of retry count. "

    Can you provide the JNDI name of the error destination alone there ?

  • Distinguishing between messages in the error destination

    Hi,
              First of all, I'm using Weblogic 8.1 SP4.
              I recognize that messages are delivered to the error destination if one of two situations occur:
              1) The message has reached the redelivery limit.
              2) The message has expired.
              In my message-driven bean that picks up messages from the error destination, I need to know the reason why a message ended up there. That is, I need to know whether it was expired or the redelivery limit was reached.
              Is this possible?
              Thanks in advance!
              Henrik Oddershede

    The JMS chapter of the book "Professional Oracle WebLogic Server" has a nice discussion of poison message handling.
    In your case, I'd recommend adding code to your inbound queue processing application to detect bad format messages and automatically redirect them to a separate queue for manual intervention. This would avoid mixing up the bad format messages with your automatically handled problem messages. You could then write a specialized application that your administrator can use to process the messages.
    Tom

  • JMS Error destination..

    Hi,
    I am developing a JMS application where i am processing message in a Queue and configured redelivery delay and redelivery limit. When the maximum redelivery limit has reached, i will move the message to an error destination which is again a Queue. I can send an email to the administartor with the message information indicating that the processing for the message has failed. But the requirment is, the administrator wants to view the message from the persistent store and resubmit the message. Is it possible? If that is the case what can be value for time-to-live for the message? I am using ServiceBus 10.3 and using the underlying weblogic server as JMS provider. Besides, i have a question on the relationship between redelivery delay, redelivery limit and time-to-live override. When i tested, if time-to-live is less than the redeliverylimit*redelivery delay, then will the message be deleted and the redelivery limit(number of retries) is not taking into effect. But if time-to-live is greater than also the message is deleted after maximum retry means time-to-live doesn't have effect. This means i am i right to say, if i specify time-to-live and there is no need to specify redeliverylimit and redelivery delay. If that is the case on what basis, the retry is made?
    Thanks in advance for your replies,
    Sam

    Hi,
    I am using ServiceBus 10.3 and using the underlying weblogic server as JMS provider. I think OSB tends to decorate JMS messages with its own private information, so I don't know if it can support arbitrarily moving them between destinations. You may be better off posting to an OSB specific forum.
    But the requirment is, the administrator wants to view the message from the persistent store and resubmit the message. Is it possible? That said, you can view, delete, move, and file import/export WebLogic JMS messages using the message management screens on the console. If you need a more sophisticated capability than the console provides, it is possible to write Java or WLST program's for the purpose.
    If you're interested in scripting, the following might be enough to get you started:
    For scripting and tracing examples, see the July 29th and August 10th 2009 newsgroup post with subject "Example using of getMessage(s) with JMS error queues?" [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3657916] and the June 10th 2009 newsgroup post with subject "JMSDestinationRuntimeMBean - possible STATE values " [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3531603 ]. Also take a look at the +Sept 23 2009 newsgroup posts with subject "Enable JMS - Queue/Topic Trace on console"+ [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3782486].
    +WARNING: Exporting too many messages at a time can cause out-of-memory errors.+
    Besides, i have a question on the relationship between redelivery delay, redelivery limit and time-to-live override. When i tested, if time-to-live is less than the redeliverylimit*redelivery delay, then will the message be deleted and the redelivery limit(number of retries) is not taking into effect. But if time-to-live is greater than also the message is deleted after maximum retry means time-to-live doesn't have effect. This means i am i right to say, if i specify time-to-live and there is no need to specify redeliverylimit and redelivery delay. If that is the case on what basis, the retry is made?By definition, an expired message is automatically deleted -- no matter what the delivery count is. If you want expired messages to be automatically redirected to a destinatin's error destination you can configure an "expiration policy" of "redirect" on the destination.
    Whether you want to use message expiration, redelivery limit, or redelivery delay very much depends on your specific use case.
    -- Redelivery limits detect messages that are rolled back many times by receiving applications (rollbacks can occur due to any number of reasons, such as database failure, application bug, etc.)
    -- Redelivery delays prevent rolled back messages from being immediately redelivered. This helps prevent zooming up CPU usage to 100% with tight loop retries of processing a problem message, assumes that whatever condition caused the original rollback is temporary, and assumes that if the message is immediately redelivered that this is too soon for the problem condition to have cleared up.
    -- Expiration detects if a message has been sitting around for a long time. It doesn't detect whether the application has attempted to process the message...
    In general, if you are coding a new application, it is sometimes helpful to avoid error destinations. Instead, let your application decide what to do with problem messages (such as queue them to another destination). This helps your application provide more customizable behavior.
    Hope this helps,
    Tom
    PS Especially for developers new to WebLogic JMS, I highly recommend purchasing a copy of the book "Professional Oracle WebLogic". In addition, I recommend reading the new "Best Practices" chapter of the JMS configuration guide, and the new "Tuning Checklist" in the JMS chapter of the Performance and Tuning guide. These new sections are in the 10.3.2 documentation.

  • Redirection of expired message to error destination topic.

              We are using weblogic 7.0 for JMS. We have two topics topic A and topic B. When
              a message gets expired in TopicA, we want this to be redirected to an error destination
              that is configured to Topic B. This is not working for us for Non durable subscribers.
              Is there anyway to find out the messages that are expired before delivered to
              the destination?
              Thanks for any help.
              Sudeer
              

    Good timing!
              Message redirection of expired messages is a new feature available in
              8.1. This feature is not available in 7.0.
              8.1 has been out for a few weeks now.
              Tom, BEA
              Sudeer wrote:
              > We are using weblogic 7.0 for JMS. We have two topics topic A and topic B. When
              > a message gets expired in TopicA, we want this to be redirected to an error destination
              > that is configured to Topic B. This is not working for us for Non durable subscribers.
              >
              > Is there anyway to find out the messages that are expired before delivered to
              > the destination?
              >
              > Thanks for any help.
              >
              > Sudeer
              

  • When attempt to publish, I get an error

    I have several flash files linked to one page of my Muse site.  When I attempt to publish I get an error
    that says I have lost contact with the server, and try later.  This has been going on for 2 days.  Always happens when the flash files are attempting to load.
    Thank you.
    Kevin

    Hi Aish;
    Here is the screen print from the error that I received. 
    I was publishing to Business Catalyst. 
    Thank you for the help.
    Kevin
    239-829-0416

  • Published directly to YouTube - edited footage - How do I update?

    I've used imovie 08 to publish directly to YouTube which works very well though decided I wanted to edit and update the file, and read the short info in their help files regarding further edits to files which states:
    If you make further edits to your project in iMovie after you’ve published it to YouTube, the title bar indicates that your project is out of date and needs to be rendered again. Old versions of the movie are deleted and replaced by new ones when you render it again.
    If you want to save the previous version of your movie before you edit it, you can do so by exporting it to the Finder.
    Not exactly very helpful, so I edited footage of said file and clicked on Share > YouTube using the exact same file name, description and keywords, only to find that I had posted another copy onto YouTube.
    Can anyone explain how to update (render) the footage already published to YouTube rather than creating a new file???
    Any help on this is much appreciated!

    Connect to iTunes on the computer you usually Sync with and “ Check for Updates “...
    See the Using iTunes Section Here...
    How to update your iPhone, iPad, or iPod touch
    The Current iOS version of iOS 6.1.3 will be Installed.

  • Original destination for messages redelivered to error destination

              Hi,
              I'm writing an admin interface for our system and one part of it needs to manage
              redelivery of messages. We have multiple destinations, and I have configured
              one queue to act as an error queue for them all. My plan had been to allow users
              to resubmit messages to their original destination - but I dont have that information.
              Message.getDestination() returns my error queue, which makes sense. I was hoping
              there'd be a header I could extract that might contain the name for of the original
              destination, but I dont seem to be able to find it.
              The only thing I can think of is to have a separate error queue for each destination,
              this would allow me to assume that all messages were initially sent to the corresponding
              queue - but it seems a little heavy handed... does anyone else have a better solution?
              cheers
              dim
              

    Sorry Dmitri, I mixed up names here.
              "Adarsh Dattani" <[email protected]> wrote in message
              news:[email protected]...
              > Terrence,
              >
              > Check out the "Error Destination Manager" sample app at
              > http://dev2dev.bea.com before you write a lot of code. I have already the
              > built the admin facility that you are talking about and have also included
              > the source code and documentation with it. Let me know if you need any
              help
              > with it.
              >
              > AD
              >
              > "Dmitri Colebatch" <[email protected]> wrote in
              message
              > news:[email protected]...
              >
              > >
              > > Hi,
              > >
              > > I'm writing an admin interface for our system and one part of it needs
              to
              > manage
              > > redelivery of messages. We have multiple destinations, and I have
              > configured
              > > one queue to act as an error queue for them all. My plan had been to
              > allow users
              > > to resubmit messages to their original destination - but I dont have
              that
              > information.
              > > Message.getDestination() returns my error queue, which makes sense. I
              > was hoping
              > > there'd be a header I could extract that might contain the name for of
              the
              > original
              > > destination, but I dont seem to be able to find it.
              > >
              > > The only thing I can think of is to have a separate error queue for each
              > destination,
              > > this would allow me to assume that all messages were initially sent to
              the
              > corresponding
              > > queue - but it seems a little heavy handed... does anyone else have a
              > better solution?
              > >
              > > cheers
              > > dim
              > >
              >
              >
              

  • The user Directory publishing service reported an error

    Some but not all of my users get this error when trying to
    connect to my CPS managed server:
    Directory publishing service reported an error.
    Error Details: End of file or no input:'Operation interupted
    or timed out'
    I've deleted, and recreated the users, but they get the same
    error. The users connect via file share, and are located at one
    site where this occours?
    Any hints would be greatly appreciated.

    Hi,
    The corresponding entry MAC is available in the following
    file:
    <User>/Library/Preferences/Contribute 4.1 preferences.
    Please open this file and search for the following entry,
    "cps notification repsonse timeout" This is under the
    [SETTINGS] in the file.
    Please note that this entry gets created only when some
    actions (for example Publish) are performed after connecting to CPS
    Thanks,
    Radhika

  • External App published directly

    Hi,
    I need to publish Yahoo mail to my portal home. I managed to configure it as external app and published it as a link. My question is:
    Can an external app be published directly to the portal instead of a link?
    Any help is appriciated.

    The new URL services in the PDK may allow you to do this. You can find information on these new services on the Portal Page on OTN. Click on the PDK link. Note that the URL services require 3.0.8 of the portal.

  • Cannot publish to MobileMe.   Error says, "iWeb couldn't connect to MobileMe. Make sure your Internet connection works and try again."  Connection is OK!

    My site will publish to a folder, but will not publish to MobileMe.   Error says, “iWeb couldn’t connect to MobileMe. Make sure your Internet connection works and try again.“  Connection is OK!

    Thank you Alancito for your reply.  The recent post you suggested was not necessary because another of your suggestions did the trick:  https://discussions.apple.com/message/11503337#11503337  In effect, it seems to have reestablished my connection to my MobileMe account, and my iWeb site now publishes on MobileMe. 
    My next step will be to transfer my iWeb site to another Personal Web Provider when MobileMe ceases to exist next June.  Any recommendations for a simple PWP?
    Thank you very much,
    William Oglesby

Maybe you are looking for