AQ Expired messages Propagation

Hi,
We have an advanced queue with expiration time set to 24hours after which the messages in the Q are routed to AQ exception queue.
We have a requirement to route the message to another queue after the expiration time, with transformation saying that the message is expired in any of the field..
Can we do this with Message Expiration property and Propagation scheduling of AQ. Appreciate your suggestions. Thanks.

Thanks for your suggestion. But what sort of deamon process can we have with respct to this scenario. We have a requriement here not to dequeue the message if the message is in the Queue for a period of 24 hours. So if we have a deamon process may be we can route the messages to another Queue, but how can we handle the requriement of not dequeing the message from the orginal queue. Please suggest. Thanks

Similar Messages

Why do I get "Evaluation Expired" message in MAX with Switch Executive

Why do I get �Evaluation Expired� message in MAX with Switch Executive on a PXI rack, which has a �Ghosted� image from and identical PXI rack(no problem with this PXI rack), when logged in as USER in Windows2000, but not when logged in as a Local Administrator. When logged in as Administrator in Windows2000 running a TestStand sequence, using a �C� code action step calling the nise.dll is ok, but not when logged in as local user. The alias switch name is unknown.

1.0.4.109 is a dll version number where as 1.0.2 is a NISE version number. The dll version number does not always line up with the product version number.
NISE 1.0 has a dll version of 1.0.1.109
NISE 1.0.1 has a dll version of 1.1.4.1
NISE 1.0.2 has a dll version of 1.2.4.7
NISE 2.0 has a dll version of 2.0.0.45154
The best way to find the product number is to launch the application and click on Help and About. You NISE version is probably 1.0 and NISE 1.0.2 will fix your licensing problem.

Hi, I cant login to the facebook app on my iphone 5 ios 6.0.2. I keep getting an error message saying 'There was an error logging in using single sign on' when im asked to log in again i get a 'session expired' message. This only started happening yeste

Hi, I cant login to the facebook app on my iphone 5 ios 6.0.2. I keep getting an error message saying 'There was an error logging in using single sign on' when im asked to log in again i get a 'session expired' message. This only started happening yesterday. Anyone else having this problem? Thanks.

I am having the same problem and took the following steps to mitigate it to no avail.
1. I deleted the Facebook app on the phone and turned off Facebook in the iPhone's system-wide settings.
2. I re-enabled Facebook in the iPhone's system-wide settings and reinstalled the Facebook app and logged in again. It worked. For about an hour.
3. I completely restored the phone to a previous backup (before the problems started) and reenabled Facebook .... reinstalled the app.... and now it works intermittenly. But it hasn't worked in about 12 hours now (just tried a few minutes ago).
Please advise.

How to resolve "Your Trial Has Expired" message when launching InDesign CS6

Hello, just joined the Creative Cloud via the "Free" option. The Adobe Application Manager downloaded and installed after which I was presented the list of Adobe Products which I could "Try" for the 30-day trial period. After installing InDesign CS6 for trial, I'm getting a "Your Trial has Expired" message when I launch InDesign C6.
My PC environment is: Windows 7 Pro - SP1 (x64 bit)
I do have Adobe Acrobat X installed (with Enfocus PitStop v10 plugin)
Any thoughts as to what is causing this error??
How do I resolve it??

Hi MickyRatz,
If the trial version indicates as being expired then it has expired. There is no way to extend the trial.
You can find more details at Adobe trial software expired early -http://helpx.adobe.com/x-productkb/global/trial-software-expired-early .html.

Getting "licensing for this product has expired" message after reinstalling CS6

