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] DSS not consuming messages from JMS queues

As you know, we can integrate WSO2 Data Services Server with WSO2 Message Broker, in a way that the WSO2 Data Services Server consumes messages from the queues of the Message Broker.

When it comes to large scale, like more than 100 data services consuming messages from Message Broker, it will throw the following exception and will not start to consume messages from queues.

WARN {org.apache.axis2.transport.jms.JMSListener} - Polling tasks on destination : xxx of type queue for service xxx have not yet started after 3 seconds.

The reason behind this warning and the situation is controlled limitation of the system. In the Data Services Server, the number of threads that consume messages from jms queues from the implementation to 100 has been limited.

It has been done by adding a configurable parameter to the start up script ( wso2server.sh) of the server. By default, the value of the parameter is snd_t_core=100. If any one gets the above exception in a situation like more than 100 consumers, you can increase this parameter to overcome that situation as shown below:

-Dcom.sun.jndi.ldap.connect.pool.authentication=simple \

-Dcom.sun.jndi.ldap.connect.pool.timeout=3000 \

-Dorg.terracotta.quartz.skipUpdateCheck=true \

-Dsnd_t_core=200 \

-Dsnd_t_max=250 \

-Djava.security.egd=file:/dev/./urandom \

Source : https://shammijayasinghe.blogspot.com/2013/07/dss-not-consuming-messages-from-jms.html