Sys.aq$_jms_text_message type queues message size limitations

Are there any size limitations for enqueing text messages into a sys.aq$_jms_text_message type queue using AQ?

yes, i understand how to describe something...
my question is how to get a list of properties.
this data type has get functions that take the name of a property. now how do i know that property name to get it?

Similar Messages

Activesync message size limits

I am running Exchange 2007 and I understand that the default size limits for activesync is 10MB. I also understand that you can increase the message size limits. What I am trying to find ot is if there is a limit or ceiling for increasing the limit? If
there is no limit what is best practice?

Best practice is to leave them alone unless you have a compelling reason not to.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Asynchronous Consumer Message Size Limitation?

Hello,
We are currently evaluating the Sun Message Queue 3.5. We are able to successfully send and asynchronously receive messages that are less than 1K. However, when we increased the size of the message to 2K or more, the asynchronous consumer does not return the message and messages that we send subsequently (large or small) do not get received. Seems like the destination is blocked at that point. We are able to retrieve the message synchronously though using the receive(1000) method.
Is there maybe a setting that we must check out for this?
Also, is it possible to support both synchronous and asynchronous messaging at the same time?
ie. Creating MessageListeners and also using the receive method for the same set of destinations?
We were planning to use this as a workaround so that if the message is greater that 1K, we'll just receive it synchronously. However, synchronous receiving doesn't seem to work if there is a listener listening to a destination that contains a large message.
Thanks for your time.

Outside of specific configurable parameters, nothing in
the system really cares about the size of the message.
A few possible reasons:
1. if you are using receive(timeout), the receive time may
be too short to complete processing the message (since
larger messages take longer to send over the network)
2. if you are setting an expiration time, the larger messages
could be expiring during the routing stage (since the
messages take longer)
3. The larger messages could be exceeding a configured
size limit on either the destination or broker
To check:
imqcmd query dst -n <name> -t t
or
imqcmd query bkr
And look at the size limits
If the size limits are exceeded, the messages will be rejected.
Additionally, if

SOAP message size limitation for sender soap adapter

Hi All,
We are facing critical production issue in case of sender SOAP Adapter,
If the sender soap message is having 114359 Bytes than the Third party is getting exception and SOAP request is not reaching XI.
If the message size is less then 100kbytes then no exception will come.
Is this a limitation that SOAP message size should not exceed 100kbyte?
Thnaks in advance
Best Regards,
Harleen Kaur Chadha

Hi ,
Thanks for your inputs,Could you please tell me which hardware configurations are you talking about?
Are you people talking about harware configurations for XI?
Best Regards,
Harleen Kaur Chadha

SBO2007: Message Size limitation

Hello all,
The size of either all SBO Messages or Alerts Messages seems to be limited, because if an Alert uses a query that returns a large of data, the resultset's lines get truncated and the last line in the Alert message is "...", indicating the data being incomplete.
Is this limitiation documented somewhere? What's the maximum query size that can be passed untruncated?
Thanks in advance,
Anton

Hi Anton,
The size limit has always been there in the versions I've worked with but the only place I found it mentioned was in SAP Note 874145 which just says:
"An alert based on a query returning long results will not display the complete list should the result be over a certain size. This implies that a query which returns, for example only the invoice number, 200 lines in the query generator may only return 123 lines in the alert."
The limit is quite low so I'd guess a 100-200K cut off.
The note suggests the workarounds of either deliberately truncating the results or sending an alert that tells the user to run the full query rather than sending the results in the alert itself.
Kind Regards,
Owen

Oracle-xi - bw integration. message size limitation

Hello,
Iu2019ve got following scenario(sap xi 3.0)
1.     Get Data from Oracle DB(jdbc adapter)
2.     Put it to BW(xi adapter (http protocol) + bw extractor)
Every think working well, but when the oracle send more then 400 rows, BW(in rsa7) doesn`t get that rows. All XI monitoring (abap and java)doesn`t have any error.
It happen with all communication channel, critical rows count around 300-500. Less then   300-500 every think working well, but when more than 300-500 rows message lost between xi and BW.
Did someone experience a similar problem?

