WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources
Article

[Blog post] WSO2 ESB caching in tenants

Overview

We use registry to store resources which will be used by artifacts deployed in WSO2 Products .This post describes some issues when enable or disable caching in WSO2 ESB.

Issue in Tenants' Cache

Often you will use registry resources in ESB artifacts. As an example you can store WSDLs, endpoints in registry and implement your proxies to use them. ESB registry caching works perfectly in super tenant mode but in other tenants you will come up with caching issues. If you enable caching registry resource updates should come same time but when disable if need to wait caching timeout (small time) to use newest version of resource. In tenant mode even you enable or disable caching registry resources updates will not use by ESB artifacts (proxies) until server restart. As an example if registry resource updated in one tenant (ex. endpoint), the ESB proxies in the same tenant still use the old version.

Reason for issue

This is because cachableDuration parameter is missing in the tenants's registry.xml file . This cache parameter is for registry configuration for Apache synapse. Since this parameter is missing it will still load old cache resources until server restart, even you disable the registry cache.

Solution for issue

You can fix this by put this configuration parameter to registry.xml of all tenants as follows.

Step 1

Go to /repository/tenants//synapse-configs/default/registry.xml

Step 2

Add

  
15000
into  element in registry.xml. It should be looked like this.


15000

Step 3

Put missing parameter to registry.xml like step 2 for all tenants and restart server to apply changes.

For your information this parameter is already contain in the super tenant registry configuration. That is why super tenant proxies have latest registry updates. You can find it in /repository/deployment/server/synapse-configs/default/registry.xml.

Recommended cachableDuration is 15000ms.

This is known issue in WSO2 ESB and already has jira created for this[1] and in progress. We will fix this issue in our next release.

[1]https://wso2.org/jira/browse/ESBJAVA-3039

Click here to refer to Waruna's blog.