RP/MSQ 5.0 (Unix,NT) - PAMS_DECLARED difference in behavior between Windows NT/Win2K and Windows 2003 server
(Doc ID 774986.1)
Last updated on FEBRUARY 24, 2017
Applies to:Oracle MessageQ / MessageQ / 5.0
Information in this document applies to any platform
Product: MessageQ for UNIX, V5.0-RP26 Operating System: Windows 2003 Server (just certified 01/08/2004) Problem: There is a difference in behavior between MessageQ V5.0 on Windows NT/Windows 2000 versus Windows 2003 Server. On Windows NT/Windows 2000, you can reconnect to a queue that was not disconnected. On Windows 2003, you get a PAMS_DECLARED error message To replicate this behavior, via the BMQ client test utility, please follow the following steps: Scenario that you can replicate: 2.1 Launch BEA's "Test Program" that comes with MessageQ. I get the following message: "MessageQ Test, V5.00" when I start the Test Program. 2.2 Select Configure > Attach Parameters. Attach Mode = By Number. Queue Number = 1 (this is the queue number that we use). Click OK 2.3 Select Actions > Attach. Note: This works fine. I get the following message: "Attached 49.1" 2.4 Close the Test Program without disconnecting from the queue. 2.5 Repeat steps 2.1 & 2.2. 2.6 Finally try to reconnect to the queue by selecting Actions>Attach. This doesn't work. I get the following message: "Attach failed: PAMS__DECLARED" This problem will occur when I run either MessageQ 4.0 or 5.0 on Win2003 Server. However, I do not have any problems when I run the same steps under WinNT. I was able to confirm the behavior on Winodws NT/Windows 2000, ie attach to queue via test utility, close test utility, reattach to same queue - success! I could not confirm the problem on a Windows 2003 server since I don't have access to one, but Kumaran was able to simulate the problem on lcw2k17 machine, ie you get a PAMS_DECLARED message.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document