I recently upgraded my operating system on the same computer from Windows 7 32-bit to Windows 7 64-bit. This of course meant I had to do a clean reinstall of all my software.
When I reinstalled Photoshop CS6, I got an error "licensing for this product has expired."
In hindsight, after researching the problem, I realize I should had deactivated CS6 on my 32-bit installation before upgrading the computer, but I didn't. I did, however, upgrade to a new hard drive when I upgraded my operating system, so I was able to put the old hard drive back in and deactivate the original installation after the fact.
However, on the 64- bit installation, even when I try uninstalling CS6 and installing it again, it accepts my serial number, but then gives me the "licensing for this product has expired message."
I have tried contacting Adobe online chat help twice. Each time I get an agent quickly, but after asking a few questions they tell me they need to transfer me to the "install department." The other night I was left in limbo a half hour waiting for the install department before I gave up. Tonight I've been on for almost an hour and am still waiting.
I assume that CS6 has left something in the registry of the 64-bit installation that no longer allows me to install Photoshop with my current (valid) serial number, but I have no idea how to fix it or get through to Adobe help. Any ideas? Thanks.

Just to update this, I was able to connect with Adobe by phone and resolve the problem. The guy on the phone was much more helpful than my two previous attempts to contact Adobe by their online chat.
The guy had me repeat the steps outlined in Solution 3 in the document that Bill refers to, however we also did the additional step of running a program called Adobe Creative Cloud Cleaner tool. That program removed the files from my system that were preventing Photoshop from running.
Thanks all.

#550 4.4.7 QUEUE.Expired; message expired ## With LastError "A storage transient failure has occurred during content conversion." In submission Queue. (Exchange 2013)

Greetings,
We seem to be having a problem with some users who are attempting to send e-mails from within the organisation to an external domain. Not all users are affected, and not all outgoing e-mails have this issue.
Some e-mails get stuck in the submission queue. This is the error message in Last Error : "A storage transient failure has occurred during content conversion."
Days later, the internal user who send the message gets a #550 4.4.7 QUEUE.Expired; message expired ## NDR.
We did have some initial configuration issues, but these were fixed more than a week ago :
- The external FQDN during EHLO was set to the wrong address, now pointing to the correct one.
- SPF record was updated with new IP adress.
Here is some additional information on the issue :
- Not on any blacklists - checked using dnsbl.info
- Telnet to remote servers works from exchange server, connections are accepted and can send mail.
- Outbound SMTP test ran using Microsoft Remote Connectivity Analyser : Passed with both External (Static) and Smarthost IP.
- This seems to happen only with emails that have an attachment and that are transfered, but only for the affected users.
- If content from these e-mails is manually copied over to a new email, email is sent to destination without problem.
Configuration information :
- Exchange 2013 running on Windows 2012 Datacenter with all latest updates.
- Outgoing e-mail is sent via smarthost. Only one outbound transport rule is active.
- Using internal DNS server.
- There is only one mailbox database.
Thank you for taking the time to read this!

On Wed, 16 Jan 2013 15:31:14 +0000, Ipigi wrote:
>Sorry, I often get some terms mixed up when I explain things as our users use the French version of outlook.
>
>E-mails are not transferred, but forwarded manually from their outlook. Message format in outlook is set to HTML and not Rich Text when they foward the e-mail.
Do they forward the message as an attachment?
>When forwarded internally, this is in the internet headers :
>
>Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary
Within your organization I'm prety sure that messages will use TNEF.
What does the message contain at the external recipient's side?
>It really seems to me that Exchange is not converting RTF to Plain Text. The first link you provided states in it's final paragraph that Exchange should be doing this conversion.
If you can, try creating a mail-enabed Contact for one of the external
recipients and set the message format on that.
>If I disabled TNEF as that link suggests, offending messages will get stuck in the submission queue again.
>
>I thank you for your help so far. This is not an issue I've had with any previous installations/migrations of Exchange that I have done.
>
>Please let me know if you need any additional information.
Have you tried UNsetting TNEF on the remote domain?
Set-RemoteDomain Default -TNEFEnabled $null
That should leave it up to the client to determine the format. It's
probably not what you're after, but see it makes a difference in the
format.
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP

Correct handling of expired Messages

