Expire messages in queue

I am wondering if there is anyone that knows how to execute code to expire certain messages in a queue after they have been enqueued.
I only want one message at a time in the queue that has the same username/tablename combo.
USERNAME is stored in corrid in the queue table:
message_properties.Correlation := NEW_USERNAME;
and tablename is a property:
message.set_string_property(property_name => 'guid',
property_value => P_TABLE_NAME);
Example:
1. when a table is update in the db, a message is enqueued with username and tablename.
2. when a client application connects to the database, if there are messages for it's username/tablename it runs a query.
Problem:
If there were hundreds of updates with the same username/tablename, then there will be hundreds of messages waiting for the client when it connects. Thus the client will runs hundreds of queries...DON'T want this.
Thanks ahead of time

Hello,
You're right. When the journaling mailbox reaches the configured storage quota, the journaling mailbox will stops accepting journal reports. Exchange will hold undelivered journal reports in a mail queue and tries to redeliver them until delivery is successfully.
It will cause high messaging traffic. So I recommend you configure journaling mailboxes without storage quotas or configure an alternate journaling mailbox.
You can configure an alternate journaling mailbox, it will receive the journal reports as attachments in the NDRs generated when the journaling mailbox or the server on which it's located refuses delivery of the journal report or becomes unavailable.
Could you explain the the max length of the queue? It refers to DatabseMaxCacheSize or others. If it means DatabaseMaxCacheSize, you can modify the value in EdgeTransport.exe.config file.
My environment is exchange 2010. At present, there is no performace issue. I recommend you use performance counters to monitor the journaling agent.
I'm afraid that there is no way to configure the journal report messages that will never expire.
If I have any misunderstanding, please free let me know.
Cara Chen
TechNet Community Support

Similar Messages

#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

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

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

Unable to delete messages from queue.

