We just upgraded from 11.3 to 11.6, and our mailbox reader services that use the logging_form parameter will not start up. We get an error that is bascially:
Failed to lookup the logging form 'FORMNAME'
There is always a corresponding error generated on the web server:
WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on component CustomisationServiceBean for method public abstract com.axiossystems.assyst.dto.customisation.custom.CustomEntityDefinitionDto[] com.axiossystems.assyst.ejb.customisation.CustomisationService.lookupCustomEntityDefinition(com.axiossystems.assyst.dto.SessionToken,com.axiossystems.assyst.lookupParameter.LookupParameter[],java.lang.String[],java.lang.Integer) throws com.axiossystems.assyst.exceptions.DAOException,com.axiossystems.assyst.exceptions.AuthorizationException: javax.ejb.EJBException: java.lang.ClassCastException
It looks like it’s some type of permissions issue, but I can’t figure out what it might be. I’ve tried:
- Checking Privilege Groups
- Checking CSGs
- Creating a Contact User for the mailbox user and DB/EJB login and gave it a license role with all features
- Checked that the form is added to a menu and is visible by default (and also visible to the alias set on the assyst user record for the mailbox reader login
- Tried a new form
- Tried a form name without spaces
- Tried a few different DB/EJB users and mailboxes that should have elevated privileges in assyst
- Tried changing the event_type parameter to “incident:”
None of that made any difference. If I comment out the logging_form parameter it works no problem and our other MBR services that don’t use a custom logging form work fine. But we have 2 MBR services configured this way, and neither work. Our mailboxes in our dev environment don’t use a custom logging form, but I was able to produce the error when dev as well when I added that param.
Any other suggestions on what to look at? I really can’t think of what it could be.
I did open a ticket with the help desk, but thought I would ask here as well.