Hi everyone,
I want to enqeue messages using PL/SQL-AQ. This works. The Message-Consumer (external JMS-Client) must not receive messages which have expired. But this is not a Problem because expired messages are being moved to the exception queue.
Now my problem:
Since due to the nature of my app it is possible that a lot of messages are being moved to the exception queue, i'm wondering how to clean up that one. Does the Queue-Monitor-Process (which I succesfully activated) clean the exception-Queue? If so, when this is done? And in General: What is the architecturaly correct way to do message-expiration-Handling?
would be grateful for anything because this problem drives me nuts and there seems nowhere to be apropriate documentation.
BTW: I'm using 9.2, but there is a plan to migrate to 11g. So please maybe point to changes in 11g if possible.
Thanks,
slavisa
Edited by: user11359024 on 24.09.2009 02:18

bstaletic wrote:
Leonid.I wrote:
And I'd probably _think_ before proposing stupid things... And then take a long look at /var/lib/pacman/local/filesystem-2014.06-1/install.
To answer the original question: you don't have to do anything.
You're wrong. Take a look at the wiki page concerning dealing with these files. Then check if there is a group like "git" or "ntp" in your earlier /etc/group. Then check if there's anything about that group in /var/lib/pacman/local/filesystem-2014.06-1/install.
I sense lots of confusion here, so let me explain in detail.
The .install script in the filesystem package is provided specifically to ensure that already running systems will keep running with new packages which require new user/groups, like systemd-timesyncd, by adding users/groups via post_upgrade() as well as checking that "standard" users/groups exist. For example
post_upgrade() {
_addgroup optical -g 93
_addgroup audio -g 92
_addgroup video -g 91
_addgroup systemd-network -g 193
_adduser systemd-network -u 193 -g 193 -d / -s /usr/bin/nologin
Yes, you may have git and ntp which were added by corresponding packages and "vanilla" passwd/group doesn't have these.
Hence, there is no need to merge {group,passwd}.pacnew files manually, just rm them. They are _not_ like other config files. In fact, they probably shouldn't even be in the backup array of filesystem (just like resolv.conf).
bstaletic wrote:Wiki says to do just what ukhippo suggested, and there's nothing about any of the groups I mentioned in the file.
Yes, and wiki is the Ultimate Truth of course, right?

Weblogic 10.3 Not Removing Expired Messages from JMS Queues

Dear All,
We have an application that is running on Weblogic 10.3.
This application (let us call this application Y) receives messages on a JMS queue. These messages are placed on the queue by another application (let us call this application X). We would like to have these messages expire within a certain amount of time (i.e. 90000 ms) if they are not consumed.
Now when application X places the messages onto the queue for application Y to consume, the JMS producer sets the time to live to 90000 ms. We can see that expiration time has been set appropriately in the weblogic console. If a message sits on the queue for longer than 90000 ms the state string of the message is changed to "receive expired". What we don't understand is why the expired messages still end up being consumed from the queue.
We understand that Weblogic is supposed to have an 'Active Message Expiration' thread that will remove expired messages from the queue. The Expiration Scan Interval for the JMS Server is set to 30 (seconds).
Can anyone tell us why our expired messages don't seem to be deleted from the queues?
Tim

Thank you for the response Rene.
We have set up both the active expiration scan and the message expiration policy. The active expiration scan is set for every 30 seconds. The message expiration policy is set to "discard". However, the expired messages are still being consumed. Is it possible we are doing something wrong? See a portion of our configuration files below.
We have set up the expiration scan time interval. See a portion of our config.xml below:
<jms-server>
<name>brokerJMSServer</name>
<target>AdminServer</target>
<persistent-store xsi:nil="true"></persistent-store>
<store-enabled>true</store-enabled>
<allows-persistent-downgrade>false</allows-persistent-downgrade>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
*<expiration-scan-interval>30</expiration-scan-interval>*
<production-paused-at-startup>false</production-paused-at-startup>
<insertion-paused-at-startup>false</insertion-paused-at-startup>
<consumption-paused-at-startup>false</consumption-paused-at-startup>
</jms-server>
<jms-system-resource>
<name>broker-jms</name>
<target>AdminServer</target>
<sub-deployment>
<name>EhrBrokerRequestQueue</name>
<target>brokerJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/broker-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
We have set up the message expiration policy in our jms descriptor. See a portion below:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<queue name="EhrBrokerRequestQueue">
<delivery-params-overrides>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>-1</redelivery-limit>
*<expiration-policy>Discard</expiration-policy>*
</delivery-failure-params>
<jndi-name>EhrBrokerRequestQueue</jndi-name>
</queue>
</weblogic-jms>
What could we be doing wrong?
Kind Regards,
Tim

Re enable dequeueing for expired messages in AQ

Dear all,
I need to reprocess expired messages in an advanced queue.
Is there a script that allows either to retry dequeuing or to re insert/enqueue again the messages?
The creation script of the queue follows:
BEGIN
SYS.DBMS_AQADM.CREATE_QUEUE
    QUEUE_NAME          =>   'CC.PMTS'
   ,QUEUE_TABLE         =>   'CC.PMTS_DATA'
   ,QUEUE_TYPE          =>   SYS.DBMS_AQADM.NORMAL_QUEUE
   ,MAX_RETRIES         =>   0
   ,RETRY_DELAY         =>   0
   ,RETENTION_TIME      =>   0
   ,COMMENT             =>   'Comment'
END;
Thanks

There is another forurm for AQ queries: https://forums.oracle.com/community/developer/english/oracle_database/advanced_queueing

Reduce / Expire Messages in Gwcheck

Hi.
Don´t know if this is the right place for Gwcheck... but I try.
Is it poosible to Reduce/Expire messages larger than 5MB and is MP3, MPEG, AVI
// Patrik

Dave Parkes wrote:
> Not with GWCheck, no - that can only select on size or age. It can't do
> anything with attachment types.
>
> Cheers Dave
>
>
Right for something like that you'll need a 3rd party product. I believe
GWAVA can do it for examle. (disclaimer I work for that company)

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

Urgent--Message Propagation problem.

Hi all,
I am trying out the following stuff:-
1)Creating a QueueTable.
2)Setting its property to setMultipleCustomer(true)
3)Create a Queue using AQ API.
then calling the followin methods.
4) queue.startEnqueue();
5) queue.schedulePropagation(null, null, null, null, null);
NOTE:- I already have a destination queue to which message should propagate in the same database. Thats why i have given all null parameters in schedule propagation.
In client code I am using JMS API to connect to the Queues to put message.
But when Iam trying to Create the queue I get Resource Not Found Exception.
But when I use in the above case setMultipleConsume(false) the code doesnt give any exception, though message propagation is not done. But my intension is to use the message propagation thru schedulePropagation method. In order to use the message propagation feature I have to setMultipleCunsumer(true). and there by ending up in this problem.
Question 1)Can anyone let me know what are the steps to do a message propagation thru Queues(Not Topic). Step by step.
Question 2) Can anyone tell me how to and what to put in the dblink in case if I want by queue to propagate to a queue on a remote db server.
NOTE :- Im using ORACLE AQ APIs to create Queues. and using JMS Client to connect to the queue.
Best Regards,
Thanks in Advance

