# ESB: hints and notes ## Studio | Item | Description | Available in | | --- | --- | --- | | cAMQP requires the Client ID to be set | When you use the cAMQP component in the Route Builder, make sure you
always set the Client ID to a unique value which is not used in other Routes
(the clientId header in cAMQP advanced settings.) If more
than one cAMQP based Routes are executed in the same Talend Runtime
container and the Client ID is not set, you will see some exceptions
like:


org.springframework.jms.UncategorizedJmsException:
Uncategorized exception occured during JMS processing; nested
exception is javax.jms.JMSException: Broker: localhost - Client:
tlnd-spappala(6968):2 already connected from
tcp://127.0.0.1:49729 |

All Talend products
with ESB | ## Runtime | Item | Description | Available in | | --- | --- | --- | | Copying an ESB Container will lead to unexpected
behaviour | A Talend Runtime container which was started once can't
be copied to a different directory or machine. It is recommended to always
use a fresh (never started) container that is shipped with the
product. |

All Talend products
with ESB | ## ESB Java Development | Item | Description | Available in | | --- | --- | --- | | Using PropertyPlaceHolder for Web-Containers | When creating Talend ESB web archives for services using Spring
contexts, note that all instances of PropertyPlaceholderConfigurer must
contain the following properties to avoid placeholder resolution problems
during startup of Spring contexts:


<property
name="ignoreUnresolvablePlaceholders" value="true" /> <property
name="ignoreResourceNotFound" value="true" /> |

All Talend products
with ESB | ## Notes about Git support | Item | Description | Available in | | --- | --- | --- | | Git implementation | The Git implementation done in Talend has a similar behavior as the SVN
one. |

All Talend products
with ESB | | All branches/tags are visible for all projects on the same Git
repository | If you create some branches/tags for one project, all other projects on
the same Git repository will have the same list. |

All Talend products
with ESB | | Unlock mode | Any item modified will be kept locally, and will never be committed /
pushed to the server until the item is unlocked. Project items will be
stored temporarily on the stash system of Git if needed, so that they are
not pushed until they are unlocked. |

All Talend products
with ESB | ## Microservices | Item | Description | Available in | | --- | --- | --- | | Context parameters naming for Microservices Deployments | During processing of context parameters for Microservices, be aware of
the following two special topics that influence the processing of context
parameter during the execution of Microservices. (only for Microservices but
not for Talend Runtime)

Context parameter might be overwritten by OS
environment variable which can lead to unexpected side effects. To avoid
this, try to use unique names which are not in conflict with names you
use in your OS environment.

Among the following parameters, Spring
Boot will take the OS environment variable as the first level variable
of the highest priority. If you specified the variable with the same
name as the system's, it will take system's.



Context parameters with some characters, for example, underscore and
numbers surrounded by underscores, will be treated according to the
Spring Relaxed binding which can lead to unexpected behaviour for your
Routes. See https://github.com/spring-projects/spring-boot/wiki/Relaxed-Binding-2.0 for the transformations and avoid
these character and character combinations in your context parameter to
prevent conflicts or use them accordingly to take advantage of this
effect. |

All Talend products
with ESB |