Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • TIBCO Cloud Messaging Release Notes


    Bill Mclane

    TIBCO Cloud? Messaging Release Notes


    June 6, 2023

    TCM 4.8.0

    New and Changed Features

    • Upgraded TIBCO FTL® and TIBCO eFTL? to 6.10.0
    • Upgraded TIBCO Enterprise Message Service?  to 10.2.1-HF002
    • Apache Pulsar and Apache Kafka services now support multi-channel messaging.
    • Message retention settings for Apache Pulsar channels can be changed using the TIBCO Cloud Messaging Admin REST API.
    • TIBCO Enterprise Message ServiceTM client connection information can be viewed with the TIBCO Cloud Messaging Admin REST API.

    Known Issues

    • MAAS-2907: TIBCO Enterprise Message ServiceTM 10.x clients that are using an older version of Java 1.8 might fail to connect to TIBCO Cloud? Messaging. Workaround: Try a newer version of Java 1.8. For example, you can use OpenJDK 1.8.0_312.
    • MAAS-2690: The plan Admin API incorrectly returns 2MB for the maximum message size. The maximum message size is 1MB. Workaround: None
    • MAAS-2419: Deleted TIBCO Enterprise Message ServiceTM topics might temporarily reappear in the topic listing after a TIBCO Cloud? Messaging service update. Workaround: None
    • MAAS-2004: If you run the Apache Kafka consumer sample first, then the Apache Pulsar consumer sample might fail to run because of an IncompatibleSchema error. Workaround: Apache Pulsar and Apache Kafka consumers can use the same topic if you start the Apache Pulsar consumer first.

    Closed Issue

    • MAAS-3113: Apache Pulsar go samples can timeout on initial connect too soon.

    January 24, 2023

    TCM 4.7.0

    New and Changed Features

    • Upgraded EMS to 10.2.1
    • Upgraded FTL to 6.9.1

    Known Issues

    • MAAS-2907: TIBCO Enterprise Message ServiceTM 10.x clients that are using an older version of Java 1.8 might fail to connect to TIBCO Cloud? Messaging. Workaround: Try a newer version of Java 1.8. For example, you can use OpenJDK 1.8.0_312.
    • MAAS-2690: The plan Admin API incorrectly returns 2MB for the maximum message size. The maximum message size is 1MB. Workaround: None
    • MAAS-2419: Deleted TIBCO Enterprise Message ServiceTM topics might temporarily reappear in the topic listing after a TIBCO Cloud? Messaging service update. Workaround: None
    • MAAS-2004: If you run the Apache Kafka consumer sample first, then the Apache Pulsar consumer sample might fail to run because of an IncompatibleSchema error. Workaround: Apache Pulsar and Apache Kafka consumers can use the same topic if you start the Apache Pulsar consumer first.

    Closed Issues

    • MAAS-3037: TCM REST API support for promoting EMS dynamic topics and queues to static

    September 22, 2022

    TCM 4.6.0

    New and Changed Features

    • Support for TIBCO Enterprise Message ServiceTM static destinations.
    • The Admin REST API now returns a ?404 Not Found? error message when you attempt to delete an EMS topic or queue that does not exist.
    • The fields ?expiration? and ?prefetch? of an EMS queue and topic are now in the new ?properties? field of the Admin REST API response.

    Known Issues

    • MAAS-2907: TIBCO Enterprise Message ServiceTM 10.x clients that are using an older version of Java 1.8 might fail to connect to TIBCO Cloud? Messaging. Workaround: Try a newer version of Java 1.8. For example, you can use OpenJDK 1.8.0_312.
    • MAAS-2690: The plan Admin API incorrectly returns 2MB for the maximum message size. The maximum message size is 1MB. Workaround: None
    • MAAS-2419: Deleted TIBCO Enterprise Message ServiceTM topics might temporarily reappear in the topic listing after a TIBCO Cloud? Messaging service update. Workaround: None
    • MAAS-2004: If you run the Apache Kafka consumer sample first, then the Apache Pulsar consumer sample might fail to run because of an IncompatibleSchema error. Workaround: Apache Pulsar and Apache Kafka consumers can use the same topic if you start the Apache Pulsar consumer first.

    Closed Issue

    • MAAS-2958: The TIBCO Cloud Messaging Swagger JSON no longer generates errors when imported into a Swagger editor.

    August 16, 2022

    TCM 4.5.0

    New and Changed Features

    • Added REST API support for filtered bulk lookup of TIBCO Enterprise Message ServiceTM destinations. For more information, see https://api.cloud.tibco.com/tcm/docs
    • Upgraded TIBCO FTL/eFTL to 6.8.1
    • Upgraded Apache Pulsar to 2.10.0

    Known Issues

    • MAAS-2907: TIBCO Enterprise Message ServiceTM 10.x clients that are using an older version of Java 1.8 might fail to connect to TIBCO Cloud? Messaging. Workaround: Try a newer version of Java 1.8. For example, you can use OpenJDK 1.8.0_312.
    • MAAS-2690: The plan Admin API incorrectly returns 2MB for the maximum message size. The maximum message size is 1MB. Workaround: None
    • MAAS-2419: Deleted TIBCO Enterprise Message ServiceTM topics might temporarily reappear in the topic listing after a TIBCO Cloud? Messaging service update. Workaround: None
    • MAAS-2004: If you run the Apache Kafka consumer sample first, then the Apache Pulsar consumer sample might fail to run because of an IncompatibleSchema error. Workaround: Apache Pulsar and Apache Kafka consumers can use the same topic if you start the Pulsar consumer first.

    Closed Issue

    • MAAS-2925: When TIBCO Enterprise Message Service? is stopped, the passport subscriptions save the TIBCO Enterprise Message ServiceTM configuration.


    User Feedback

    Recommended Comments

    There are no comments to display.


×
×
  • Create New...