Tasks stuck in 'In Queue' status

Hi,
Recently we upgraded from OIM 8.5.3 to OIM 9.1. We have a Websphere Clustered environment.
Whenever an Approver or SA approved a pending task or sets response to the Open Tasks, the task's status becomes In Queue and remains as that only. It doesn't go off from the Items To Review (for AAs) and Open Tasks (for SAs) tables.
All the JMS queues are set properly and so also the JMS Cluster. There is no error/exception in the logs.
Any idea why its behaving like this? Any suggestions/solutions?
Thanking you,
Kulesh...

JMS related problems can be really hard to resolve. I assume that you have raised an SR with Oracle?
The JMS tables are mirrored into database tables named after the name of your Websphere hosts. You might learn something by checking the content of these tables.
The whole JMS system was rebuilt in 9.1 with the addition of multiple JMS queues. There might be some kind of issue with some part of the JMS system not upgrading properly.
Are you still using Microsoft SQL server?
Best regards
/Martin

Similar Messages

Messages stucked in moni with queue status as "RUNNING"

Hi All,
Few of messages stucked in moni with queue status as "RUNNING" from the past 6 to 7 hours. all the stucked messages running on same dialog instance app server 03 (ucobpi03_PIP_03). i checked PIP appserver its working fine.
Can any one please expalin me how to clean the queues..is there any effect of other queues ?
Thanks,
Siva.

Hi,
it can be due to multiple reasons....
check the interface logic built ...it can be either due to this or can be of large volume of data...
Also check the queues have been registered or not...
HTH
Rajesh

Queue Status in SMQ2 = RUNNING, but Stuck.

I have a queue that sometimes gets stuck in SMQ2 in status RUNNING (for no apparent reason).
If I activating the queue manually (as suggested in
http://help.sap.com/saphelp_nw04/helpdata/en/d9/b9f2407b937e7fe10000000a1550b0/frameset.htm)
usually solves the problem.
Therefore, this queue processes messages 24x7 and cannot get stuck for more than 5 minutes.
Question n1)Is there a way I can do this automatically (scheduling a JOB) (itu2019s a specific queue, that is only used for this single process)?
Question n2) Sometimes, after activating the queue again, the message continues in status RUNNING, and the only solution is to delete the message and activating the queue manually (when I do this, after processing every message in the queue, when new messages begin to arrive, the queue goes to status READY for a LONG time.) Does anyone knows whats going on?
obs.: The message is ALWAYS processed successfully, and there is no problem to process it 2 times. The only thing that cannot happen is STOP the process.
Thank you.
At.,
Bernardo Tavares Braga

1) I already registered all the queue through sxmb_adm - didn't change anything.
2) This queue is on SAP PI/XI, but the message goes to SAP ECC.
Since the process is executed, what I think happens is that the message updates SAP ECC, but somehow it doesn't give a return to SAP PI/XI.
So SAP PI/XI thinks its still executing.
Pinangshuk, the MONITOR QRFC_RESTART_ALLOWED is set to value 1(in the Integration Engine configuration - sxmb_admin)
Also, this enables the restart of stuck queues manually. Is there a way to do this automatically?

Send Commit to message stuck in "Message Scheduled" status

Hello,
I generated some messages using ABAP Proxy. However, the commit work never happened in the program that created the message. Now these messages are stuck in "Message Scheduled" status. How can I push the message forward. Can I trigger a commit? If so, how?
Regards
Cerish

Hi Cerish,
Are you getting this status in the XI ? If so, go to Queue Monitor and try to activate the same.
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Also check the SXMB_MONI of Application System(R/3) if you have a access about is proxy message is executed or not .
If the status is restart not possible, then you need to reprocess that.
Hope this helps,
regards,
moorthy

Stuck messages in Queue

