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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
nfz11
Creator III
Creator III

Cannot open job due to java.lang.StackOverflowError error

 

This just started though I have been working on this job for months.  When I try to open the job to edit, I get an error.  Here is the start of the stack from the logs and I am also attaching the whole log file.

 

!SESSION 2019-06-27 01:34:54.859 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_162
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86_64

This is a continuation of log file C:\Talend-Studio-20180411_1414-V7.0.1\workspace\.metadata\.bak_2.log
Created Time: 2019-06-27 01:58:26.014

!ENTRY org.eclipse.ui 4 0 2019-06-27 01:58:26.014
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.StackOverflowError
	at org.eclipse.osgi.internal.framework.FilterImpl.compare(FilterImpl.java:549)
	at org.eclipse.osgi.internal.framework.FilterImpl.matches(FilterImpl.java:303)
	at org.eclipse.osgi.internal.container.Capabilities.matches(Capabilities.java:170)
	at org.eclipse.osgi.internal.container.Capabilities$NamespaceSet.match(Capabilities.java:158)
	at org.eclipse.osgi.internal.container.Capabilities$NamespaceSet.findCapabilities(Capabilities.java:140)
	at org.eclipse.osgi.internal.container.Capabilities.findCapabilities(Capabilities.java:264)
	at org.eclipse.osgi.container.ModuleDatabase.findCapabilities(ModuleDatabase.java:826)
	at org.eclipse.osgi.container.ModuleContainer$ContainerWiring.findProviders(ModuleContainer.java:1312)
	at org.eclipse.osgi.internal.framework.legacy.PackageAdminImpl.getBundles(PackageAdminImpl.java:181)
	at org.eclipse.core.internal.runtime.InternalPlatform.getBundle(InternalPlatform.java:182)
	at org.eclipse.core.runtime.Platform.getBundle(Platform.java:1398)
	at org.talend.core.PluginChecker.isPluginLoaded(PluginChecker.java:133)
	at org.talend.core.PluginChecker.isJobLetPluginLoaded(PluginChecker.java:183)
	at org.talend.designer.core.ui.editor.nodes.Node.isJoblet(Node.java:5175)
	at org.talend.designer.core.ui.editor.nodes.Node.getOutgoingConnections(Node.java:1694)
	at org.talend.core.model.utils.NodeUtil.getLinkedMergeInfo(NodeUtil.java:629)
	at org.talend.core.model.utils.NodeUtil.getLinkedMergeInfo(NodeUtil.java:645)
	at org.talend.core.model.utils.NodeUtil.getLinkedMergeInfo(NodeUtil.java:645)
	at org.talend.core.model.utils.NodeUtil.getLinkedMergeInfo(NodeUtil.java:645)
	at org.talend.core.model.utils.NodeUtil.getLinkedMergeInfo(NodeUtil.java:645)
... keeps logging above line

This thread describes the same issue but it is not clear if it is resolved:

https://community.talend.com/t5/Design-and-Development/Error-Stackoverflow/td-p/55949

 

I tried the following which did not work:

  • restarting Talend studio
  • Copying my job, the copied version did the same thing
  • Editing a joblet that the job uses
  • building the job from the context menu

 

Other jobs open fine.  This seemed to happen after I dropped a tLogRow into my flow.  Also, tonight is the first time I uploaded and ran this job in the cloud.  I ran it both in the cloud and locally successfully a few times after uploading to the cloud.

 

I am on Talend 7.0 and Java 8

Talend-Studio-20180411_1414-V7.0.1

Java jre1.8.0_162

 

Please help, thanks.

 

Labels (5)
1 Solution

Accepted Solutions
nfz11
Creator III
Creator III
Author

This was fixed with patch TPS-3242 in support case 00141714.

View solution in original post

3 Replies
Anonymous
Not applicable

Hello,

Are you using talend subscription solution V 7? Does this issue only repro on your specific job? Are there any detailed steps for us to reproduce your issue in V 7 from our end?

Best regards

Sabrina

nfz11
Creator III
Creator III
Author

This was fixed with patch TPS-3242 in support case 00141714.

Anonymous
Not applicable

Hello,


@nfz11 wrote:

This was fixed with patch TPS-3242 in support case 00141714.


Thanks for letting us know the patch id and support case id.

Best regards

Sabrina