[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::decmessageq

Title:	NAS Message Queuing Bus
Notice:	KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:	PAMSRC::MARCUSEN

Created:	Wed Feb 27 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2898
Total number of notes:	12363

2897.0. "getting -130 instead of -54 when client not there?" by WHOS01::ELKIND (Steve Elkind, Digital SI @WHO) Thu Jun 05 1997 21:15

    I have a customer who is using v3.0B for Unix.  He has implemented a
    server implementing a subscription service, and a client.  After the
    client has subscribed, the server when needed sends event notifications
    (alarms).  He is using PDEL_MODE_WF_MEM for the event notifications.
    
    In his lab tests, when the client was no longer there, his put_msg() on
    the server returned -54 as expected.  In production, however, he is
    getting -130 (REMQUEUEFAIL).
    
    Any ideas as to why this is happening?

T.R	Title	User	Personal Name	Date	Lines
2897.1	more info	WHOS01::ELKIND	Steve Elkind, Digital SI @WHO	`Thu Jun 05 1997 21:18`	3
	FWIW, the client is running the DmQ client library on HP-UX connected to a dmqcls process on an HP-UX server, and the server is running on Solaris.
2897.2	My 2 cents worth...	OZROCK::THOMAN	For SII support dial 110 ! (OZY internal only)	`Thu Jun 05 1997 23:47`	18
	Are the queue quotas the same in the prod'n env as in the dev & test env ? Are quotas being enforced (ie: are they enabled.) Also, are the system configuration parameters for shared memory etc the same or better in production? from the DMQ error text function -130 means: "Failed to properly dequeue a message buffer" Hope this might help. Craig. Digital SI-Engineering Australia.
2897.3	but what does that mean?	WHOS01::ELKIND	Steve Elkind, Digital SI @WHO	`Fri Jun 06 1997 00:40`	8
	My problem is in understanding what can cause a failure "to properly dequeue a message buffer". All that the CSC can tell me is that it is usually due to an IPC resource problem. And yes, I will check what their parameters are in production vs. lab. The puzzling thing is this happens only if the client is not there, attached to its temporary queue, anymore.