Error queues

I am looking to build an error handling service that will process the contents of an error queue. At present, TMQFORWARD is configured to forward the messages into the 'Read from Queue' service. I would assume that the TMQFORWARD can be re-configured to also forward messages from the error queue to the error handling service. From my understanding of it, the '-q' command line option in the 'CLOPT' can be used to specify the names of one or more queues/services for the forwarding of messages. I understand that messages are then sent to a server providing a service whose name matches the queue name from which the message is read. Is it the case that by adding both service names to the '-q' option and ensuring that the relevant service and queue names match, that the TMQFORWARD will be able to forward messages from the correct queue to the correct service? Thanks, dsmith78

Seems reasonable because errorQ is also one common queue. However, the
potential problem is if the error handling service has any problem, it will
make TMQFORWARD redequeue to the error Q which may lead loop which should be
handled correctly.
/Bruce
<Derek Smith> wrote in message news:[email protected]..
I am looking to build an error handling service that will process thecontents of an error queue. At present, TMQFORWARD is configured to forward
the messages into the 'Read from Queue' service. I would assume that the
TMQFORWARD can be re-configured to also forward messages from the error
queue to the error handling service. From my understanding of it, the '-q'
command line option in the 'CLOPT' can be used to specify the names of one
or more queues/services for the forwarding of messages. I understan
d that messages are then sent to a server providing a service whose namematches the queue name from which the message is read. Is it the case that
by adding both service names to the '-q' option and ensuring that the
relevant service and queue names match, that the TMQFORWARD will be able to
forward messages from the correct queue to the correct service? Thanks,
dsmith78

Similar Messages

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

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.

Mail the message while transferring to error queue

Hi,
          I want to mail the message when a message is sent to error queue.
          I have configured error queue in weblogic console.
          Thanks and Regards
          A.SathishKumar

"Stickied" in the top section of this Windows Hotsync board is a thread with instructions to do a clean uninstall of Palm Desktop. Try that, then reinstall the previous version.
smkranz
I am a volunteer, and not an HP employee.
Palm OS ∙ webOS ∙ Android

How to send payload to error queue if the transaction is rolled back.

Hey,
If we get a error then the transaction needs to be rolled back. I need to send the input payload to a errored Queue if the transaction is roled back (not to the actual Queue from which input payload is consumed). Can any body tell how to do it.
Thanks,
Rakes.

Hi Rakes,
When a transaction is rolled back, the message (input payload ) will roll back to the "exception queue" of the initial queue. You may think of it as an error bucket inside the JMS queue. AIA provides manual scripts to resumbit this message once error is fixed.
If you are using AQ, you could specify your own queue as exception queue. You could have a custom SQL solution to move messages from initial exception queue to your custom queue.
Regards
Rohit

SAP HANA D3 Library errors - "queue" is not a function

