I Chronicles 2:34-41 · Bible study
1 Chronicles 2:34-41 Commentary: Egyptian Servant in Judah's Line
Hebrew · 8 what the commentators say
Meaning in one sentence
Why does the Chronicler include the marriage of Sheshan's daughter to an Egyptian slave?
Research Summary
- Meaning: The Chronicler records the line of Sheshan through his daughter and Egyptian servant Jarha, showing God's inclusion of outsiders and his preservation of the covenant family.
- Key words: bānîm (sons), bānôt (daughters), ‘eved (servant/slave), miṣrî (Egyptian), nātan (gave).
- Main debate: Whether Jarha's marriage violated Mosaic law against mixed marriages. Some see a concession; others argue he became a proselyte.
- Theological theme: God's sovereignty in preserving lineage through unconventional means, and the openness of the covenant community to foreigners who join.
- Best use: Illustrate God's grace in including foreigners and the value of every person in God's redemptive plan, especially in sermons on identity and belonging.
Translation Comparison
BSB Berean Standard Bible 2020
34Sheshan had no sons, but only daughters; but he did have an Egyptian servant named Jarha.
35Sheshan gave his daughter in marriage to his servant Jarha, and she bore to him Attai.
36Attai was the father of Nathan, Nathan was the father of Zabad,
37Zabad was the father of Ephlal, Ephlal was the father of Obed,
38Obed was the father of Jehu, Jehu was the father of Azariah,
39Azariah was the father of Helez, Helez was the father of Elasah,
40Elasah was the father of Sismai, Sismai was the father of Shallum,
41Shallum was the father of Jekamiah, and Jekamiah was the father of Elishama.
WEB World English Bible 2000
34Now Sheshan had no sons, but only daughters. Sheshan had a servant, an Egyptian, whose name was Jarha.
35Sheshan gave his daughter to Jarha his servant as wife; and she bore him Attai.
36Attai became the father of Nathan, and Nathan became the father of Zabad,
37and Zabad became the father of Ephlal, and Ephlal became the father of Obed,
38and Obed became the father of Jehu, and Jehu became the father of Azariah,
39and Azariah became the father of Helez, and Helez became the father of Eleasah,
40and Eleasah became the father of Sismai, and Sismai became the father of Shallum,
41and Shallum became the father of Jekamiah, and Jekamiah became the father of Elishama.
KJV King James Version 1769
34Now Sheshan had no sons, but daughters. And Sheshan had a servant, an Egyptian, whose name was Jarha.
35And Sheshan gave his daughter to Jarha his servant to wife; and she bare him Attai.
36And Attai begat Nathan, and Nathan begat Zabad,
37And Zabad begat Ephlal, and Ephlal begat Obed,
38And Obed begat Jehu, and Jehu begat Azariah,
39And Azariah begat Helez, and Helez begat Eleasah,
40And Eleasah begat Sisamai, and Sisamai begat Shallum,
41And Shallum begat Jekamiah, and Jekamiah begat Elishama.
ASV American Standard Version 1901
34Now Sheshan had no sons, but daughters. And Sheshan had a servant, an Egyptian, whose name was Jarha.
35And Sheshan gave his daughter to Jarha his servant to wife; and she bare him Attai.
36And Attai begat Nathan, and Nathan begat Zabad,
37and Zabad begat Ephlal, and Ephlal begat Obed,
38and Obed begat Jehu, and Jehu begat Azariah,
39and Azariah begat Helez, and Helez begat Eleasah,
40and Eleasah begat Sismai, and Sismai begat Shallum,
41and Shallum begat Jekamiah, and Jekamiah begat Elishama.
YLT Young's Literal Translation 1898
34And Sheshan had no sons, but daughters, and Sheshan hath a servant, an Egyptian, and his name is Jarha,
35and Sheshan giveth his daughter to Jarha his servant for a wife, and she beareth to him Attai;
36and Attai begat Nathan, and Nathan begat Zabad,
37and Zabad begat Ephlal, and Ephlal begat Obed,
38and Obed begat Jehu,
39and Jehu begat Azariah, and Azariah begat Helez, and Helez begat Eleasah,
40and Eleasah begat Sismai, and Sismai begat Shallum,
41and Shallum begat Jekamiah, and Jekamiah begat Elishama.
Darby Darby Bible 1890
34And Sheshan had no sons, but daughters; and Sheshan had an Egyptian servant, whose name was Jarha;
35and Sheshan gave his daughter to Jarha his servant as wife, and she bore him Attai.
36And Attai begot Nathan, and Nathan begot Zabad,
37and Zabad begot Ephlal, and Ephlal begot Obed,
38and Obed begot Jehu, and Jehu begot Azariah,
39and Azariah begot Helez, and Helez begot Elasah,
40and Elasah begot Sismai, and Sismai begot Shallum,
41and Shallum begot Jekamiah, and Jekamiah begot Elishama.
Douay-Rheims Douay-Rheims Bible 1899
34And Sesan had no sons, but daughters and a servant an Egyptian, named Jeraa.
35And he gave him his daughter to wife: and she bore him Ethei.
36And Ethei begot Nathan, and Nathan begot Zabad.
37And Zabad begot Ophlal, and Ophlal begot Obed.
38Obed begot Jehu, Jehu begot Azarias.
39Azarias begot Helles, and Helles begot Elasa.
40Elasa begot Sisamoi, Sisamoi begot Sellum,
41Sellum begot Icamia, and Icamia begot Elisama.
Verse in Context
Original Language (Biblical Hebrew)
Old Testament · Biblical Hebrew · I Chronicles 2:34
Source: STEPBible TAGNT/TEHB (CC-BY 4.0). Click or tap a morphology code to see the full parsing.
Scholars' Consensus
Commentators agree this passage records an unusual but accepted practice within the tribe of Judah. Sheshan had no surviving sons, so he gave his daughter to his Egyptian servant Jarha, effectively making Jarha his heir. Gill notes that Jarha was likely a proselyte, having embraced the faith of Israel. Jamieson-Fausset-Brown similarly argues that Jarha had abandoned Egyptian idolatry, removing any legal difficulty with the marriage. The Cambridge Bible compares the act to Abraham's regard for Eliezer as heir (Genesis 15:2, 3). The genealogy continues through Attai and eventually produces Zabad, who is listed among David's mighty warriors (1 Chronicles 11:41). The Chronicler's inclusion of this line, despite its foreign origin, demonstrates that God's covenant community could incorporate outsiders who joined themselves to Israel.
Wesley adds that Jarha was probably an eminent man, not merely a slave. The text uses the Hebrew word ʿeved, which can mean servant or slave, and Jarha is identified as Egyptian (miṣrî). The consensus reads the passage as a deliberate record of how God preserved a family line through non‑traditional means, affirming that belonging to God's people is not strictly a matter of blood.
How settled is the interpretation?
Interpretive difficulty: Medium
Main views:
- Lawful proselyte marriage: Jarha converted to Israel's faith (JFB, Gill). The marriage was therefore legitimate under the law, as proselytes were fully accepted.
- Violation of the law: Michaelis (cited by JFB) argues that marriage to an Egyptian, even a freed slave, violated the prohibition against mixed marriages (Deuteronomy 7:3). The passage records a fact without endorsing it.
- Pragmatic adoption: The Cambridge Bible compares the act to known Eastern customs where a childless man adopts a servant to carry on his name, similar to Abraham and Eliezer.
What is clear: The Chronicler includes this marriage and its offspring as part of the genealogy of Judah, indicating that the line was considered legitimate within the covenant community.
What Scholars Agree and Debate
| Topic | Agreed | Debated |
|---|---|---|
| Sheshan's lack of sons | Sheshan had no surviving sons at the time of his death. | Whether he had only one daughter (Ahlai, 1 Chr 2:31) or multiple daughters (the text uses the plural). Gill suggests the plural may be for a single child. |
| The marriage of Jarha | The marriage was an accepted practice within Judah's genealogy; the Chronicler records it without disapproval. | Some see it as a violation of the law against mixing with Egyptians (Michaelis, cited by JFB). Others argue Jarha converted and became a proselyte, removing the prohibition (Gill, JFB). |
| Significance of the genealogy | The line leads to Zabad, one of David's mighty warriors (1 Chr 11:41), showing the family's contribution to Israel. | Whether the names are strictly historical or include some symbolic elements. The Chronicler's source likely came from existing records. |
Historical & Cultural Context
This passage sits within the genealogies of Judah (1 Chronicles 2:1, 4:23), a section of the Chronicler's work addressed to the post‑exilic community returning from Babylon. After the exile, questions of identity, land inheritance, and purity pressed heavily on the people. The Chronicler retraces the tribes to show continuity with the past and to affirm that God's promises to the patriarchs still stand.
Sheshan belonged to the family of Jerahmeel, a branch of Hezron's line. He had no sons (v. 34), a crisis in a culture where a man's name was carried on through male children. The Hebrew verb hāyâ (“it belonged”) with the negative lō’ emphasizes the lack. His solution, marrying his daughter to an Egyptian servant named Jarha, was not unknown in the ancient Near East. Abraham, childless, considered his servant Eliezer as heir (Genesis 15). The practice of a childless man adopting a trusted servant and giving him a daughter in marriage is attested in other Eastern contexts.
The name Jarha is Egyptian, and the text stresses his origin. For a daughter of Judah to marry an Egyptian might have raised eyebrows, but the Chronicler records it without comment, indicating acceptance. The Targum and later Jewish tradition add that Sheshan first freed Jarha. Most commentators believe Jarha converted to the faith of Israel. The genealogy that follows, Attai, Nathan, Zabad, and others, spans several generations, likely reaching into the period of the monarchy. Zabad appears as a mighty warrior of David in 1 Chronicles 11:41, confirming that this line contributed to David's kingdom.
The list of names from Attai to Elishama (vv. 35, 41) forms a chain of eleven generations. Several names are otherwise unknown, but the Chronicler preserves them faithfully. This attention to detail reminds the reader that every link in the chain matters. The passage quietly asserts that God's redemptive plan moves through ordinary families and unconventional circumstances, not only through famous heroes.
Textual Notes
The consulted sources note no significant textual variants for this passage. The main manuscript traditions (Masoretic Text, Septuagint, Vulgate) agree closely. Minor spelling differences appear in the name Sisamai (KJV) versus Sismai (WEB, ASV), but these do not affect meaning.
Reception History
Early Jewish tradition, reflected in the Targum, added that Sheshan first freed Jarha before the marriage, ensuring the union was honorable. Medieval Jewish commentators (Rashi, Kimchi) noted the precedent of Abraham and Eliezer. Christian readers from the patristic period onward saw in this Egyptian servant a type of the Gentile inclusion into the people of God. The Reformation commentators (Geneva Bible, Matthew Henry) stressed the providence of God in preserving the line despite apparent dead ends. In modern scholarship, the passage is often cited as evidence that the Chronicler's genealogies are not merely dry lists but convey theological themes of inclusion and grace.
Preaching This Verse
Three‑point outline
- God works through broken family situations. Sheshan had no sons, a dead end. Yet the Chronicler does not hide the problem. God's grace meets human limitation.
- God includes outsiders. Jarha was an Egyptian, a foreigner and a servant. His marriage to Sheshan's daughter brought him into the covenant line. This foreshadows the inclusion of Gentiles.
- God's purposes continue through ordinary genealogies. Most names here appear nowhere else. Yet each one is part of the story that leads to David and ultimately to Christ.
Five‑point outline
- The crisis: Sheshan's lack of sons threatens his family line.
- The solution: He marries his daughter to a trusted Egyptian servant.
- The result: A legitimate lineage that continues through Attai and beyond.
- The connection: Zabad, a descendant, becomes one of David's mighty warriors (1 Chr 11:41).
- The lesson: God's people are a gathered community, not a closed bloodline.
Illustration hooks
- A family business passed to a loyal employee who proved more faithful than a biological heir.
- Someone who converted to Christianity in adulthood and became a spiritual leader, tracing their “faith genealogy” back to that decision.
- A church directory listing dozens of names, most forgotten by history but each known to God.
Questions your congregation is asking
- Why does the Bible spend time on obscure names I can't pronounce?
- Does this passage mean it is okay to marry a non‑believer if they convert?
- How can I find meaning in a family history that feels ordinary or even broken?
Leading a Discussion
This short passage challenges assumptions about who belongs to God's people. Sheshan's lack of sons threatened his family line, but God provided through an unexpected path, giving his daughter to an Egyptian servant. As you discuss, consider how this story speaks to inclusion, trust in God's provision, and the value of every person in the covenant community.
Discussion questions
- What stands out to you about Sheshan's situation? How would you feel if you were in his place?
- Why do you think the Chronicler records the marriage to an Egyptian servant without any criticism or explanation?
- In what ways does Jarha's inclusion parallel the story of Abraham and Eliezer (Genesis 15)?
- This genealogy eventually produces Zabad, a mighty warrior of David (1 Chr 11:41). What does that connection tell you about how God uses ordinary people?
- How does this passage expand your understanding of who can be part of God's family?
- Are there people in your life whom you might be tempted to exclude but whom God might be including?
- What does this genealogy teach about trusting God with the future of your family or your legacy?
Word Study
The key original-language words in this verse. Select any word for its full lexicon entry — meaning, every occurrence in Scripture, and related words.
Cross-References
Source: Treasury of Scripture Knowledge (TSK, public domain)
| I Chronicles 11:41 | Uriah the Hittite, Zabad the son of Ahlai, |
Interlinear and lexical data from STEPBible (CC BY 4.0). Cross-reference data from OpenBible.info (CC BY 4.0). Commentaries are public domain.
For personal reflection
Read the devotional page — prayer, application, and "for families"
What the Commentators Say
6 public-domain commentaries, condensed into plain language.
Adam Clarke's Commentary Methodist/Wesleyan 1826
Clarke points to the Targum's reading that the slave Jarha was given both his freedom and Sheshan's daughter as a wife. His note emphasizes that the original verse implies a double act of liberation and marriage, not merely a transaction.
Cambridge Bible for Schools and Colleges Anglican 1880
The commentator notes that Sheshan giving his daughter to his servant Jarha was essentially making the servant his heir, a practice known in Eastern cultures. This mirrors Abraham's initial view of Eliezer his steward as his potential heir before Isaac's birth.
Gill's Exposition of the Bible Baptist 1748
Gill observes that Sheshan gave his daughter in marriage to Jarha, an Egyptian servant whom he first freed and who was a proselyte. This echoes Eliezer in Abraham's household, showing that even a foreign servant could be brought into the covenant family through marriage to an Israelite daughter.
Jamieson-Fausset-Brown Commentary Protestant 1871
JFB defends the marriage of Sheshan's daughter to his Egyptian servant Jarha as lawful, noting that such adoptions and marriages of foreign slaves are common in the East. The commentator argues Jarha likely became a Jewish proselyte, and as a foreign slave with no tribal inheritance, the union would not harm Israel's tribal structure.
Lange's Commentary Reformed 1857
Lange notes that the Chronicler's genealogy of Judah is not systematically ordered but rather a patchwork of fragmentary ancient records. He cautions against over-harmonizing duplicate names like
Wesley's Explanatory Notes Methodist/Wesleyan 1754
Wesley observes that an Israelite would not give his only daughter to a mere proselyte. He therefore concludes that Jarha must have been not only a convert to Judaism but also a man of considerable status and reputation to warrant such a match.