I have not seen this issue, so keen to see what responses you get. But out of interest, is your print agent running on the same host as the Application Server? Perhaps the App Server is loosing connection with the Print Agent host?
Hope the bounce of the system resolves your issue.
I have not seen this issue, so keen to see what responses you get. But out of interest, is your print agent running on the same host as the Application Server? Perhaps the App Server is loosing connection with the Print Agent host?
Hope the bounce of the system resolves your issue.
Hi Mike, we have a dedicated print server which is independent of the application server, so you could be onto something. Hopefully someone can give some insight of what to try next.
Hi @darren j turner,
Were you able to resolve this after the restart; if not have you checked the answers provided via following threads;
Thanks & Best Regards,
Yasas
Hi Yasas,
Thank you for this… One of the answers from Chanaka in the Print Job Waiting question has given me a number of things to check. I have checked all of his points and found errors for the specific print jobs in the J2EE under ifs-alerts. This has pointed to an error message:
Current database user:
IFSSYS
Error message:
ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package body "IFSAPP.PRINT_JOB_API" has been invalidated
ORA-04065: not executed, altered or dropped package body "IFSAPP.PRINT_JOB_API"
ORA-06508: PL/SQL: could not find program unit being called: "IFSAPP.PRINT_JOB_API"
ORA-06512: at "IFSAPP.PRINT_QUEUE_API", line 1658
ORA-06512: at "IFSAPP.PRINT_QUEUE_API", line 1670
ORA-06512: at line 1
SQL statement:
BEGIN IFSAPP.PRINT_QUEUE_API.START_JOB (
:1 );
END;
Bind parameters:
PrintJobId = 195067.0
The logs show the same error message shows for all of the 1st print jobs that are stuck.
I will document how I found this and report this to IFS Support.
Thanks all for your assistance.
Darren
IFS have now provided us with a patch that appears to have resolved this issue.
Hi @darren j turner,
Thanks for updating; could you please provide us with the Patch ID or solution id that you have received or simply the Case ID?
Thanks & Best Regards,
Yasas
Hi,
The reference we have is bug id 156423 and our IFS case ID G2269199.
Regards
Darren