Rejecting document as there is no enabled Trigger registered

, ,
1

Hi All,

We are continuously getting the below errors in our production environment (6.x). But we could see the interfaces are working fine.

Error Details::

[44847]Rejecting document as there is no enabled Trigger registered: laf.frc.ASTER_3D.notification:notifInsert_ENT_BEXMONT_3DPublishDocument.
[44846]2013-10-03 13:08:59 CEST [ART.0116.3001E] Adapter Runtime (Notification): Notification error during execution of laf.frc.ASTER_3D.notification:notifInsert_ENT_BEXMONT_3D. Error: [ART.116.3010] Adapter Runtime (Notification): Error publishing notification laf.frc.ASTER_3D.notification:notifInsert_ENT_BEXMONT_3D. Error: Rejecting document as there is no enabled Trigger registered: laf.frc.ASTER_3D.notification:notifInsert_ENT_BEXMONT_3DPublishDocument.
[44845]2013-10-03 13:08:59 CEST [ISS.0098.0024C] No Trigger available for incoming Document laf.frc.ASTER_3D.notification:notifInsert_ENT_BEXMONT_3DPublishDocument. Rejecting Document
[44844]2013-10-03 13:08:59 CEST [ISS.0098.0082E] Unable to persist Document: laf.frc.ASTER_3D.notification:notifInsert_ENT_BEXMONT_3DPublishDocument to Document Store: laf.frc.ASTER_3D.trigger:tgrLaunchSalesOrderRequest_3D. Exception: com.wm.app.b2b.server.dispatcher.exceptions.DupeMsgException: com.wm.app.store.TSDupeMsgException: [BAT.0000.0032] duplicate message for store id laf.frc.ASTER_3D.trigger:tgrLaunchSalesOrderRequest_3D in parent container id TriggerConsumer

Can anybody faced such problem. Please share your inputs on how to get rid of the above alerts.

Best Regards,
Venkat.

2

What adapters and listeners you are running on the IS?

This seems to be related to pub/sub and the triggers related.I believe there was publishable document which is not being subscribed by the trigger may be you are no more using that publishable document? can you check more on the interface related to it?

HTH,
RMG

3

Hi RMG,

Thank you for your reply.

The problem was due to the environment migration to the different network. DNS resolver was failing to identify the server alias name.

Now the issue is resolved.

Steps followed:

  1. Created index in source DB.
  2. Changed the server name (FDNS) with the IP address in adapter connections.
  3. Restarted the IS.

Thank you and have a great time.

Best Regards,
Venkata Reddy K.

4

Glad to hear it got resolved now :smiley: