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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Port 80 already in use

When I create a Service, assign a job for it, close Talend and re-open I get the following error when I try t run the Job: 

 

Starting job JobServicePortType_JobServiceOperation at 09:26 05/11/2017.

[statistics] connecting to socket on port 3703
[statistics] connected
Exception in thread "Thread-1" java.lang.IllegalArgumentException: Cannot start provider with uri: . Port 80 already in use.
at sandbox.jobserviceporttype_jobserviceoperation_0_1.JobServicePortType_JobServiceOperation$HandlerThread_tESBProviderRequest_1.run(JobServicePortType_JobServiceOperation.java:745)
sudo lsof -i -n -P | grep TCP | grep :80

I've searched for other processes that might be holding port 80 but I never find anything. I've even tried deleting the Service and Job and then rebooting.

 

 

Labels (3)
5 Replies
Anonymous
Not applicable
Author

Hello,

Is your port 80 busying by other server?

If your port 80 is free, it seems that the WSDL under Services was not recognized by Talend.

Could you please try this following to see if it works?

1. Delete the used WSDL under "Services"
2. Delete the whole Job.
3. Restart Talend Studio
4. Create WSDL under "Services"
5. Create a new Job again

Feel free to let us know if it is OK with you.

Best regards

Sabrina

 

Anonymous
Not applicable
Author

Thanks, this works but only until the next time it happens again. Is There a reason why it's not being recognized as a Service by Talend?

Anonymous
Not applicable
Author

Hello,

So far, we cannot address this issue from description. Are you using talend subscription solution?

Best regards

Sabrina

Anonymous
Not applicable
Author

I cannot reproduce this since i decided to spin up a Windows 10 VM and use it instead. It seems that the Windows build is stable compared to the macOS build. We can close this up. thanks for the replay.

Anonymous
Not applicable
Author

Hi,

Feel free to let us know if this issue still repro on your side.

Best regards

Sabrina