Hello all,
i have a question regarding D3 Integration into SAP HANA and hope one can help me.
The last days i developed a D3 Choropleth (spatial data) with hover effects, tooltips and a legend. I have an existing SAPUI5 and HANA XS application running and now i wanted to integrate my D3 Choropleth.
1 ) First of all, i added the following tags into the head section of the index.html file of my SAPUI5 project as i need those libaries.
<script type="text/javascript" src="http://d3js.org/d3.v3.min.js"></script>
<script type="text/javascript" src="http://d3js.org/queue.v1.min.js"></script>
<script type="text/javascript" src="http://d3js.org/topojson.v1.min.js"></script>
2) Then, i added the program code of my D3 Choropleth into the view.js of my SAPUI5 project:
var html2 = new sap.ui.core.HTML("d3choropleth", {
                content: "<div class='D3Choropleth'>" + "</div>",
                preferDOM: false,
                afterRendering: function() {
                              .... here is my code ...
I have a SAPUI5 shell with different NavigationItems (tabs) and for this D3 Choropleth tab i am writing:
case "WI_choropleth":
oShell.setContent(html2);
break;
When i start my SAPUI5 project and klick on the tab where the D3 Choropleth should be rendered, i get the following errors:
d3.scale.threshold is not a function
d3.geo.albers center is not a function
queue is not a function
Moreover, i have to say that my D3 Choropleth works standalone outside HANA very well, that is why i assume it is a library integration issue.
In my browsers (firefox) developer console i can see that there is a D3 library loaded by default (as it is one of SAPUI5s components) with the path: sap/ui5/1/resources/sap/ui/thirdparty/D3.js.
BUT this is a really old version of D3 (2.9), the current release is D3 (3.4), so maybe the problem is that the D3 libary that is loaded by default overwrites my integration of D3 (script tag above)?
Does anyone have the same issues and knows how to solve that? Furthermore it seems that the d3 queue library is also not integrated as the error "queue is not a function" occurs and i also ask me how to solve that error.
We have SAP HANA Developer Edition Revision 80 (by AWS), HANA Studio and Client are on revision 73 (64bit).
It would be great if anyone could help me with my issue.
Further question: Is the current release of D3 going to be integrated into the next HANA revision?
Thanks a lot & regards,
Andreas

Hi Andreas,
You are right. The way you integrate the libraries in your code is not the way that will work for HANA XS projects. This is why it doesn't accept the queue function (library is not loaded) and also why the 3.x only D3JS funcitons are not accepted (only the internal D3JS library is loading and these functions were not a part of 2.9 yet).
To integrate third party libraries, you need to add XSJSLIB files to your project. These need to pass the server-side JSLint checks before accepted by the XS engine. (Client-side checks that fail might not count though).
Please see this post from David Brookler for more information.
http://scn.sap.com/community/developer-center/hana/blog/2013/12/23/db001-using-libraries-in-xs
Best regards,
Tobias

Programaticaly reexecute transaction that was in a error-queue

I am writing an "error handler" to correct the error queue. I use the CUSTOMIZE package as described in the docs (section 3.6.1) . So far I am able to delete wrong entries from the c$eq and ceq$... tables. But how can I reexecute these transactions?
I don't want to copy the data by hand into the cfm$.. and c$in_messages tables because there is an API-Function "ConsolidatorManager.executeTransaction".
I wrote a java-class which is able to call this function. Unfortunately I can't call this function after loading it into the database because Oracle can't find all required classes. I get ORA-29521 errors.
Ideas?

Hi,
Basically we call the report in the form where the viewer control is placed, however in your case we can pass the report document object from a global variable or a session (in case of web application.
More over how does it behave when you try using this statement:
CrystalReportViewer1.ReportSource = "
AdvancedReports\AdvancedReports\RptRecepMerc.rpt"
Does it help?
Regards,
AG.

Examples for JMS Error Queue implementation in BPEL

Hi ,
Please anyone provide me examples for JMS error queue implementaion in BPEL.
Regards
Narsi p

Hi Narsi p,
Please remember to mark answers accordingly... Helpful or correct, following the forum rules
https://forums.oracle.com/forums/ann.jspa?annID=330
Can you tell us more about what are you trying to achieve here?
If you are just trying to configure an error queue to put the messages that couldn't be delivered, you can do this in weblogic directly.
Configuring an Error Destination for Undelivered Messages
http://docs.oracle.com/cd/E17904_01/web.1111/e13727/manage_apps.htm#JMSPG254
Cheers,
Vlad

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

Example using of getMessage(s) with JMS error queues?

Hi,
I'm cobbling together various tools for easier management of replaying messages left in error queues and the likes, and whilst I've got messages being moved around the place on demand, I can't make any progress using getMessage() and getMessages() to print out vital statistics of a message / all the messages in a queue, including hopefully ripping out excerts of the XML payload in them. Can someone provide / point me to an example of these being in use? I can get a successful execution of getMessages() but am usure what to really do next with the object returned, how to iterate through and such.
Thanks
Chris.

Hi Chris,
There are open source solutions for message management. In particular, you might want to investigate Hermes:
http://blogs.oracle.com/jamesbayer/2008/01/hermes_jms_open_source_jms_con.html
As for browsing messages via getMessages(), here's a code snippet. Note that one should never attempt to get too many messages at a time via "getNext()" -- instead call getNext() multiple times. Otherwise, if there are too many messages, the client or server might run out of memory.
# create a cursor to get all the messages in the queue
# by passing ‘true’ for selector expression,
# and long value for cursor timeout
cursor1=cmo.getMessages(‘true’,9999999)
# get the next 5 messages starting from the cursor’s
# current end position
# this will adjust the cursor’s current start position and
# end position “forwards” by 5
msgs = cmo.getNext(cursor1, 5)
# print all the messages’ contents
print msgs
# get 3 messages upto the cursor’s current start position
# this will adjust the cursor’s current start and end position backwards by 3
# this will the current position of the message by 1
msgs = cmo.getPrevious(cursor1, 3)
# print all the messages’ contents
print msgs
Finally, here's code based on public APIs that can help with exporting messages to a file.   It uses Java, not WLST. I haven't tested it personally. I'm not sure if there's away to do this in WLST.
* pseudo code for JMS Message Export operation based on
* current implementation in the Administration Console
import java.io.File;
import java.io.FileOutputStream;
import java.io.OutputStreamWriter;
import java.io.BufferedWriter;
import java.io.Writer;
import java.io.IOException;
import java.util.ArrayList;
import java.util.Collection;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import weblogic.apache.xerces.dom.DocumentImpl;
import weblogic.apache.xml.serialize.OutputFormat;
import weblogic.apache.xml.serialize.XMLSerializer;
import weblogic.management.runtime.JMSDestinationRuntimeMBean;
import weblogic.management.runtime.JMSDurableSubscriberRuntimeMBean;
import weblogic.management.runtime.JMSMessageManagementRuntimeMBean;
import javax.management.openmbean.CompositeData;
import weblogic.jms.extensions.JMSMessageInfo;
import weblogic.jms.extensions.WLMessage;
import weblogic.messaging.kernel.Cursor;
public void exportMessages(
    String fileName,
    JMSDestinationRuntimeMBean destination,
    /* or JMSDurableSubscriberRuntimeMBean durableSubscriber */,
    String messageSelector) throws Exception {
    BufferedWriter bw = null;
    try {
      File selectedFile = new File(file);
      if (destination == null /* or durableSubscriber == null */) {
        throw new IllegalArgumentException("A valid destination runtime or durableSubscriber runtime mbean must be specified");
      JMSMessageManagementRuntimeMBean runtime = (JMSMessageManagementRuntimeMBean) destination /* durableSubscriber */;
      bw = new BufferedWriter(new OutputStreamWriter(new FileOutputStream(file),"UTF-8"));
      String xmlDeclaration = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>";
      String exportStart = "<JMSMessageExport>";
      final String exportEnd = "</JMSMessageExport>";
      final String indent = "    ";
      bw.write(xmlDeclaration);
      bw.newLine();
      bw.write(exportStart);
      bw.newLine();
      bw.newLine();
      bw.write(indent);
      CompositeData[] messageInfos = null;
      OutputFormat of = new OutputFormat();
      of.setIndenting(true);
      of.setLineSeparator("\n"+indent);
      of.setOmitXMLDeclaration(true);
      XMLSerializer ser = getXMLSerializer(bw, of);
      String cursor = JMSUtils.getJMSMessageCursor(runtime, selector,0);
      while ((messageInfos = runtime.getNext(cursor,new Integer(20))) != null) {
        for (int i = 0; i < messageInfos.length; i++) {
          JMSMessageInfo mhi = new JMSMessageInfo(messageInfos);
Long mhiHandle = mhi.getHandle();
CompositeData m = runtime.getMessage(cursor, mhiHandle);
// need to get the message with body
JMSMessageInfo mbi = new JMSMessageInfo(m);
WLMessage message = mbi.getMessage();
ser.serialize(message.getJMSMessageDocument());
messageInfos[i] = null;
bw.newLine();
bw.write(exportEnd);
bw.flush();
bw.close();
runtime.closeCursor(cursor);
LOG.success("jms exportmessage success");
} catch (Exception e) {
try {
if(bw != null)
bw.close();
} catch (IOException ioe) { }
LOG.error(e);
LOG.error("jms exportmessage error");
throw(e);
LOG.success("jms exportmessage success");
private XMLSerializer getXMLSerializer(
Writer writer,
OutputFormat of) {
return new XMLSerializer(writer, of) {
protected void printText(
char[] chars,
int start,
int length,
boolean preserveSpace,
boolean unescaped) throws IOException {
super.printText(chars,start,length,true,unescaped);
protected void printText(
String text,
boolean preserveSpace,
boolean unescaped ) throws IOException {
super.printText(text,true,unescaped);
public static String getJMSMessageCursor(
JMSMessageManagementRuntimeMBean runtime,
String selector,
int cursorTimeout) throws weblogic.management.ManagementException
return runtime.getMessages(
selector,
new Integer(cursorTimeout),
new Integer(Cursor.ALL));
Hope this helps,
Tom

Handling Error queue and Resolving issues - Best practices

This is related to Oracle 11g R2 streams replication.
I have a table A in Source and Table B in destination. During the replication by Oracle streams, if there is an error at apply process, the LCR record will go to error queue table.
Please share the best practices on the following:
1. Maintaining error table operation,
2. monitor the errors in such a way that other LCRs are not affected,
3. Reapply the resolved LCRs from error queue back to Table B, and
4. Retain the synchronization without degrading the performance of streams
Please share some real time insight into the error queue handling mechanism.
Appreciate your help in advance.

This is related to Oracle 11g R2 streams replication.
I have a table A in Source and Table B in destination. During the replication by Oracle streams, if there is an error at apply process, the LCR record will go to error queue table.
Please share the best practices on the following:
1. Maintaining error table operation,
2. monitor the errors in such a way that other LCRs are not affected,
3. Reapply the resolved LCRs from error queue back to Table B, and
4. Retain the synchronization without degrading the performance of streams
Please share some real time insight into the error queue handling mechanism.
Appreciate your help in advance.

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 Queue Problem

Hi,
          I have defined an error queue for a given queue. The problem is that
          the error queue doesn't get any messages when there is an error, etc.
          For example (WebLogic configuration for the queue1) -
          Error Destination: errorqueue8.
          Time To Live Override: 20000.
          I want the messages in the queue1 to be transferred to errorqueue8
          when the time-to-live expires. But this doesn't happen!
          Does anyone know whats wrong? Am I doing something wrong with the
          configurations?
          I am using WebLogic 7.
          Thanks in Advance.


Good timing!
          WebLogic 8.1, which is out in restricted beta at the moment, and
          will be out in public beta "soon", has this extension. You can
          configure a WebLogic 8.1 destination to redirect expired messages
          to an error destination. Prior versions of WebLogic do not
          have this extensions.
          Tom, BEA
          mal wrote:
          > Thanks for the answer!
          >
          > So what if I want to send the undilivered messages, for a given time,
          > to go to another queue (without them getting lost)? Is there a way
          > that I can do it within WebLogic 7? Or should I program for it in the
          > application?
          >
          > Thanks,
          >
          >
          > "Bart Simpson" <[email protected]> wrote in message news:<3e445c0c$[email protected]>...
          >
          >>Hi,
          >>
          >>How are you doing? If the TTL expires the messages are lost. So, WLS is behaving
          >>as expected.
          >>
          >>Error destination makes sense for redelivery of messages that have already been
          >>redelivered so many times...
          >>
          >>Best regards,
          >>-Bart Simpson
          >

Trex queue return error: code 6002, QS error: queue not found

Hi all,
in TREX Administrator tool, in the queue area I see "index01". When I try to perform some operation I receive the error QS error: queue not found. I check services status and I see that queueserver isn't running. I stop the TREX server, delete all file in lock folder, and restart. After few seconds the queueserver crash and stop it.
Please, can you help me?
Fabio Sambugaro.

Hello Duncan,
Thanks for the reply.
Can I do the same from
System Administration > System Configuration > Knowledge Management > Index Administration
We have around 7400 documents to be indexed. The indexing seems to be very slow. Is there any reason for slow indexing?
Kind Regards,
jelbin

OEM takes Lot of time to show Error Queue

I have configured Multi-Master Advanced Replication for 3 master sites (Using Oracle Enterprise Edition 9.2.0.1.0 on MS Windows2K). But I have observed a problem during this week that the size of SYSTEM tablespace has been growing rapidly. After further analysis it was observed that a major portion of the tablespace is covered by DEF$_AQCALL. It has nearly 21,763,626 rows on master definition site and increasing day by day while there are just less that 6650,400 rows in participating other master sites. Due to this larger size when I try to observe the Error Queue using OEM, It takes more than 45 minutes to just show the Errors transactions list. Please have a look on the following script, I have run:-
SQL> select count(*) from def$_aqcall;
COUNT(*)
21763626
SQL> select count(*) from deferror;
COUNT(*)
3
SQL> select count(*) from deftrandest;
COUNT(*)
1466
Transactions are being propagated normally. But If I have to see the Error Queue to check the error transactions for possible data conflicts, it takes a long time. I have moved this table to USERS tablespace and then move again to SYSTEM tablespace but alas its size doesn't vary. Can I truncate this table i.e. DEF$_AQCALL. As its size is going to be bigger and bigger due to increasing number of rows in it. what should I do ?
Thanks
Masood

You should read the documentation for multimaster replication because mulitimater replication between two databases is easy but the replication between more then two databases required complete knowledge and strong understanding of oracle server working as well as replication concept. If you not create replication between more then two database with proper considration then it will create a very big overhead on the server and situation which you already mention.
Moreover create Replication with API rather then GUI tools. it will includes more option to create replication environment.

WebLogic JMS error queue

Hello. I have problem after sending message to JMS queue. Message by log file sending is success. But Message don't put to queue and put to error queue.
Message don't put to queue in 25 % cases.
Speak please, what can be reasons what message put to error queue ?

give me please need section link.
I closing the sender, session and connection in method destroy();
That class, That is EJB:
@Stateless(name = "BeanName", mappedName = "ejb.un.BeanName")
@Local(BeanLocal.class)
public class BeanName implements ReleaserLocal {
@PreDestroy
public void destroy() {
try {
jmsSender.close();
} catch (Exception ex) {
try {
jmsSession.close();
} catch (Exception ex) {
try {
jmsConnection.close();
} catch (Exception ex) {
private void sendMessage(String payload, String channel, long qId){
try {
jmsSender.send(message);
if (log.isDebugEnabled()) {
log.debug("message SEND");
I running this app from depployed in weblogic.

Error queues

Similar Messages

Maybe you are looking for