Hi,
Check in SXMB_MONI what error you are getting, if it is message expired, or any timeout error you need to set the timeout parameters accordingly in Visual Admin.
Thanks!

Can not dequeue JMS message of type SYS.AQ$_JMS_TEXT_MESSAGE using DBMS_AQ

I'm having a problem using DBMS_AQ package to dequeue a JMS message of type SYS.AQ$_JMS_TEXT_MESSAGE that was put on the queue using Java JMS API.
Both JMS header and payload return empty but if I do "select user_data" from the queue table, I can see the message.
Appreciate any helps or tips.
Kim

This has been asked a lot of times - I'm not sure how my initial searching missed all of the other questions/answers related to this topic.
In our case, the solution was to:
1) Leave the queue as a sys.aq$_jms_text_message type
2) Construct a sys.xmltype object with our desired payload
3) Do a getStringVal() on the xmltype object and use that string as the payload for our queue message
- Nathan

Publishing SYS.aq$_jms_text_message to Oracle Streams Queue

I've created a streams queue using dbms_streams_adm and by default the payload type for the queue created is Sys.AnyData. How do I publish a message of type aq$_jms_text_message in PL/SQL to this streams Queue. I guess it all comes down to converting aq$_jms_text_message to AnyData in pl/sql. Sys.AnyData does NOT have anything to convert aq$_jms_text_message.
Any help would be appreciated.
Thanks,
Das

This has been asked a lot of times - I'm not sure how my initial searching missed all of the other questions/answers related to this topic.
In our case, the solution was to:
1) Leave the queue as a sys.aq$_jms_text_message type
2) Construct a sys.xmltype object with our desired payload
3) Do a getStringVal() on the xmltype object and use that string as the payload for our queue message
- Nathan

Exchange 2013 Mail Size Limits

I am having an issue with setting the max send and receive size on Exchange 2013. I keep getting the following error when I attempt to send a 20 meg file server to an internal exchange account OR if I attempt to send a 20 meg file from the exchange
server to an external account:
#550 5.3.4
ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##
I have checked the mail sizes and below is the report. I currently have both send and receive set to 100MB. Is there some other setting in 2013 that I am not aware of?
AnonymousSenderToRecipientRatePerHour                       : 1800
ClearCategories
: True
ConvertDisclaimerWrapperToEml                               : False
DSNConversionMode
: UseExchangeDSNs
ExternalDelayDsnEnabled                                     : True
ExternalDsnDefaultLanguage                                  :
ExternalDsnLanguageDetectionEnabled                         : True
ExternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
ExternalDsnReportingAuthority                               :
ExternalDsnSendHtml
: True
ExternalPostmasterAddress                                   :
GenerateCopyOfDSNFor                                        :
HygieneSuite
: Standard
InternalDelayDsnEnabled                                     : True
InternalDsnDefaultLanguage                                  :
InternalDsnLanguageDetectionEnabled                         : True
InternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
InternalDsnReportingAuthority                               :
InternalDsnSendHtml
: True
InternalSMTPServers
JournalingReportNdrTo                                       : <>
LegacyJournalingMigrationEnabled                            : False
LegacyArchiveJournalingEnabled                              : False
LegacyArchiveLiveJournalingEnabled                          : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling                : False
MaxDumpsterSizePerDatabase                                  : 18 MB (18,874,368 bytes)
MaxDumpsterTime
: 7.00:00:00
MaxReceiveSize
: 100 MB (104,857,600 bytes)
MaxRecipientEnvelopeLimit                                   : 500
MaxRetriesForLocalSiteShadow                                : 2
MaxRetriesForRemoteSiteShadow                               : 4
MaxSendSize
: 100 MB (104,857,600 bytes)
MigrationEnabled
: False
OpenDomainRoutingEnabled                                    : False
RejectMessageOnShadowFailure                                : False
Rfc2231EncodingEnabled                                      : False
SafetyNetHoldTime
: 2.00:00:00
ShadowHeartbeatFrequency                                    : 00:02:00
ShadowMessageAutoDiscardInterval                            : 2.00:00:00
ShadowMessagePreferenceSetting                              : PreferRemote
ShadowRedundancyEnabled                                     : True
ShadowResubmitTimeSpan                                      : 03:00:00
SupervisionTags
: {Reject, Allow}
TLSReceiveDomainSecureList                                  : {}
TLSSendDomainSecureList                                     : {}
VerifySecureSubmitEnabled                                   : False
VoicemailJournalingEnabled                                  : True
HeaderPromotionModeSetting                                  : NoCreate
Xexch50Enabled
: True

