We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

How to set IPC limits in Solaris 2.51

Medium Priority
541 Views
Last Modified: 2013-12-26
Hi:

I've got a little program that is trying to add (about) 1000 messages to
an IPC message
queue that it has created.  I've set the following system parameters in
Solaris
2.51 in /etc/system to:  

        set msgsys:msginfo_msgtql = 65560
        set msgsys:msginfo_msgmnb = 1024000

This should set the maximum number of messages in any queue to be 65K,
and the total
number of bytes for a message queue to 1M.

The program is running on an Ultra 1 with 128 meg of memory, and the
system is not taxed.
The program is to add a finite number of messages to the queue, and a
reader
is to later read the messages from the queue.

I am able to create ONLY 341 messages before I get the error EAGAIN
(errno == 11),
and strerror() prints the text:  "Resource temporarily unavailable".  I
limit at 341
regardless of whether IPC_NOWAIT is set in the flags or not.

I have changed the msgtql from 65560 to 512, and I can still add only
341 messages
before croaking.  Does anyone know what's going on here?  

One other simple question:  Do Solaris Message Queues have built-in
semaphore protection
(unlike Shared Memory where you have to roll  your own semaphores)?
That is to say,
can multiple processes add to and remove from a particular Message Queue
without
having to implement a semaphore?

Any help would be most gratefully appreciated.  Please respond to the
news group or to: mshack@interaccess.com.

Thanks.

Mark

PS:

What I'm trying to do is to obtain timing information from a
transactional processing
system.  I want to track a number (say, 1000) of transactions through
their lifetimes
in the system.  Each application type will create a message recording
the transaction type, their application type, and the time that the
transaction was
acted upon by the application. Each of these "timings" are then to be
added to
the message queue.  For 1000 records, the message queue needs to be able
to hold about
5000 21-byte messages.  We are using a message queue because we want to
be able
to "live" store a number of "timing records" with as little trouble and
impact (ala
Heisenberg) as possible.  Once all the transactions have been processed,
we
want to dump the message queue out via a reader and analyze the timings.
If you have any suggestions as to how this can be better done by
something other
than message queues, please let me know.  I'm using message queues
because
they have IPC, a record-based structure capable of storing more than one
message/record easily, and because I think it has built-in semaphore
support.
Please advise if there are caveats to that last assumption.
Comment
Watch Question

Commented:
There is also a system inposed limit on the total number of messages that can be in queues, have you checked what your system has it set to?
Check out the limits on: datasize, stackzize & memorysize
-Eric.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.