Print jobs keep being canceled

Question

I don't understand why my print job keeps being canceled. Could someone explain to me what I'm doing wrong? I tried making it a separate thread, but that doesn't work either.
/*used to print out reports*/
class printer implements Runnable{
     String filename;
     public printer(String theFile){
          filename = theFile;
     public void run(){
          try{
               PrintRequestAttributeSet pras =
               new HashPrintRequestAttributeSet();
               DocFlavor flavor = DocFlavor.INPUT_STREAM.PNG;
               PrintService printService[] =
               PrintServiceLookup.lookupPrintServices(flavor, pras);
               PrintService defaultService = PrintServiceLookup.lookupDefaultPrintService();
               PrintService service = ServiceUI.printDialog(null, 200, 200,
               printService, defaultService, flavor, pras);
               if (service != null) {
                    DocPrintJob job = service.createPrintJob();
                    FileInputStream fis = new FileInputStream(filename);
                    DocAttributeSet das = new HashDocAttributeSet();
                    Doc doc = new SimpleDoc(fis, flavor, das);
                    job.print(doc, pras);
                    /*wait for the damn print to finish!*/
          }catch(Exception e){JOptionPane.showMessageDialog(new JFrame(), "Error: "+e);}
}

Answer 1

Hello Kevin,
To determine why the spooler is stopping we need to look at the cups error log. This is located in the Console application. With it open, click on the Logs icon and then expand the /var/log entry. Then expand the cups entry. Under here you will see the error_log. The error will be shown with an E to the left and show what process failed. To determine what that process was look back up the log for the process ID (PID) for that print job. It will probably show a filter or plugin that is stopping the print.
Now the repair permissions is usually enough to fix this. But sometimes you need to do this after booting from the OS X disc and running the Disk Utility from here so that the cups daemon hasn't started.
If that doesn't help then look at trying Fixamac's Printer Setup Repair utility and/or running the Intel Combo updater.
Paul