Integration Broker Messages Stuck in New State

by Apurva T. on March 30, 2014

in PeopleSoft Integration Broker

PeopleSoft Integration Broker is tricky and sometimes when issues arise, it can take you a long time to resolve the issues unless you troubleshoot issues in a logical and systematic way.

I will lay out the steps, which you should check. Following these steps will resolve your issue in 99% of the cases. I did not find any material available online, which can help you troubleshoot issue of integration broker messages in new state.

Let’s have a look:

Issue – PeopleSoft Integration Broker Messages Stay in New Status

  1. Check if PUBSUB enabled application server is not down.
  2. Verify that PUBSUB is enabled in psadmin.
  3. Check the status of the application server and verify that the following 6 programs are running (Fig. 2): PSBRKDSP.exe, PSBRKHND.exe, PSPUBDSP.exe, PSPUBHND.exe, PSSUBDSP.exe and PSSUBHND.exe
  4. Check the Domain status in Integration Broker -> Service Operations Monitor -> Administration ->  Domain Status : You should have domains which are Active. Update the status if they are inactive by using “All Domains Active”
  5. Check Domain status (as in Fig. 1) – It is possible that only one domain is configured for PUBSUB services and is set as a slave domain in psappsrv.cfg. It is also possible that all the domains are set as slave in case of multiple domains (picture below). A value of 0 will initialize the PUB/SUB servers in normal (Master) mode.
  6. You will need to bounce the appserver if you change the settings of Domain Slave Mode. Also, If domains change the status back to inactive after you manually update them to active – you should restart the pubsub enabled application servers.
  7. Check the Queue status in Integration Broker -> Service Operations Monitor -> Administration ->  Queue Status : The status of the queue should not be Paused. If it is paused, run it.
  8. Ping Node to verify that you get the Success (117,73) message. Do this ping node test for all the nodes, which are not processing the messages, including the default local node.
  9. Check if there are messages stuck in the following status: “Timeout” or “Started” or “Working” – if messages are in this status, it means that they are being submitted again and again to be processed. This causes “New” status queue to increase. Debug the reason why they are stuck in this state or cancel them to allow the new ones to be processed. Make sure that you can work on the cancelled ones later on.
  10. Bounce the PUBSUB enabled appserver if nothing works.
Also Read:  Cannot establish HTTP connection (158, 2842)

Click Here To Learn PeopleSoft Integration >>

both integration broker domains as slaveFig. 1 – Both domains are slave

 

integration broker servicesFig. 2 – Integration Broker programs

Click Here To Learn PeopleSoft Integration >>

{ 6 comments… read them below or add one }

Aravind September 16, 2014 at 1:28 am

cool article.Thanks.

Reply

Anh Nguyen January 7, 2015 at 3:53 pm

May I add in 1 more helpful solution: after a tools upgrade, we had AC on PT8.53.xx connected to HR 8.51.xx and FS on 8.52.xx; any of the above and boucing the app servers did not solve the issue. On GSC, found a suggestion to run HCM registry refresh, after clearing the caches, bouncing the servers. It worked, all NEW messages were processed; this was due to a higher version of tools (8.53.14) connecting to lower versions (8.52 and 8.51).
Enjoy.

Reply

Prashant January 8, 2015 at 10:11 am

Thanks Anh!

Reply

jigisha thakkar January 4, 2017 at 11:19 am

I’m in the exact situation you describe here. I am higher tools connecting to lower version all message are in New status. I’ve tried all the above suggestions and I think I may have to try a registry refresh and clearing caches. I’m not a sysadmin, so could you provide more details on how to do the refresh and also where to clear the pertinent caches on the servers? Thanks!!

Reply

Shan April 7, 2016 at 6:29 am

Great article, I am having a query. Is there a way to find the corresponding queue name, if we know the server name?

Reply

Swati Sharma August 3, 2016 at 5:07 am

Hi Apurva,

We are trying to run sync between HCM 9.2 and ELM 9.2 and facing the same problem i.e. messages are stuck into NEW status in Pub contract.

I have followed all your steps mentioned above and verified everything. But the issue still persists.

Could you please advice? It will be a great help.

Thanks

Reply

Leave a Comment

Previous post:

Next post: