Database, HTTP, File and JMS connector behaviors
How the Database Connector calls stored procedures and limits Select results, how the HTTP Request operation resolves hosts, builds the Host header and streams bodies, how File Read locks behave, and how JMS acknowledgement modes decide redelivery.
Design Mule applications using common features of core connectors.
~8 min read · 7 practice questions
What the exam expects
- Write a stored procedure call the Database Connector supports: parameter order, defaults and date handling.
- Bound a large Select by total rows and network chunk size.
- Recognize HTTP Request behaviors that break partner calls (round-robin DNS, the generated Host header) and their controls.
- Distinguish chunked, internal and response streaming by Mule runtime version.
- Predict File Read lock behavior and JMS redelivery under each acknowledgement mode.
Callable statement: the { call name(:p1, …) } text a Stored procedure runs. Fetch size: rows returned per network chunk. Round-robin DNS: spreading requests across every IP a host resolves to. Request streaming: sending an HTTP body in chunks. ackId: the attribute identifying a received JMS message for its connection (HTTP Request, JMS acknowledgement).
Sources for this section (2)
Key facts
- Detail
- All of them, in declaration order, parameterized; no named parameters
- Detail
- Does not push the procedure's default value
- Detail
- Transparent and always enabled
- Detail
- Total row cap / rows per network chunk (driver default often 10)
- Detail
- Round-robin DNS by default; opt out per host with
mule.http.disableRoundRobin
- Detail
- Default port included when none configured; omit property needs Mule 4.5+ and HTTP 1.10.3+
mule.http.requestStreaming.enable- Detail
- false on Mule 4.4 and earlier, true on 4.5 and later
- Detail
FILE:FILE_LOCKerror
- Detail
- Unacknowledged messages are not redelivered; recover on the receiving connection
- What is the default maximum size of the HTTP request header section, and which property changes it?
- When a stored procedure's return value is an output parameter, how must the start of the call be written?
- When the JDBC driver is Snowflake, how does the callable statement differ from the standard form?
- Why can a processor after a streamed HTTP response stall, and what bounds the wait?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both