According to the stack trace, the method throwing the error is:
[FATAL]: integrations_2.write_file_using_tac_excel_0_14.write_file_using_tac_excel - tFileOutputExcel_1 0
java.lang.ArrayIndexOutOfBoundsException: 0
at sun.font.CompositeFont.getSlotFont(CompositeFont.java:375)
Looking at the debug trace, the FONT parameter is empty:
[DEBUG]: integrations_2.write_file_using_tac_excel_0_14.write_file_using_tac_excel - tFileOutputExcel_1 - Parameters:VERSION_2007 = true | USESTREAM = false | FILENAME = "/tmp/test.xlsx" | SHEETNAME = "Data" | INCLUDEHEADER = true | APPEND_FILE = false | FIRST_CELL_Y_ABSOLUTE = false | FONT = | IS_ALL_AUTO_SZIE = false | AUTO_SZIE_SETTING = [{IS_AUTO_SIZE=false, SCHEMA_COLUMN=Name}, {IS_AUTO_SIZE=false, SCHEMA_COLUMN=newColumn}] | CREATE = true | FLUSHONROW = false | ADVANCED_SEPARATOR = false | ENCODING = "UTF-8" | DELETE_EMPTYFILE = true |
So, the sun.font.CompositeFont.getSlotFont method probably expects the FONT parameter to be defined before it is called. I don't have a copy of Talend available at the moment, but are there any parameters under the Advanced tab of the tFileOutputExcel component that might populate that parameter (I can't think of any, but worth a check)?
If not, I would consider raising this as a bug report with Talend; someone probably needs to look at the Java code that is generated, because my guess is that the FONT parameter is supposed to be populated by an internal method that the user has no direct control over. For some reason, that's not happening. Unfortunately, you probably won't have access to the internal methods to find the bug yourself, and even if you did, there's not much you can do other than exporting the code outside of Talend, fixing the error, then running it in a Java interpreter.
I hope this helps; if there's anything more I can do, please let me know.
