Service broker message stuck in Transmission Queue

Hi,
I have a fairly simple Service Broker set up to send messages between 2 DBs within the same instance. Since there is no cross-networking here, I did not set up any routes. So I have a SendQ associated with SendService in DB1 and a ReceiveQ associated with ReceiveService in DB2. Both are on Server S1.
I've set TRUSTWORTH on both DBs.
ALTER DATABASE <DBNAME> SET TRUSTWORTHY ON
Since I'm using Integrated Windows security, I also granted send permission to public
GRANT SEND ON SERVICE::ReceiveService TO [public];
However when I send out a message, it doesn't go to either the SendQ or ReceiveQ. Instead it sits in the sys.transmission_queue with the following message
An exception occurred while enqueueing a message in the target queue. Error: 916, State: 3. The server principal "S-1-9-3-4070899528-1141234901-971043712-2725434662." is not able to access the database "DB2" under the current security context.
Can anyone please help me with what I might be doing wrong or missing here? Thanks,

Please have a look at the following thread, it may help you solve your problem: http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/07dcab8c-b830-4ca9-8afc-3e75772f44d3/

Similar Messages

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".

Messages stuck in Inbound Queue with Ready Status

Hi All,
The messages in the Inbound queue are getting stuck in Ready status.
I have to manually Unlock each queue to start the processing.
After some time again all the message queue are back to the Ready State.
Please help me on this issue.
Regards
Milan

go to --> sxmb_adm
Manage Queue
Select all Queues, Activate Queues.
& check your scenarios, now it will not stuck due to this error.

Messages stuck in Java Queues

I am running PI7.0 SP10 on a MCOD system running ECC6.0 and EP.
We had an issue last week on our Production system where the Java Stack went down, and when the system came back up, we cleared the issues in SMQ1, SMQ2 and SM58 and now we have over two hundred messages stuck in the java queues.
There is nothing locked in SM13, in sxmb_moni all the messgaes are successfully processed... In the RWB the status of the messages are "To be delivered".
I have tried reactivating the adapters but this has not worked.
The queues can be seen in the http://host.fqdn:5<SYSNO>00/MessagingSystem/monitor/systemStatus.jsp
specifically : File_http://sap.com/xi/XI/SystemRecv
and
SOAP_http://sap.com/xi/XI/SystemRecv
where the "isStarted" is set to false, where all the others are true...
How can I go about starting these and processing the backlog of messages??
I have searched OSS, SDN and SAPFans but had not luck!
I have subsequently done a full cache refresh and CPACache refresh but this has not helped.
There are no locked users (XI/PI users) holding this up!

Ok,
It seems to be ok, the return can be http 200 or http 500.
The Soap and File are destinations, ok.
The messages are with status "delivering" on rwb... really, increasing the number of threads will not solve this...
I don't have access to visual admin (only basis team can access it here). I thought it could be something wrong with destination (but you already checked it)... so, the only thing can be done is to find in visual admin somewhere about system properties, conection parameters searching for something wrong there... here are our parameters if you would like to find something (sorry for the size of message)...
AFW.Call.maxConsumers 10
AFW.Recv.maxConsumers 5
AFW.Rqst.maxConsumers 10
AFW.Send.maxConsumers 5
BC_http://sap.com/xi/XI/System.Call.maxConsumers 20
BC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
BC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
BC_http://sap.com/xi/XI/System.Send.maxConsumers 10
BcAdapter.Call.maxConsumers 10
BcAdapter.Recv.maxConsumers 5
BcAdapter.Rqst.maxConsumers 10
BcAdapter.Send.maxConsumers 5
CIDXAdapter.Call.maxConsumers 10
CIDXAdapter.Recv.maxConsumers 5
CIDXAdapter.Rqst.maxConsumers 10
CIDXAdapter.Send.maxConsumers 5
CIDX_http://sap.com/xi/XI/System.Call.maxConsumers 20
CIDX_http://sap.com/xi/XI/System.Recv.maxConsumers 10
CIDX_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
CIDX_http://sap.com/xi/XI/System.Send.maxConsumers 10
EOIO.lockTimeout 5
File_http://sap.com/xi/XI/System.Call.maxConsumers 20
File_http://sap.com/xi/XI/System.Recv.maxConsumers 10
File_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
File_http://sap.com/xi/XI/System.Send.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Call.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Send.maxConsumers 10
JMS_http://sap.com/xi/XI/System.Call.maxConsumers 20
JMS_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JMS_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JMS_http://sap.com/xi/XI/System.Send.maxConsumers 10
JPR.Call.maxConsumers 10
JPR.Recv.maxConsumers 5
JPR.Rqst.maxConsumers 10
JPR.Send.maxConsumers 5
MPA.Call.maxConsumers 10
MPA.Recv.maxConsumers 5
MPA.Rqst.maxConsumers 10
MPA.Send.maxConsumers 5
Mail_http://sap.com/xi/XI/System.Call.maxConsumers 20
Mail_http://sap.com/xi/XI/System.Recv.maxConsumers 10
Mail_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
Mail_http://sap.com/xi/XI/System.Send.maxConsumers 10
Marketplace_http://sap.com/xi/XI/System.Call.maxConsumers 20
Marketplace_http://sap.com/xi/XI/System.Recv.maxConsumers 10
Marketplace_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
Marketplace_http://sap.com/xi/XI/System.Send.maxConsumers 10
RFC_http://sap.com/xi/XI/System.Call.maxConsumers 20
RFC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RFC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RFC_http://sap.com/xi/XI/System.Send.maxConsumers 10
RNIF11Adapter.Call.maxConsumers 20
RNIF11Adapter.Recv.maxConsumers 10
RNIF11Adapter.Rqst.maxConsumers 20
RNIF11Adapter.Send.maxConsumers 10
RNIF11_http://sap.com/xi/XI/System.Call.maxConsumers 20
RNIF11_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RNIF11_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RNIF11_http://sap.com/xi/XI/System.Send.maxConsumers 10
RNIFAdapter.Call.maxConsumers 10
RNIFAdapter.Recv.maxConsumers 5
RNIFAdapter.Rqst.maxConsumers 10
RNIFAdapter.Send.maxConsumers 5
RNIF_http://sap.com/xi/XI/System.Call.maxConsumers 20
RNIF_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RNIF_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RNIF_http://sap.com/xi/XI/System.Send.maxConsumers 10
SOAP_http://sap.com/xi/XI/System.Call.maxConsumers 20
SOAP_http://sap.com/xi/XI/System.Recv.maxConsumers 10
SOAP_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
SOAP_http://sap.com/xi/XI/System.Send.maxConsumers 10
bulkCommit.threshold 100
cluster.timeout 60000
connection.0.ackListener null
connection.0.exceptionListener localejbs/AFWListener
connection.0.jms.messageSelector null
connection.0.jms.profile null
connection.0.jms.provider null
connection.0.jms.queue null
connection.0.messageListener localejbs/AFWListener
connection.0.name AFW
connection.0.pollAttempts 60
connection.0.pollInterval 60000
connection.1.ackListener localejbs/MarketPlaceAdapterListener
connection.1.exceptionListener localejbs/MarketPlaceAdapterListener
connection.1.jms.messageSelector null
connection.1.jms.profile null
connection.1.jms.provider null
connection.1.jms.queue null
connection.1.messageListener localejbs/MarketPlaceAdapterListener
connection.1.name MPA
connection.1.pollAttempts 60
connection.1.pollInterval 60000
connection.2.ackListener null
connection.2.exceptionListener localejbs/JPR
connection.2.jms.messageSelector null
connection.2.jms.profile null
connection.2.jms.provider null
connection.2.jms.queue null
connection.2.messageListener localejbs/JPR
connection.2.name JPR
connection.2.pollAttempts 60
connection.2.pollInterval 60000
connection.3.ackListener null
connection.3.exceptionListener localejbs/RNIFMessageListener
connection.3.jms.messageSelector null
connection.3.jms.profile null
connection.3.jms.provider null
connection.3.jms.queue null
connection.3.messageListener localejbs/RNIFMessageListener
connection.3.name RNIFAdapter
connection.3.pollAttempts 60
connection.3.pollInterval 60000
connection.4.ackListener null
connection.4.exceptionListener localejbs/CIDXMessageListener
connection.4.jms.messageSelector null
connection.4.jms.profile null
connection.4.jms.provider null
connection.4.jms.queue null
connection.4.messageListener localejbs/CIDXMessageListener
connection.4.name CIDXAdapter
connection.4.pollAttempts 60
connection.4.pollInterval 60000
connection.5.ackListener localejbs/BcAdapterListener
connection.5.exceptionListener localejbs/BcAdapterListener
connection.5.jms.messageSelector null
connection.5.jms.profile null
connection.5.jms.provider null
connection.5.jms.queue null
connection.5.messageListener localejbs/BcAdapterListener
connection.5.name BcAdapter
connection.5.pollAttempts 60
connection.5.pollInterval 60000
connection.6.ackListener null
connection.6.exceptionListener localejbs/TestListener
connection.6.jms.messageSelector null
connection.6.jms.profile null
connection.6.jms.provider null
connection.6.jms.queue null
connection.6.messageListener localejbs/TestListener
connection.6.name test
connection.6.pollAttempts 60
connection.6.pollInterval 60000
connection.7.ackListener null
connection.7.exceptionListener localejbs/RNIF11MessageListener
connection.7.jms.messageSelector null
connection.7.jms.profile null
connection.7.jms.provider null
connection.7.jms.queue null
connection.7.messageListener localejbs/RNIF11MessageListener
connection.7.name RNIF11Adapter
connection.7.pollAttempts 60
connection.7.pollInterval 60000
connections (name=AFW, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=MPA, messageListener=localejbs/MarketPlaceAdapterListener, exceptionListener=localejbs/MarketPlaceAdapterListener, ackListener=localejbs/MarketPlaceAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=JPR, messageListener=localejbs/JPR, exceptionListener=localejbs/JPR, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=RNIFAdapter, messageListener=localejbs/RNIFMessageListener, exceptionListener=localejbs/RNIFMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=CIDXAdapter, messageListener=localejbs/CIDXMessageListener, exceptionListener=localejbs/CIDXMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=BcAdapter, messageListener=localejbs/BcAdapterListener, exceptionListener=localejbs/BcAdapterListener, ackListener=localejbs/BcAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=test, messageListener=localejbs/TestListener, exceptionListener=localejbs/TestListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)(name=RNIF11Adapter, messageListener=localejbs/RNIF11MessageListener, exceptionListener=localejbs/RNIF11MessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)
debug HTTP
failover.reassignOnNodeLoss true
initial.delay 0
jdbc.autoConfigure false
jdbc.datasource jdbc/SAP/BC_XI_AF_MSG
jdbc.dbProductName ORACLE
jdbc.substituteEmptyString true
jdbc.supportsOpenSQL true
jdbc.supportsScrollableResultSet false
jms.0.dmq SonicMQ.deadMessage
jms.0.messageLengthKey message_length
jms.0.password ********
jms.0.provider
jms.0.url
jms.0.username
monitoring.displayDefault fromParty, toParty, status, timesFailedRetries, sentRecvTime
persistMessageRemover.checkInterval 1440
proxy.password ********
proxy.user
reassignCheck.waitTime 30
ssl.httpsHandler iaik.protocol.https.Handler
ssl.securityProvider iaik.security.provider.IAIK
ssl.serverNameCheck false
ssl.trustedCACerts.viewName TrustedCAs
startup.delay 0
syncMessageRemover.checkInterval 60
syncMessageRemover.messageCount 1000
syncMessageRemover.removeBody true
system.deafaultMaxConsumersPerQueue 10
system.failNonDelivered false
system.message.lazyRead true
system.node 23654950
system.queueConsumerThreadPoolSize 0
system.statusLog System,Send,Recv,Call,Rqst
system.transactionManager ts
test.Call.maxConsumers 20
test.Recv.maxConsumers 10
test.Rqst.maxConsumers 20
test.Send.maxConsumers 10
throughputStatistics enabled
regards
roberti

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.

Messages stuck in the queue... how do I make them to be processed again?

Hi,
I'm new to SAP PI and kinda confused with queues.
I have file -> bpm -> file scenario and there was an error in mapping within bpm process.
When I went to qRFC Monitor (smq2), I see that in XBQO$PE_WS90000002 queue,
there's an error, 'Permanent error in BPE inbound processing'... which is expected.
Now, I run the interface scenario again several times but they don't get processed
but stuck in the same queue. At this stage, I didn't know what to do...
I thought by deleting the error message, other messages will be processed...
I deleted the error message but the other messages are still in the queue...
I have two questoins.
1. What is the best way to handle an error in the queue... can I just delete it? or is there a better way to handle an error in the queue?
2. After deleting the queue, what should I do to make the other messages to be processed again...
Thank you.
-Won

Hi Won,
There are programs for restarting the LUW entries:
programs
· RSARFCRD: tRFC Monitor (transaction SM58)
· RSARFCSE: Restart an LUW (background job)
· RSARFCEX: Restart tRFC LUWs (background job)
· RSQOWKEX: Restart QOUT qRFC LUWs
· RSQIWKEX: Restart QIN qRFC LUWs
· RSARFCSE: Delete an LUW (background job)
· RSARFCER: Delete various LUWs
Also, check the url:
http://help.sap.com/saphelp_nw04/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm
Hope this helps.
Regards,
Sushama