I have a journaling rule setup to send mail to a archive appliance. I have two messages in my queue that are From Address:<> to my recipient (my archiver's email address). The journal rule works fine since it is working for all my users mail, but I have two messages stuck in my queue complaining that they could not be categorized and an event 9213 for MSExchangeTransport every 30 minutes.
"A non-expirable message with the internal message ID 7996 could not be categorized. This message may be a journal report or other system message. The message will remain in the queue until administrative action is taken to resolve the error. Other messages may also have encountered this error. To further diagnose the error, use the Queue Viewer or the Mail Flow Troubleshooter."
I have tried via the GUI and Shell to remove these two messages. The GUI gives me an error:
Microsoft Exchange Error
Action 'Remove (with NDR)' could not be performed on object 'RE: Test to determine if email can be delivered & Received'.
RE: Test to determine if email can be delivered & Received
Failed
Error:
The requested operation can't be performed for the object with identity MyMailServerName\Submission\7999.
OK
The Shell will actually not report back an error but I still have those messages in the queue. The command to see info about the message was:
Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*[email protected]*" } | Format-List
Then I tried deleting the message using the "InternetMessageID" info I gathered from this.
Remove-Message -Filter {InternetMessageID -eq "[email protected]"} -WithNDR $false
This prompts me for a Yes, No, etc... responce (I thought I had it this time) and gave me no error, but the message still resides in queue.
I am at a loss. Any help?

Correct, two messages stuck in queue and cannot remove.
Environment is a Windows 2003 R2 w/ SP2 64bit server, Exchange 2007 SP1 with all roles, AD/DNS is also Windows 2003 R2 w/ SP2 64bit.
This just seemed to start happening a few days ago and just with these two particular messages. I have a archive appliance from ArcMail and a journal rule setup in Exchange to journal all mail to the ArcMail appliance. This has been working and continues to work except for these two messages.
[PS] C:\>Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*[email protected]*" } | Format-List
Identity          : CO-MAIL1\Submission\7996
Subject           : RE: Test to determine if email can be delivered & Received
InternetMessageId : <[email protected]>
FromAddress       : <>
Status            : Retry
Size              : 29638B
MessageSourceName : Journaling
SourceIP          : 255.255.255.255
SCL               : 0
DateReceived      : 9/18/2008 1:39:34 PM
ExpirationTime    :
LastError         : Categorization failed. The message will be deferred and ret
                    ried because it was marked for retry if rejected.
RetryCount        : 0
Queue             : CO-MAIL1\Submission
Recipients        : {[email protected]}
IsValid           : True
ObjectState       : Unchanged
Identity          : CO-MAIL1\Submission\7999
Subject           : RE: Test to determine if email can be delivered & Received
InternetMessageId : <[email protected]>
FromAddress       : <>
Status            : Retry
Size              : 29623B
MessageSourceName : Journaling
SourceIP          : 255.255.255.255
SCL               : 0
DateReceived      : 9/18/2008 1:39:34 PM
ExpirationTime    :
LastError         : Categorization failed. The message will be deferred and ret
                    ried because it was marked for retry if rejected.
RetryCount        : 0
Queue             : CO-MAIL1\Submission
Recipients        : {[email protected]}
IsValid           : True
ObjectState       : Unchanged
Domain Controller Diagnosis
Performing initial setup:
   Done gathering initial info.
Doing initial required tests
   Testing server: co-site\CO-DNS1
      Starting test: Connectivity
         ......................... CO-DNS1 passed test Connectivity
Doing primary tests
   Testing server: co-site\CO-DNS1
      Starting test: Replications
         ......................... CO-DNS1 passed test Replications
      Starting test: NCSecDesc
         ......................... CO-DNS1 passed test NCSecDesc
      Starting test: NetLogons
         ......................... CO-DNS1 passed test NetLogons
      Starting test: Advertising
         ......................... CO-DNS1 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... CO-DNS1 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... CO-DNS1 passed test RidManager
      Starting test: MachineAccount
         ......................... CO-DNS1 passed test MachineAccount
      Starting test: Services
         ......................... CO-DNS1 passed test Services
      Starting test: ObjectsReplicated
         ......................... CO-DNS1 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... CO-DNS1 passed test frssysvol
      Starting test: frsevent
         ......................... CO-DNS1 passed test frsevent
      Starting test: kccevent
         ......................... CO-DNS1 passed test kccevent
      Starting test: systemlog
         ......................... CO-DNS1 passed test systemlog
      Starting test: VerifyReferences
         ......................... CO-DNS1 passed test VerifyReferences
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
   Running partition tests on : lcsd
      Starting test: CrossRefValidation
         ......................... lcsd passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... lcsd passed test CheckSDRefDom
   Running enterprise tests on : lcsd.local
      Starting test: Intersite
         ......................... lcsd.local passed test Intersite
      Starting test: FsmoCheck
         ......................... lcsd.local passed test FsmoCheck
[PS] C:\>Remove-Message -filter {FromAddress -eq "<>"} -withNDR $false -debug -verbose
VERBOSE: Remove-Message : Beginning processing.
Confirm
Are you sure you want to perform this action?
Removing the messages that match filter "FromAddress -eq "<>"".
Yes Yes to All No [L] No to All Suspend [?] Help
(default is "Y"):Y
VERBOSE: Remove-Message : Ending processing.
[PS] C:\>Remove-Message -Filter {InternetMessageID -eq "[email protected]"} -WithNDR $false -debug -verbose
VERBOSE: Remove-Message : Beginning processing.
Confirm
Are you sure you want to perform this action?
Removing the messages that match filter "InternetMessageID -eq
"[email protected]"".
Yes Yes to All No [L] No to All Suspend [?] Help
(default is "Y"):Y
VERBOSE: Remove-Message : Ending processing.
[PS] C:\>Remove-Message -filter {FromAddress -eq ""} -withNDR $false -debug -ver
bose
VERBOSE: Remove-Message : Beginning processing.
Confirm
Are you sure you want to perform this action?
Removing the messages that match filter "FromAddress -eq """.
Yes Yes to All No [L] No to All Suspend [?] Help
(default is "Y"):Y
VERBOSE: Remove-Message : Ending processing.
[PS] C:\>
Tried several filter options and all had the same result. No events in the event viewer and did not remove the stuck messages.

Drop messages in queue that have a blank sender

I'm getting hundreds of messages in the Queue where the From Address is < >.
Do I just let these build up or is there a setting somewhere that would just drop the message if it has a blank sender?
Here is an example of one that I've received;
Identity: Pebbles\512\21474838371
Subject: Undeliverable: MUST READ: Vehicle's Below Kelly-Blue-Book*
Internet Message ID: <[email protected]>
From Address: <>
Status: Ready
Size (KB): 10
Message Source Name: DSN
Source IP: 255.255.255.255
SCL: -1
Date Received: 5/27/2014 11:51:09 AM
Expiration Time: 5/29/2014 11:51:09 AM
Last Error: 400 4.4.7 Message delayed
Queue ID: Pebbles\512
Recipients: [email protected];2;2;[{LRT=};{LED=400 4.4.7 Message delayed};{FQDN=};{IP=}];0;CN=outbound,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT)....
1 email server in domain; Exchange 2013 sp1/Win2012 Standard
PennyM

