Infor WMS 10.3 Build 30240 – EpiDataException when modifying an ASN

FerHue97

Hello,

I am working with Infor WMS 10.3, Build 30240 (on-premise) and I am experiencing an issue when trying to modify a specific ASN/Receipt.

The application displays the following error:

Uncaught Exception running extension {0}

I also see the following exception in the log:

java.lang.NullPointerException
    at com.epiphany.shr.data.dp.sql.SQLDPConnectionFactory.getConnection(SQLDPConnectionFactory.java:153)
    at com.epiphany.shr.data.dp.sql.SQLDPConnectionFactory.getConnection(SQLDPConnectionFactory.java:86)
    at com.epiphany.shr.data.dm.UnitOfWorkImpl.getConnection(UnitOfWorkImpl.java:2644)
    at com.epiphany.shr.data.dm.UnitOfWorkImpl.fetchRecords(UnitOfWorkImpl.java:1278)
    at com.epiphany.shr.data.dm.UnitOfWorkImpl.fetchRecordsForQueryResultCollection(UnitOfWorkImpl.java:929)
    at com.epiphany.shr.data.dm.QueryResultCollection.getMoreRecords(QueryResultCollection.java:71)
    at com.epiphany.shr.data.dm.RecordCollection.getMoreRecords(RecordCollection.java:346)
    at com.epiphany.shr.data.dm.RecordCollection.size(RecordCollection.java:186)
    at com.epiphany.shr.data.dm.BioCollectionImpl.size(BioCollectionImpl.java:153)
    at com.epiphany.shr.data.dm.AbstractBioCollectionImpl.size(AbstractBioCollectionImpl.java:85)
    at com.epiphany.shr.sso.service.useraudit.helper.UserAuditHandler.codelkupCheck(UserAuditHandler.java:1089)
    at com.epiphany.shr.sso.service.useraudit.ejb.EpnyUserAuditServiceBean.setLogoutData(EpnyUserAuditServiceBean.java:129)

The issue occurs with one ASN, while another ASN with apparently similar information can be modified successfully.

Geetha Nathan

this is from Gemini AI:

• Inspect SQLDPConnectionFactory.java (Line 153): Look at the exact line in your source code to see which variable is null (e.g., a DataSource, a configuration object, or a factory instance).
• Check Configuration Files: Ensure that database connection properties are properly defined in your environment's configuration files (e.g., persistence.xml, application.properties, or JNDI server configuration).
• Verify Bean Initialization / Injection: Confirm that dependency injection (like @Autowired or @Resource ) for the data source or connection factory is working correctly and not returning null.
• Review Logout Lifecycle Order: Ensure the user audit service executes before the HTTP session or database contexts are destroyed during the logout sequence.

I don't know anything further. Thanks. Hope your issue will be resolved soon.