Messages Stuck in Submission Queue after Database failover to DR site

Hi Everyone,
Yesterday Night we had a Database failover to DR site but emails were stuck in the submission queue to resolve we failed back the Database. We have Exchange 2010 SP3 Ru4 with Active-Active DAG across 2 AD sites.
After checking the connectivity logs on the Transport server i found out that the Transport server was trying to connect to the mailbox server where this database was residing directly instead of using the Transport servers in the 2nd site.
We have 4 more databases on the same server but for those databases there was no issues and the mail flow was working fine.
Only thing i checked is that we have about 700 GB of log files for this database. Could that can cause this issue.

Hi,
Thanks for your response.
I did not restart transport service. I assume restarting transport service might have resolved the issue.
But, i want to know the reason why this happened as we have stretch DAG so this can cause major outage in case more mailbox database fails over.
Removing the logs files is what i am thinking to do maybe within this week.

Web service scenario -- message stuck in receiver PI engine

Hello expert
I have scenario HTTP --> PI --> WS (ABAP backend).
I have PI 7.1 and the backend is based on NW 7.0
I have configured the scenario in ID with receiver agreement of ws adapter. In the backend, I've generated the server proxy based on the service interface and configured endpoint in soamanager.
After everything is done, I tested the scenario. In MONI in PI, everthing looks good, message send to ws of hte backend. In MONI in the backend, I see the message with green flag indicating Released for processing (WS). Looks like message arrived at the local PI engine of the backend, but it doesn't know how to process it (by calling the web service). Does anybody know what could be the problem?
Thanks
Eric