On Exchange 2010 you have antispam agents that can help you discard such messages.
Sender filtering has a check box called drop messages with blank senders select that and restart the transport service on the servers to get that updated quickly.
In 2013 server, you have sender filtering as well.

Prosecced messages in queue

Hello!
Came across puzzle when do dequeue messages:
We want to dequeue all messages for particular consumer.
We do dequeue with no_wait, first_message, consumer_name.
It works all right.
All messages for specified consumer is dequeued.
Immediately querying view AQ$QUEUE_T_QUEUE_x - we can see that dequeued messages are in 'PROCESSED' status
and in 'READY' status in table QUEUE_T_QUEUE_x.
Wait some Time - query view/table again - and we dont see them any more in the queue.
Queue retention is set to 25 hours. So messages deleted from queue much more fast.
The main question is - what does the
Time between message is in 'PROCESSED' state after dequeue
and
time it disappears from queue
depend on?
We see different Time on different instances.
AQ_TM_PROCESSES=10
We guess that may be it's Queue Monitor that responsible for that?
Does anybody know what is going on and how to control it?
Any help is appreciated!
Thanks in advance!

Hi maha,
Yes, queue monitor has responsible for post-process of dequeued messages in queue table.
In 10gR2, Queue Monitor processes deqeueud messages every 30 seconds.
If queue retention time are already expired when a queue monitor checks qtable, then a Queue Monitor removes messages from qtable. Otherwise, Queue Monitor update "deq_time" column in qtable. (deq_timestamp column in view is differ from deq_time in qtable.)
However, I don't know why your messages are removed from qtables even though you set queue retention to 25 hours. And I have no idea to control Queue Monitor cycle, behavior, and so on,

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?

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

TTL of message in queue

Hi all!
How can I define message time-to-live in queue? I've got some messages in queue with expiraton date by the year 2038.

