---
id: MAXCONNECT-PAIN-006
title: Legacy custom Java can fail in MAS deployment pods
type: PAIN
state: red
area: A-problem-market
purpose: notebooklm-tier2-decomposition
priority: A
work_kind: A
provenance: research
confidence: medium
triangulated: false
engagement: maxconnect
sources:
- uri: file://notebooklm/answers/20260611T200650Z-07-community-opportunity.md
role: supporting
- uri: file://notebooklm/answers/20260611T200650Z-03-migration-risks.md
role: supporting
relates_to: []
feeds_atoms: []
open_questions: []
needs_validation:
- Validate with technical practitioners before external publication.
resolution_log:
- 2026-06-12: Decomposed from broad NotebookLM synthesis into pack-grade atom for Max Connect Discovery.
module:
---
Community synthesis says admins porting legacy 7.6 custom Java classes to MAS9 can encounter configdb and maxinst pod deployment failures. This ties to the broader customization archive migration burden.