Affects Version/s: 18.104.22.168-fuse
Fix Version/s: 22.214.171.124M1-fuse
Similar Issues:Show 10 results
ESB-1070 JDBC failover not working as documented. ESB-1084 JDBC failover not working as documented. ESB-1529 Fuse ESB 4 (Pax Web + Karaf) does not support JSF2 + Primefaces ESB-529 A camel route contains camel-mail endpoint does not work if deployed into Fuse ESB 4 container ESB-569 The steps required for installing FUSE ESB 4 as a Windows service are not documented. ESB-789 Can't get JBI SA that had worked in FUSE ESB 3.3.1 running properly in FUSE ESB 4.1 ESB-1103 Possible hang with slave instances of the ESB when using Oracle JDBC lock. ESB-538 Camel XSLT does not work in Fuse ESB 126.96.36.199 ESB-1012 Actional AOP interceptors need to work in FUSE ESB 4 ESB-617 Functionality to deploy applications to a FUSE ESB 4 cluster
If you configure FUSE ESB 4 to use a JDBC lock for failover (i.e. the following configuration) then ServiceMix will fail with the error:
Could not obtain lock: FATAL: database "postgres;create=true" does not exist
Configuration (in system.properties):
I've checked the Karaf code for JDBCLock, and the string ';created=true' is always being added to the jdbc URL. I suspect that this approach has only been tested with Derby? When used with PostgreSQL, the JDBC driver errantly thinks that this suffix is in fact part of the database name.