Hi,
I have a scenario SAP ECC > PI > 3rd Party.
Messages are being send from SAP ECC to PI however the messages encountered an authorization error when sending to PI. During the fix, almost 1500 messages were stuck in the different queues in SAP ECC - SMQ2. the status of the other messages were in Green flag while the others are in Red flag.
Now the fix has been made, the messages that we are now transacting is still stuck in the queue.Why are the other messages stuck in queue? Shouldnt it proceed? Does the queue in SMQ2 have a threshold or limit in continuing the other messages even the first messages were in error?
thank you.

Hi,
use TCODE--SMQR for registering and deregistering.
The queues which are avialbale in SMQR are the registerd and activated queues.
each queue has type and mode.
where type 'R' means registered and activated
Regards
Mastan

Queue status is stopped

Hi,
I have a File to Proxy assync. scenario. The file has been read, and then the message stops in the queue. I checked it on sxmb_moni, the message is posted on a queue and the queue status is "stopped" (with a red stop button printed on).
I have already read all the posts about this and couldn't find any solution... Can anyone help?
Thanks.
Shwetha

Yes connection is set proper now.
And the scenario involves EOIO
Since it is EOIO, i would suggest that you see the status of the messages in RWB (it may be in Holding)....if it is Holding then follow the lead given in this blog: /people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Regards,
Abhishek.

File to IDOC stuck in the queue

Hi Expert,
I have a file to IDOC scenario. I checked in SXMB_MONI, I can see the file coming in. But it just stuck in the queue and won't send out to SAP system. When I checked the SMQ2, it tells me the status is "SYSFAIL'. I have checked my RFC, port, logical systems, profile etc. Just don't know where is wrong. Can somebody tell me what else I need to check? Thank you very much!
Charles

Hi Charles
Check SMQ2 and double click on the queue with sysfail status.
It will show you a new screen with a more detailed error description.
Regards,
Giuseppe

Message stuck in inbound queue of r/3 for inbound proxy

Hi Experts,
The scenerio is Inbound Proxy.
I m using standard prgram rfbibl00 to post a document (FB01) in Inbound proxy. When the message is triggered from XI, it get stuck in inbound queue of R/3 ( SMQ2) giving the status text "Session 1: Special character for 'empty field' .
Please help to resolve this issue.
Thanks in advance.

dear experts,
did u get chance to look into this issue.
Thanks in advance.

Some Journaled Calendar Requests get stuck in Submission queue - 550 5.6.0 - storage error in content conversion

I am having an issue on hub transport servers running Exchange 2010 SP3 RU6.
Where some journaled meeting request related messages (acceptances, etc.) get stuck in the Submission queue.
The error is:
400 4.4.7 The server responded with: 550 5.6.0 M2MCVT.StorageError; storage error in content conversion. The failure was replaced by a retry response because the message was marked for retry if rejected.
I raised the issue with our mail archiving vendor and they indicated this was an Exchange Server problem which should have been fixed in Exchange 2010 SP3 RU3, however we are running SP3 RU6 and the issue continues to occur.
I realize that we could just delete the stuck messages from queue but has anyone run in to this before and know how to prevent it from happening?
Thank You.

Hi Mike,
If you temporary disable\bypass third party Archiving , then what happens in the Queue.
Thanks , Prakash
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Message getting stuck in XBQO queue - Time limit exceeded

Hi All,
We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.
However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.
Any pointers to this will be really appreciated.
Thanks & Regards,
ROSIE SASIDHARAN

H Rosie,
1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)
The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.
2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.
The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
See SAP Note 335162 for sysfail issue....
Hope these will help u....
Regds,
Pinangshuk.

TNEF Issue - Winmail.dat or messages stuck in submission queue