Hello Landfish,
Good Day...
The output gives the information that Size limit set for Receive and Send is 100 mb, but setting could have changed. So you can follow the below steps to resolve the issue.
There are basically three places where you can configure default message size limits on Exchange:
Organization transport settings
Send/receive connector settings
User mailbox settings.
To check your server’s current limit you can open Exchange Management Shell
Try the below commands to check the Message quota size limit
get-transportconfig | ft maxsendsize, maxreceivesize
get-receiveconnector | ft name, maxmessagesize
get-sendconnector | ft name, maxmessagesize
get-mailbox Administrator |ft Name, Maxsendsize, maxreceivesize
To change the above size limits based on your requirement.
Set-TransportConfig -MaxSendSize 200MB -MaxReceiveSize 500MB (Size is based on your requirement)
Attachment size limit
To set up the rule you can use the below PowerShell cmdlet, as the method is quite simple
New-TransportRule -Name LargeAttach -AttachmentSizeOver 20MB -RejectMessageReasonText "Message attachment size over 20MB - email rejected."
For More info
https://technet.microsoft.com/en-us/library/bb124708(v=exchg.150).aspx
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts @ Techrid.com

Limit message size per recipient domain

Is there a feature to set maximum message size per recipient domain (incoming emails) in the roadmap maybe?

While you cannot do it by 'domains' for maximum message size limitations, you can limit the connection mail hosts.
IE: domain1.com may use the connecting mail host of mail.domain1.com
domain2.com may use the connection mail host of mx.domain2.com
Then you can create new sendergroups for the respective domains mail servers to match, and with the sendergroup you will need to create a new mail flow policy with the size limits you would like to impose.
Once this is done, simply add the mail.domain1.com into the respective sendergroup and it will impose this limitation.
Key points to note:
Size limits should account for MIME inflation.
IE: 10mb limitation you want to implement should be 14MB on the mail flow policy to account for MIME inflation.
Alternatively, if you would like to do it 'by domain'
SImply increase your mail flow policy for the sendergroup that these domains normally match (under default it would normally be UNKNOWNLIST) and have it at 14MB (to allow for 10MB emails)
Then run a message filter (so it gets actioned at the start)
FilterDomain1:
if (mail-from =="@domain1.com") AND (body-size > 5M)
drop();
Etc. to impose the limits this way.
Note:
Body size refers to the size of the message, including both headers and attachments. The body-size rule selects those messages where the body size compares as directed to a given number.

Remove Message Size Restriction

Hello,
Please suggest a powershell to achieve below two tasks for bulk mailboxes (in .csv), NOT for individual mailbox;
1) To apply Message Size Restriction
2) To remove Message Size Restriction, so it will utilize default
Thanks

Hi,
I edit Johnpaul’s command to set message size limits not quotas.
To apply Message Size Restriction
Import-Csv "C:\temp\users.csv" | Foreach-object {Set-Mailbox -Identity $_.name -MaxReceiveSize 1GB –MaxSendSize 2GB}
To remove Message Size Restriction, we just set the value to unlimited.
Import-Csv "C:\temp\users.csv" | Foreach-object {Set-Mailbox -Identity $_.name -MaxReceiveSize unlimited–MaxSendSize unlimited}
By the way, message size limit can be set on the following levels:
Organizational Level
Send Connector
Receive Connector
AD Site Links
Routing Group Connectors
Individual
The path evaluated is as follows: User Send Limit > Receive Connector > Organization Checks > Send Connector > User Receive Limit
For more information, please refer to this document:
https://technet.microsoft.com/en-us/library/bb124345(v=exchg.141).aspx
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Setting a Default Organisation Message Size Limit and a Higher Limit on an Individual Mailbox

