Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
AS suggested i have changed the TOS_DI-win-x86_64 file values as below
-vmargs
-Xms4096m
-Xmx8192m
i have tried 1024/2048 , 2048/4096 , 4096/8192 but still i am getting the same problem
Logs i am getting from below location
C:\talend\TOS_DI-Win32-20170510_1410-V6.4.0\workspace\.metadata
!ENTRY org.eclipse.ui 4 0 2017-06-14 12:27:08.104
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.OutOfMemoryError: Java heap space
at org.apache.xmlbeans.impl.store.Cur.createElementXobj(Cur.java:257)
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.startElement(Cur.java:2992)
at org.apache.xmlbeans.impl.store.Locale.loadNode(Locale.java:1413)
at org.apache.xmlbeans.impl.store.Locale.loadNodeChildren(Locale.java:1396)
at org.apache.xmlbeans.impl.store.Locale.loadNode(Locale.java:1438)
at org.apache.xmlbeans.impl.store.Locale.loadNodeChildren(Locale.java:1396)
at org.apache.xmlbeans.impl.store.Locale.loadNode(Locale.java:1438)
at org.apache.xmlbeans.impl.store.Locale.loadNodeChildren(Locale.java:1396)
at org.apache.xmlbeans.impl.store.Locale.loadNode(Locale.java:1438)
at org.apache.xmlbeans.impl.store.Locale.loadNodeChildren(Locale.java:1396)
at org.apache.xmlbeans.impl.store.Locale.loadNode(Locale.java:1438)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1378)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1363)
at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:370)
at org.apache.poi.POIXMLTypeLoader.parse(POIXMLTypeLoader.java:144)
at org.openxmlformats.schemas.spreadsheetml.x2006.main.WorksheetDocument$Factory.parse(Unknown Source)
at org.apache.poi.xssf.usermodel.XSSFSheet.read(XSSFSheet.java:183)
at org.apache.poi.xssf.usermodel.XSSFSheet.onDocumentRead(XSSFSheet.java:175)
at org.apache.poi.xssf.usermodel.XSSFWorkbook.parseSheet(XSSFWorkbook.java:438)
at org.apache.poi.xssf.usermodel.XSSFWorkbook.onDocumentRead(XSSFWorkbook.java:403)
at org.apache.poi.POIXMLDocument.load(POIXMLDocument.java:190)
at org.apache.poi.xssf.usermodel.XSSFWorkbook.<init>(XSSFWorkbook.java:266)
at org.talend.repository.ui.wizards.metadata.connection.files.excel.ExcelReader.init(ExcelReader.java:144)
at org.talend.repository.ui.wizards.metadata.connection.files.excel.ExcelReader.<init>(ExcelReader.java:93)
at org.talend.repository.ui.wizards.metadata.connection.files.excel.ExcelFileStep1Form.viewExcelFile(ExcelFileStep1Form.java:629)
at org.talend.repository.ui.wizards.metadata.connection.files.excel.ExcelFileStep1Form.access$5(ExcelFileStep1Form.java:604)
at org.talend.repository.ui.wizards.metadata.connection.files.excel.ExcelFileStep1Form$7.modifyText(ExcelFileStep1Form.java:481)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
It's not the JVM settings for the Studio you need to worry about so much here, it is the JVM settings for the job. This will show yo where you need to set these (http://garpitmzn.blogspot.co.uk/2013/08/talend-modify-jvm-arguments-for-job.html). By the way, there is no need to set the Xms to such a high value. The Xms is the initial memory allocation pool. This is meant to grow. Upping this will just immediately reserve that memory instead of letting it grow as it is needed.
Hi I have changed the VM argument value as -Xms1024M and -Xmx2048M but still i was getting the same problem.
So you have changed the VM arguments as per the link I posted and ticked the "Use specific JVM arguments" on the "Advanced settings" tab on the "Run" tab of the job? You are running the job from the Studio, right?
If the answer is yes to the above, then how big is your Excel file?
Ah I see, so when you are creating the metadata?
Sorry, I misunderstood. It sounds like a bug. If the file is not that big I would recommend manually creating the metadata for it (build the schema manually) and use that. Are you using the open source edition or the enterprise edition and what version? If you have a support contract, I would raise this.
Hello,
Does this issue only occur when you upload a large excel? Is it Ok with you when upload a simple excel? Could you try to use V 6.3 to see if this issue repro?
Best regards
Sabrina