1. I've applied patch 116568-53 on my test system.
2. I've executed patch-config and install-newconfig. Then imsimta chbuild and imsimta cnbuild have been executed.
3. start-msg
4. My directory has been updated from cfgdir_diff.ldif and ugdir_diff.ldif.
5. imta.cnf contain:
defaults logging notices 1 2 4 7 copywarnpost ......
! tcp_local
tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver sa
slswitchchannel tcp_auth missingrecipientpolicy 0
tcp-daemon
etc.
6. After that I've sent message on [email protected]
7. root@sun/opt/SUNWmsgsr/sbin> ./imsimta cache -dump
channel : tcp_local
file name : /opt/SUNWmsgsr/data/queue/tcp_local/011/ZXe0j750N0so7.00
subdirectory : 11
enqueue time : 22-Sep-2004 16:43:38.00
last delivery attempt : 22-Sep-2004 17:12:07.00
processing priority : 3
destination system : ddddddd.com
recipient count : 1
message size : 1 (kbyte)
owner : mailsrv
expiration date : 19-Jan-2038 06:14:07.00
8. qm.maint> his 1
Message id: 1
Filename: /opt/SUNWmsgsr/data/queue/tcp_local/011/ZXe0j750N0so7.00
Transport layer information:
Envelope From: address: [email protected]
Envelope To: addresses: [email protected]
Message delivery history:
Wed, 22 Sep 2004 16:43:39 +0400 (MSD)
TCP active open: Failed connect() Error: Connection refused
Wed, 22 Sep 2004 16:55:23 +0400 (MSD)
TCP active open: Failed connect() Error: Connection refused
What does "expiration date" mean ? Why 2038 year ?

Delivery expired (message too old)

