Waiting for GP

Dear all,

we have the issue that in the MWO applications (Windows) the MWO is stating “Waiting for Server”. In the Logs the following is showing:

What could be the reason for IFS Applications and the MWO Group Push to fail?

Please advice.

 

T&R

In addition it would be great to have the information, where to look in more detail for errors and logs. Since the MWO and IFS are somewhat quiete about that.

Hi @NEJANO. The issue is, that it worked already once. Do you know if security certificates for connections between MWS, TAS and IFS might cause such issues?

You can read about Grouped Push here:

Mobile Framework Synchronization Guide (ifs.com)

Synchronization Rules (ifs.com)

Grouped Push Transaction Queue (ifs.com)

Cheers

James

Check that all DB Process and Batch Queues are active and running.

Also check that the GP User has been granted access to the Sites you want to see data for and that you haven’t just granted all sites for to the GP user

GP User doesn’t need any access rights. 

Any errors shown in any of the logs?

You could try increase the log levels of the Grouped Push process and see if anything gets reported in the Grouped Push logs

Started a new initialization and this is the outcome

Ok, so here are the Traces

Hi

If you see ‘Init waiting for GP’ for longer period for device app, then it could be because of large no of data in the GP entities due to the missing data filters (permission Set Filters). 

Once you increase the log level to INFO for both (batch and Init under GP application parameters), please search for below trace lines to find what’s going on with the GP Init database process: 

• Search for the GP trace for below text ‘INIT sub-task has been running in%’. This will tell if init transaction is stuck and the time in seconds. 
• In case init transaction is stuck then need to kill that. You can do this after apply filters to users. Otherwise it create another init session and again goes to the same stage. Search for the GP trace for the text ‘Started background job %‘ this will give you the Oracle job id and DBA need to kill it. 

Here is the Output of the Grouped Push Transaction Traces.

In the file you can find this

INIT sub-task has been running in [5088419.009] seconds and has not finished yet. Nothing to accept.

But I can’t find the according background job. So I will try to set filters as you said. Never done this before though.

EDIT:

User Filter looks like this at the moment. I didn’t configure anything beforehand.
Looks that someone has already done changes.

Hi

as the environment is hosted by IFS Managed Cloud, I don’t have access to TAS or DB directly.

I will try to set up Permission Filter with a colleague in April and will try to get the DB jobs killed.

Thanks for your feedback so far!