I/O buffer size switch by itself

Hi, whenever I'm playing my guitar in Logic Pro 9, the latency suddenly changes, and I start to hear this delay in the sound.
Then I have to modify the I/O buffer size switch by (e. like128 to 256) to hear the sound in real time again.
It doesn't let me record as it changes when I'm playing.
What is Logic doing this? and how can I fix it.
It started doing this after I updated to maverick, before I had no problems at all with this.
Thanks
Using Logic Pro 9
9.1.8
Macbook Pro
OS X 10.9

You will find several threads on the M-Audio website dedicated to Mavericks issues with M-Audio Fast Tracks...
Here is the major one I believe.....
http://community.m-audio.com/m-audio/topics/os_x_mavericks_fast_track_pro_suppor t
It does not make for good reading i am afraid to say..... and although there are a variety of different issues discussed there.. it basiclaly amounts to..
The interface doesn't have 10.9 compatible drivers and it may be several weeks until M-Audio release updated ones....
Sorry!

Similar Messages

How do you determine ip and op buffer size on a 3550-12G

I have a Cisco 3550-12G switch and I want to check to see if the input buffers and the output buffers for port gi0/12 are the same size. Is there a simple way to do this, I tried using the show buffers command but I couldn't seem to find what I was looking for. Help!

Hi,
"The 3550 switch uses central buffering. This means that there are no fixed buffer sizes per port. However, there is a fixed number of packets on a Gigabit port that can be queued. This fixed number is 4096. By default, each queue in a Gigabit port can have up to 1024 packets, regardless of the packet size."
http://www.cisco.com/warp/public/473/187.html#topic7
HTH,
Bobby
*Please rate helpful posts.

How to set local file copy buffer size?

Is there any sysctl parameter or any other mechanism to set or change file copy buffer sizes? I'm backing up a huge number of files to a local hard drive connected by firewire, and I'd like to play with file copy buffer sizes for the best performance. The machine used is a new macbook pro running OS-X 10.6.7. Any ideas?

Here is a bash script that uses the dd command to copy a file. Use the -b option to set the file size.
example:
/Users/mac/config/forumcopy.command -vb 4096 /Applications\ $Mac\ OS\ 9$/Civilization\ II/Civ\ II\ Map\ Editor /Applications\ $Mac\ OS\ 9$/Civilization\ II/Civ\ II\ Map\ Editorv8
I haven't tested this a lot.
Of course, I haven't figured out how best to post code. Trying HTML mode. Using the <pre> tag.
#!/bin/bash
# macteracopy [ -b blocksize ] [-v ] [-V ] input_file output_file
# Purpose of this script:
# Copy a file with optional block size. Default size of 4096.
# Notes:
# chmod u+x macteracopy
# You may have to restart the finder to notice a customized file icon.
# Copyright 2010 rccharles
# GNU General Public License
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, version 3
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# For a copy of the GNU General Public License see
# <http://www.gnu.org/licenses/>.
# debug info
export PS4='+(${BASH_SOURCE}:${LINENO}):'
## not in the tiger version of bash ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
declare -x verbose="No" \
 veryVerbose="No"
blockSize=4096
# Check for command-line options used when calling the script
if [ $# -gt 0 ] ; then
 while getopts "b:vV" Option ; do
 case "${Option}" in
 b ) blockSize=$OPTARG
 v ) verbose="Yes"
 V ) veryVerbose="Yes"
 \? ) echo 'usage macteracopy -b blocksize -V input_file output_file'
 * ) echo "Unknown argument among arguments $* on command line."
 exit 6
 esac
 done
fi
# We're done with switches / options from the command line
shift $(($OPTIND - 1))
[ "${veryVerbose}" = "Yes" ] \
 && set -x
inputFile="${1}"
outputFile="${2}"
[ "${verbose}" = "Yes" ] \
 && echo \
 && echo "$0 script revised $(GetFileInfo -m $0)" \
 && echo
[ ! -f "${inputFile}" ] && echo "File not found. ${inputFile}" && exit 4
[ -d "${inputFile}" ] \
 && echo "Directories are not supported, yet. ${inputFile}" \
 && exit 4
[ "${veryVerbose}" = "Yes" ] \
 && ulimit -a \
 && df \
 && echo