Hello,
I am getting a few errors each day related to the following type of message. I have done some web searches, and a few pointed to Windows 2008 DNS as a possible problem. However, our Ironports point to our external DNS which is BIND.   Here is the relevant data from message tracking.
SMTP delivery connection (DCID 163673330) opened from IronPort interface 10.193.13.181 to IP address 10.192.3.45 on port 25.
19 Jul 2011 17:20:01 (GMT -04:00)
(DCID 163673329) Message 492404228 to [email protected] bounced by destination server. Reason: 5.4.7 - Delivery expired (message too old) ('000', ['[Errno 61] Connection refused']) [(\'X-SBRS\', \'None\'), (\'X-HAT\', \'Group: RELAYLIST, Policy: $RELAYED\'), (\'X-VITAFiles\', \'Attached: image001.jpg, image002.jpg\'), (\'subject\', \'RE: orientation\'), (\'from\', \'"Evans, PATRICIA EVANS (DBHDS)" <[email protected]>\'), (\'to\', \'"Breeding, Myra" <[email protected]>\')]
Anyone else see this? Any ideas on how to fix it?
Thanks ahead of time!
Elias

Greetings Elias,
With the data you provided its a bit difficult to say if this is related to a DNS issue or not. A couple of things you may want to do here to further diagnose this.
If delivery attempts fail, this means the destination's mail server did not accept a given message after 72 hours or 100 iterations of consecutive tries (example).   This issue can be seen either incoming (delivery to your internal groupware server) or outgoing (towards another domain via the Internet).   While this does not necessarily signal a problem with your local IronPort ESA, you can work around this by extending the retransmission period or number of attempts, and therefore increasing the chances for successful delivery.   These values are controlled by the IronPort's Bounce Profiles.
Note: If you wish to make the retransmission timeout more lax, increasing the value may increase your chance for successful delivery.   The overall duration (i.e., "maximum number of seconds") defines times in terms of seconds. The default value is 259,200 seconds, or three days. We'd recommend increasing this threshold to 345,600 seconds (four days) or 432,000 (five days) if necessary.
To edit the "Default" bounce profile via the GUI:
1) Go to Network > Bounce Profiles > select your Profile Name
2) set "Maximum Number of Retries" to change the number of times we attempt delivery
3) set "Maximum Time in Queue" to specify the total length of time to store the message for retransmission
4) set "Maximum Time to Wait per Message" to give the maximum interval between retries
Alternatively, we can use the CLI 'bounceconfig' command to set the same values.
You may also want to enable the domain debug logs to this host. This way you can see the full smtp conversation between your appliance and the remote host. This may provide some more detail on the previous failures before it gets to this state.
Additionally you may want to also consult the mail logs for the previous failures.
Below is some more information on setting up the domain debug logs.
The domain debug log is a system log designed to record all SMTP traffic between a specific domain and an   Email Security Appliance (ESA) for a finite number of sessions. This log type can assist in troubleshooting issues that relate to a specific recipient domain or host. Each session is recorded until the number of session defined has been reached, at which time the log will stop collecting data. You can stop domain debug before all sessions have been recorded by deleting or editing the log subscription.
Configuration
Logs can be configured and created through the IronPort CLI   using the logconfig command or via the GUI.
To configure logs via the GUI, see the Advanced User Guide: Log Subscriptions .
Below is an example of creating a Domain Debug Log subscription using the CLI:.
example.run> logconfig
Currently configured logs:
1. "antispam" Type: "Anti-Spam Logs" Retrieval: FTP Poll
2. "antivirus" Type: "Anti-Virus Logs" Retrieval: FTP Poll
3. "asarchive" Type: "Anti-Spam Archive" Retrieval: FTP Poll
4. "avarchive" Type: "Anti-Virus Archive" Retrieval: FTP Poll
5. "bounces" Type: "Bounce Logs" Retrieval: FTP Poll
6. "cli_logs" Type: "CLI Audit Logs" Retrieval: FTP Poll
7. "error_logs" Type: "IronPort Text Mail Logs" Retrieval: FTP Poll
8. "euq_logs" Type: "IronPort Spam Quarantine Logs" Retrieval: FTP Poll
9. "euqgui_logs" Type: "IronPort Spam Quarantine GUI Logs" Retrieval: FTP Poll
10. "ftpd_logs" Type: "FTP Server Logs" Retrieval: FTP Poll
11. "gui_logs" Type: "HTTP Logs" Retrieval: FTP Poll
12. "mail_logs" Type: "IronPort Text Mail Logs" Retrieval: FTP Poll
13. "reportd_logs" Type: "Reporting Logs" Retrieval: FTP Poll
14. "reportqueryd_logs" Type: "Reporting Query Logs" Retrieval: FTP Poll
15. "scanning" Type: "Scanning Logs" Retrieval: FTP Poll
16. "sntpd_logs" Type: "NTP logs" Retrieval: FTP Poll
17. "status" Type: "Status Logs" Retrieval: FTP Poll
18. "system_logs" Type: "System Logs" Retrieval: FTP Poll
19. "updater_logs" Type: "Updater Logs" Retrieval: FTP Poll
Choose the operation you want to perform:
- NEW - Create a new log.
- EDIT - Modify a log subscription.
- DELETE - Remove a log subscription.
- SETUP - General settings.
- LOGHEADERS - Configure headers to log.
- HOSTKEYCONFIG - Configure SSH host keys.
[]> new
Choose the log file type for this subscription:
1. IronPort Text Mail Logs
2. qmail Format Mail Logs
3. Delivery Logs
4. Bounce Logs
5. Status Logs
6. Domain Debug Logs
7. Injection Debug Logs
8. System Logs
9. CLI Audit Logs
10. FTP Server Logs
11. HTTP Logs
12. NTP logs
13. LDAP Debug Logs
14. Anti-Virus Logs
15. Anti-Virus Archive
16. Scanning Logs
17. IronPort Spam Quarantine Logs
18. IronPort Spam Quarantine GUI Logs
19. Reporting Logs
20. Reporting Query Logs
21. Updater Logs
[1]> 6
Please enter the name for the log:
[]> debug_example
Enter the name of the domain for which you want to record debug information.
[]> example.com
Please enter the number of SMTP sessions you want to record for this domain.
[1]> 8
Choose the method to retrieve the logs.
1. FTP Poll
2. FTP Push
3. SCP Push
4. Syslog Push
[1]>
Filename to use for log files:
[example.com.text]>
Please enter the maximum file size:
[10485760]>
Please enter the maximum number of files:
[10]>
Currently configured logs:
1. "antispam" Type: "Anti-Spam Logs" Retrieval: FTP Poll
2. "antivirus" Type: "Anti-Virus Logs" Retrieval: FTP Poll
3. "asarchive" Type: "Anti-Spam Archive" Retrieval: FTP Poll
4. "avarchive" Type: "Anti-Virus Archive" Retrieval: FTP Poll
5. "bounces" Type: "Bounce Logs" Retrieval: FTP Poll
6. "cli_logs" Type: "CLI Audit Logs" Retrieval: FTP Poll
7. "debug_example" Type: "Domain Debug Logs" Retrieval: FTP Poll
8. "error_logs" Type: "IronPort Text Mail Logs" Retrieval: FTP Poll
9. "euq_logs" Type: "IronPort Spam Quarantine Logs" Retrieval: FTP Poll
10. "euqgui_logs" Type: "IronPort Spam Quarantine GUI Logs" Retrieval: FTP Poll
11. "ftpd_logs" Type: "FTP Server Logs" Retrieval: FTP Poll
12. "gui_logs" Type: "HTTP Logs" Retrieval: FTP Poll
13. "mail_logs" Type: "IronPort Text Mail Logs" Retrieval: FTP Poll
14. "reportd_logs" Type: "Reporting Logs" Retrieval: FTP Poll
15. "reportqueryd_logs" Type: "Reporting Query Logs" Retrieval: FTP Poll
16. "scanning" Type: "Scanning Logs" Retrieval: FTP Poll
17. "sntpd_logs" Type: "NTP logs" Retrieval: FTP Poll
18. "status" Type: "Status Logs" Retrieval: FTP Poll
19. "system_logs" Type: "System Logs" Retrieval: FTP Poll
20. "updater_logs" Type: "Updater Logs" Retrieval: FTP Poll
Choose the operation you want to perform:
- NEW - Create a new log.
- EDIT - Modify a log subscription.
- DELETE - Remove a log subscription.
- SETUP - General settings.
- LOGHEADERS - Configure headers to log.
- HOSTKEYCONFIG - Configure SSH host keys.
[]>
example.run> commit
Domain Debug Log
Below is an example of a Domain Debug Log looks like when the IronPort appliance delivers a message to the recipient domain: "example.com".
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '220 ESmtp mail.example.com ESMTP service ready'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'EHLO ironport.com'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250-mail.example.com'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250-8BITMIME'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250-SIZE 31981568'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250 PIPELINING'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'MAIL FROM:<[email protected]>'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250 sender <[email protected]> ok'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'RCPT TO:<[email protected]>'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250 recipient <[email protected]> ok'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'DATA'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '354 go ahead'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'Received: from unknown (HELO)(10.250.7.164)rn by ironport.com with SMTP; 22 Mar 2005 16:52:08 -0800rn'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'Message-ID: <[email protected]>rnFrom: "User" <[email protected]>rnTo:<[email protected]>rn Subject:TestrnDate:Tue,22Mar200516:57:28-0800rnMIME-Version:1.0rn
Content-Type:multipart/alternative;rntboundary="----=_NextPart_000_000A_01C52F00.3AA3B580"rnX-Priority: 3rnX-MSMail-Priority: Normalrn X-Mailer: Microsoft Outlook Express 6.00.2900.2180rnX-MimeOLE: Produced ByMicrosoft MimeOLEV6.00.2900.2180rnrnThis is a multi-part messageinMIMEformat.rnrn------=_NextPart_000_000A_01C52F00.3AA3B580rnContent-Type:text/plain;rntcharset= "iso-8859-1"rnContent-Transfer-Encoding: quoted-printablernrnThis isthebodyofthemail.rnThisisadisclaimer.rnrn------=_NextPart_000_000A_01C52F00.3AA3B580rnContent-Type:text/html;rntcharset=   "iso-8859-1"rnContent-Transfer-Encoding:quoted-printablernrnrnrnrnrnrnrnrnThis is the body of thernmail.
This is a disclaimer.rn rnrn------=_NextPart_000_000A_01C52F00.3AA3B580--rn'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: '.rn'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250 ok dirdel'
Tue Mar 22 16:52:12 2005 Info: 411 Sent: 'QUIT'
Tue Mar 22 16:52:12 2005 Info: 411 Rcvd: '221 mail.example.com'
Christopher C Smith
CSE
Cisco IronPort Customer Support

