Redirecting failed messages to other consumers of distributed queue

Hi,
We have a simple cluster with two servers A and B, each hosting one MDB whose task is to consume message from a distributed queue and forward them to an EIS via a JCA resource adapter. Server B acts as a failover server. If the resource adapter is unable to deliver the message, the MDB will throw a runtime exception and the message will therefore be redelivered. In order to achieve high-availability, we have configured the distributed queue to send the redelivered message to an error destination (dead-letter-queue DLQ). The DLQ again has another instance of the MDB as a consumer with a different resource adapter.
Using DLQs is working fine as a high-availability mechanism when the MDB is unable to deliver the message to the EIS, but is this a common or valid approach?
An alternative to using DLQs would be to configure weblogic to send redelivered message to other consumers on the distributed queue. The problem we have is that the failed message always gets redelivered to the same MDB (i.e. the MDB which consumes messages but throws an exception because the resource adapter fails). Is it somehow possible to configure the MDB or even change the MDB code to notify weblogic to send the failed message to another consumer of the distributed queue? Would the MDB be able to disconnect the JMS connection when throwing the exception and if so, would the disconnection cause the application server to deliver the message to another consumer?
Many thanks

Thanks Tom,
Setting the distributed-destination-connection property to EveryMember seems to be exactly what we need to allow other distributed queue member to consume the message which has been put back on the queue after a rollback. In order to ensure that it won't be the same MDB consuming the failed message again, we would have to temporarily suspend the MDB. From what I read, one approach is to sleep the MDB after throwing the runtime exception (but is this possible, i.e. is it not going to interrupt the onMessage before going to sleep?). I also read that there is a new property from WLS 9.0 onwards to automatically stop the MDB for a certain time after an exception has ocurred, how can I configure this? Are we also going to have to set the MDB pool size to 1 in order to ensure that the message gets consumed by an MDB on a different server?
We have also tried to use a non-collocated approach instead using a collocated approach with distributed queues but we end up with the same problem that a message does not get redelivered to MDBs on other servers after a runtime exception has been thrown.
Thanks a lot

