Resolution:
Description:
===========
Hot deployment will give exception if external Java jar files are present inside the .ear file being hot deployed.

Environment:
============
All Operating Systems
TIBCO BusinessEvents 4.x and 5.x

Symptoms :
============
java.util.ConcurrentModificationException in the log trace .
Sample log output:
2012 Jun 18 16:58:42:376 GMT +2 JRG-PC Error [HotDeployPoller] - [runtime.session] Hot deployment of ./../EARs/Example.ear failed!!!
java.util.ConcurrentModificationException
    at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
    at java.util.HashMap$KeyIterator.next(HashMap.java:828)
    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.newNameToByteCode(RuleServiceProviderImpl.java:1608)
    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.notify(RuleServiceProviderImpl.java:1458)
    at com.tibco.cep.repo.hotdeploy.DirectoryDeployer.poll(DirectoryDeployer.java:88)
    at com.tibco.cep.repo.hotdeploy.DirectoryDeployer.run(DirectoryDeployer.java:48)
    at java.lang.Thread.run(Thread.java:662)

Root Cause:
============
One of the root causes is the presence of external jar files in the ear .

Resolution:
============
Ensure that no external Java jar files are present inside the .ear file which is to be hot deployed . If the external Java jar file is inside the project folder structure , it can be excluded from the .sar file while creating the .ear file by adding a filter inside of the Studio preferences (Go to Window-&gtPreferences-&gtTeam-&gtIgnored Resources.) Refer to the attachment StudioPreferences.png for the exact location of said resource in TIBCO Business Events 4 or 5 studio . Manually removing external jar files from the ear file will also enable successful hot deployment .

Attachments :
=============
StudioPreferences.png