Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

JBoss Datasource Error Causing Production Outages

Written By

Kenny Back

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How to articles!

While we make every effort to ensure this Knowledge Base is accurate,it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • We had two production outages today and observed the following error:
ERROR [liferay/search_writer/SYSTEM_ENGINE-7][ElasticsearchIndexWriter:143] 
java.lang.IllegalStateException: Future got interrupted

Caused by: javax.resource.ResourceException: IJ000470: 
You are trying to use a connection factory that has been shut down: 
java:jboss/datasources/LiferayPool at 
org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection
(AbstractConnectionManager.java:777)
at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)   
... 94 more 

Environment

  • DXP 7.2

Resolution

Additional Information

  • Generally speaking datasource connection types typically have capabilities to test and discard connections that have failed. Based on this stacktrace snippet it looks to be using a JNDI defined connection using a JBoss connection pool so in this situation you may want to configure there to test a connection before handing it to an application for use. However, given JBoss is a third party software we are again just diagnosing broadly here for this is dependent on specific implementation as well. It is hard to say then concretely as we suspect this also isn’t testing that someone would manually do, so it’s again likely a configuration on the pool to have it test and verify connections before handing them out.

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?