Similar Messages

  • Message payload logging for Uniform Distribute Queue

    Hi All,
    We have a requirement to log the message payload, of every jms message received in a Uniform Distribute Queue in Weblogic.
    Please let us know how can we achieve this.
    Thanks.

    If you want to avoid use of the Path Service, then the alternative is to make the destination members highly available. This will help ensure that the host member for a particular UOO is up.
    One approach to HA is to configure "service migration". For more information see the Automatic Service Migration white-paper at
    http://www.oracle.com/technology/products/weblogic/pdf/weblogic-automatic-service-migration-whitepaper.pdf
    In addition, I recommend referencing Best Practices for JMS Beginners and Advanced Users
    http://docs.oracle.com/cd/E17904_01/web.1111/e13738/best_practice.htm#JMSAD455 to help with WL configuration in general.
    Hope this helps,
    Tom

  • Consumers for distributed queues -- writing the JMS API

    Hi,
    I have Created a cluster MS_01 and MS_02.
    JmsServer-MS01 for MS_01 and JmsServer-MS02 for MS_02.
    Also have create a distributed queue called DistributedQueue-0 and a distributed connection factory called ConnectionFactory-0.
    I have been successfully able to loadbalance sending of messages using the cluster address.
    When i try to consume messages the consumers gets pinned to a MS_01. (As expected)
    I am looking for ways where in using JMS API i can read messages from both the manages instances.
    Appreciate any help.
    thanking you all in advance.
    Regards
    Girish Subbaramu.

    Hi,
    For consuming messages from a distributed queue, by far the best option is to use a WebLogic MDB, which has internal code designed to work well with WebLogic distributed destinations. When a distributed queue runs in the same cluster as the MDB, the MDB service will ensure that there's an MDB deployment instance that is locally servicing each queue member -- even when the queue members migrate between servers, or when they are added or removed due to configuration changes. When the MDB is communicating with a distributed queue in a remote cluster, an MDB running on a single server will automatically set up consumers for each remote member and will dynamically react to member up/down add/remove events.
    If you must use a straight javax.jms client, then I think there are two basic options. The first option is to ensure that that there are more than enough consumers to provide full coverage, and periodically close and re-open the consumers. The periodic close and re-open forces the consumers to load-balance again, and therefore helps handle the case when new destination members become available after the consumers have all attached. The second option is to create consumers directly on each member rather than on the distributed queues logical name (each member has a unique name that's advertised in JNDI).
    Hope this helps,
    Tom

  • Message Listener Listening to only 1 queue in distributed queue setup!

    Hi guys,
    This may be the wrong place to place this post.
    We created a message system with OSB proxies moving messages back and forth between distributed queues. After all this shuffling messages around, the messages end up in a distributed queue where a java client is waiting to pick up results. Our problem is, it's only reading one of the queues in this distributed queue.
    The following is the code segment that waits for the message with a specific id:
    public Message receiveMessage(String queueName, String messageId) throws FrameworkException {
    BytesMessage bytesMessage = null;
    if (null == queueSession) {
    init();
    try {
    Queue receiveQueue = lookupQueue(queueName);
    QueueReceiver queueReceiver = null;
    String selector =null;
    if (null == messageId) {
    queueReceiver = queueSession.createReceiver(receiveQueue);
    } else {
    selector = "JMSCorrelationID = '" + messageId + "'";
    queueReceiver = queueSession.createReceiver(receiveQueue, selector);
    bytesMessage =(BytesMessage) queueReceiver.receive();
    queueReceiver.close();
    }catch{...
    Will queueReceiver.receive() listen to every member in a distributed queue (spread across 2 managed servers in a cluster)?
    Thanks alot

    Yes, the uniform distributed queue should be available on all targeted servers, providing that the jms module has been targeted to all of the OSB servers, and that your java app ( .war file? ) is targeted to both.
    You can stop the java application so that messages remain in the queue "long enough" for you to see them from within the WL console. Then you can shutdown nodes in your cluster individually, so conform that the message is truly being distributed. Then the issue is whether the java app is reading from the entire distributed queue instead of just one node.
    When you use the monitoring tab on your queue, do you see a queue entry for each jms server ( each mgd server needs one )?
    Or is the issue that the java client is only reading from one server?

  • JMS Server on a cluster stores all  msgs posted to Distributed Queue on 1 server failure

              Hi
              I have a Cluster setup with 2 managed servers srvr1 & srvr2 each running its own
              JMS server.
              Product version in use is Weblogic SP2.
              Configured a Distributed Queue and deployed it on both the JMS servers.
              Set the load-balancing to round-Robin and Server-Affinity to False on the connection
              factory.
              The producer is an external client which posts 100 messages to the Distributed
              queue.
              Consumers are MDBs pinned to the respective physical queues on the respective
              JMS servers.
              Each server has its own store.
              Once 100 messages are posted to the Distributed Queue. The messages are distributed
              to
              the 2 Physical Destinations equally i.e 50-50 each.
              While the MDBs are processing the msgs, server srvr1 is brought down at a point
              when it has consumed only 10 of its 50 msgs.
              When the srvr1 is brought up again, i am finding that the store for that JMS server
              contains the 40 unprocessed msgs in its physical queue + the msgs on the other
              queue that were unprocessed at the time this server crashed.
              When srvr1 went down, srvr2 was running and it went on to process all its 50 msgs
              completly. Why would those processed msgs show up again when srvr1 is brought
              up ?
              Please provide some input !!
              Ravi.
              

              The log message is from the distributed destination
              "forwarders". In distributed queues, these forwarders
              automatically move messages from queues without
              consumers to queues that have them (queue
              forwarders are disabled by default). In distributed topics,
              the forwarders serve
              to replicate a published message from the local
              topic member to each of the remote topic members.
              "Raviprasad Athivilli" <[email protected]> wrote:
              >
              >Tom
              >
              >I think you are right. When the server1 is brought up again, its picking
              >up all
              >the messages
              >that were written to the store.
              >
              >But as it starts processing them, i get this exception on the server2
              >that has
              >been running from the beginning.
              >
              ><Oct 10, 2003 6:20:19 PM EDT> <Error> <JMS> <040366> <JMS Distributed
              >Destination
              >member "MyQueue@JMSServer-02" in "MyQueue"
              >unable to accept connection from remote member "MyQueue@JMSServer-01"
              >due to exception
              >weblogic.jms.common.JMSException: can't find
              >queue target jndi table for MyQueue@JMSServer-01 != MyQueue
              >weblogic.jms.common.JMSException: can't find queue target jndi table
              >for MyQueue@JMSServer-01
              >!= MyQueue
              > at weblogic.jms.backend.BEDestination.setupSystemSubscription(BEDestination.java:3466)
              > at weblogic.jms.backend.BEManager.sessionAndTopicSubscriberCreate(BEManager.java:234)
              > at weblogic.jms.backend.BEManager.invoke(BEManager.java:384)
              > at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:602)
              > at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:152)
              > at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncFuture(DispatcherImpl.java:396)
              > at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
              >Source)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
              > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
              > at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:821)
              > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
              > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
              >
              >What does this mean ?
              >
              >Ravi.
              >Tom Barnes <[email protected]> wrote:
              >>Seems more than odd. Are you sure that q1 got unprocessed
              >>messages from q2? How did you confirm?
              >>
              >>Perhaps q1 got messages its MDB already processed back again -
              >>an indication that the MDB is throwing Runtime exceptions
              >>or Errors, and the container is rolling back transactions.
              >>
              >>Raviprasad Athivilli wrote:
              >>> Hi
              >>>
              >>> I have a Cluster setup with 2 managed servers srvr1 & srvr2 each running
              >>its own
              >>> JMS server.
              >>> Product version in use is Weblogic SP2.
              >>> Configured a Distributed Queue and deployed it on both the JMS servers.
              >>> Set the load-balancing to round-Robin and Server-Affinity to False
              >>on the connection
              >>> factory.
              >>>
              >>> The producer is an external client which posts 100 messages to the
              >>Distributed
              >>> queue.
              >>> Consumers are MDBs pinned to the respective physical queues on the
              >>respective
              >>> JMS servers.
              >>> Each server has its own store.
              >>>
              >>> Once 100 messages are posted to the Distributed Queue. The messages
              >>are distributed
              >>> to
              >>> the 2 Physical Destinations equally i.e 50-50 each.
              >>>
              >>> While the MDBs are processing the msgs, server srvr1 is brought down
              >>at a point
              >>> when it has consumed only 10 of its 50 msgs.
              >>>
              >>> When the srvr1 is brought up again, i am finding that the store for
              >>that JMS server
              >>> contains the 40 unprocessed msgs in its physical queue + the msgs
              >on
              >>the other
              >>> queue that were unprocessed at the time this server crashed.
              >>>
              >>> When srvr1 went down, srvr2 was running and it went on to process
              >all
              >>its 50 msgs
              >>> completly. Why would those processed msgs show up again when srvr1
              >>is brought
              >>> up ?
              >>>
              >>> Please provide some input !!
              >>>
              >>> Ravi.
              >>
              >
              

  • JMS Timestamp in a Uniform Distributed Queue on Weblogic Console

    Dear Experts,
    I should need a clarification on how JMS Timestamp is valorized in a Uniform Distributed Queue. I explain me better :
    I will use the JMS Timestamp to re-order messages fetched from the Uniform Distributed Queue. Is it reliable ? How can I synchronize the this JMS property to be sure it is not dependent from physical machine where Uniform Distributed Queue is deployed ?
    Thanks a lot,
    Mike

    Try posting this in the weblogic jms forum : WebLogic Server - JMS where you might get help from Tom Barnes who is the weblogic jms development team lead.
    As far as I know time synchronization across machines should be a routine task for system admins. We had windows environment , where it was done using windows time service. The time server was configured on the domain controller and the time service running on the windows nodes periodically resynchronized its time with that of the time server.

  • Trying to update Photoshop 5 Camera Raw. Get message installation failed. No other information. Please advise.

    Trying to update Photoshop 5 Camera Raw. Get message installation failed. No other information. Please advise. Running Windows 7 64 bit on Dell Precision m4500. 8G 500G. Is there an alternative way to update the camera profiles in ACR. I am trying to add a Nikon D750 and Canon Powershot G15.

    you can update ps cs5 manually:, http://www.adobe.com/downloads/updates/
    but you can only update to cr 6.7 and that camera needs 8.7 or better.
    your options are to upgrade your ps or use the dng converter, Adobe - Adobe Camera Raw and DNG Converter : For Windows : Adobe DNG Converter 8.7

  • How can I redirect all messages to 2 another mail servers?

    Hi all
    ./imsimta version
    Sun Java(tm) System Messaging Server 7.3-11.01 64bit (built Sep 1 2009)
    libimta.so 7.3-11.01 64bit (built 19:54:45, Sep 1 2009)
    I wanted to redirect all messages(in and out) to another mail server, I configured as follows,
    - imta.cnf
    ! tcp_local
    tcp_local smtp mx single_sys ....... sourcefilter file:///backother.filter
    ! tcp_intranet
    tcp_intranet smtp mx single_sys ....... sourcefilter file:///backother.filter
    - backother.filter
    require ["fileinto"];
    if address :all :matches ["From"]["*"]{
    redirect "[email protected]";
    keep;
    stop;
    One e-mail account receives all messgaes and those messages will be kept in sender's or receiver's mail storage.
    I want , however, redirect all messages 2 or 3 mail servers.
    I tried several things to do this include edit backother.filter(this is written in Sieve ), but I failed.
    Is there any way to redirect messages to another mail servers?
    Any way would be good , using sieve script, make antoher channel or channel keyword
    Thanks
    Edited by: leeky41 on Mar 9, 2010 10:58 PM
    Edited by: leeky41 on Mar 9, 2010 11:06 PM
    Edited by: leeky41 on Mar 9, 2010 11:07 PM

    leeky41 wrote:
    Redirecting the message means it will not be delivered to the original recipient.I know so I wrote 'keep' keyword to deliver messages to the original recipient.
    capture "[email protected]";
    I tested it but the capture's behavior was very weird, subject had changed to something like,'deliverd status notice', sender had changed to postmaster and additional notice messgae inserted into mail body.The default sieve capture action encapsulates the email to keep a copy of both the envelope information and the original message. MS7u3 also supports the Exchange journal encapsulation format through the addition of the ":journal" parameter.
    I edited 'capture' like this..
    capture :message "[email protected]";
    The ":message" flag removes the encapsulation -- therefore you will have no idea of who the original sender/recipients were as the envelope information has been discarded.
    It worked fine. It was same as the result of 'redirect'.
    but the following line, sent10 messages to each recipients.(receive_01,receive_02)
    capture :message "[email protected],[email protected]";
    maybe there was some 'loop' actions happened.The email produced by the capture sieve action is being "captured" which is resulting in a loop. You can stop this by adding an envelope test e.g.
    require ["envelope"];
    if not envelope :is ["to"] ["[email protected]","[email protected]"]
            capture :message "[email protected]";
            capture :message "[email protected]";
    }Regards,
    Shane.

  • Messages in Distributed Queue remain on one JMSServer in Cluster

    Hi,
              the situation is as follows:
              We're having Distributed Queues on a two-Node server setup. A queue therefore exists two times, once on each JMSServer on each node.
              Forward-Delay has been set on the DistibutedQueue to value 1 second (we tested with values 0 and 10, too).
              External Java client (both cluster nodes in the provider_url for initialcontext) connects to the DistributedQueue and sends messages. In the weblogic console you can see these messages on the physical queue on the JMSServer, let's call it QueueA on NodeA.
              An external java process to consume messages (again both clusters nodes in the jndi-connection-string) is started to consume messages. Because of round-robin it sometimes get's connections to QueueB (part of same DistributedQueue as QueueA, but on the other node in the cluster).
              When connected to QueueB on NodeB no single message is received. You can even see in the weblogic console that QueueA on NodeA has zero consumers and 50 messages, QueueB on NodeB has zero messages but one consumer.
              When we restart the consumer java process and it randomly get's connected to QueueA on NodeA it consumes fine, as it should.
              Should'nt Forward-Delay do exactly this? Transport messages from QueueA on NodeA with zero consumers to QueueB on NodeB which actually has consumers?
              Any help would be appreciated.
              Axel van Lil

    Hi,
              thanks for your answer. We opened a support case today for this issue... I don't know. Cluster seems to run fine, no warnings, no exceptions.
              The next step of this issue is the following (just to give an idea of our upcoming problems :-)
              External Java process listens on QueueA on NodeA (QueueA is part of a Distributed Queue). Currently receives all the messages located on that queue. We kill NodeA on that machine to simulate failover.
              The external process failovers immediately to NodeB (which is good! proven by netstat and debugger) but just doesn't receive messages even though there are messages in that queue! It seems that the new consumer is just being forgotten by the BEA server.
              I don't know... somehow our configuration is quirked... or the BEA implementation doesn't work at all...
              Rgds,
              Axel

  • SubmitEditData() - redirect fails...

    Hi,
    I've got a weird error.
    In the portlet customization code (JSP) I call the PortletRendererUtil.submitEditData() method. I managed to get it work before, and does work for all my other portlets, but doesn't for the recent one.
    Although, all the customization values are sent to and saved by the personalization manager, the browser doesn't get redirected to the edit renderer JSP page. It starts to display a kind of page with the logos etc. on the top of it instead.
    This portlet shares the provider with some other customizable portlets. I'd appreciate any ideas how I could track down this issue.
    Thanks,
    Peter
    Snippets of my provider.xml:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <?providerDefinition version="2.0"?>
    <!DOCTYPE provider [
    <!ENTITY virtualRoot "/changeMe/">
    <!ENTITY physicalRoot "C:\Change\Me">
    ]>
    <provider class="oracle.portal.provider.v1.http.DefaultProvider">
    <session>true</session>
    <useOldStyleHeaders>false</useOldStyleHeaders>
    <portlet class="oracle.portal.provider.v1.http.DefaultPortlet">
    <id>5</id>
    <name>Number2Image</name>
    <title>Number2Image - JSP portlet</title>
    <description>This is a simple JSP portlet converting numbers to images.</d
    escription>
    <timeout>30</timeout>
    <timeoutMessage>JSP number2image portlet example timed out</timeoutMessage
    >
    <acceptContentType>text/html</acceptContentType>
    <showEdit>true</showEdit>
    <showEditDefault>false</showEditDefault>
    <showDetails>true</showDetails>
    <showPreview>true</showPreview>
    <hasHelp>true</hasHelp>
    <hasAbout>false</hasAbout>
    <renderer class="oracle.portal.provider.v1.RenderManager">
    <contentType>text/html</contentType>
    <appPath>/jspportlet</appPath>
    <appRoot>/private/oracle/9iAS_1022/Apache/Apache/htdocs/jportlets/ilt_demo/jsp/</appRoot>
    <showPage>number2image.jsp</showPage>
    <helpPage>number2image_help.html</helpPage>
    <editPage>number2image_edit.jsp</editPage>
    </renderer>
    <personalizationManager class="oracle.portal.provider.v1.FilePersonalizationManager" >
    <dataClass>portlets.demo.jsp.Number2ImagePersonalization</dataClass>
    </personalizationManager>
    </portlet>
    <provider>

    I have partial page rendering in all pages with af:showOneTab. So, to prove if redirect failure is related to PPR. I picked one page with af:showOneTab and got rid of all components with PPR so that it became PPR free. However, redirecting still fails if user clicks on any other tab of af:showOneTab after session has expired.
    If user clicks say on any of the crumbs presented on the page to navigate to parent pages, the redirect succeeds and he is successfully pushed to home page.
    Long story short, redirect fails whenever user clicks on any of the af:showOneTab tabs after session has expired no matter if page has or has no PPR components.
    I hope I answered your questions.
    I know that af:showOneTab uses PPR and that may explain why redirect isn't working, not sure. However, I wish we can have a workaround for this problem.
    Any thoughts ?
    Thanks
    Sam
    Message was edited by:
    samsam

  • Disregard Certain Delivery failed MEssages

    I have messaging server 5.2 (Patch 2)
    I have setup a channel filter that forwards (keep;redirect;) all mail to an external email archive server (It bcc's it), and thats working fine.
    I am aware that if the email_archive server goes offline, that the emails may be returned to sender with a "Delivery Notification: Delivery has failed" message.
    Is their a way to discard those? Keep in mind that I only want to disregard the ones that have failed going to the email_archive server.
    Thanks

    mrMerclyn wrote:
    I have messaging server 5.2 (Patch 2)
    I have setup a channel filter that forwards (keep;redirect;) all mail to an external email archive server (It bcc's it), and thats working fine.
    I am aware that if the email_archive server goes offline, that the emails may be returned to sender with a "Delivery Notification: Delivery has failed" message.
    Is their a way to discard those? With MS6.3 you could use the "capture" sieve keyword instead of redirect.
    The "capture" keyword changes the envelope sender to be the postmaster address and therefore any bounces go back to the postmaster rather then the 'original' sender e.g.
    capture :message "[email protected]";
    Keep in mind that I only want to disregard the ones that have failed going to the email_archive server.I tried a few combinations of filters/mapping rules to achieve this with iMS5.2 but without any success. So at this juncture I suggest you go with either Jay's suggestion if you don't want to upgrade to MS6.3 or the capture sieve option if you do upgrade.
    Regards,
    Shane.

  • Using Firefox 19.0 WIFI logon fails page redirect fails

    Attempting to use Firefox at a variety of airports and hotels fails. The initial logon page is displayed but then the following pages which are redirects fail. Usual message is "Page not Found" Using the captive IP address does not work. Various combinations of settings do not work. AP has been associated and an optimum MTU has been determined via ping to the default gateway.

    You should not need to disable antivirus to connect.
    I assume you are not having Firefox block all redirects. You can check that setting here:
    orange Firefox button ''or'' classic Tools menu > Options > Advanced > General > ''uncheck'' "Warn me when websites try to redirect or reload the page"
    What are your connection/proxy settings in Firefox? If you choose "Use system proxy settings" then Firefox should use IE's settings. Or if you choose "No proxy" then Firefox should default to your wi-fi connection.
    orange Firefox button ''or'' classic Tools menu > Options > Advanced > Network > "Settings" button
    Can you think of any add-on changes you might have made since the T-Mobile days? A standard diagnostic to bypass interference by extensions (and some custom settings) is to try Firefox's Safe Mode.
    First, I recommend backing up your Firefox settings in case something goes wrong. See [[Backing up your information]]. (You can copy your entire Firefox profile folder somewhere outside of the Mozilla folder.)
    Next, restart Firefox in Firefox's Safe Mode ([[Safe Mode]]) using
    Help > Restart with Add-ons Disabled
    In the dialog, click "Start in Safe Mode."
    If you can load sites normally, this points to one of your extensions or custom settings as the problem.

  • Forward Delay on Uniform Distributed queues with no consumers

    Suppose you have a cluster with 2 members, and a uniform distributed queue targeted to the cluster. Messages are produced onto the queue by an application targeted to the cluster, so both distributed members should receive messages. Messages within the queues are consumed by a remote WL server which intermittantly connects ( with t3:// ).
    By default, the forward delay is disabled ( set to -1 ) on a queue, so no messages will be forwarded from a queue with no consumers to a queue that does have consumers. A load balancer in front of the cluster should result in the remote cluster's JMS consumer alternating its connection across the cluster.
    If the remote server is connecting to only a single node within the cluster, it will only consume messages from one queue, leaving the other queue's messages un-consumed. But if both queues are configured to use forward delay, and there are no consumers to either queue, will the messages be continuously forwarded back and forth between the queues?
    Or, once the forward delay has expired, will the queues wait for a consumer to show up and then forward all its messages at once?
    I'm wondering how much "sloshing" there's going to be between the nodes of the cluster, as messages are pushed back and forth between the queues.

    From the documentation, a distributed queue forward delay is:
    The amount of time (in seconds) that a distributed queue member with messages, but no consumers, will wait before forwarding its messages to other queue members that do have consumers.Therefore, messages will not forward if a consumer attaches before the configure idle period passes, or if there are no consumers on other queue members.
    I think one case where "Sloshing" would occur if all of the following were true: consumers are transitory and only exist for slightly more than the idle period, message rates are sufficiently high so that the consumer sometimes cannot keep up for significant periods of time, not all destinations are concurrently serviced by consumers, and the limited number of consumers that do exist frequently do not re-attach to the same member.
    Obligatory distributed queue best practice note: For the best performance, simplicity, HA, and message ordering support, it's generally a best practice to ensure that every member of a distributed queue is serviced by a consumer. WebLogic MDBs are specifically designed to handle this need simply and automatically.
    Tom
    Edited by: TomB on Apr 23, 2009 6:27 AM

  • I am trying to create another email account with talk talk. and I keep getting a failed message saying 'mail could not log into the mail server talk talk. Yet I already have another email account with talk talk. Not sure what I am doing wrong

    I am trying to create another email account with Talktalk. I already have one account.
    I try to input the new email address and password and get a failed message
    'Mail could not lot into the mail server talktalk.net.
    I have tried several times and keep getting the same message.
    Any ideas

    Accessing your emails from any computer connected to the Internet or from a Smart phone should be straightforward.
    For help on how to set up your e-mail on some of the most common software applications and devices, see How do I set up my TalkTalk email?
    If your software application or device isn't listed, all you need to connect to your TalkTalk e-mail mailbox are the TalkTalk e-mail settings. Make sure you use the right email settings for your specific email address.
    TalkTalk email addresses only
    Login / Username
    [email protected]
    [email protected]
    Incoming mail server
    mail.talktalk.net
    mail.talktalk.net
    Incoming Port
    110
    143
    Outgoing mail server
    smtp.talktalk.net
    smtp.talktalk.net
    Outgoing Port
    587
    587
    Outgoing SSL
    Yes
    Yes
    Outgoing Authentication
    Yes
    Yes

  • How to process one message at a time on a distributed queue

    I have a situation where I need to execute/process a task of a type
              asynchronously and this should be done one at a time. To do that I am thinking of setting
              up a distributed queue (for load balancing and failover). Now I have
              this requirement that only one task should be processed at one time. So
              for example if two messages (m1 followed by m2) are sent to distributed
              queue and I have the distributed queue which points to two physical
              queues on two different instances of weblogic(wl1 and wl2), the
              distributed queue will likely send m1 to wl1 and m2 to wl2 (assuming
              distributed queue is setup with round robin policy). If m1 has started
              executing/processing in my MDB on wl1, I do not want start processing
              m2 on wl2 untill m1 has been processed by wl1. Is it possible to do
              this on weblogic 8.1 JMS?
              If this is not supported I was thinking of implementing a database
              based locking framework and each mdb will use that framework to check
              if a task of a particular type is being processed before processing a
              new task. Also in this case I will need to use max. 1 mdb for each
              queue on each weblogic server.
              --Navjeet                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Hello navjeet,
              I don't think there are any parameters that you can set on a distributed queue to ensure messages are handled in the sequential manner you describe so it looks like you will have to implement your own locking mechanism.
              In reposponse to your other question you can set the number of MDbeans in the free pool to 1 (or the number of queues you have) in the MDBean deployment descriptor.
              see:
              http://e-docs.bea.com/wls/docs81/ejb/message_beans.html#1120592
              Cheers,
              Hoos

Maybe you are looking for