ALC-WKS-007-040 error

[_Nith_]

I'm getting this error occasionally when rendering the PDF in the workspace.

If I just open the PDF and save it with some minor changes it works fine.

I am unable to find the root cause for this problem.

This happens for both 'Default Render ES Update 1' and for my 'Custom Renderer'.

Any help is appreciated.

Nith

[Jasmin_Charbonn]

This is problem with the render service.

I would recommend to enable record and playback to see where it fails. The log file, or the stack trace of the error would be useful.

Jasmin

[_Nith_]

I looked into the log file and seems to be no issues with the Render.

One thing i noticed is the bam.log is growing a lot from time to time. And there were few Out of Memory error present in the log file.

Is it possible to disable the BAM as we are not using the BAM dashboards for now.

Thanks,

Nith

[Jasmin_Charbonn]

If you get an ALC-WKS-007-040, you will have an error in the log. You would also be able to use Record and Playback to check where it fails. This has nothing to do with BAM.

That being said, you can remove the Lava_Adobe.ear file from the JBoss deploy folder if you're not planning on using BAM to free some memory and speed up the JBoss start time.

Jasmin

[_Nith_]

I had a look at the process recodings when i got the render issue.

In that only the first component (Read Resource from Repository) executed successfully (with no errors).

But all other activities in the sequence are not executed.

Nith

[_Nith_]

After increasing the default document disposal timeout value, this seems to be working fine.

Thank you Jasmin.

Nith

[Former Community Member · Accepted solution]

Hi Nith,

I have the same problem, can you show me how to increase the default document disposal timeout value.

Thanks in advance,

Han Dao

[_Nith_]

See the attached screenshot and markings.

Nith

[_Nith_]

This may not be the only solution for the 007-040 related issues.

Any errors in the render produces this error.

If you find any error(in the log file) similar to "Document is not available on the sending side anymore", you should use this solution (increasing document disposal timeout).

If you still face the problem, post your log file for an insight.

Nith.

[Balaji_Gurumurt]

Hi all,

          Am currently working in LC ES2. Am facing an issue of ALC-WKS-007-027 when i try to open the form in the worklist after submitting in the workspace. Can u help me here.?

Desc.: In Assign Task service --> Presentation & Data --> i use .xdp as an assest and Initial Task Data variable as xml.

          In Assign Task service --> Output --> Output Data variable is the document type.

I am not sure of the different variable types to be used.

Pls anyone help me of which variable and type of variable to be used so that this doesnt cause any issue in initiating the workflow.

Thanx in advance

Balaji

[_Nith_]

Did you try to leave the Output option blank and submit?

Nith

[Balaji_Gurumurt]

yes anand, i did try it.

Still the same scenario happens.

Thanks

Balaji

[Jasmin_Charbonn]

What about if you put the same xml variable for the output.

Jasmin

[Jasmin_Charbonn]

Can you post the server.log. It might contain more information on the error.

Jasmin

[Balaji_Gurumurt]

i have attached the server log along with the other issue faced :

     2010-01-21 21:20:27,190 ERROR [com.adobe.workflow.AWS] stalling action-instance: 122251 with message: ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.java:152)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor.java:140)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.DocumentPassivationInterceptor.intercept(DocumentPassivationInterceptor.java:53)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(TransactionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTransactionCMTAdapterBean.java:357)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(EjbTransactionCMTAdapterBean.java:227)
at sun.reflect.GeneratedMethodAccessor299.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

Hope this helps u to solve my issue.

Thanx

Balaji.

[AnkitY]

Hi,

The exception trace shows two distinct exceptions.

1. com.adobe.idp.taskmanager.dsc.client.task.TaskManagerException: CustomUI is specified, but no CustomUI Path is specified for Task: 9557

This exception is there because "Workspace User Interface" in Assign Task is set to custom, but no path has been provided. Please set it to default. Or if the requirement is of a custom UI, please provide the path.

2. 2010-01-21 21:09:17,868 WARN  [com.adobe.workflow.AWS] ALC-FUT-001-001: Unable to overwrite file c:\test\.

This is the same exception as discussed here (http://forums.adobe.com/message/2536189#2536189).

Thanks