Plainview, NY, USA
1994
  |  By meshIQ
The alert comes in at 2 AM: your order processing service is unresponsive. The application is not crashed, threads are running, the JVM is healthy, but no messages are being sent. Your operations team traces it to a blocked send() call on an ActiveMQ connection. Hours later, after restarting the application, someone finds this line in the broker log from 11 PM the previous day.
  |  By meshIQ
One of ActiveMQ's most powerful and underappreciated capabilities is its protocol polyglotism: a single broker can simultaneously accept Java JMS clients over OpenWire, Python services over AMQP, IoT sensors over MQTT, and Ruby scripts over STOMP, all routing messages between each other without protocol bridges or translation middleware.
  |  By Jennifer Knutel
Building custom middleware monitoring appears cost-effective but creates expensive maintenance debt, fragmented visibility, and operational risk. Enterprise teams spend 60-80% of IT budgets on software maintenance while unified platforms deliver immediate, production-ready capabilities.
  |  By Jennifer Knutel
Enterprise AI struggles not from inadequate models, but from fragmented data architecture. Critical business data remains trapped in legacy systems or lost in streaming complexity. Success requires bridging the gap between modern intelligence layers and underlying systems of record.
  |  By meshIQ
A single leaky application can crash your entire IBM MQ estate by consuming OS resources through unclosed connections. Traditional monitoring misses these silent killers. Learn how proactive observability detects OPPROCS anomalies before they trigger infrastructure failures.
  |  By meshIQ
On May 27, the Apache ActiveMQ project shipped two releases on the same day: 5.19.7 and 6.2.6. Look at the changelogs side by side and the story is clear — this isn’t a feature drop. It’s a coordinated security-hardening pass applied to both maintained branches of ActiveMQ Classic at once, with the same fixes deliberately backported so that no supported line is left behind.
  |  By meshIQ
The latest Apache ActiveMQ releases – 5.19.7 and 6.2.6, both from May 27 – are good releases to apply. They close known dependency CVEs and tighten the broker’s default posture. (We covered the full list of changes in our release overview.) But here’s the catch with any “secure-by-default” update: hardening defaults means turning things off.
  |  By meshIQ
meshIQ MFT Flow Intelligence converts fragmented file transfers into observable transaction ecosystems, ensuring secure, timely delivery across hybrid environments while reducing operational risk and enhancing regulatory compliance for modern enterprise operations.
  |  By meshIQ
Every persistent message in ActiveMQ must survive a broker restart. That guarantee is the contract behind DeliveryMode.PERSISTENT is what separates a messaging system from a memory buffer. It is also what makes message persistence configuration the most consequential decision in ActiveMQ architecture.
  |  By meshIQ
Kubernetes is now the default deployment substrate for most enterprise platform teams. But ActiveMQ on Kubernetes presents a specific challenge that pure stateless workloads do not: message brokers are stateful.
  |  By meshIQ
Application and integration DevOps professionals rely heavily on messaging, event processing, and streaming to build mission-critical applications. meshIQ delivers a single pane of glass that provides visibility into complex M/E/S/H environments, significantly reducing the risks to application stability and performance.
  |  By meshIQ
Welcome to meshIQ
  |  By meshIQ
Nastel XRay 1.5 release builds on industry analyst acclaim for leading AIOps & transaction observability vendor. Nastel Technologies, the leader in integration infrastructure management (i2M) solutions, announced today significant enhancements to its versatile AIOps and Transaction Observability solution, including machine learning for integration management, and visualization of business flows and IoT locations.
  |  By meshIQ
Introduction video for Nastel Technologies' solution for managing and monitoring your digitized transaction flow based on middlewares such as IBM MQ, Kafka, Solace or TIBCO. Nastel can help you through all processes of workflow digitization.
  |  By meshIQ
Frustrated with how long it takes to roll out new applications (and updates) when changes are required to messaging middleware environments? Is your team getting blamed for issues outside your control? During this short webinar and open Q&A, we will discuss.
  |  By meshIQ
This 45 minute video covers the fundamentals of MQ statistics, including architecture, setup and usage and several related use cases.
  |  By meshIQ
Nastel MSK is an option for using Apache Kafka. This introduction explains the basics of Amazon MSK and the show how in just a matter of minutes, you can be using Nastel to manage, monitor and track your Kafka usage.
  |  By meshIQ
This demo covers Custom attributes and how they can be used to display, filter and monitor data managed by Nastel.
  |  By meshIQ
IBM DataPower Gateway is the latest variant of DataPower and helps organizations meet the security and integration needs of a digital business in a single multi-channel gateway. It provides security, control, integration and optimized access to a full range of mobile, web, application programming interface (API), serviceoriented architecture (SOA), B2B and cloud workloads.
  |  By meshIQ
This a complex question with deep implications that touch many areas of the business including the executive team, finance, procurement and Human Resources. In this short webinar we will discuss some of the areas that must be considered and provide you with some strategic ideas to improve your business. This presentation is gleaned from the hundreds of man-years of experience our experts have had in answering this exact question.

Observability Platform for Messaging, Event Processing, and Streaming Across Hybrid Cloud (MESH).

Application and integration DevOps professionals rely heavily on messaging, event processing, and streaming to build mission-critical applications. meshIQ delivers a single pane of glass that provides visibility into complex M/E/S/H environments, significantly reducing the risks to application stability and performance. This speeds up mean-time-to-resolution (MTTR) and improves mean-time-between-failures (MTBF), ultimately improving application SLAs and customer experience. From modern Kafka-based streaming to legacy messaging technologies like IBM MQ, meshIQ supports every major platform out there.

A must have for every Messaging Deployment:

  • Governance: meshIQ delivers granular access controls to manage configurations across the MESH to reduce downtime and quick recovery from outages.
  • Introspection: Provides the ability to find, browse, track, and trace messages to detect bottlenecks and speeding up root-cause analysis.
  • Intelligence: Unlocks the integration blackbox to deliver visibility across the MESH infrastructure to visualize, analyze, report, and predict.
  • Action: Delivers the ability to trigger automated actions based on pre-defined criteria or intelligent actions determined by AI/ML.

Intelligence From Integration.