JMS Message Buffer Size

Hi All,
          I am in need of some clarification regarding the following:
          According to the docs on:[url http://]http://edocs.bea.com/wls/docs92/perform/jmstuning.html#wp1149307
          The Message Buffer Size option specifies the amount of memory that will be used to store message bodies in memory before they are paged out to disk. The default value of Message Buffer Size is approximately one-third of the maximum heap size for the JVM, or a maximum of 512 megabytes.
          The question for me is: is the max of 512 megabytes, per weblogic server instance or per JMS server or per persistent store?
          Any help is greatly appreciated!
          -jeroen

Per JMS Server (the option is a JMS server option).
Tom

Similar Messages

JMS Server Message Buffer Size & Thresholds and Quotas settings

On WLS10MP1,
For persistent messages:
1.Does "JMS Server Message Buffer" setting serve the same purpose as "Bytes Threshold High" under Threshold ?
2.If no, can someone explain the difference pls.
Many thanx,

Message Buffer Size relates to the number of message the JMS server keeps in the memory. The value of this determines when the server should start paging the message out of memory to a persistence store. So this is directly related with the memory/storage issue and the size of messages.
Bytes Threshold High relates to the performance of the JMS server. When this limit is reached JMS server starts logging the message and may even instruct he producer to slow down the message input.
So the if you get Bytes Threshold High messages that means you should check on your consumer (MDB who is picking up messages from the que), and try to increase its performance.
However if your Message Buffer Size is crossing limits then you should think of increasing the momory so that more messages can be kept in memory and disck IO can be reduce.
Anyone wants to add something more to it?

JMS Message Max Size

Hi,
          Could any of you please tell me what is the maximum JMS message size (text) in 6.1 and 7.0. How can we find this from the console?
          Thanks,
          -Sri


There is no max message setting on the JMS destination prior
          to 8.1, and there is no limit to JMS message size.
          Essentially, max message size is limited by network settings
          and JVM memory.
          The WL server's network settings, which
          apply to all network traffic to the server, not just
          JMS traffic, have a default max message size of 10MB. You
          can tune this via the MaxT3MessageSize parameter.
          I believe that this setting is deprecated in 8.1,
          (8.1 replaces it with a more generic network setting
          that is not protocol specific.) Note that JMS
          messages that are pushed from server to async
          consumers are aggregrated - so there may be
          up to 10 messages by default in a T3 network
          packet - this aggregation is configurable by the connection
          factory's "MessagesMaximum" setting - which is
          not a quota, but is instead limits the size
          of any aggregrated push.
          Tom
          Sri wrote:
          > Hi,
          >
          > Could any of you please tell me what is the maximum JMS message size (text) in 6.1 and 7.0. How can we find this from the console?
          >
          > Thanks,
          > -Sri

How to read messages longer than network buffer size

The logic of my application is:
the client sends a request to the server and wait, in blocking mode, for its response.
The server can responde with strings longer than 64KB (size of their sending and receiving buffer size), so under the hood, can also execs more than one socketChannel.write
Nothing in the message says where it finish, nevertheless the client needs to assemble all in one big
string.
How can the client deal with this ? I'd like keep it as simple as possible (without using a selector)
any thoughts ?
thanks in advance

Your above post suggests that it can send more than one packet (even ignoring the 64k limit.)
In that case the data of the message must contain sufficient information. If not then the solution is not determinate.
Ideally what you should received is a message and not just data. The message defines it contents. So you know how long it is and maybe even when it ends.
Alternatively the data might contain something. For example if you are recieving well formatted XML then you can create a simple parser that just looks for the end tag. If it isn't well formatted, or at least you can not rely on that then it is much harder.

Network Stream Error -314340 due to buffer size on the writer endpoint

Hello everyone,
I just wanted to share a somewhat odd experience we had with the network stream VIs. We found this problem in LV2014 but aren't aware if it is new or not. I searched for a while on the network stream endpoint creation error -314340 and couldn't come up with any useful links to our problem. The good news is that we have fixed our problem but I wanted to explain it a little more in case anyone else has a similar problem.
The specific network stream error -314340 should seemingly occur if you are attempting to connect to a network stream endpoint that is already connected to another endpoint or in which the URL points to a different endpoint than the one trying to connect.
We ran into this issue on attempting to connect to a remote PXI chassis (PXIe-8135) running LabVIEW real-time from an HMI machine, both of which have three NICs and access different networks. We have a class that wraps the network stream VIs and we have deployed this class across four machines (Windows and RT) to establish over 30 network streams between these machines. The class can distinguish between messaging streams that handle clusters of control and status information and also data streams that contain a cluster with a timestamp and 24 I16s. It was on the data network streams that we ran into the issue.
The symptoms of the problem were that we if would attempt to use the HMI computer with a reader endpoint specifying the URL of the writer endpoint on the real-time PXI, the reader endpoint would return with an error of -314340, indicating the writer endpoint was pointing to a third location. Leaving the URL blank on the writer endpoint blank and running in real-time interactive or startup VI made no difference. However, the writer endpoint would return without error and eventually catch a remote endpoint destroyed. To make things more interesting, if you specified the URL on the writer endpoint instead of the reader endpoint, the connection would be made as expected.
Ultimately through experimenting with it, we found that the buffer size of the create writer endpoint for the data stream was causing the problem and that we had fat fingered the constants for this buffer size. Also, pre-allocating or allocating the buffer on the fly made no difference. We imagine that it may be due to the fact we are using a complex data type with a cluster with an array inside of it and it can be difficult to allocate a buffer for this data type. We guess that the issue may be that by the reader endpoint establishing the connection to a writer with a large buffer size specified, the writer endpoint ultimately times out somewhere in the handshaking routine that is hidden below the surface.
I just wanted to post this so others would have a reference if they run into a similar situation and again for reference we found this in LV2014 but are not aware if it is a problem in earlier versions.
Thanks,
Curtiss

Hi Curtiss!
Thank you for your post! Would it be possible for you to add some steps that others can use to reproduce/resolve the issue?
Regards,
Kelly B.
Applications Engineering
National Instruments

Exceeds data buffer size discarding this snmp request

Morning
Cisco Prime LMS 4.2.3 is sending SNMP request too big for asa interface buffer.
LMS is running on Windows server
incoming SNMP request (528 bytes) from IP address x.x.x.x Port 50592 Interface "inside" exceeds data buffer size, discarding this SNMP request.
212005: incoming SNMP request (%d bytes) from %s exceeds data buffer size, discarding this SNMP request.
It is very much like this error
Error Message    %PIX-3-212005: incoming SNMP request (number bytes) on interface
interface_name exceeds data buffer size, discarding this SNMP request.
Explanation    This is an SNMP message. This message reports that the length of the incoming SNMP request, destined for the firewall, exceeds the size of the internal data buffer (512 bytes) used for storing the request during internal processing; therefore, the firewall is unable to process this request. This does not affect the SNMP traffic passing through the firewall via any interface.
Recommended Action    Have the SNMP management station resend the request with a shorter length, for example, instead of querying multiple MIB variables in one request, try querying only one MIB variable in a request. This may involve modifying the configuration of the SNMP manager software.
how do I change the SNMP request size in LMS?
I can only find the following that might be an option
http://blogs.technet.com/b/mihai/archive/2012/05/14/reducing-the-maximum-number-of-oids-queried-in-a-single-batch-in-om-2012.aspx
any thoughts on the matter would be appreciated
just using default settings with snmpv3

Bug in lms 4.2.3
CSCtj88629            Bug Details
SNMP packet size requests from LMS is too large
Symptom:
LMS sends more than 512 SNMP requests to the FWSM, so it rejects the requests.
Conditions:
This occurs with FWSM and ASA's.
Workaround:
None.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtj88629

JMS messaging not working with LCDS and Fiorano

Hi there,
Been struggling at this all day with no luck. I have a finished Flex application which uses JMS messaging, and it has worked just fine on my Tomcat server while using ActiveMQ. As soon as I switched to using the JMS provider Fiorano however, my application can no longer use JMS resources. It fails whenever the application tries to subscribe or publish to a JMS topic. I made all the appropriate JMS related changes to messaging-config.xml.
In the tomcat log, I turned on LCDS debugging and saw this error whenever a publisher or subscriber was trying to start:
"JMS invocation caught exception: SECURITY_EXCEPTION :: Security exception occurred while trying to perform operation :: CreateSubscriber failed,creation of Non-durable Subscriber NOT allowed."
I am passing my JMS security credentials via messaging-config.xml AND even tried doing it via the Flex application (setRemoteCredentials(..)). I know they are correct because I have a working Java application with the exact same credentials and other JMS settings working just fine. It seems only the Flex application fails using the same JMS credentials/settings.
Is there some other file that needs modification other than messaging-config.xml to get a new JMS provider to work? Any idea what may be going on?
Thanks!

A large number of messages, or messages large in size, basically total size of all messages can hang things up. Back up your messages with a GPStore app. Erase them. Lower your message character size. IF it still continues, its the recipients phone. Both of you should power down, remove SIM, reinsert, power up.

How to increase the buffer size ?

Our BI system displays the following message when I execute a query on the web : buffer too small
How to increase the buffer size ?
Thanks in advance

Indeed, we are using Bex Web 7.0
The query uses a big structure and when I execute it on the web, it takes a long time (> 5 min) and I receive folowing message on top of the result page : " could not buffer query structures. Buffer too small "
When I execute the query in Bex analyzer, it takes a long time too but we dont get the message
I have checked the cache size:
- Local cache : 100 MB
- Global cache : 200 MB
Please let me know any solution as there is no BASIS TEAM. The guy who installed the soft was a consultant and is no more reachable.
Thanks in adavnce

Getting recv buffer size error even after tuning

I am on AIX 5.3, IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3...), Coherence 3.1.1/341
I've set the following parameters as root:
no -o sb_max=4194304
no -o udp_recvspace=4194304
no -o udp_sendspace=65536
I still get the following error:
UnicastUdpSocket failed to set receive buffer size to 1428 packets (2096304 bytes); actual size is 44 packets (65536 bytes)....
The following commands/responses confirm that the settings are in place:
$ no -o sb_max
sb_max = 4194304
$ no -o udp_recvspace
udp_recvspace = 4194304
$ no -o udp_sendspace
udp_sendspace = 65536
Why am I still getting the error? Do I need to bounce the machine or is there a different tunable I need to touch?
Thanks
Ghanshyam