if [ "${verbose}" = "Yes" ] ; then
 dd bs=${blockSize} if="${inputFile}" of="${outputFile}"
 dd bs=${blockSize} if="${inputFile}/rsrc" of="${outputFile}/rsrc"
else
 dd bs=${blockSize} if="${inputFile}" of="${outputFile}"
 dd bs=${blockSize} if="${inputFile}/rsrc" of="${outputFile}/rsrc"
 } 2>/dev/null
fi
[ "${verbose}" = "Yes" ] \
 && echo \
 && ls -l "${inputFile}" \
 && ls -l "${inputFile}"/rsrc \
 && GetFileInfo "${inputFile}" \
 && ls -l "${outputFile}" \
 && ls -l "${outputFile}"/rsrc \
 && GetFileInfo "${outputFile}" \
 && echo
SetFile -a $(GetFileInfo -a "${inputFile}" ) \
 -c $(GetFileInfo -c "${inputFile}" | sed 's/"// g' ) \
 -t $(GetFileInfo -t "${inputFile}" | sed 's/"// g' ) \
 "${outputFile}"
[ "${verbose}" = "Yes" ] \
 && echo "after SetFile" \
 && GetFileInfo "${outputFile}"

Buffer Sizes Are Not Equal

Okay what does this term mean:
Buffer Sizes Are Not Equal
I am playing with transitions. I have two clips with enough handles.
I'm using the gradient wipe and putting a Photoshop file in the "well".
That message pops up in the timeline when I'm stopped at that place in the timeline (similar to the media offline message). When I try to render the effect, the same message appears and doesn't even attempt to render.
FCP 5.1.4

The image is RGB...
The image itself is a blue circle over a transparent background. That's the only layer.
I did change it to a jpg file, and I stopped getting the error message...but obviously I also lost the alpha channel.
John

Redo log and buffer size

Hi,
i'm trying to size redolog and the buffer size in the best way.
I already adjusted the size of the redo to let them switch 1/2 times per hour.
The next step is to modify the redo buffer to avoid waits.
Actually this query gives me 896 as result.
SELECT NAME, VALUE
FROM V$SYSSTAT
WHERE NAME = 'redo buffer allocation retries';
I suppose this should be near to 0.
Log_buffer is setted to 1m.
And i read "sizing the log buffer larger than 1M does not provide any performance benefit" so what can i do to reduce that wait time?
Any ideas or suggestions?
Thanks
Acr

ACR80,
Every time you create a redo entry, you have to allocate space to copy it into the redo buffer. You've had 588 allocation retries in 46M entries. That's "close to zero"..
redo entries 46,901,591
redo buffer allocation retries 588The 1MB limit was based around the idea that a large buffer could allow a lot of log to accumulate between writes with the result that a process could execute a small transaction and commit - and have to wait a "long" time for the log writer to do a big write.
If in doubt, check the two wait events:
"log file sync"
"log buffer space".
As a guideline, you may reduce waits for "log buffer space" by increasing the size of the log buffer - but this introduces the risk of longer waits for "log file sync". Conversely, reducing the log buffer size may reduce the impact of "log file sync" waits but runs the risk of increasing "log buffer space" waits.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Lower buffer size

I just found out that I can use 64 buffer without safety buffer when using no plugins in the concert view.
I use Mainstage for playing guitar and I wondered why I can't use the same buffer setting, that I could use in Logic with the same channel strips.
I'm switching between 5 patches with GuitarAmp Pro basically.
After deleting the plugins in the Concert the performance became much better.

Channel strips at Concert level are always active, therefore always cost CPU load. That could push your machine with a 64 buffer size "over the edge". A similar situation are channel strips at Set level, which are active as long as that Set is active.

What is the default buffer size if we dont specify in buffer write?

If we dont specify what is the default buffer size in BufferedWriter. How to increase/decrease the size of it?
What is the purpose of flush?
If flush() is not used, only partial content is written to the file. Is it because of the default size of the buffer.

THis is the bufferedwriter class, it helps to look at them, look at the bold underlined, thats answers your defualt buffer size
* @(#)BufferedWriter.java 1.26 03/12/19
* Copyright 2004 Sun Microsystems, Inc. All rights reserved.
* SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
package java.io;
* Write text to a character-output stream, buffering characters so as to
* provide for the efficient writing of single characters, arrays, and strings.
* The buffer size may be specified, or the default size may be accepted.
* The default is large enough for most purposes.
* A newLine() method is provided, which uses the platform's own notion of
* line separator as defined by the system property <tt>line.separator</tt>.
* Not all platforms use the newline character ('\n') to terminate lines.
* Calling this method to terminate each output line is therefore preferred to
* writing a newline character directly.
* In general, a Writer sends its output immediately to the underlying
* character or byte stream. Unless prompt output is required, it is advisable
* to wrap a BufferedWriter around any Writer whose write() operations may be
* costly, such as FileWriters and OutputStreamWriters. For example,
* <pre>
* PrintWriter out
* = new PrintWriter(new BufferedWriter(new FileWriter("foo.out")));
* </pre>
* will buffer the PrintWriter's output to the file. Without buffering, each
* invocation of a print() method would cause characters to be converted into
* bytes that would then be written immediately to the file, which can be very
* inefficient.
* @see PrintWriter
* @see FileWriter
* @see OutputStreamWriter
* @version 1.26, 03/12/19
* @author Mark Reinhold
* @since JDK1.1
public class BufferedWriter extends Writer {
private Writer out;
private char cb[];
private int nChars, nextChar;
private static int defaultCharBufferSize = 8192;
* Line separator string. This is the value of the line.separator
* property at the moment that the stream was created.
private String lineSeparator;
* Create a buffered character-output stream that uses a default-sized
* output buffer.
* @param out A Writer
*public BufferedWriter(Writer out) {*
* this(out, defaultCharBufferSize);*
* Create a new buffered character-output stream that uses an output
* buffer of the given size.
* @param out A Writer
* @param sz Output-buffer size, a positive integer
* @exception IllegalArgumentException If sz is <= 0
public BufferedWriter(Writer out, int sz) {
 super(out);
 if (sz <= 0)
 throw new IllegalArgumentException("Buffer size <= 0");
 this.out = out;
 cb = new char[sz];
 nChars = sz;
 nextChar = 0;
 lineSeparator = (String) java.security.AccessController.doPrivileged(
new sun.security.action.GetPropertyAction("line.separator"));
/** Check to make sure that the stream has not been closed */
private void ensureOpen() throws IOException {
 if (out == null)
 throw new IOException("Stream closed");
* Flush the output buffer to the underlying character stream, without
* flushing the stream itself. This method is non-private only so that it
* may be invoked by PrintStream.
void flushBuffer() throws IOException {
 synchronized (lock) {
 ensureOpen();
 if (nextChar == 0)
 return;
 out.write(cb, 0, nextChar);
 nextChar = 0;
* Write a single character.
* @exception IOException If an I/O error occurs
public void write(int c) throws IOException {
 synchronized (lock) {
 ensureOpen();
 if (nextChar >= nChars)
 flushBuffer();
 cb[nextChar++] = (char) c;
* Our own little min method, to avoid loading java.lang.Math if we've run
* out of file descriptors and we're trying to print a stack trace.
private int min(int a, int b) {
 if (a < b) return a;
 return b;
* Write a portion of an array of characters.
* Ordinarily this method stores characters from the given array into
* this stream's buffer, flushing the buffer to the underlying stream as
* needed. If the requested length is at least as large as the buffer,
* however, then this method will flush the buffer and write the characters
* directly to the underlying stream. Thus redundant
* <code>BufferedWriter</code>s will not copy data unnecessarily.
* @param cbuf A character array
* @param off Offset from which to start reading characters
* @param len Number of characters to write
* @exception IOException If an I/O error occurs
public void write(char cbuf[], int off, int len) throws IOException {
 synchronized (lock) {
 ensureOpen();
if ((off < 0) || (off > cbuf.length) || (len < 0) ||
((off + len) > cbuf.length) || ((off + len) < 0)) {
throw new IndexOutOfBoundsException();
} else if (len == 0) {
return;
 if (len >= nChars) {
 /* If the request length exceeds the size of the output buffer,
 flush the buffer and then write the data directly. In this
 way buffered streams will cascade harmlessly. */
 flushBuffer();
 out.write(cbuf, off, len);
 return;
 int b = off, t = off + len;
 while (b < t) {
 int d = min(nChars - nextChar, t - b);
 System.arraycopy(cbuf, b, cb, nextChar, d);
 b += d;
 nextChar += d;
 if (nextChar >= nChars)
 flushBuffer();
* Write a portion of a String.
* If the value of the <tt>len</tt> parameter is negative then no
* characters are written. This is contrary to the specification of this
* method in the {@linkplain java.io.Writer#write(java.lang.String,int,int)
* superclass}, which requires that an {@link IndexOutOfBoundsException} be
* thrown.
* @param s String to be written
* @param off Offset from which to start reading characters
* @param len Number of characters to be written
* @exception IOException If an I/O error occurs
public void write(String s, int off, int len) throws IOException {
 synchronized (lock) {
 ensureOpen();
 int b = off, t = off + len;
 while (b < t) {
 int d = min(nChars - nextChar, t - b);
 s.getChars(b, b + d, cb, nextChar);
 b += d;
 nextChar += d;
 if (nextChar >= nChars)
 flushBuffer();
* Write a line separator. The line separator string is defined by the
* system property <tt>line.separator</tt>, and is not necessarily a single
* newline ('\n') character.
* @exception IOException If an I/O error occurs
public void newLine() throws IOException {
 write(lineSeparator);
* Flush the stream.
* @exception IOException If an I/O error occurs
public void flush() throws IOException {
 synchronized (lock) {
 flushBuffer();
 out.flush();
* Close the stream.
* @exception IOException If an I/O error occurs
public void close() throws IOException {
 synchronized (lock) {
 if (out == null)
 return;
 flushBuffer();
 out.close();
 out = null;
 cb = null;
What Flush(); does
Example, you have a file called c, your writer is b and buffereredwriter is a. so your programs calls a, a talks to b, and b talks to c. when you call the Flush method, the information is sent to the outfile which is c immediately before you even close the file, because when you write to the file, it does not write directly, it writes to a buffer, so flush actually causes the buffer to write to file. Also if you call the close method on that file without the flush, the buffer will still get flushed.
consider BufferedWriter c = new BufferedWriter(new PrintWriter("c:\\c"));
you wrap printwriter into a buffered writer, now if you close this "connection" to the file, the buffer will get flushed, noting that all the data is sitting in the buffered and not yet in the file, and this happens if something dont break...

Linux Serial NI-VISA - Can the buffer size be changed from 4096?

I am communicating with a serial device on Linux, using LV 7.0 and NI-VISA. About a year and a half ago I had asked customer support if it was possible to change the buffer size for serial communication. At that time I was using NI-VISA 3.0. In my program the VISA function for setting the buffer size would send back an error of 1073676424, and the buffer would always remain at 4096, no matter what value was input into the buffer size control. The answer to this problem was that the error code was just a warning, letting you know that you could not change the buffer size on a Linux machine, and 4096 bytes was the pre-set buffer size (unchangeable). According to the person who was helping me: "The reason that it doesn't work on those platforms (Linux, Solaris, Mac OSX) is that is it simply unavailable in the POSIX serial API that VISA uses on these operating systems."
Now I have upgraded to NI-VISA 3.4 and I am asking the same question. I notice that an error code is no longer sent when I input different values for the buffer size. However, in my program, the bytes returned from the device max out at 4096, no matter what value I input into the buffer size control. So, has VISA changed, and it is now possible to change the buffer size, but I am setting it up wrong? Or, have the error codes changed, but it is still not possible to change the buffer size on a Linux machine with NI-VISA?
Thanks,
Sam

The buffer size still can't be set, but it seems that we are no longer returning the warning. We'll see if we can get the warning back for the next version of VISA.
Thanks,
Josh

What's the optimum buffer size?

Hi everyone,
I'm having trouble with my unzipping method. The thing is when I unzip a smaller file, like something 200 kb, it unzips fine. But when it comes to large files, like something 10000 kb large, it doesn't unzip at all!
I'm guessing it has something to do with buffer size... or does it? Could someone please explain what is wrong?
Here's my code:
import java.io.*;
import java.util.zip.*;
* Utility class with methods to zip/unzip and gzip/gunzip files.
public class ZipGzipper {
public static final int BUF_SIZE = 8192;
public static final int STATUS_OK = 0;
public static final int STATUS_OUT_FAIL = 1; // No output stream.
public static final int STATUS_ZIP_FAIL = 2; // No zipped file
public static final int STATUS_GZIP_FAIL = 3; // No gzipped file
public static final int STATUS_IN_FAIL = 4; // No input stream.
public static final int STATUS_UNZIP_FAIL = 5; // No decompressed zip file
public static final int STATUS_GUNZIP_FAIL = 6; // No decompressed gzip file
private static String fMessages [] = {
 "Operation succeeded",
 "Failed to create output stream",
 "Failed to create zipped file",
 "Failed to create gzipped file",
 "Failed to open input stream",
 "Failed to decompress zip file",
 "Failed to decompress gzip file"
 * Unzip the files from a zip archive into the given output directory.
 * It is assumed the archive file ends in ".zip".
public static int unzipFile (File file_input, File dir_output) {
 // Create a buffered zip stream to the archive file input.
 ZipInputStream zip_in_stream;
 try {
 FileInputStream in = new FileInputStream (file_input);
 BufferedInputStream source = new BufferedInputStream (in);
 zip_in_stream = new ZipInputStream (source);
 catch (IOException e) {
 return STATUS_IN_FAIL;
 // Need a buffer for reading from the input file.
 byte[] input_buffer = new byte[BUF_SIZE];
 int len = 0;
 // Loop through the entries in the ZIP archive and read
 // each compressed file.
 do {
 try {
 // Need to read the ZipEntry for each file in the archive
 ZipEntry zip_entry = zip_in_stream.getNextEntry ();
 if (zip_entry == null) break;
 // Use the ZipEntry name as that of the compressed file.
 File output_file = new File (dir_output, zip_entry.getName ());
 // Create a buffered output stream.
 FileOutputStream out = new FileOutputStream (output_file);
 BufferedOutputStream destination =
 new BufferedOutputStream (out, BUF_SIZE);
 // Reading from the zip input stream will decompress the data
 // which is then written to the output file.
 while ((len = zip_in_stream.read (input_buffer, 0, BUF_SIZE)) != -1)
 destination.write (input_buffer, 0, len);
 destination.flush (); // Insure all the data is output
 out.close ();
 catch (IOException e) {
 return STATUS_GUNZIP_FAIL;
 } while (true);// Continue reading files from the archive
 try {
 zip_in_stream.close ();
 catch (IOException e) {}
 return STATUS_OK;
} // unzipFile
} // ZipGzipperThanks!!!!

Any more hints on how to fix it? I've been fiddling
around with it for an hour..... and throwing more
exceptions. But I'm still no closer to debugging it!
ThanksDid you add:
e.printStackTrace();
to your catch blocks?
Didn't you in that case get an exception which says something similar to:
java.io.FileNotFoundException: C:\TEMP\test\com\blah\icon.gif (The system cannot find the path specified)
 at java.io.FileOutputStream.open(Native Method)
 at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
 at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
 at Test.unzipFile(Test.java:68)
 at Test.main(Test.java:10)Which says that the error is thrown here:
 // Create a buffered output stream.
 FileOutputStream out = new FileOutputStream(output_file);Kaj

Sychronize AO/AI buffered data graph and measure data more than buffer size

I am trying to measure the response time (around 1ms) of the pressure drop indicated by AI channel 0 when the AO channel 0 gives a negetive single pulse to the unit under test (valve). DAQ board: Keithley KPCI-3108, LabView Version: 6.1, OS system: Win2000 professional.
My problem is I am getting different timed graph between the AI and AO channels every time I run my program, except the first time I can get real time graph. I tried to decrease the buffer size less than the max buffer size of the DAQ board (2048 samples), but it still does unreal time graph from AI channel, seems it was still reading from old data in the buffer when AO writes the new buffer data, that is my guessing. In my p
rogram, the AO and AI part is seperated, AO Write buffer is in a while loop while AI read is not. Would that be a problem? Or it's something else?
Also, I am trying to measure data much larger than the board buffer size limit. Is it possible to make the measurement by modifying the program?
I really appreciate any of your help. Thank you very much!
Best,
Jenna

Jenna,
You can modify the X-axis of a chart/graph in LabVIEW to display real-time. I have included a link below to an example program that illustrates how to do this.
If you are doing a finite, buffered acquisition make sure that you are always reading everything from the buffer for each run. In other words, If you set a buffer size of 5000, then make sure you are reading 5000 scans (set number of scans to read to 5000). This will assure you are reading new data every time you run you program. You could always put the AI Read VI within a loop and read a smaller number from the buffer until the buffer is empty (monitor the scan backlog output of the AI Read VI to see how many scans are left in the buffer).
You can set a buffer size larger than the FIFO
buffer of the hardware. The buffer size you set in LabVIEW is actually a software buffer size within your computer's memory. The data is acquired with the hardware, stored temporarily within the on-board FIFO, transferred to the software buffer, and then read in LabVIEW.
Are you trying to create a TTL square wave with the analog output of the DAQ device? If so, the DAQ device has counters that can generate a highly accurate digital pulse as well. Just a suggestion. LabVIEW has a variety of shipping examples that are geared toward using counters (find examples>>DAQ>>counters). I hope this helps.
Real-Time Chart Example
http://venus.ni.com/stage/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3E95556A4E034080020E74861&p_node=DZ52038&p_submitted=N&p_rank=&p_answer=&p_source=Internal
Regards,
Todd D.
National Instruments
Applications Engineer

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

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.

PLZ help me!!!! N91 switching off itself after few...

my nokia N91 4 gb got disconnected during software update which cause a severe damage.i take it to a software repairer who flash it but then he replied me that the IMEI is corrupted.then i took it to some one else who installed the software eventually by flashing 2.20 008,the latest version in my N91(Rm 43) but it is switching off itself after few hours.it sometime take 1 hour, some time half hour and some time 5 hours then switch off itself.it turns on again when i turn it on and works for same period and then again switch off.could u plz help me as i am in great trouble now.what to do now to repair it.when i went to the software repairer who repaired it.he replied that its the hardware fault.i was astonished to hear this as there was no problem before repairing the software.plzzzzzzzzzzzzzzzzzzzz help.

hello,
i am having the exact same problem. however i do nott know how it occured. the phone continues to shutdown by itself every few hours. i don't know what too do
pls help
thanks
peter

Where can I change the buffer size for LKM File to Oracle (EXTRENAL TABLE)?

Hi all,
I'd a problem on the buffer size the "LKM File to Oracle (EXTRENAL TABLE)" as follow:
2801 : 72000 : java.sql.SQLException: ORA-12801: error signaled in parallel query server P000
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-29400: data cartridge error
KUP-04020: found record longer than buffer size supported, 524288, in D:\OraHome_1\oracledi\demo\file\PARTIAL_SHPT_FIXED_NHF.dat
Do you know where can I change the buffer size?
Remarks: The size of the file is ~2Mb.
Tao

Hi,
The behavior is explained in Bug 4304609 .
You will encounter ORA-29400 & KUP-04020 errors if the RECORDSIZE clause in the access parameters for the ORACLE_LOADER access driver is larger than 10MB and you are loading records larger than 10MB. Which means their is a another limitation on read size of a record which is termed as granule size. If the default granule size is less then RECORDSIZE it limits the size of the read buffer to granule size.
Use the pxxtgranule_size parameter to change the size of the granule to a number larger than the size specified for the read buffer.You can use below query to determine the current size of the granule.
SELECT KSPFTCTXPN PARAMETER_NUMBER,
KSPPINM PARAMETER_NAME,
KSPPITY PARAMETER_TYPE,
KSPFTCTXVL PARAMETER_VALUE,
KSPFTCTXDF IS_DEFAULT,
KSPPIFLG MODIFICATION_FLAG,
KSPFTCTXVF VALUE_FLAG
FROM X$KSPPI X, X$KSPPCV2 Y
WHERE (X.INDX+1) = KSPFTCTXPN AND
KSPPINM LIKE '%_px_xtgranule_size%';
There is no 'ideal' or recommended value for pxxtgranule_size parameter, it is safe to increase it to work around this particular problem. You can set this parameter using ALTER SESSION/SYSTEM command.
SQL> alter system set "_px_xtgranule_size"=10000;
Thanks,
Sutirtha

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

I/O buffer size switch by itself

Similar Messages

Maybe you are looking for