Hi guys,
I've looked around the forums and have found people that have had submission queue issues when they set TNEF to $null or $false, and have found that the unified answer is to set TNEF to $true.
I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
I have both issues. If I set TNEF to $true, I encounter the winmail.dat file problem. If I set TNEF to $false or $null, I encounter the submission queue issue (submission queue states "A transient storage failure occured", and users get a queue
expiration bounce). Neither of these states are acceptable. I cannot have messages stuck in the queue only to be expired, and I cannot have recipients in remote domains failing to receive attachments in emails.
Does anyone have a possible workaround that might resolve this particular situation? It seems that this has been an issue in Exch 2010.
Current Environment Configuration:
I am running Exchange 2013 SP1 Standard on both of my CAS/MBX servers, running on Server 2012 R2 patched to the latest updates. I have an inbound spam filter, but mail outbound is not filtered, therefore the spam filter on our side should not play a role.
I do have not made any changes to the exchange default malware filter either. Other than this issue, mail is flowing correctly and as expected.

I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
Hi,
According to your description, my understanding is that all the remote domain's recipients would receive winmail.dat files when you send the message to them if TNEF is set to $true, right?
The Winmail.dat file is used to preserve Rich Text formatting. Outlook uses it when sending a Rich Text-formatted message. During transport, the content of the message may be changed, preventing the receiving client from being able to read the formatting
instructions. In other cases, the receiving client does not use or recognize the winmail.dat file.
I recommend that you refer to the following article to solve the issue:
http://support.microsoft.com/kb/278061
Method 1: Change the default message format
The sender can change the format of the email messages that they send by using the following steps:
On the Tools menu, click Options, and then click
Mail Format.
In Compose in this message format, click to select Plain Text, and then click
OK.
NOTE: To send to certain recipients that use RTF format and others recipients that use plain text format, the sender must set the option for the recipient in either the Personal Address Book or the recipient's contact record.
Method 2: Modify the recipient's entry in the Personal Address Book
The sender can use the following steps to remove the RTF format from the recipient attribute in the Personal Address Book:
On the Tools menu, click Address Book.
In Show Names From, click the Personal Address Book.
Select the addressee that you want to set as plain text, and then click
Properties on the File menu.
In the SMTP-General tab, click to clear the Always send to this recipient in Microsoft Exchange rich text format check box, and then click
OK.
Method 3: Change the specific contact format
The sender can use the following steps to set plain text in the recipient's contact record:
Open the recipient's record in the Contacts folder.
Double-click the recipient's e-mail address.
In the E-Mail Properties dialog box, click Send Plain Text only under
Internet Format.
Method 4: Set the Outlook Rich Text Format Internet e-mail setting
In Outlook 2003 and Outlook 2007, click Options on the Tools menu.
Click the Mail Format tab.
Click Internet Format.
Under Outlook Rich Text options, click either Convert to HTML format or
Convert to Plain Text format.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
Niko,
The Winmail.dat issue is only part of the problem, as described in my original post. For these messages (which it's a different set of messages every time, and it's becoming impossible for me to track them all down), if I set exchange or outlook to encode
the message in Rich Text, the message gets encoded and sent to the recipient. Some of our recipients will reject the message because it is rich text, others receive a winmail.dat file.
However, if I set exchange to not encode messages (TNEF= $false or $null), the message becomes stuck in the submission queue and eventually times out with an error resembling "Storage Transient Failure".

HELP! Mail stuck in the queue.

Hey All,
We just noticed that none of us here recieved any mail today and that all of our messages incoming/outgoing have been stuck in the queue all day.
We seem to be able to view old messages with our mail clients as well as any folders. But any new messages that we send or recieve just go to the server and sit there.
It's quite puzzeling because we haven't changed anything on it, the server has just been quietly humming along for a while now.
However, this seems to have started happening after we restarted the box this morning because a web app we were building on it ended up in an infinite loop.
I tried re-starting the box, restarting the mail service, resending the queue and nothing, messages hit the queue and fail to be delivered to mailboxes.
Looking at my logs I saw this:
Nov 9 16:56:28 resserver imap[4733]: DBERROR: critical database situation
Nov 9 17:00:07 resserver imap[4833]: DBERROR: critical database situation
Nov 9 17:15:56 resserver reconstruct[5700]: DBERROR: critical database situation
Nov 9 17:16:02 resserver reconstruct[5726]: DBERROR: critical database situation
In the queue some messages say this at the end:
host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down, closing channel (in reply to end of DATA command
Looking in my resources and in other places on the forums I've tried the following so far in hopes to narrow down and fix the problem:
- rebuilt with mailbfr (as per petrobytes suggestion with someone else)
- turned on and off content filtering
- confirmed that the machine has the same IP
- confirmed that it resolves forward and backward to it's hostname/IP
I can post any conf files you need, I'm desperate to get this fixed! Any help or insight anyone could provide would be well appreciated!
eMac, iBook, iMac, xServe, PowerBook Mac OS X (10.4.3)

I'm noticing some interesting stuff happening in the logs can someone make sense of this?
solutionim.com /usr/bin/amavisd[7872]: (07872-01) Requesting process rundown after fatal error
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7872]: (07872-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 2 results at (eval 41) line 150.
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T184715-07873
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TIMING [total 350 ms] - SMTP EHLO: 23 (7%), SMTP pre-MAIL: 2 (1%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 9 (3%), SMTP DATA: 9 (3%), body_hash: 3 (1%), mkdir parts: 3 (1%), mime_decode: 72 (21%), rundown: 226 (65%)
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 568.
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) Requesting process rundown after fatal error
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) ESMTP::10024 /var/amavis/amavis-20061109T184715-07876: <[email protected]> -> <[email protected]> Received: SIZE=50687 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07876-01 for <[email protected]>; Thu, 9 Nov 2006 18:47:15 -0500 (EST)
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) Checking: [216.46.146.115] <[email protected]> -> <[email protected]>
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p004 1 Content-Type: multipart/mixed
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p005 1/1 Content-Type: multipart/alternative
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p001 1/1/1 Content-Type: text/plain, size: 259 B, name:
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p002 1/1/2 Content-Type: text/html, size: 2227 B, name:
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p003 1/2 Content-Type: application/vnd.ms-excel, size: 33280 B, name: Emploment Application.xls
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7879]: (07876-01) run_command: child process [7879]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7879]: (07876-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T184715-07876
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 3 results at (eval 41) line 150.
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T184715-07876
Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TIMING [total 366 ms] - SMTP EHLO: 24 (7%), SMTP pre-MAIL: 3 (1%), mkdir tempdir: 2 (0%), create email.txt: 2 (1%), SMTP pre-DATA-flush: 25 (7%), SMTP DATA: 31 (8%), body_hash: 3 (1%), mkdir parts: 3 (1%), mime_decode: 95 (26%), rundown: 178 (49%)
Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 771.
Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) Requesting process rundown after fatal error
Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 18:48:33 resserver.resolutionim.com /usr/bin/amavisd[7759]: Net::Server: 2006/11/09-18:48:33 Server closing!
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: starting. /usr/bin/amavisd at resserver.resolutionim.com amavisd-new-2.2.0 (20041102), Unicode aware
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: user=, EUID: 0 (0); group=, EGID: 0 0 (0 0)
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Perl version 5.008006
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: 2006/11/09-18:48:36 Amavis (type Net::Server::PreForkSimple) starting! pid(7927)
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Binding to UNIX socket file /var/amavis/amavisd.sock using SOCK_STREAM
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Binding to TCP port 10024 on host 127.0.0.1
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Setting gid to "82 82"
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Setting uid to "82"
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Amavis::Conf 2.033
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Archive::Tar 1.22
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Archive::Zip 1.14
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Compress::Zlib 1.33
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Convert::TNEF 0.17
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Convert::UUlib 1.03
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module DB_File 1.810
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Entity 5.416
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Parser 5.416
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Tools 5.416
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::Header 1.65
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::Internet 1.65
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::SpamAssassin 3.001005
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::Cmd 2.26
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::DNS 0.58
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::SMTP 2.29
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::Server 0.94
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Time::HiRes 1.65
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Unix::Syslog 0.99
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Amavis::DB code NOT loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Amavis::Cache code NOT loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Lookup::SQL code NOT loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Lookup::LDAP code NOT loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: AMCL-in protocol code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: SMTP-in protocol code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: ANTI-VIRUS code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: ANTI-SPAM code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Unpackers code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $file at /usr/bin/file
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $arc, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $gzip at /usr/bin/gzip
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $bzip2 at /usr/bin/bzip2
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $lzop, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $lha, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unarj, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $uncompress at /usr/bin/uncompress
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unfreeze, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unrar, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $zoo, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $cpio at /usr/bin/cpio
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $ar, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $rpm2cpio, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $cabextract, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $dspam, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found secondary av scanner Clam Antivirus - clamscan at /usr/bin/clamscan
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: SpamControl: initializing Mail::SpamAssassin
Nov 9 18:48:44 resserver.resolutionim.com /usr/bin/amavisd[7927]: SpamControl: done
SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 350.
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9584]: (09584-01) Requesting process rundown after fatal error
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9584]: (09584-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09586: <[email protected]> -> <[email protected]>,<[email protected]> Received: SIZE=236428 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09586-01; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) Checking: [192.168.1.121] <[email protected]> -> <[email protected]>,<[email protected]>
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09587: <[email protected]> -> <[email protected]> Received: SIZE=2799147 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09587-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p008 1 Content-Type: multipart/alternative
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p001 1/1 Content-Type: text/plain, size: 1103 B, name:
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p009 1/2 Content-Type: multipart/mixed
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p002 1/2/1 Content-Type: text/html, size: 4971 B, name:
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p003 1/2/2 Content-Type: application/vnd.ms-excel, size: 16384 B, name: Feed Locations.xls
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p004 1/2/3 Content-Type: application/octet-stream, size: 15355 B, name: Example of Feed Locations.pdf
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p005 1/2/4 Content-Type: image/jpeg, size: 68882 B, name: zurlftoct06.JPG
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p006 1/2/5 Content-Type: image/jpeg, size: 65599 B, name: extrrtlondsoct06.JPG
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p007 1/2/6 Content-Type: text/html, size: 184 B, name:
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9588]: (09586-01) run_command: child process [9588]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9588]: (09586-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09586
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 7 results at (eval 41) line 150.
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09586
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TIMING [total 435 ms] - SMTP EHLO: 22 (5%), SMTP pre-MAIL: 3 (1%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 10 (2%), SMTP DATA: 45 (10%), body_hash: 6 (1%), mkdir parts: 3 (1%), mime_decode: 158 (36%), rundown: 185 (42%)
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 3144.
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) Requesting process rundown after fatal error
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09589: <[email protected]> -> <[email protected]> Received: SIZE=2244 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09589-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) Checking: [65.54.246.141] <[email protected]> -> <[email protected]>
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) p001 1 Content-Type: text/plain, size: 1084 B, name:
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9590]: (09589-01) run_command: child process [9590]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9590]: (09589-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09589
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 1 results at (eval 41) line 150.
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09589
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TIMING [total 240 ms] - SMTP EHLO: 19 (8%), SMTP pre-MAIL: 2 (1%), mkdir tempdir: 1 (1%), create email.txt: 2 (1%), SMTP pre-DATA-flush: 8 (3%), SMTP DATA: 2 (1%), body_hash: 2 (1%), mkdir parts: 3 (1%), mime_decode: 36 (15%), rundown: 165 (69%)
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 67.
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) Requesting process rundown after fatal error
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9591]: (09591-01) ESMTP::10024 /var/amavis/amavis-20061109T194145-09591: <[email protected]> -> <[email protected]> Received: SIZE=2799145 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09591-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:45 -0500 (EST)
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) Checking: [65.54.246.171] <[email protected]> -> <[email protected]>
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9591]: (09591-01) Checking: [65.54.246.173] <[email protected]> -> <[email protected]>
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p003 1 Content-Type: multipart/mixed
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p001 1/1 Content-Type: text/html, size: 6064 B, name:
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p002 1/2 Content-Type: video/x-ms-wmv, size: 2025860 B, name: JBSklip.wmv
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9592]: (09587-01) run_command: child process [9592]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9592]: (09587-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09587
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 2 results at (eval 41) line 150.
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09587
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) TIMING [total 1950 ms] - SMTP EHLO: 22 (1%), SMTP pre-MAIL: 4 (0%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 9 (0%), SMTP DATA: 868 (44%), body_hash: 34 (2%), mkdir parts: 3 (0%), mime_decode: 610 (31%), rundown: 397 (20%)
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) ESMTP::10024 /var/amavis/amavis-20061109T194146-09587: <[email protected]> -> <[email protected]> Received: SIZE=14124 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09587-02 for <[email protected]>; Thu, 9 Nov 2006 19:41:46 -0500 (EST)
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) Checking: [64.233.166.181] <[email protected]> -> <[email protected]>
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p003 1 Content-Type: multipart/alternative
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p001 1/1 Content-Type: text/plain, size: 2089 B, name:
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p002 1/2 Content-Type: text/html, size: 9454 B, name:
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9593]: (09587-02) run_command: child process [9593]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9593]: (09587-02) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194146-09587

