Consume exception queue messages (Topic)

Hi,
Context : 1 topic - 2 consumers (BPEL consumers) A and B.
If A fails to consume a message, this message is sent to the exception queue even if B managed to consume it.
It's normal.
If I move this message from the exception queue to the original queue, it will be consumed by A and again by B.
Is it normal ?
I expected that the message would be only consumed by A ...
Is it possible ?
Thanks,
romain.

i ll answer my question
first set exception queue dequeue enable
BEGIN
dbms_aqadm.start_queue(queue_name => 'aq$_request_qt_e',dequeue => TRUE,enqueue => FALSE);
END;
then dequeue messages with null consumer name ;)

Similar Messages

Exception queue messages

is there anyway to dequeue exception queue messages
my main queue is multiconsumer
Message was edited by:
JAA

i ll answer my question
first set exception queue dequeue enable
BEGIN
dbms_aqadm.start_queue(queue_name => 'aq$_request_qt_e',dequeue => TRUE,enqueue => FALSE);
END;
then dequeue messages with null consumer name ;)

Consuming from Queue

I am working with a group, and they need to be able to look at an item on the Queue without consuming it. I think this can be done?? The item you are looking at should be locked to keep other elements from using it while you evaluate this using the item.
If that makes sense???
I am not sure if the default JMS implements this behavior. Can anyone confirm..

Hi,
Yes, you can browse messages from a queue (have a look at QueueBrowser). However a queue browser returns a snapshot therefore the messages that are browsed are not �locked� i.e. they can be consumed and browsed.
A solution that may be useful to you is to consume the queue messages within a transacted session. The consumed messages are not visible to other consumers and your client application can have a look at them in isolation. You can then rollback the transaction whenever you need to �release� those messages. Note that if you don�t want to reinsert those messages in the queue you only need to commit your transaction. It is a bit of a hack but it should work.
Hope this helps,
Arnaud
www.arjuna.com

Business messages are not pushed back to the aq exception queue in case of errors

Hi,
I have the scenario, where I have configured the business events in ebs and implemented the soa interface which consumes the event message from wf_bpel_q.
SOA interface is able to pickup the messages succesfully and same message will be pushed back to the same queue with the status=READY in case of exceptions as well. Ideally as per default functionality of AQ, in case of errors, messages will be pushed to exception queue.
Please suggest why mesages are not pushed back to exception queue in case of errror scenarios with the status='Errored'. Please let me know what i have been missing here in the setup.
Regards,
Anjana

Hi Anjana,
I am not familiar with the SOA interface, so I can't help you in detail, but take a closer look to the following documents.
Doc ID 1374461.1 , Doc ID 1075611.1 , Doc ID 1356146.1
Maybe you hit a known bug ....
Hope that helps.

When using rabbitmq-jms for vFabric RabbitMQ javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card