Sessions require session cookies.
If the user has cookies off then the session won't be retained by the server automatically.
The solution to this is to use URL rewriting.
There is a method: HTTPResponse.encodeURL( String url )
It automatically adds the JSESSIONID used to track the session onto the url if the browser is not accepting cookies.
You need to do this on every link in the website so that session is maintained.
Cheers,
evnafets

Page has expired message on clickiong the "Back" button on Browser

Hi ,
I get Page has expired message on clicking the "Back" button in the browser. I want the user to get directed to the previous page with out viewing this message.
I am using tomcat 5.0 web server and struts framework for my application.
Kindly help me in this regard.

me too i am facing the same problem,
what i found is:
1.you can use get instead of post method action.
2 remove the no cache from your system and make the system caching normally.
any one has any other solution?

ONLY Office365 users sending to our domain getting '550 4.4.7 QUEUE.Expired; message expired' errors

We are having issues with Office365 users sending to our exchange server. We are a small exchange shop. No office365 here. But we have had 3 DIFFERENT domains sending emails our direction receiving the '550 4.4.7 QUEUE.Expired; message expired' returned
email error messages. When using gmail or any other mail service we've tried this issue does not happen. What does Office365/hosted exchange look for differently than any other service?
Regards,
Jay

Diagnostic information for administrators:
Generating server: DM2PR07MB591.namprd07.prod.outlook.com
Total retry attempts: 50
[email protected]
Remote Server returned '550 4.4.7 QUEUE.Expired; message expired'
Original message headers:
Received: from DM2PR07MB528.namprd07.prod.outlook.com (10.141.157.19) by
DM2PR07MB591.namprd07.prod.outlook.com (10.141.176.142) with Microsoft SMTP
Server (TLS) id 15.0.1024.12; Mon, 15 Sep 2014 17:09:01 +0000
Received: from DM2PR07MB528.namprd07.prod.outlook.com ([10.141.157.19]) by
DM2PR07MB528.namprd07.prod.outlook.com ([10.141.157.19]) with mapi id
15.00.1024.012; Mon, 15 Sep 2014 17:09:01 +0000
From: USER [email protected]
To: USER2 [email protected]: subject here
Thread-Topic: subject here
Thread-Index: AQHP0QdOHkZOlFhB10CYHLOZcOgKJA==
Date: Mon, 15 Sep 2014 17:09:00 +0000
Message-ID: [email protected]
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [55.55.55.55]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:;
x-forefront-prvs: 03355EE97E
x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(199003)(189002)(81342001)(90102001)(36756003)(81542001)(4396001)(117636001)(2656002)(97736003)(46102001)(50986999)(85306004)(54356999)(20776003)(16236675004)(99286002)(95666004)(19580395003)(83322001)(19580405001)(99396002)(101416001)(80022001)(66066001)(21056001)(76482001)(64706001)(77982001)(107046002)(105586002)(74502001)(87936001)(19627405001)(86362001)(106116001)(106356001)(74662001)(79102001)(85852003)(83072002)(92566001)(92726001)(229853001)(19625215002)(31966008);DIR:OUT;SFP:1102;SCL:1;SRVR:DM2PR07MB591;H:DM2PR07MB528.namprd07.prod.outlook.com;FPR:;MLV:sfv;PTR:InfoNoRecords;A:1;MX:1;LANG:en;
Content-Type: multipart/alternative;
boundary="_000_141080094032474853domain_"
MIME-Version: 1.0
X-OriginatorOrg: domain.com

Expired messages not logged correctly

The Expiration Policy is set to "Log" and the Expiration Logging Policy is set to "%header%,%properties%" yet there are no entries in the server log.
          I am using a JMS template to configure my destinations and I can see that the other template settings (Redelivery Delay Override, Redelivery Limit) are correctly recognized. This is configured on WebLogic Server 8.1 SP5
          I can see the messages are being redelivered as many times as specified in the template but after the final attempt nothing is logged in the server log. Please advise how to resolve this issue.

TimeToLive is a synonym for "expiration time".
          TimeToDeliver is only activated if your application or configuration has enabled an optional extension for scheduled messaging - sometimes also referred to as "setting the message's birth time" to be sometime in the future rather than immediate.
          Expired messages and messages that have reached redelivery limit can be automatically moved to an error destination - see http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_jmsqueue_config_redelivery.html
          Tom

AQ Expired messages Propagation

Similar Messages

Maybe you are looking for