Hi, Please see attached.
1. Queue names should be fixed in about 5 tables (make all simple) 2. Queue data string is updated in the model 3. Subscriber data string is updated in the model 4. Subscriber has a UUID as subscriber ID now. 5. Subscriber connection is base64 encoded. Code will decode and work. In 3.1.0 there was nothing like that. 6. Inactive durable topic subscribers are derived from the queues now. No entries in subscriber table. Since there is a lot of changes in schema and code, IMO migrating from 3.1.0 to 3.2.0 is error prone. Mainly this is because the model of working is different now. Can we migrate a production MB customer to EI using below approach? 1. Create an EI cluster. MB cluster is in production. 2. Switch publishers to EI cluster. Let subscribers be done with MB cluster 3. Switch subscribers also to EI cluster. For durable topic/queue subscribers above should work. WDYT? -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
data changes between mb 3.1.0 and 3.2.0
Description: Binary data
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
