2:34Meaning
Sheshan’s problem and Jarha’s identity The text states that Sheshan has no sons, only daughters. It then introduces a key figure for what follows: Sheshan has a servant who is Egyptian, and his name is Jarha.
Preparing Context
Loading the book, timeline, map, and study notes.
Book
World Stage
Structure
Historical Setting
1 Chronicles 2:34-41
The genealogy pauses for Sheshan’s lack of sons, then continues through his daughter’s marriage to Jarha and a long descendant chain.
Meaning in context
The genealogy pauses for Sheshan’s lack of sons, then continues through his daughter’s marriage to Jarha and a long descendant chain.
Section 6 of 8
Sheshan's Daughter and Jarha Line
The genealogy pauses for Sheshan’s lack of sons, then continues through his daughter’s marriage to Jarha and a long descendant chain.
Movement
Remembering David after exile
Artifact
Genealogies and temple preparation
Biblical Timeline
Exile & Return
1 Chronicles context: 586 BC - 400 BC
Biblical Timeline
Exile & Return
1 Chronicles context
Exile & Return / 586 BC - 400 BC
1 Chronicles context is set in the exile and return, where Babylonian exile, return, rebuilding, and renewed covenant life under Persian rule.
Scripture Text
Thesis
The genealogy pauses for Sheshan’s lack of sons, then continues through his daughter’s marriage to Jarha and a long descendant chain.
Verse by Verse
Sheshan’s problem and Jarha’s identity The text states that Sheshan has no sons, only daughters. It then introduces a key figure for what follows: Sheshan has a servant who is Egyptian, and his name is Jarha.
A marriage that carries the line forward Sheshan gives his daughter to Jarha, his servant, as a wife. The couple has a son, Attai, which becomes the new starting point for the descendants listed next.
The first stretch of named descendants The genealogy proceeds in a straight line: Attai fathers Nathan; Nathan fathers Zabad; Zabad fathers Ephlal; Ephlal fathers Obed; Obed fathers Jehu; Jehu fathers Azariah. The effect is a continuous chain from the marriage in v. 35.
Literary Context
This unit sits inside the early genealogies of 1 Chronicles 1–9, where the writer maps Israel’s tribes and key family lines to show how the community is connected to its past. Chapter 2 focuses on Judah and several branches within Judah, often slowing down to clarify unusual turns in a family line. Verses 34–41 are one of those clarifications: instead of simply listing names, the text explains why inheritance and descent proceed through a daughter’s marriage. After that explanation, the genealogy resumes its regular rhythm of “X fathered Y,” extending the Judah line through Jarha and Sheshan’s daughter.
Historical Context
Chronicles is commonly placed in the Persian period, when Judah existed as a small province within a larger empire and community identity depended heavily on remembered ancestry and established households. Genealogies served practical social functions: they linked living families to recognized forebears, supported claims of belonging, and preserved the memory of lines that might otherwise be overlooked. This passage also reflects a household world where servants could be integrated into a family through marriage, and where cross-ethnic elements (here, an Egyptian servant) could appear within Judah’s recorded lineage when a household arranged it.
Theological Significance
Questions
Keep Studying
The line continues to a final name The same pattern continues: Azariah fathers Helez; Helez fathers Eleasah; Eleasah fathers Sismai; Sismai fathers Shallum; Shallum fathers Jekamiah; and Jekamiah fathers Elishama. The passage ends by stopping at Elishama, without adding more narrative about him.
This brief genealogy explains how one Judahite family line continues when a man has no sons. The text explicitly states that Sheshan had daughters but no sons, and that he had an Egyptian servant named Jarha (vv. 34–35). Sheshan gives his daughter in marriage to Jarha, and the line is then traced through their son Attai down through many generations to Elishama (vv. 35–41). The passage’s main contribution is continuity: the family is not treated as a dead end.
It also shows that Chronicles can present a household’s story (marriage and descent) as an accepted part of Judah’s recorded ancestry, even when it includes someone identified as non-Israelite by origin (an “Egyptian”). That point is an inference from what the genealogy includes and does not criticize, but it aligns with the text’s straightforward listing.
Two main questions get different answers:
What “servant” implies about Jarha’s status (v. 34). Some read it as a clear marker of slave status. Others read it more broadly as a dependent household member or official servant, without being able to specify conditions of servitude from this verse alone.
What the mention “Egyptian” is doing (v. 34). Some take it as highlighting a surprising social boundary being crossed (a foreign servant marrying into a Judahite line). Others think it is mainly an identifier (distinguishing which Jarha), with any social implications left unstated.
Why the disagreement exists The text is very sparse: it gives labels ("servant," "Egyptian") but no background about Jarha’s life, legal standing, or how the marriage was viewed by the wider community. Because Chronicles elsewhere uses genealogies to support belonging and continuity, readers infer significance from what is included, but the passage itself does not comment.
What this passage clearly contributes The unit makes explicit that descent can be preserved through a daughter’s marriage when there is no son, and it treats the resulting descendants as a legitimate, traceable line within Judah’s records (vv. 34–41). It also preserves a memory that a person identified as an Egyptian became an ancestor in a Judahite genealogy through integration into a household (v. 34), without explaining the social mechanics beyond the marriage (v. 35).
helez (ḥā·leṣ)