545 mb file stuck in inbound queue

Hi
we are sending article master data from IS Retail to ftp server as flat file.
data size is around 545 mb...it got stuck in inbound queue(smq2) ..
error is : " Internally required memory is not available".
XI server config : RAM - 16 gb.
How to process such big file.
what are the hardware configuration needed ?
Regards
Abhijit

Hi Michal
Thanks for your response
This activity is done in PRD server.
An idoc with 545 mb data is triggred from SAP.
But it got stuck in inbound queue.
I came across a thread ..
Re: Processing large XML messages (>100Mb) in PI 7.1
According to this thread we need to maintain a parameter
icm/HTTP/max_request_size_KB has default value of 102400 & maximum it can accept is 2097152
Please suggest on this...do we need to maintain this parameter ?
Regards
Abhijit

Exchange 2010 inbound email (external/internal) randomly stuck in delivery queue

Dear all,
We got a problem email is not deliver to mailbox normal.
For example. I send a email to recipient A,B and C in same internal email.
The result is A can receive email normally, but B and C email is stuck in delivery queue.
We need to re-start the CAS transport service to release the email from delivery queue.
Any idea for this kind of email deliver issue?
Exchange server environment:
1. Two CAS/HT server in NLB mode (Exchange std. ver.)
2 Two Mailbox server in DAG mode (Exchange Ent. ver.)
We got this issue around 12 months on production migrate from 2000 to 2007 to 2010.
Felix.

hi,
What's the last error in the queue viewer? Do you have some error code?
You can use message tracking log to find more information about your issue.
If you create 3 new users and send a test mail to they, can they always receive the mail. May be your user account have some problem.
we need more information about your issue. Always is the stationary users or it is randomly?,The frequency of occurrence and so on.
hope can help you
thanks,
CastinLu
TechNet Community Support

** Message being processed - Queue status green colour

Hi Friends,
Many messages in our SXMB_MONI shows green color in the queue id column. It shows 'Message being processed'. All messages are in queue, still they are not delivered. Processing takes more hours. These messages are not EOIO queue. While we check this thru SMQ1 and SMQ2 it shows 'Running'. So, what could be the problem ...?
Kindly help friends, to solve this issue. (Points rewarded for helpful answer)
Kind Regards,
Jeg P.

HI,
QUEUE STATUS RUNNING BASICALLY MEANS THT
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
HOPE THIS WILL SOLVE THE PROBLEM
PLZ REWARDS POINTS
VIKAS

Tasks stuck in 'In Queue' status

Similar Messages

Maybe you are looking for