Can you please provide the stacktrace?

-- 

Best regards,

Benoit TELLIER

General manager of Linagora VIETNAM.
Product owner for Twake-Mail product.
Chairman of the Apache James project.

Mail: [email protected]
Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)


Le janv. 16, 2026 8:54 PM, de Scoopta <[email protected]>I'm coming from 
3.7.5 to 3.9.0 and I saw the mention of      reindexing in the upgrade info (on 
top of the server not starting      until I deleted my lucene folder in var). I 
didn't realize there      was a reindexall command, I tried running it but got 
this error      alongside a stack trace.

    Trampoline must not be defined by the bootstrap classloader

    On 1/16/26 12:49 AM, Benoit TELLIER      wrote:
                    Please check the CLI

        https://james.apache.org/server/manage-cli.html#Re-indexing
        
        Can you please provide the version you were using prior and afer        
the upgrade

        In practice if adoptiong 3.9.x from 3.8.x the reindex is wise as        
we went from Lucene 3.6.2 to 10.2.1 (!)      -- 

        Best regards,

        Benoit TELLIER

        General manager of Linagora VIETNAM.
        Product owner for Twake-Mail product.
        Chairman of the Apache James project.

        Mail: [email protected]
        Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)


            Le janv. 16, 2026        4:52 AM, de Scoopta Via Server-user        
<[email protected]>      I        recently upgraded to the latest 
version of james and needed to        delete
        and reindex lucene, I'm using the spring wiring which from        
reading the
        documentation doesn't appear to support the REST API to trigger        a
        reindex, is reindexing lucene necessary or is deleting it        enough?
        Additionally if reindexing it is important is there any way to        
do this
        with spring?


---------------------------------------------------------------------
        To unsubscribe, e-mail: [email protected]
        For additional commands, e-mail: [email protected]


            

Reply via email to