Ok. So here's the problem. I've read all the articles on setting message size limits for Organisation, Transport Send Connectors, Transport Receive Connectors, setting precedence, etc., but they don't detail how to solve this problem.
One person in our organisation is to get a raised message size limit for sending and receiving internally and externally. I've already set up limits on the Organisation Transport Global Settings, Send Connectors, Receive Connectors, etc. So,
as this individual requires a higher limit, I've raised the limits on their mailbox, and the aforementioned connector settings, etc., except the
Organisation Configuration / Hub Transport / Global Settings / Transport Settings / Maximum Receive
and Send Sizes. The theory is that I can keep these two values at the original lower setting as these are overridden by the individual's new, higher, mailbox settings, but they will continue to act as the default for other existing mailboxes
and newly created mailboxes. Right ? Wrong! For the individual's mailbox, this will only raise the limit for messages sent internally (not to or from external email addresses).
Now, I could change all existing mailboxes to have the old default lower limit using a PowerShell / EMS command, but this wouldn't work either. Newly created mailboxes will still default to the new larger limit. Most of our mailbox creation is
scripted, though some are created manually. I don't want to alter the script and inform the admins as this is too much work and admins will forget about the new limits. TBH, I'll probably forget about the new limits. That's just a messy inefficient
approach. What I want is to set a new default for message size limits, with the original low limits. I.e., a setting that applies to existing mailboxes with no explicit message size limits set, and also newly created mailboxes, but not any mailbox
with an explicitly specified higher message size limit. Any mailbox with explicitly specified higher limits should be able to send larger messages both internally
and externally. Can anyone help ? Like I said, I've already read the articles so I don't need links to these thanks. I'm more looking to people who have done this kind of thing already.
BTW, we are using Exchange 2007 SP3. It has a mailbox server Single Copy Cluster (SCC) with two nodes. It also has two Client Access / Hub Transport servers. Just so you know ;-)
-- huddie
"If you're not seeking help or offering it, you probably shouldn't be here."

Hi huddie71,
Thank you for your question.
I've raised the limits on their mailbox, and the aforementioned connector settings, etc.,
except the Organization Configuration / Hub Transport / Global Settings / Transport Settings / Maximum Receive and Send Sizes.
By my understand, we could modify the global settings by the following path:
Organization Configuration / Hub Transport / Global Settings / Transport Settings / Maximum Receive and Send Sizes.
Because it will work on existed user and new user without explicit message size limits sets.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Hi Jim-Xu. That would result in everyone getting an increased limit. I only want one person to have an increased limit. See the 2nd paragraph in my original post.
-- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

PLSQL Notification on a multi-subscriber queue with sys.aq$_jms_text_messag

Hi all,
I am trying to get PLSQL notification working on a multi subscriber queue with sys.aq$jms_text_message as the payload type. The commands to create my queue are as follows:
dbms_aqadm.create_queue_table(
queue_table => 'SOA_JMS.RJMTESTxx_QTAB',
multiple_consumers => true,
queue_payload_type => 'sys.aq$_jms_text_message'
dbms_aqadm.create_queue(
queue_name=>'RJMTESTQ',
queue_table => 'SOA_JMS.RJMTESTxx_QTAB',
retention_time => 86400, --Keep processed messages for 24 hours
max_retries => 3,
retry_delay => 1
dbms_aqadm.start_queue('RJMTESTQ');
dbms_aqadm.add_subscriber(
queue_name => 'SOA_JMS.RJMTESTQ',
subscriber => sys.aq$_agent('SUBSCRIP1',null,0),
rule => NULL,
transformation => NULL,
queue_to_queue => FALSE,
delivery_mode => dbms_aqadm.persistent
I then create a procedure with the following signature:
create or replace procedure SOA_JMS.EXCEPTION_QUEUE_NOFIFYCB_1(
p_context in raw,
p_reginfo in sys.aq$_reg_info,
p_descr in sys.aq$_descriptor,
p_payload in raw,
p_payloadl in number
And register it as follows:
reginfo := sys.aq$_reg_info(
'SOA_JMS.RJMTESTQ:SUBSCRIP1',
DBMS_AQ.NAMESPACE_AQ,
'plsql://SOA_JMS.EXCEPTION_QUEUE_NOFIFYCB_1?PR=0',
--utl_raw.cast_to_raw('STANDARDJMS')
HEXTORAW('FF')
reg_list := sys.aq$_reg_info_list(reginfo);
dbms_aq.register(reg_list,1);
The problem is the notifications are not firing as they should be.
I have done some tracing and found an error:
Error in PLSQL notification of msgid:BA964334E5A057A4E040C69BAF397075
Queue :"SOA_JMS"."RJMTESTQ"
Consumer Name :SUBSCRIP1
PLSQL function :SOA_JMS.EXCEPTION_QUEUE_NOFIFYCB_1
: Exception Occured, Error msg:
ORA-00604: error occurred at recursive SQL level 2
ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'EXCEPTION_QUEUE_NOFIFYCB_1'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
This says that the parameters I have for my procedure is wrong. Looking through the documents I think it is something to do with the ?PR=0 used in the register call, but I can’t find any documentation telling me what the required parameters are.
Does anyone here know?
Thanks
Robert

Hi,
I have found the solution and I am posting here in case it helps anyone else.
The paramater names must match the callback not just the types and in/out.
So the following works:
create or replace procedure SOA_JMS.EXCEPTION_QUEUE_NOFIFYCB_2(
context in raw,
reginfo in sys.aq$_reg_info,
descr in sys.aq$_descriptor,
payload in raw,
payloadl in number
Robert

OSB Service with Oracle AQ with payload type SYS.AQ$_JMS_TEXT_MESSAGE

I am trying to write a web-service to Enqueue/Dequeue messages from an AQ with payload type SYS.AQ$_JMS_TEXT_MESSAGE defined in Oracle DB.
In my understanding is that I need to create a JMSModule within weblogic with a ForeignServer defined within it to enqueue/dequeue message to/from the AQ.
I have created Datasource, JMSServer, JMSModule, ForeignServer (created ConnectionFactory with localJNDIName="MyQueueCF" and RemoteJNDIName as "QueueConnectionFactory" and Destination with localJNDIName="MyQueueDest" and RemoteJNDIName="Queues/<queue_name_in_DB>")
My business service has an endpoint "http://localhost:7001/MyQueueCF/MyQueueDest"
When I am testing my service to populate message on to the Queue. I get the following error:
The error was oracle.jms.AQjmsException: Error creating the db_connection
My questions are:
* Am I following the correct procedure to talk to AQ with JMS text message type payload?
* If yes, how can I get around the issue I am stuck with?
Please help!
Thanks.
Edited by: user4696353 on 27-Sep-2011 11:43
Edited by: user4696353 on 27-Sep-2011 11:49
Edited by: user4696353 on 27-Sep-2011 12:25

Example:
conn / as sysdba
begin
dbms_aqadm.create_queue_table
( queue_table=> 'SCOTT.AQJMS'
, queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE'
, compatible=> '9.1'
end;
This worked fine for me after a standard DB-installation.

Select from a queue table with SYS.AQ$_JMS_MAP_MESSAGE type

We are using the SYS.AQ$_JMS_MAP_MESSAGE type for our queue so that we can access the queue using plsql as well as java (via jms). The queue table that gets created contains a column user_data that is of the above type. This type has two columns BYTES_RAW and BYTES_LOB which I assume contains the data. Is there a way in sql (or in plsql) to get access to the data. Also, we are retaining the messages after they have been consumed (from an audit standpoint) and might need access to the data.
Thank you
Navin

yes, i understand how to describe something...
my question is how to get a list of properties.
this data type has get functions that take the name of a property. now how do i know that property name to get it?

Sys.aq$_jms_text_message type queues message size limitations

Similar Messages

Maybe you are looking for