Receiving expired messages

Hi,
We keep receiving expired messages. The JMS specification says 'The JMS provider should do its best to expire messages accurately', so no guarantees here.
Is this normal behaviour?
Test-code at http://www.invenso.com/upload/openmq.test.zip
We use Open Message Queue 4.3 Build 7-g
Thanks,
Brecht

I'm not sure if I understand your question. The sentence that you're referring to describes how the messages should be expired. What it means is that if you set the expiration time to something very small you may have problems, the messages may arrive on the broker already expired or it may be expire while being processed by the consumer and before it has a chance to ack it. Also due to overhead of message processing on the broker and the load the expire thread may have problems maintaining the accuracy when the expire time is very small.
Tom

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.

Issue while posting message to queue

Hi ,
I am getting following exception while posting message into queue.For every new build I am getting this exception and after 2 or 3 times of restart of corresponding OBPM related weblogic server,Issue is getting resolved
A component failed while executing activity '/COM/OU/UserlProcess#Default-3.0/ComponentExecution[PreProcessor]' (BP-method preProcessor) over instance '/COM/OU/UserlProcess#Default-3.0/15141/0'.
Details:
The task could not be successfully executed.
Reason: 'fuego.connector.ConnectorException: Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Detail:Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Caused by: Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Detail:Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Caused by: Connector [MAIN_Q:null:JMS] returned the wrong class [com.tibco.tibjms.naming.TibjmsConnectionFactoryAttributes] for a resource of type [2].
Detail:Connector [MAIN_Q:null:JMS] returned the wrong class [com.tibco.tibjms.naming.TibjmsConnectionFactoryAttributes] for a resource of type [2].
fuego.lang.ComponentExecutionException: The task could not be successfully executed.
Reason: 'fuego.connector.ConnectorException: Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Detail:Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
     at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1091)
     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1277)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.runCil(ComponentExecutionMicroActivity.java:126)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:84)
     at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57)
     at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
     at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
     at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251)
     at fuego.ejbengine.ItemExecutionBean$1.execute(ItemExecutionBean.java:217)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
     at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:203)
     at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:115)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4123)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:4013)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4541)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: fuego.connector.ConnectorException: Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
Detail:Connector [MAIN_Q:null:JMS] caused an exception when getting a resource of type [7].
at fuego.connector.ConnectorException.exceptionOnGetResource(ConnectorException.java:95)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:324)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:298)
     at fuego.connector.JMSHelper.getSession(JMSHelper.java:75)
     at fuegoblock.msg.DynamicJMS.sendMessage(DynamicJMS.java:145)
     at xobject.Utility.JMSService.writeToAppQueue(JMSService.xcdl:11)
     at xobject.Utility.Notification.sendAuditNotification(Notification.xcdl:19)
     at XXX.ManualProcess.Default_3_0.Instance.CIL_preProcessor(Instance.xcdl:20)
     at XXX.ManualProcess.Default_3_0.Instance.CIL_preProcessor(Instance.xcdl)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1082)
     ... 31 more
Please help how can I resolve this issue
Thanks
Sailendra

I am also getting the same issue. Sailendra, did you resolve the issue?
If not could anyone help us to resolve this issue.
I am using Tibco JMS for queue and I have set 'ConnectionFactory' as Connection Factory Lookup Name value in the external resourse.
Thanks in advance.
Regards,
Ramanan

Expire messages in queue

Similar Messages

Maybe you are looking for