Kbase 19664: Changes in SonicMQ 2000.1 - ActiveX Client
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/12/2000 |
|
SUMMARY:
This document applies to Progress SonicMQ Version 2000.1.
Several changes in the way the ActiveX client behaves were implemented in Progress SonicMQ 2000.1. As a result, changes are required for applications created with Progress SonicMQ 2000.0 to run successfully under Progress SonicMQ 2000.1.
SOLUTION:
The changes are as follows:
- .wrx file for Progress SonicMQ Bean Control.
For Progress applications using the SonicMQ Bean Control,
you must generate a new .wrx file. To do this, rename the
original.wrx file, load the source .w file into the
ProgressAppBuilder, and compile.
- JMS 1.0.2 compliance.
Progress SonicMQ 2000.1 is Java Message Service (JMS) 1.0.2
compliant. The previous release is JMS 1.0.1 compliant.
Because of changes in the JMS specification, the steps to
unsubscribe a durable subscriber have changed. Progress
SonicMQ 2000.0, under JMS 1.0.1, required a durable
subscriber to be active before it could be unsubscribed.
Progress SonicMQ 2000.1 (and any subsequent JMS 1.0.2
compliant release) requires a durable subscriber to be
inactive in order to unsubscribe. This means that while the
code to unsubscribe a durable subscriber in a SonicMQ 2000.0
ActiveX Client is:
jms_Unsubscribe(sessionid, username)
the SonicMQ 2000.1 code must be:
jms_MessageConsumer_close(subscriberID).
jms_Unsubscriber(sessionID, subscriptionName).
Any attempt to unsubscribe a durable subscriber that is
still active results in the message:
"Subscriber Already Active??
References To Written Documentation:
SonicMQ 2000.1 Product Update Booklet - Ch 4, "Adherence to JMS 1.0.2
Specification".