AceMQ supports Pentaho 24/7 across Americas, EMEA and APAC on Pentaho Data Integration (Kettle), Carte servers and Pentaho Server, whether you run the Community or the Enterprise Edition. Most calls begin with one of three problems: a job that succeeds but loads wrong or missing rows, a repository or scheduler that stops responding, or a transformation that broke after a Java or database driver change.
AceMQ keeps Pentaho Data Integration (Kettle) and Pentaho Server running in production — driver mismatches after infrastructure patches, repository lock contention, and jobs that silently stop firing after an upgrade. We also help teams that are honestly ready to move off Pentaho plan that migration properly.
Support quotes answered within 1 hour, by a senior engineer.
Each row is a failure we have traced in Pentaho Data Integration and Pentaho Server, with the first log, setting or table an engineer opens.
Common Pentaho production problems and how AceMQ resolves them
Symptom you're seeing
What we check first
A job reports success and the target table is short
Check the step metrics in the log (read, written, rejected, errors) and any "continue on error" or error-handling hop that silently routes rejected rows. Then compare row counts at each step with the source.
Memory exhaustion in a large transformation
Check PENTAHO_DI_JAVA_OPTIONS (-Xmx), step row-set size (Nr of rows in rowset), and Sort Rows, Group By or Merge Join steps that hold everything in memory. Fixes are streaming joins, sorting in the database and sizing Sort size.
Pentaho Server will not start or the repository hangs
Check the Jackrabbit or database repository connection pool, lock rows and the catalina.out log. Repository lock contention often traces to a crashed process that never released its lock.
Scheduled jobs stop firing after an upgrade
Check the Quartz tables, trigger state and the server's time zone, then whether the job path in the repository changed.
A Carte slave falls out of the cluster
Check the slave's status page, slave-server-config.xml and the master's list of registered slaves. Clustered transformations do not recover a partition automatically.
A driver mismatch breaks one connection
Check the JDBC driver in the lib directory against the database version and the Java version. An operating system or Java patch that raised a TLS minimum is a frequent cause.
Logging tables grow until the scheduler slows
Check the job and transformation log tables and the cleanup job. Unbounded logging into the repository database makes every run slower.
Each fix ends in a root-cause analysis that names the step, driver or trigger responsible.
A Pentaho job stopped and finance is waiting? Send a quote request and a senior engineer replies within one hour.
Hitachi Vantara does not offer professional support for Community Edition (see note below)
Defects needing a change to Pentaho's code
Pentaho Enterprise Edition (PDI and Pentaho Server)
Operations beside the Hitachi Vantara ticket
Hitachi Vantara subscription support
Enterprise-only defects
Carte clusters
Cluster setup, slave health, partitioning
As above
Network faults
Pentaho Server repository and scheduler
Repository health, Quartz, content migration
As above
Underlying database faults
Pentaho to other tools
Assessment and migration planning, with lineage recovered first
Not applicable
Tool licences
Support options
Hitachi Vantara support or independent support?
Hitachi Vantara Pentaho Enterprise
AceMQ independent support
EditionEnterprise Edition, sold on an annual subscription that bundles support and updates
EditionCommunity and Enterprise
Product patchesYes
Product patchesNo vendor patches
PricingNot published
Pricing$24,000 to $72,000 a year (USD), by SLA, scope and deployment
What's Included
Everything in your Pentaho support contract
Kettle jobs, Carte clusters and the Pentaho repository are covered under one contract, with no separate charge per incident.
01
Emergency Incident Response
A production ETL job that finance, reporting, or downstream systems depend on stops running. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.
02
Root Cause Analysis
Every P1 closes with a written RCA: what failed, why, the fix applied, and the specific driver, config, or scheduler change that prevents recurrence.
03
Performance Tuning
Carte and PDI engine memory tuning, step-level optimization to push work into the database instead of the transformation engine, and job orchestration cleanup for large batch runs.
04
Legacy Version Maintenance
Support for end-of-life Pentaho versions still running in regulated or change-controlled environments, including workarounds for known bugs with no official patch available.
05
Migration Planning & Execution
Honest assessment of whether to keep, upgrade, or replace a Pentaho deployment — and execution of a migration to Airbyte or a modern ELT stack when that's genuinely the better path.
06
Repository & Scheduler Health Reviews
Quarterly checks on repository integrity, Quartz scheduler configuration, and job/transformation inventory so upgrade risk and technical debt don't compound silently.
Why AceMQ
Why teams keep AceMQ on their PDI estate
Named Engineers, Zero Cold Start
The same senior engineers stay on your account. They know your transformation inventory, your repository structure, and where the fragile jobs are — so a P1 starts with diagnosis, not an environment walkthrough.
No Tier-1 Triage Layer
You reach a senior Pentaho engineer directly by phone, email, or Slack. No help desk collecting information to pass along, no approval process between you and someone who can fix it.
We Still Know Kettle Deeply
Most consultancies have moved on from Pentaho entirely. Our engineers still work in PDI transformations regularly, which matters when the fix requires actually understanding step-level behavior, not just restarting a service.
Genuine Follow-the-Sun Coverage
Round-the-clock coverage for customers in 26+ countries. Your overnight batch failure is someone's mid-afternoon — no waiting for a region to wake up.
Honest About Maintain vs. Migrate
We will tell you plainly when a Pentaho deployment is stable and cheap to keep running, and when the maintenance burden or end-of-life risk means migration is the better financial decision. Neither answer earns us more retainer revenue than the other.
Full-Stack, Not Just the ETL Tool
Pentaho problems are frequently JDBC driver, JVM, OS patch, or database-side problems wearing a Pentaho error message. We diagnose across the whole stack because that's where root causes usually live.
Where we run Pentaho support
Pentaho Server on a single host, Carte clusters behind a master, and locked-down networks with no outbound access to AceMQ.
Pentaho Server (on-premise)
Pentaho Data Integration / Kettle
AWS EC2 & self-managed cloud
VMware vSphere
Bare metal & on-premise data centers
Clustered Carte deployments
Air-gapped / no outbound access
Legacy end-of-life versions (7.x, 8.x)
Hybrid on-prem to cloud warehouse
Regulated / change-controlled environments
Version coverage
Pentaho versions we support
Pentaho versions we support
Release line
What we do on it
10.x
24/7 support and upgrades
9.x
24/7 support and upgrade planning
8.x and 7.x
24/7 support, driver and Java compatibility work, and upgrade or migration planning
Escalation Path
Your first hour of a Pentaho outage
The engineer who picks up a stalled batch run knows Kettle, so the first question is which step or scheduler trigger failed.
From 15 min (by plan)first responseEmergencyProduction down: Pentaho Server will not start, the repository is locked, or the nightly PDI batch has stopped
1 hourfirst responseCriticalSevere degradation: jobs run but load short or wrong data, Carte slaves drop out, memory exhaustion in large transformations
4 hoursfirst responseHighScheduler triggers misfiring after an upgrade, JDBC driver mismatches, log tables slowing runs
Next Dayfirst responseStandardQuestions on step design, kettle.properties settings, upgrade planning and migration options
Response targets by plan: an overnight Pentaho batch failure and a daytime question get different clocks.
Want a named Pentaho engineer on call for your batch window? Get a quote or send us a message.
Pentaho support typically runs $24,000–72,000 a year. The size of the contract follows how many Pentaho Server and Carte nodes you run, how critical the batch window is, and whether you use the Enterprise or Community edition.
Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. A contract that also covers your data stores or other tools earns a multi-technology discount.
Support In Practice
Pentaho jobs we have helped recover
Pentaho support and migration work from AceMQ. Each card links to the full write-up: the batch estate, what AceMQ diagnosed or changed, and the result.
Support
Pentaho Job Failure and Data Integrity Support
Logistics and Distribution Company
Ongoing support for a Pentaho Data Integration estate that must keep running reliably while a longer-term replacement is planned.
AceMQ offers Pentaho support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for batch estates your team runs, proactive monitoring that finds fragile jobs and repository problems first, managed Pentaho on your own infrastructure, and fully managed Pentaho on AceMQ infrastructure. Current versions, 9.x and legacy 8.x and 7.x are covered in all four.
Your team runs itAceMQ runs it
Tier 1
Pentaho 24/7 Support & Incident Management
Your ETL team runs PDI, we take the escalations
Best for: Teams that own their transformations and need a senior Kettle engineer when a batch run breaks.
Tier 2
Pentaho 24/7 Support with Proactive Monitoring
We review your jobs and repository with you
Best for: Teams tired of finding out about driver, repository or Quartz problems from a failed overnight run.
Tier 3
Managed Pentaho on Your Infrastructure
We operate Pentaho Server and Carte in your estate
Best for: Regulated shops whose Pentaho Server and Carte nodes must stay on their own hosts.
Tier 4
Fully Managed Pentaho on AceMQ Infrastructure
We run Pentaho Server and its scheduler for you
Best for: Teams who want the reports and scheduled jobs without owning the Pentaho Server operations.
One partner for Pentaho
Everything else AceMQ does for Pentaho.
The same engineers handle Pentaho consulting, migration planning to Airbyte or another ELT stack, and the databases your jobs load into.
Hitachi Vantara, for Enterprise Edition, and independent providers such as AceMQ. Community Edition users rely on forums unless they buy independent support.
Can you fix a transformation that broke after an OS or Java patch?
Yes. We compare the Java and driver versions, TLS settings and kettle.properties before the patch and after, then pin or update the right component.
Why did the job succeed but load wrong data?
Usually an error-handling hop, a lookup that returns null, or a type conversion that truncates. We trace row counts through each step.
Do you still have engineers who know Kettle?
Yes. Kettle and PDI work is part of our regular support.
Should we migrate away from Pentaho?
We help you decide. We recover lineage first, then price the options. Some jobs are cheaper to keep.
What do you do about Carte cluster problems?
Check slave registration, status pages and partitioning, then redesign jobs that depend on a fragile cluster.
How fast do you respond to a Pentaho outage?
A response starts within 15 minutes on the top plans, any hour. Take a Sev 1 where Pentaho Server will not start after a Java patch: an engineer joins a bridge, reads catalina.out and the repository connection, and you get a written root cause afterwards. P2 is answered in 1 hour, P3 in 4 hours and P4 by the next business day.
Do we have to sign an annual Pentaho contract?
No. You can hire AceMQ for one piece of Pentaho work, such as a failed upgrade, a repository recovery or a migration assessment, or take an annual agreement with 24/7 cover and named engineers. Most teams with a legacy PDI estate start with one engagement and move to the annual agreement.
What decides the price of a Pentaho support contract?
Contracts usually fall between $24,000 and $72,000 a year (USD). The main inputs are the number of Pentaho Server and Carte nodes, how many production job schedules depend on them, the edition and version you run, and the response level you choose. Send the details and we reply with a quote within 1 hour.
Let's talk
Your Pentaho Jobs Shouldn't Depend on Nobody Touching Them
Send us your PDI version and the job that fails. We reply with a quote within 1 hour.
A senior Pentaho engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership