Web service not working when deployed to ESB server, runs fine locally..

[Anonymous]

Hi all,

I've created a fairly simple web service job, which runs perfectly locally. I'm having some issues when deploying this to our ESB server. 

This job should only connect to our salesforce organization, run a SOQL query (which only returns 1 result), and return a 200 response code. I'm not even trying to do any mappings yet.

I'm getting error messages when I'm trying to hit this endpoint using postman, the first time I send a request I get;

and every time thereafter I get;

I've added an additional route that just returns "hello world" which works perfectly from the ESB server. The Salesforce component seems to be causing an issue, If I remove the salesforce component, then it successfully hits the response component

tJava_2 is empty placeholder so I can connect the Salesforce component

Any ideas would be great as I'm very quickly running out of things to try. I'm currently using Talend Open Studio 7.2.1

[Anonymous]

Could you copy and paste the errors as text rather than as screenshots. I'll take a look at the current jiras if you can do this. It is quite time consuming and prone to typing errors when trying to copy the text from an image

[Anonymous]

Hi Richard,

As below..

loader constraint violation in interface itable initialization: when resolving method "org.talend.daikon.i18n.TranslatableImpl.setI18nMessageFormatter(Lorg/talend/daikon/i18n/I18nMessages;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, org/talend/daikon/properties/property/Property, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for interface org/talend/daikon/i18n/Translatable have different Class objects for the type org/talend/daikon/i18n/I18nMessages used in the signature

Could not initialize class org.talend.components.api.component.ComponentDefinition

Thanks

[Anonymous]

Thanks for this. I have searched and not found a relevant bug. Therefore I have raised one. You can see it here: https://jira.talendforge.org/browse/TESB-27304?filter=-2

[Anonymous]

Thanks Richard.

Is there any kind of ETA for a developer to look in to this?

[Anonymous]

Recently I've been getting a couple of days turnaround for an initial response. In many cases this has been with a workaround or an indication that it is being worked on for a new release. However R&D are pretty busy at the moment, so I really can't make any promises unfortunately. Voting for Jiras tends to get some attention, so if you sign in to Jira and vote for it, it might help.As an "off the top of my head" workaround, you could try wrapping the Salesforce part of the service into a subjob (using a tRunJob). That *might* get a different response. However, as I said, that is just something that I would try as a temporary measure

[Anonymous]

Hi Richard,

Replacing the Salesforce component with a tRunJob just seems to create more problems. I moved the salesforce component it to its own job (tSalesforceConnection -> tSalesforceInput -> tLogRow) and tried to hit the end point, it errored (below). 

Unresolved compilation problems: 
	The type org.apache.avro.generic.IndexedRecord cannot be resolved. It is indirectly referenced from required .class files
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components.salesforce.tsalesforceinput.TSalesforceInputProperties cannot be resolved to a type
	org.talend.components.salesforce.SalesforceConnectionProperties cannot be resolved to a variable
	org.talend.components.salesforce.SalesforceConnectionProperties cannot be resolved to a variable
	org.apache.avro cannot be resolved to a type
	org.talend.components.api.properties cannot be resolved to a variable
	org.talend.daikon.properties cannot be resolved to a type
	org.talend.daikon.properties cannot be resolved to a type
	org.talend.components.api.properties cannot be resolved to a variable
	org.talend.daikon.properties cannot be resolved to a type
	org.talend.daikon.properties cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components.api.component.ConnectorTopology cannot be resolved to a type
	org.talend.daikon.runtime cannot be resolved to a type
	org.talend.components.api.component.runtime.ExecutionEngine cannot be resolved to a variable
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.daikon.properties cannot be resolved to a type
	org.talend.daikon.properties.ValidationResult cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.daikon.properties cannot be resolved to a type
	org.talend.daikon.properties.ValidationResult cannot be resolved to a variable
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.apache.avro cannot be resolved to a type
	org.talend.daikon.avro cannot be resolved to a type
	org.apache.avro.generic.IndexedRecord cannot be resolved to a type
	org.talend.daikon.avro cannot be resolved to a type
	org.apache.avro.generic.IndexedRecord cannot be resolved to a type
	org.talend.daikon.avro cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components.api.component.ComponentDefinition cannot be resolved to a type
	org.talend.components.api.component.ComponentDefinition cannot be resolved to a variable
	org.talend.components.api.component.ComponentDefinition cannot be resolved to a variable
	org.talend.components.api.component.ComponentDefinition cannot be resolved to a variable
	Reader cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	org.talend.components cannot be resolved to a type
	SharedConnectionsPool cannot be resolved to a type

Talend doesn't seem to catch this error either, as the job stopped itself, but seems to think its still running.. "unable to start job because something is already running on port 8090". Closing Talend Studio doesn't resolve this either, as if you restart the studio and try to run the job I get..

I'm guessing there's a process somewhere that needs ending somewhere.. managed to resolve it by restarting my machine but now I'm in exactly the same spot where I have to restart again... 

Hopefully R&D won't take too long to come back to us

[Anonymous]

Sorry that didn't work. It was the first thing I would have tried. If you vote for this Jira, hopefully we will get a response soon

[Anonymous]

No problem, thanks for the suggestion.

I've voted and watched the issue on Jira.

Interestingly, tRunJob seems to produce a similar error to the second error message that the ESB server provides us with which might be useful for debugging

[TRF]

Strange... I have services built with 7.2 subscription using salesforce and no problem to signal.