Eric
Looks like your SRT is not set up yet. Try running program SRT_ADMIN_CHECK (I am not sure about the exact program name but it is somelike this) and see if you get some errors. The WS adapter uses bgRFC and hence you are not going to find anything in SMQ2.
Run program SRT_ADMIN in client 000 (using DDIC user) and in all clients where you will be using WS adapter. Please note this is a part of post installation configuration and I am assuming your system hasn't been set up for the SRT yet.
You also will have to set up a user ID for bgRFC and RFC destination (in Tcode SBRFCCONF). Please refer to the documentation from service market place for post installation tasks or take from your basis admin guys for setting up the SRT.
Thanks
KK

SSIS Catalog views are not executing from PROC calling from a service broker

Hi Exprets,
I have a package deployed on SSISDB (the new concept in MS SQL 2012, SSIS catalogs). I have t-sql code in which i will be able to execute SSIS package in SSISDB with no problems. But if i place the same t-sql code inside of a procedure which will be called
by a service broker , the code is not executing.
I am using the following code to execute a package in the SSISDB catalog
Declare @execution_id bigint
EXEC [SSISDB].[catalog].[create_execution] @package_name=N'LoadToABC.dtsx',
@execution_id=@execution_id OUTPUT, @folder_name=N'ABC', @project_name=N'LoadToABC',
@use32bitruntime=False, @reference_id=Null
DECLARE @var0 NVARCHAR(200)
= N'D:\MyData\SampleText20120830100001.txt'
EXEC [SSISDB].[catalog].[set_execution_parameter_value] @execution_id, @object_type=30,
@parameter_name=N'strFileName', @parameter_value=@var0
EXEC [SSISDB].[catalog].[start_execution] @execution_id
This code executes if run it alone or placed in a regular stored procedure , but not executes if i palce this same code inside of a procedure which is being called/executed by a service broker call like this:
CREATE QUEUE dbo.SampleQueue
WITH STATUS=ON, ACTIVATION
(STATUS = ON, MAX_QUEUE_READERS
= 1,
PROCEDURE_NAME = spMessageProcSample,
EXECUTE AS OWNER);
The problem occurs if we call the SSIS catalogs inside a proc which will be calling through a service broker queue.
I am running all these steps on my local instance of SQL SERVER 2012 in which i am the administrator.
Please advice where i am doing wrong ?
Thanks,
Jyodhu.

Hi ArthurZ,
Thanks for reply. What i ment was i tried with all the "EXECUTE AS" options. but no luck.
Can you please explain step by step if you can ? That would be great help.
This is the error message from server log.
Message
The activated proc '[dbo].[spMessageProcSample]' running on queue 'FileTableDB.dbo.SampleQueue' output the following: 'The server principal "USA\cccsat1nmg" is not able to access the database "SSISDB" under the current security context.'
I logged in with WIndows authentication (Admin) and i created all the objects including Integration services Catalog.
Thanks,
Jyodhu.

Java Proxy stuck in JPRRqst Queue

Hi,
I try to do Synchronous process between RFC to Java Proxy. it was wokrikg fine but suddenly Messages stuck in queue.
RFC sends a message after mapping. I looked sxmb_moni it looks like message delivered to Java Proxy but it didn't. after a while outbound service interface gives "no response" error because of time out. but when i look at http://*****:50000/mdt/Systatus    proxy messages stuck in JPRRqst Queue
Queue Name   Threads Assigned/Working
JPRRqst           11/11
My proxy didn't even start. Strange thing this process did work fine and when this error happens, I receive different data from data that come from RFC. example
RFC sends
MANDT   001
MATNR   3N5979
SERVICE_ID 16261
But i receive
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Z************ xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
   <I_TPARTAV>
      <MANDT>000</MANDT>
      <MATNR>979</MATNR>
      <SERVICE_ID>0000</SERVICE_ID>
Have you any ideas?

try this - in RWB in msg monitoring at AE level see the msgs for this scenario......try to find first msg in error and cancel it...then see whether ur remaining msgs are getting processed or not........

Messages stuck in AQ

