quick context: We have a simple route using FTP endpoint and scheduled to run every few minutes using cronscheduledroute policy. The attempt is to enable clustering (in JBoss EAP 6.0) for the route. JDBCDatastore is used with cluster enabled.
The route was deployed in a .ear in clustered JBoss instances. The ear is successfully installed and deployed in first instance. When the deployment is attempted at the second instance, an "ObjectAlreadyExistsException" exception gets thrown. Camel: 2.10.2; camel-Quartz - 2.10.2; Quartz scheduler - 1.8.6 The same resulted even if the deployment is performed on 2 non-clustered jboss instances. Are we missing something basic here? ----- Ravishankar Singaram Technical Lead Amadeus Software Labs -- View this message in context: http://camel.465427.n5.nabble.com/Cluster-in-camel-using-Quartz-ObjectAlreadyExistsException-tp5737167.html Sent from the Camel - Users mailing list archive at Nabble.com.