Can you try running the attached utility, and send us the output. It will simply try to allocate a variety of socket buffer sizes and report which succeed and which fail. Based on the Coherence log message I expect this program will also fail to allocate a buffer larger then 65536, but it will allow you verify the issue externally from Coherence.
There was an issue with IBM's 1.4 AIX JVM which would not allow allocation of buffers larger then 1MB. This program should allow you to identify if 1.5 has a similar issue. If so you may wish to contact IBM support regarding obtaining a patch.
thanks,
Mark Attachment: so.java (*To use this attachment you will need to rename 399.bin to so.java after the download is complete.) Attachment: so.class (*To use this attachment you will need to rename 400.bin to so.class after the download is complete.)

Imp-00020 long column too large for column buffer size (22)

Hi friends,
I have exported (through Conventional path) a complete schema from Oracle 7 (Sco unix patform).
Then transferred the export file to a laptop(window platform) from unix server.
And tried to import this file into Oracle10.2. on windows XP.
(Database Configuration of Oracle 10g is
User tablespace 2 GB
Temp tablespace 30 Mb
The rollback segment of 15 mb each
undo tablespace of 200 MB
SGA 160MB
PAGA 16MB)
All the tables imported success fully except 3 tables which are having AROUND 1 million rows each.
The error message comes during import are as following for these 3 tables
imp-00020 long column too large for column buffer size (22)
imp-00020 long column too large for column buffer size(7)
The main point here is in all the 3 tables there is no long column/timestamp column (only varchar/number columns are there).
For solving the problem I tried following options
1.Incresed the buffer size upto 20480000/30720000.
2.Commit=Y Indexes=N (in this case does not import complete tables).
3.first export table structures only and then Data.
4.Created table manually and tried to import the tables.
but all efforts got failed.
still getting the same errors.
Can some one help me on this issue ?
I will be grateful to all of you.
Regards,
Harvinder Singh
[email protected]
Edited by: user462250 on Oct 14, 2009 1:57 AM