DB version: Oracle Database 10g Enterprise Edition Release 10.1.0.3.1
A small number of messages stuck in a queue table when our messaging system load is high.
The 'state' column has value '3' in all these rows. What does that mean ?
Why they are stuck over there ?
thanks
We got following rows when query the queue table:
SQL> select * from trans_t_2;
Q_NAME MSGID
CORRID
PRIORITY STATE
DELAY
EXPIRATION
TIME_MANAGER_INFO
LOCAL_ORDER_NO CHAIN_NO CSCN DSCN
ENQ_TIME
ENQ_UID ENQ_TID
DEQ_TIME
DEQ_UID DEQ_TID RETRY_COUNT
EXCEPTION_QSCHEMA EXCEPTION_QUEUE STEP_NO
RECIPIENT_KEY DEQUEUE_MSGID SENDER_NAME
SENDER_ADDRESS
SENDER_PROTOCOL
USER_DATA(STORE_ID)
USER_PROP()
AQ$_TRANS_T_2_E 495DCB163CD07743E040A8C039014231
:EMAILDRIVER:
0 3
0
0 0 0 0
26-MAR-08 03.22.56.895319 PM
WIRELESS 34.16.7968
0
TRANS_Q_2 0
0
TRANS_STORE_OBJECT(738922)
AQ$_TRANS_T_2_E 495E82B0D97B33BBE040A8C0390145BC
:EMAILDRIVER:
0 3
0
0 0 0 0
26-MAR-08 03.22.56.914877 PM
WIRELESS 2.34.522909
0
TRANS_Q_2 0
0
TRANS_STORE_OBJECT(738924)

Hello,
The messages are not stuck they have expired and been placed in the default exception queue AQ$_TRANS_T_2_E. The messages will have been put in the queue for the EXPIRATION_REASON given in the AQ$TRANS_T_2 view. The messages will have been placed in the exception queue by the qmon processes for that reason and when designing your application you need to consider the possibility that messages may be placed in the exception queue and what you intend to do when they are placed there.
When examining the state of messages in the queues associated with a queue table you should be querying the view AQ$TRANS_T_2 and not the underlying objects. The view interprets the underlying values for you and gives consistent information generated from all the objects associated with a queue table.
Thanks
Peter

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.

JMS messages stuck in queue in weblogic v923 cluster

Hi all,
Enviornment details:
In our pre-production weblogic v923 cluster enviornment with Oracle 10g database, there are 10 server boxes with 2 managed nodes running on each server box in linux enviornment.
There are 3 JMS queues and 1 error queue per managed node.
All the queues are durable and the persitence store is a database table. There is a single database table per single managed node.
High loads of JMS messages from client applications coming on each of the 3 JMS queue are processed by the cluster on daily basis.
The JMS messages that failed to be processed the very first time due to the application logic exceptions are put on error queue since the retry is set to zero on the non-error queue.
The application exceptions are logged to a database table for futher reference.
The falied messages from the error queue are read by spring based MDP and resent to the application for reprocessing.
If no application exceptions, the message will be persisted in a relational database; in the case of failures, MDP code puts the failed message back on to the error queue.
The auto_ack is true on the JMS message.
It is observed about less than 1% of the messages fail the original processing and are in error queue on daily basis.
99.9% of the time, the reprocessing of the messages from the error queue is a success.
Currently due to some obvious reasons, the system administrator stops a managed node when the disk is full and start a different managed node on the same server box. This approach will be stopped in the very near future so that all nodes on all servers are running at any point of time by making few enviornment changes.
Problem:
1a) Occasionally, it is observed that 1 - 4 JMS messages are stuck in the error queue. There are no signs of reprocessing as there are no application exceptions or the corresponing insert into the database. The JMS persistence store table still has the JMS message.
1b) It is observed that over time, the same JMS messages that were originally stuck on server 1's managed node A are no longer there but are found in a different node (say node B) on a different server box.
As far as I understand the JMS, a message could be in a Pending state if MDP (in my case) does not automatically send ACKNOWLEGMENT back due to an issue in the Spring Defaultlisternercontainer before calling MDP's onMessage(). I am not sure as what happens to that status over time).
It is also observed that the stuck messages content is not much different than the other messages that are processed fine.
Any pointers/input is highly appreciated.
Thanks in advance for your valuable input and time.

Off the top of my head, I can only think of two reasons why a message might move from node to node:
(A) An application is dequeueing them and enquening them elsewhere.
(B) The application is using distributed queues, and the distributed queue has been configured to enable "queue forwarding". The forwarding feature automatically moves messages from distributed queue members that have no consumers to members that do have consumers. Queue forwarding is sometimes enabled as a work-around to better enable MDP support of WL distributed destinations, unlike WebLogic MDBs, MDPs have no container logic to ensure that all members of a distributed destination are serviced by a consumer under all circumstances...
Regards,
Tom

Messages stuck in "Retry" in Submission Queue - Exchange 2013

Hello,
We have 2013 Exchange consisting of 2 CASs and 2 MBX servers spanning two locations via VPN, 1 of each server in each location. We are hosting exchange for an outside domain, and have just transferred them into our organization within the last month. There
are two users who consistently have messages stuck in the "Retry" status in the submission queue. Not all of their messages, but usually 2-4 are stuck and eventually kicked back to them.
I have read other forums about a potential issue with conversion to RTF. I have forced the queues empty and attempted this fix, but within a week the users had messages stuck again.
Has anybody run into this and possibly found a fix?

Thank you for all your replies.
It appears this issue has been resolved. At first I made the following change:
Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $False
Restarted Transport services on both mailbox DB Servers and the messages remained in the queue and more messages were getting stuck.
Then I made this change:
Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $True
Restarted Transport services on both mailbox DB Servers and the messages cleared from the queues and it seems no more messages are getting stuck as they were before.
I also changed the message timeout from 2 days to 2 hours. I'd rather know sooner than later that a message was stuck. I plan to continue monitoring this.
Thanks again.
Stop Stop Stop, this isn't a solution! Every single post I run into this answer, but it is a real crappy "solution". Simple: there is no solution yet, if everyone take this for an answer there will never we a good answer! This is a work around,
we got mails stucked in the queue for 2 months and it start with no reason. We have every update, enough disk space etc. Settinf the remote domain to true brings you the problem with Apple users and Gmail, hotmail etc. They will receive an email.dat or no
attachment when you send HTML mail. The False or Null is a future that make mail HTML so you can use signatures, pictures etc. It always worked, now only for 2 days and we must reboot again. Set de Remote domain to true we have problems with customers who
doens't receive their email correct!.
Microsoft please solve this problem and stop making crappy excuses or crappy workarounds, a solution is what we need!!!

Messages stuck in SMQ2 Inbound Queue.

Scenario: File->XI->Proxy
When I put 50 files at the same time in a directory, channel is configured Exactly Once in Order and we have created queue with the name GATQUEUE. The messages are picked up from directory and sent one by one to BPM process. 31 messages out of 50 poccesed succesfully but 19 of them get stuck in the queue always. Though GATQUEUE is released lately but they are stuck in 'XBQO$PE_WS90000013' queue. This is seen in SMQ2 Inbound Queue.
Could you please tell me how to release this message which are already stuck and what bit of configuration required so that it works for 1000s of files/messages at a time?
Thanks
K

Hi Kiran,
Just add the below parameter in XI tcode : SXMB_ADM
Execure Integration Engine and Configuration.
Click on Specific Configuration, go to change mode
Click on New entries
Category : MONITOR
Parameter :QRFC_RESTART_ALLOWED
Current Value : 1
Save.
Regards,
Venu.

Service broker message stuck in Transmission Queue

Similar Messages

Maybe you are looking for