Error Port already in use java.net.BindException Address already in use: JVM_Bind

[Papademuchos]

I have a Talend Studio job with several Child jobs.  One of the child jobs is throwing an error ONLY when I run against the Remote Engine server.  It runs fine on localhost.  Up until now it was running fine even in the TMC against the RE Server, but I just published a new version and now it's throwing the error over there as well.  If I open the child job up independently and run it, it works with no errors.  Only when combined with the master job does it fail.  This is one of several other child jobs - not the other only one.  I have other jobs with many "children" that are all fine.  Any ideas or leads to follow?  So far my research via google and this community haven't helped.   I appreciate any suggestion!

[FATAL]: tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load - tRunJob_3 Child job returns 1. It doesn't terminate normally.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 555; nested exception is:
java.net.BindException: Address already in use: JVM_Bind

java.lang.RuntimeException: Child job returns 1. It doesn't terminate normally.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 555; nested exception is:
java.net.BindException: Address already in use: JVM_Bind

at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tRunJob_3Process(ACUITYnxt_Provider_Load.java:33021)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tDBRow_2Process(ACUITYnxt_Provider_Load.java:32548)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tDBRow_5Process(ACUITYnxt_Provider_Load.java:32150)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tDBRow_4Process(ACUITYnxt_Provider_Load.java:31755)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tSystem_1Process(ACUITYnxt_Provider_Load.java:31368)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tDBRow_3Process(ACUITYnxt_Provider_Load.java:31032)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tRunJob_2Process(ACUITYnxt_Provider_Load.java:30326)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tDBConnection_1Process(ACUITYnxt_Provider_Load.java:19873)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tHashInput_1Process(ACUITYnxt_Provider_Load.java:3186)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tDBRow_1Process(ACUITYnxt_Provider_Load.java:2382)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tRunJob_1Process(ACUITYnxt_Provider_Load.java:1986)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.jblLoadGenericContext_1_tFixedFlowInput_1Process(ACUITYnxt_Provider_Load.java:40148)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.jblLoadGenericContext_1_tDBInput_1Process(ACUITYnxt_Provider_Load.java:39360)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.jblLoadGenericContext_1_tJava_1Process(ACUITYnxt_Provider_Load.java:42342)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.jblLoadGenericContext_1_tFileInputProperties_1Process(ACUITYnxt_Provider_Load.java:42091)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tJava_1Process(ACUITYnxt_Provider_Load.java:42748)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.tPrejob_1Process(ACUITYnxt_Provider_Load.java:42533)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.runJobInTOS(ACUITYnxt_Provider_Load.java:45975)
at tcs_dev.acuitynxt_provider_load_0_3.ACUITYnxt_Provider_Load.main(ACUITYnxt_Provider_Load.java:45656)

[Anonymous · Accepted solution]

quick question, do you use multiple threads to call child job?

[Papademuchos]

Hi!  Yes, I had the option "Use an independent process to run child job" checked on several child jobs that are grouped together.  That is, they follow one after another. Tomorrow I can try to uncheck that option and re-run to see if it solves the problem. If it does, then I'm curious how to make that option work without getting this error.

[Papademuchos]

I updated the job and unchecked to option to run as a separate thread, and it worked.  I can run it against the RE without error.  Any light on this would be appreciated.  How can one run them in separate threads without conflicting ports?  Thanks again.