Thanks, but this note is for older releases, 7.3 to 8.0...
In my case both export and import were made on a 11.2 database.
I didn't use datapump because we use the same processes for different releases of Oracle, some of them do not comtemplate datapump. By the way, shouldn't EXP / IMP work anyway?

Error -200609 occurred at DAQmx Write: Selected Buffer Size Too Small

Hello, I'm writing some simple test VI's that I will eventually build upon to make an externally clocked analog output VI. I started with a very simple program to output finite samples using the onboard clock with the DAQmx Timing.VI. When I run the program, I almost immediately get an error. The error message is below.
Error -200609 occurred at DAQmx Write (Analog DBL 1Chan 1Samp).vi:1
Possible reason(s):
Generation cannot be started, because the selected buffer size is too small.
Increase the buffer size.
Conflicting Property
Property: Output.BufSize
Corresponding Value: 1
Minimum Supported Value: 2
Task Name: _unnamedTask<1C>
I have used DAQmx VI's before in similar applications and never encountered this error. Additionally, I read at the link below that DAQmx Timing.VI should be generating the buffer automatically. Any ideas as what could be causing this?
Specs:
Windows 7
Labview 2012
PCIe-6353 as DAQ board
Below is a picture of my block diagram and the VI is attached.
Solved!
Go to Solution.
Attachments:
FiniteSamplesTest.vi ‏18 KB

Oops. Just realized my very silly mistake: I forgot to add the Start Task VI. I did so and it works as designed.

Increasing usb buffer size on HP Pavilion g6 / Windows 8

I have recently loaded Traktor Audio 2 DJ software and have run diagnostics on the system because of sound drag and distortion. The error message suggested increasing the USB buffer size to solve the problem. How do I do that - and do any forum members who use Traktor reckon that will solve the problem?

Thanks for the information, Here is a link to the keyboard troubleshooting steps for your computer. Click on the link and select the option for wrong character appear when typing. This should allow you to change the keyboard layout. What keyboard language do you have selected? What country was the computer purchased in?

Changing Buffer Size - Logic Tweaks Out

I find that I'm unable to change the buffer size (for instance, after I record and want to play back without any glitches) without having to quit Logic and reload the file. I usually get a message that "some plug-ins have been disabled."
Everything is usually fine after I quit the file and reload. But I'm wondering if anyone else has this issue and if it can be avoided. It's mostly just a time-waster.
Thanks.

Nevermind. Thanks.

JMS - Message Loss

Hi All,
I am trying to read message from SUN - JMS Queue to XI
After reading the message XI is trying to persist the message to Database and here I am getting a SQL Exception That The JMS Message ID is of 71 characters
where as the host field in XI DataBase is of size 63 only
This message is not reaching Integration Engine ( I dont see the msg in SXMB_MONI)
Please suggest me some fix.
Thanks
Kavitha

Getting this error from server log :
com.sap.sql.log.OpenSQLException: Cannot assign a java.lang.String object of length 71 to host variable 1 which has JDBC type VARCHAR(63).
Other details in the server log
Category: /System/Database/sql/types
Location: com.sap.sql.types.VarcharResultColumn
Application: sap.com/com.sap.xi.mdt
Regards
Kavitha

Unzipping a gz file that's in a JMS Message

Could anyone please help me figure out how to unzip a message from a JMS Message. I have tried all sorts of things and I just can't get it to work.
Jeremy

Hi I can just help you out how to extract file from
zip format and hope it will help you out and i am
giving you it by showing you one example.
import java.util.*;
import java.io.*;
import java.text.*;
import java.util.zip.*;
public class sandyzip
     public static void main(String[] args)
     {     try{
               Enumeration entries;
               ZipFile zipFile;
               ZipEntry entry =null;
               byte[] buffer = new byte[10000];
               int len;
               InputStream in=null;
               OutputStream zout=null;
zipFile = new
new ZipFile("D:\\JavaPractice\\04-04-2007data.zip");
               System.out.println(zipFile);
               entries = zipFile.entries();
               System.out.println(entries);
while(entries.hasMoreElements()) {
ry = (ZipEntry)entries.nextElement();
               in=zipFile.getInputStream(entry);
zout=new BufferedOutputStream(new
new
FileOutputStream(""+"D:\\JavaPractice\\"+entry.getName
               System.out.println("**************"+entry.getName()
               System.out.println(zout);
               while((len = in.read(buffer)) >= 0)
               zout.write(buffer, 0, len);
               System.out.println("Unzip done");
          catch (Exception ex) {
               ex.printStackTrace();
Hope it will server your purpose.
Cheers
Sandyand where did JMS fit into the equation?

JMS Message Buffer Size

Similar Messages

Maybe you are looking for