Windows update breaks Output service on JBoss

JBossWe saw an interesting issue arise the other day where a Windows Server update caused a Production server instance to fail during a render operation. Both the Development and Test instances were patched successfully and no issues were seen in those environments.

Server was AEM Forms 6.1 SP1 on JBoss

The errors looked like this (extra lines removed for brevity):

16:57:35,336 WARN [com.adobe.formServer.docservice.LifeCycleImpl] (IDPSchedulerService_Worker-1) ALC-OUT-002-701: ServiceUtil already inititalized with service: OutputService. Aborting cache re-initialization.
16:57:35,575 INFO [com.adobe.output.config.OutputConfigImpl] (IDPSchedulerService_Worker-1) FSC008: Using the database to access and persist configuration properties.
16:57:36,057 INFO [com.adobe.service.ProcessResource] (IDPSchedulerService_Worker-1) ALC-BMC-001-505: Service XMLFormService: Starting native process with command line "D:\\Adobe\\Adobe_Experience_Manager_forms\\jboss\\standalone\\svcnative\\XMLFormService\\bin\\XMLForm.exe" -MyPath D:\Adobe\Adobe_Experience_Manager_forms\jboss\standalone\svcnative\XMLFormService -IOR IOR:000000000000002249444C3A636F6D2F61646F62652F736572766963652F4D616E616765723A312E300000000000000100000000000000BC000102000000000F31302E3133312E3131322E31393200000DC8000000000018383136363634303033362F42522D312F0100000000000000000000040000000000000008000000004A4143000000000100000020000000000501000100000001000100010001010900000002050100010001010000000014000000080000001A00000DC90000002100000030000000000000000100000000000000220000000000000000000000000000000000000000000000000000000000000000 -AppServer jboss
16:57:37,767 INFO [com.adobe.service.ProcessResource] (RequestProcessor-5) ALC-BMC-001-508: Service XMLFormService: Native process PID = 4476
16:57:37,915 WARN [com.adobe.service.J2EEConnectionFactoryManagerPeerImpl] (IDPSchedulerService_Worker-1) Service: XMLFormService resource: ProcessResource@6fb137ba(name=XMLForm.exe,pid=4476) could not schedule an interrupt for transaction: TransactionImple < ac, BasicAction: 0:ffff0a8370c0:-2618bc79:57ff2163:30dd status: ActionStatus.RUNNING > because excessive time was spent waiting in queue. Supplied timeout: 0s, Wait adjustment: 1s, Effective timeout: -1s.
16:57:37,956 INFO [com.adobe.document.XMLFormService] (RequestProcessor-5) ALC-XTG-101-000: UseProximity=false
16:57:38,380 ERROR [com.adobe.formServer.PA.XMLFormAgentWrapper] (IDPSchedulerService_Worker-1) ALC-OUT-002-013: XMLFormFactory, PAexecute failure: "java.lang.NullPointerException"
16:57:38,386 ERROR [stderr] (IDPSchedulerService_Worker-1) com.adobe.printSubmitter.PrintException: java.lang.NullPointerException in com.adobe.livecycle.formsservice.exception.RenderFormException, cause: java.lang.NullPointerException in com.adobe.livecycle.formsservice.exception.FormServerException
16:57:38,387 ERROR [stderr] (IDPSchedulerService_Worker-1) at com.adobe.printSubmitter.util.FormSubmitter.submit(FormSubmitter.java:211)
...
16:57:38,488 ERROR [stderr] (IDPSchedulerService_Worker-1) ... 300 more
16:57:38,490 ERROR [stderr] (IDPSchedulerService_Worker-1) Caused by: com.adobe.livecycle.formsservice.exception.FormServerException: java.lang.NullPointerException
...
16:57:38,492 ERROR [stderr] (IDPSchedulerService_Worker-1) ... 303 more
16:57:38,494 ERROR [stderr] (IDPSchedulerService_Worker-1) Caused by: java.lang.NullPointerException
16:57:38,494 ERROR [stderr] (IDPSchedulerService_Worker-1) at com.adobe.formServer.PA.XMLFormAgentWrapper.doPAExecute(XMLFormAgentWrapper.java:429)
16:57:38,495 ERROR [stderr] (IDPSchedulerService_Worker-1) ... 308 more
16:57:38,507 ERROR [com.adobe.workflow.AWS] (IDPSchedulerService_Worker-1) An exception was thrown with name com.adobe.livecycle.output.exception.OutputException message:com.adobe.printSubmitter.PrintException: java.lang.NullPointerException in com.adobe.livecycle.formsservice.exception.RenderFormException, cause: java.lang.NullPointerException in com.adobe.livecycle.formsservice.exception.FormServerException while invoking service OutputService and operation generatePDFOutput2 and no fault routes were found to be configured.

Solution

Delete the following JBoss temporary directories:

  • [aem_forms_install_dir]\jboss\standalone\svccommon
  • [aem_forms_install_dir]\jboss\standalone\svcnative
  • [aem_forms_install_dir]\jboss\standalone\tmp
  • [aem_forms_TEMP_dir] (C:\Windows\Temp by default on Windows)
aemblog

Everything AEM aka CQ5 based on my experience listed here.

Adobe AEM The Right Way

Best practices, tips, and tricks for your Adobe AEM project

/home/bkondepudi

A WCM journey with Day/Adobe CQ

Technoracle (a.k.a. "Duane's World")

A multi-purpose toolkit for the Adobe LiveCycle and AEM Forms developer.

Adobe LiveCycle Blog

A multi-purpose toolkit for the Adobe LiveCycle and AEM Forms developer.

A multi-purpose toolkit for the Adobe LiveCycle and AEM Forms developer.

XFA@Mobile

A multi-purpose toolkit for the Adobe LiveCycle and AEM Forms developer.

Code Monkey

Ramblings of a Developer