axiom-impl-1.2.21.jar is old and unsupported. Axis2 2.0 ships with Axiom 2.0.
That being said, the stack trace indicates a problem with lotus higher up and the Axiom error is perhaps a side effect. These things are often temporary and it wouldn't surprise if the problem no longer happens. On Sun, Jan 25, 2026 at 3:02 AM Boppana, Gnanadev (Contractor) via java-user <[email protected]> wrote: > > > Hi Team, > > > > Domino Java agent fails with Axiom meta factory error: *“No meta factory > found for feature 'default'”*, indicating axiom-impl.jar not found in > classpath or META-INF/axiom.xml not readable. > > > > We are running a *Java agent* (Notes/Domino web service agent using > Axis2/Axiom) on: > > - *Domino version:* Domino 14 FP5 > - *Domino Java:* Java 17 (Domino Java 17) > - *Classpath base:* C:\Domino\ndext > - *Axiom jar present/version:* axiom-impl-1.2.21 (in Dev/Pre-Prod) > > The agent fails at runtime with the following error: > > > > No meta factory found for feature 'default'; this usually means that > axiom-impl.jar is not in the classpath or that the META-INF/axiom.xml > resource can't be read > > at WebServiceClient.buildRequest(Unknown Source) > > at JavaAgent.NotesMain(Unknown Source) > > at lotus.domino.AgentBase.runNotes(Unknown Source) > > at lotus.domino.NotesThread.run(Unknown Source) > > > > *Troubleshooting Done * > > - Verified axiom-impl-1.2.21.jar exists under C:\Domino\ndext. > - Confirmed agent fails consistently. > - Suspect classpath/classloader issue or jar conflict under Domino > Java agent runtime. > > > > Note :- This agent worked perfectly till 11th December 2025.No changes > made to code , but Windows server was patched and rebooted on December 11, > 2025 (KB5071544) . > > > > Could you please help us in resolving this issue. > > > > Regards > > Gnanadev Boppana > > CFP Application Support|IBM - Chennai > > Email Id: [email protected] > > Mobile : (+91) 9789094562 > > > > Public >
