Legacy Knowledge Base
Published Sep. 10, 2025

Service "com.liferay.portal.kernel.messaging.DestinationFactory" is unavailable

Written By

Thanga Meena

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

  • What does this error mean? When it will occur?
2021-07-21 00: 02: 06.207 ERROR [ServerService Thread Pool - 111] [ServiceProxyFactory: 109] Service "com.liferay.portal.kernel.messaging.DestinationFactory" is unavailable in 60000 milliseconds while setting field " _destinationFactory " for class "com.liferay.portal.kernel.messaging.DestinationFactoryUtil", will retry ... 

021-07-22 06: 10: 23.096 ERROR [ServerService Thread Pool - 130] [ServiceProxyFactory: 109] Service "com.liferay. portal.kernel.messaging.DestinationFactory "is unavailable in 60000 milliseconds while setting field" _destinationFactory "for class" com.liferay.portal.kernel.messaging.DestinationFactoryUtil ", will retry ...

Environment

  • Liferay DXP 7.0

Resolution

  • The above error says that the Messagebus doesn't know about this destination to be created. Liferay now knows about the message you're sending and that you're interested to receive it, but Messagebus is looking for the destination.
  • Since this is tracing as an error rather than a warning, it's good to check the custom implementation to resolve it. For further assistance, connect with the developer expert or with our GS team as they will be providing the suggestions or the implementation approaches by reviewing your custom development.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base