[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

2855.0. "Lazy server - doesn't wake up until 2nd message queued" by MIASYS::DLUGOSZ (My reality check just bounced) Mon Apr 21 1997 18:45

    We're seeing some strange problems here. We have been porting a
    large application from VAX to Alpha. The software was initially
    built on a single Alpha host and tested - all worked well. We
    were also using DmQ v3.2 on that host. 
    
    We moved the software to the customer's development cluster
    which is set up so that the clients are on one node and the 
    servers on another. Both are running 3.2B and all software was
    (I am promised) recompiled and relinked against 3.2B. 
    
    Message 1 is sent to a server. The server (which is sitting in
    PAMS_GET_MSGW) doesn't read the message. You can see it pending
    in the monitor. Message 2 is sent. The server reads and processes
    both messages.
    
    Has anybody run into something like this before? Why for would 
    the server not be awaken'd until the second message arrives?
    
    Ron

T.R	Title	User	Personal Name	Date	Lines
2855.1	Fixed with ECO 3250...	KLOVIA::MICHELSEN	BEA/DEC MessageQ Engineering	`Mon Apr 21 1997 23:30`	5
	This problem has been fixed with ECO 3250. You can copy it from PAMSRC::DMQ$KITS:[DMQ32B.VMS.PATCHES]DMQ-V32B-AXP-3250.BCK. Marty
2855.2	A couple of followup questions	MIASYS::DLUGOSZ	My reality check just bounced	`Tue Apr 22 1997 14:34`	14
	Marty, We're a little confused about prerequisites for the 3250 patch. We're seeing the described behavior so does this imply the kit they have installed already has patch 3240? Also the instructions mention a file EXEC-V32B-AXP-3250.OBJ (substituting the x's). The kit contains EXEC-V32-AXP-3250.OBJ. Which file name should be used - or does it matter? Never have learned much about VMS.... Ron
2855.3	It's a V3.2B patch...	KLOVIA::MICHELSEN	BEA/DEC MessageQ Engineering	`Wed Apr 23 1997 09:00`	21
	re: .2 > We're a little confused about prerequisites for the 3250 patch. > We're seeing the described behavior so does this imply the kit > they have installed already has patch 3240? V3.2B contains ECOs 3201-3246, therefore, the pre-requisite should have been stated as V3.2B. > Also the instructions mention a file EXEC-V32B-AXP-3250.OBJ > (substituting the x's). The kit contains EXEC-V32-AXP-3250.OBJ. > Which file name should be used - or does it matter? Typo in the command procedure that created the patch files. The file should have been named EXEC-V32B-AXP-3250.OBJ. In other words, the file is correct only the name of it is slightly wrong. Marty