'Application Monitoring' 'PL/SQL Access Provider configuration test' (`Plsqlap_Server_API.Ping_Result__`) returns 0 instead of the expected 1, with a debug log showing a timeout waiting on an AQ (Advanced Queuing) response — even though the connection string, ACL, and SSL setup all check out and the rest of the application works fine (apart from Business Reporter report ordering). What changed to cause an AQ-based timeout here specifically?

Question

'Application Monitoring' > 'PL/SQL Access Provider configuration test' (`Plsqlap_Server_API.Ping_Result__`) returns 0 instead of the expected 1, with a debug log showing a timeout waiting on an AQ (Advanced Queuing) response — even though the connection string, ACL, and SSL setup all check out and the rest of the application works fine (apart from Business Reporter report ordering). What changed to cause an AQ-based timeout here specifically?

Accepted Answer

From Apps10 UPD5 onward, the PL/SQL Access Provider mechanism (used by Business Reporter connectivity) changed from making direct HTTP calls from the database to instead using JMS messages processed by a batch processor on the main server, routed through an Oracle Advanced Queue (commonly named something like BATCH_PROC_QUEUE_MAIN). A ping timing out while waiting on that queue's response points to that specific Oracle queue not being properly enabled for enqueuing. In IFS EE's navigator, open the 'Oracle Queues' screen, locate that queue, and try right-clicking to stop and then restart it — if the problem persists, also try purging the queue's underlying table before restarting it.

Answer