Troubleshooting
Problem
The print queue frequently hangs, causing all subsequent jobs to remain in a queued state without progressing, resulting in a failure to print on the physical printer. The most likely cause for this behavior is the printer or the interconnecting network.
This might happen especially but not limited to large batches of print jobs. This intermittent issue causes the print queue to become unresponsive. Upon observation, the job appears to be downloaded into the printer's memory, as indicated by the running status and 100% completion in the queue. However, no actual printing takes place on the physical printer.
Cause
The cause of the problem can be attributed to the printer being a JetDirect attached printer. The functionality of this printer attachment relies heavily on the TCP connection being fully compliant with the TCP standard. AIX system remains unaware that the print job has finished. This occurs because the backend system lacks information about whether the print job was successfully processed, failed, or is still being processed by the printer.
Diagnosing The Problem
In the FIN_WAIT_2 state, one side of the connection (usually the server) has completed sending data by transmitting a FIN packet and has received an acknowledgment. However, it is still in a waiting state for the other side to finish its transmission.
Resolving The Problem
To conclude, it is crucial to consult with your network/firewall administrator regarding any potential network problems.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
13 May 2024
UID
ibm17150562