Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Streamlining user types in Qlik Cloud capacity-based subscriptions: Read the Details
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] Error deploying route - Processing an attachment

Hello everybody,
I can't deploy my route on TAC , I receive an error 500: the call failed on the server:

However this route works correctly in Studio:


Logs:
2016-01-13 15:27:51 INFO  BusinessLogger  - ;'Creation of new EsbTask ';businessLog.esbtask.creation;


15:25:38,618 | WARN  | 1370468171-53392 | eclipse.jetty.server.HttpChannel  481 | 77 - org.eclipse.jetty.util - 9.2.10.v20150310 | Could not send response error 500: java.lang.IllegalStateException: Committed
15:25:38,634 | WARN  | 1370468171-53392 | rg.eclipse.jetty.server.Response  565 | 77 - org.eclipse.jetty.util - 9.2.10.v20150310 | Committed before 404 null15:25:38,634 | WARN  | 1370468171-53392 | pse.jetty.servlet.ServletHandler  628 | 77 - org.eclipse.jetty.util - 9.2.10.v20150310 | /system/console/bundlesjava.lang.IllegalStateException: Committed at


To see the whole post, download it here
Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hi,
The IllegalStateException WARN is another problem which is not related to your route deploy failed. could you please check the scenario below?
* build a kar file for your route from Studio using "build job"
* copy this kar file into Runtime/deploy folder
* check the Runtime/logs/tesb.log to see if there is any exceptions; check from Runtime console with "list" command to see if the installed bundles in the Active status.
Regards.

View solution in original post

2 Replies
Anonymous
Not applicable
Author

Hi,
The IllegalStateException WARN is another problem which is not related to your route deploy failed. could you please check the scenario below?
* build a kar file for your route from Studio using "build job"
* copy this kar file into Runtime/deploy folder
* check the Runtime/logs/tesb.log to see if there is any exceptions; check from Runtime console with "list" command to see if the installed bundles in the Active status.
Regards.
Anonymous
Not applicable
Author

Hi,
Hard deployment seems to resolve this issue
Thank you