When using rabbitmq-jms for vFabric RabbitMQ javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card. I have tested with both 1.0.3 and 1.0.5 clients with RabbitMQ 3.1.5.
I was wondering if the community was aware of this problem and if there are any workarounds? If not what is the proper channel to file a bug report. An example code snippet is below. The test fails because the TextMessageMatcher expects the destination passed in on construction (second parameter) to equal the desination on the message received (aquired from getJMSDestination).
        Mockery context = new Mockery();
        final MessageListener messageListener = context.mock(MessageListener.class);
        final Latch latch = new LatchImpl();
        final String prefix = "test" + System.currentTimeMillis();
        context.checking(new Expectations() {
                oneOf(messageListener).onMessage(with(new TextMessageMatcher("MSG1", prefix + ".1234")));
                will(new CustomAction("release latch") {
                    @Override
                    public Object invoke(Invocation invocation) throws Throwable {
                        latch.unlatch();
                        return null;
        final Connection connection = createConnection(null, null);
        Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
        connection.start();
        Topic wildcardTopic = (Topic) getInitialContext().lookup(prefix + "." + "#");
        Topic destination = (Topic) getInitialContext().lookup(prefix + ".1234");
        final MessageConsumer consumer = session.createConsumer(wildcardTopic);
        consumer.setMessageListener(messageListener);
        MessageProducer producer = session.createProducer(null);
        producer.send(destination, session.createTextMessage("MSG1"));
        latch.await(5000);
        connection.close();
        Thread.sleep(5);
        context.assertIsSatisfied();

Check where your MDB sends the [response] messages to.

Message not moving to default exception queue when max retries reached

Hi
I've set up an advanced queue with max retrie of 5 but when the dequing fails the retry count increments but it never goes to the exception queue. The retry count stays at 6, msg_state = READY, deq_txn_id = RETRY_EXCEEDED. Any ideas?
-- drop queue if it exists
exec dbms_aqadm.stop_queue (queue_name => 'AQ$_JY_METER_ENABLE_QTAB_E');
exec dbms_aqadm.stop_queue (queue_name => 'JY_METER_ENABLE_QUE');
exec dbms_aqadm.drop_queue (queue_name => 'JY_METER_ENABLE_QUE') ;
exec dbms_aqadm.drop_queue_table( queue_table => 'JY_METER_ENABLE_QTAB');
-- create the payload for the messages
CREATE TYPE jy_meter_enablement_typ AS OBJECT
request_id                VARCHAR2(30) ,
request_system_code       VARCHAR2(20) ,
business_process_ref      VARCHAR2(20) ,
request_type_ref          VARCHAR2(20) ,
meter_serial_number       VARCHAR2(10) ,
message_request_content   CLOB
-- Create queue table.
-- This one has a sort list so items will be enqueued first based on priority and then based on enq_time
BEGIN
   dbms_aqadm.create_queue_table (queue_table        => 'JY_METER_ENABLE_QTAB',
                                  queue_payload_type => 'JY_METER_ENABLEMENT_TYP',
                                  multiple_consumers => TRUE ,
                                  sort_list          => 'priority,enq_time' ,
                                  comment            => 'Queue table to handle JY Meter Enablement messages');
END;
-- Create Queue based on table
BEGIN
-- retention time set 3600 seconds (ie 1 hour) so the message is kept on the queue for 1 hour after it has been dequeued.
   dbms_aqadm.create_queue (queue_name     => 'JY_METER_ENABLE_QUE',
                            queue_table    => 'JY_METER_ENABLE_QTAB' ,
                            max_retries    => 5 ,
                            retry_delay    => 2 ,
                            retention_time => 3600 ,
                            comment     => 'Queue to handle JY Meter Enablement messages in priority/enq_time order');
END;
-- start the queue
BEGIN
dbms_aqadm.start_queue (queue_name => 'JY_METER_ENABLE_QUE');
END ;
-- Add and register a subscriber to the queue to run the Dequeue procedure
BEGIN
   dbms_aqadm.add_subscriber (queue_name => 'EMO_METER_MGMT.JY_METER_ENABLE_QUE',
                              subscriber => SYS.AQ$_AGENT('JY_METER_ENABLE_QUE_SUBSCRIBER',
                                                          NULL,
                                                          NULL )
    dbms_aq.register (SYS.AQ$_REG_INFO_LIST(SYS.AQ$_REG_INFO('JY_METER_ENABLE_QUE:JY_METER_ENABLE_QUE_SUBSCRIBER',
                                                             DBMS_AQ.NAMESPACE_AQ,
                                                             'plsql://EMO_METER_MGMT.DEQUEUE.dequeue_jy_request',
                                                             HEXTORAW('FF'))),1);
END;
-- start the default exception queue
BEGIN
dbms_aqadm.start_queue(queue_name => 'EMO_METER_MGMT.AQ$_JY_METER_ENABLE_QTAB_E',
                        enqueue => FALSE,
                        dequeue => TRUE);
END ;
/Thanks

Sorry, forgot to add db version
select banner from v$version/
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
5 rows selected.

Message entering the exception queue instead of regular queue

Hi ,
First of all , hello everyone.
I'm new to streams technology and i found this forum that seem to be very helpful.
I have a problem - I defined a queue XYZ and then built a capture process queue that enters changes on some scheme to this queue.
The problem is that the changes enters the exception queue table aq$XYZ_table instead the regular queue table XYZ_table.
I checked the capture process and it seems working fine.
does anyone has a direction of why this problem happens?
thanks in advance,
Arnon

Hi ,
here is what i found in the trace file.
*** 2008-08-12 18:03:23.129
*** SERVICE NAME:(SYS$USERS) 2008-08-12 18:03:23.128
*** SESSION ID:(205.1) 2008-08-12 18:03:23.128
08/12/2008 18:03:23
*** 2008-08-13 02:01:07.154
knlc_ProcessMVDD-1: MISSING Streams multi-version data dictionary!!!
knlldmm: gdbnm=TEST.EVEN
knlldmm: objn=-40016372
knlldmm: objv=1
knlldmm: scn=3519960438
knlldmm: opnum=7
*** 2008-08-13 02:01:17.308
knlc_ProcessMVDD-1: MISSING Streams multi-version data dictionary!!!
knlldmm: gdbnm=TEST.EVEN
knlldmm: objn=-40016371
knlldmm: objv=1
knlldmm: scn=3519960509
knlldmm: opnum=7
*** 2008-08-14 02:01:33.888
knlc_ProcessMVDD-1: MISSING Streams multi-version data dictionary!!!
knlldmm: gdbnm=TEST.EVEN
knlldmm: objn=-40016358
knlldmm: objv=1
knlldmm: scn=3521410760
knlldmm: opnum=7
*** 2008-08-14 02:01:46.086
knlc_ProcessMVDD-1: MISSING Streams multi-version data dictionary!!!
knlldmm: gdbnm=TEST.EVEN
knlldmm: objn=-40016357
knlldmm: objv=1
knlldmm: scn=3521411166
knlldmm: opnum=7
i checked on this error and i found that i need to run DBMS_CAPTURE_ADM.PREPARE_TABLE_INSTANTIATION in order to fix it but it also didn't help , and the capture process still not working.

Strange MDB behaviour: All MDBs in pool consuming a single message.

Greetings,
I'm noticing rather bizzarre behaviour with an MDB. The MDB in question does nothing
more than consume a message, to a tiny bit of processing, and sends to another JMS
queue.
I set the max pool size to 2, initial pool size to 2. I then put a single JMS message
onto the queue that the MDB is bound to. This is where the problem starts. Both
MDBs in the pool consume the said message (and I end up with two messages in my outbound
queue). I have confirmed that indeed only one message is placed on the queue the
MDBs are bound to. If I set the pool sizes to larger values, all the MDBs in the
pool still end up consuming that one message.
Any ideas?
-Matt.
P.S. Crossposting to .ejb.ejb20

I'm not sure what the problem can be, but check that:
1- you're really using a queue and not a topic.
2- your transaction didn't roll back. Catch any throwables in onMessage() to
make sure.
Does this fix it?
Emmanuel
"Matthew" <[email protected]> wrote in message
news:3cd7fb5c$[email protected]..
>
Greetings,
I'm noticing rather bizzarre behaviour with an MDB. The MDB in questiondoes nothing
more than consume a message, to a tiny bit of processing, and sends toanother JMS
queue.
I set the max pool size to 2, initial pool size to 2. I then put a singleJMS message
onto the queue that the MDB is bound to. This is where the problemstarts. Both
MDBs in the pool consume the said message (and I end up with two messagesin my outbound
queue). I have confirmed that indeed only one message is placed on thequeue the
MDBs are bound to. If I set the pool sizes to larger values, all the MDBsin the
pool still end up consuming that one message.
Any ideas?
-Matt.
P.S. Crossposting to .ejb.ejb20

Exception Queue cleanup.

hi all,
i am using oracle 9i.
is there a way to automatically remove messages from the exception queue?
if so, what determines when this removal occurs?
Thanks ahead,
Lior.

i ll answer my question
first set exception queue dequeue enable
BEGIN
dbms_aqadm.start_queue(queue_name => 'aq$_request_qt_e',dequeue => TRUE,enqueue => FALSE);
END;
then dequeue messages with null consumer name ;)

Queue versus Topic in JMS

Can somebody tell me the difference between queue and Topic in JMS?

Queues are used to send messages between single applications, as far as I recall. App A puts a message in Queue Q and App B consumes the message, once B has consumed the message no other application can 'read' it.
A topic allows application A to broadcast a message to every other application that is listeningo on the topic.
It's the difference between whispering and shouting.
J

BPEL Process for AQ Exception Queue

Is there a way to configure AQ adapter to dequeue message from default exception queue. I have tried doing so but it fails to find the exception queue. If not then what are the better ways of handling exception messages for a multiconsumer queue.
I need to enqueue the messages from exception queue once the issue is resolved.
-AA

Any one who can help me on this ?
-AA

Dequeue from exception queue failing

i'm having trouble dequeueing a message that has been moved to the exception queue. i can 'see' the message by looking at the queue table using Toad, but any attempt to dequeue it using DBMS_AQ.DEQUEUE results in the procedure timing out without dequeuing the message. when i try to dequeue it explicitly, using the ID, the process hangs. either way, there are no error messages.
i'm using the default exception queue, which i have started and enabled for dequeue.
thanks in advance for any help, simon

after banging my head on the wall for three days, a shutdown and restart of the database solved this problem....

Exception queue

How can i tell what caused a message to go to the exception queue.
For instance say i have a message that has reached its expiration period and goes to the exception queue how would i be able to find out that the reason it went to the exception queue is because it had expired?
version 10g
select * from AQ$<queue_table> will show the reason why the message went to the exception queue.
Edited by: user457357 on May 6, 2009 5:37 PM

When you define a queue table and queue, there will be an exception queue there automatically - you can't avoid it being created.

Browsing Exception Queue

Hi there,
I have a JMS messaging arquitecture using the OJMS provider. I created one queue and as I've read, automatically an exception queue was created. I'm trying to browse that exception queue and list the messages in, but despite there are messages, the method getEnumeration() does not retrieve me anything. Anyone knows why?
I'm using Oracle 10.1.0.1.
Thanks in advance.
Carolina Antón
carolina.anton_at_gmail.com

Hi Henry,
Unless your concern is about Microsoft scheduling solution "PROJECT", you should post your thread in the appropriate forum in order to have an helpful hand.
Regards.
Guillaume Rouyre - MBA, MCP, MCTS

How to automatically empty the exception queue?

Hi.
I have an exception queue that contains over 140000 messages. Is there some way of making Oracle empty this queue on a regular basis? I have set "dequeue" to "disabled" because I am not interested in this queue's messages, but the queue just continues to grow larger and larger...
Any help would be very appreciated!
Regards,
-Christer

Is this really not possible? Do I have to make a trigger on the table or manually delete it to stop growing?

Consume exception queue messages (Topic)

Similar Messages

Maybe you are looking for