Skip to main content

Print Jobs remains in Print Manager Window in waiting state without processing


Crystal operational reports are sending automatically as background jobs to process, saying it takes time
Then all Print jobs in the Print Manager window remains in the  Waiting state and they are not getting processed 

There are no errors in Oralce Alert log.
But in reporting pods, there are few errors,

In ifsapp-reporting pod,

{"event.module":"liberty_message","host":"ifsapp-reporting-6dfbfccd68-pcfdx","ibm_userDir":"\/opt\/ifs\/wlp\/usr\/","ibm_serverName":"defaultServer","message":" CWSIP0291W: An attempt to send a message to exception destination _SYSTEM.Exception.Destination on messaging engine defaultME failed due to the following : com.ibm.ws.sib.processor.exceptions.SIMPLimitExceededException: CWSIK0025E: The destination _SYSTEM.Exception.Destination on messaging engine defaultME is not available because the high limit for the number of messages for this destination has already been reached.","ibm_threadId":"00041708","_timestamp":"2024-06-13T06:28:54.264+0000","module":"com.ibm.ws.sib.utils.ras.SibMessage","log.level":"WARNING","event.sequence":"1718260134264_00000000C14E5"}


In ifsapp-reporting-cr pod,

m    26.818012s]  INFO ThreadId(01) inbound:server{port=8080}:rescue{client.addr=10.1.1.18:37702}: linkerd_app_core::errors::respond: Request failed error=error trying to connect: Connection refused (os error 111) error.sources=rConnection refused (os error 111)]

This issue comes after around 2 hours from starting the IFS Cloud 23R1 SU5. Then we cannot print reports. So then we needs to restart ifsapp-reporting-cr pod to start previewing reports. Again after few hours same issue arise.

Any solution please?

reporting pod log files attached


Reply