One of my customers who uses Coherence made some changes to the tangosol-coherence-override.xml file and started up their application. The changes did not take effect. The log file revealed that Coherence wasn't reading this configuration file even though it was on the classpath. Instead it was using a backup of the override file they copied to C:\, the root of the disk partition the JVM had been launched from. C:\ was not on the classpath.
Here are the relevant messages from the log. Note the third message in particular.
[Coherence] 2013-10-29 20:03:43,230 INFO : 2013-10-29 20:03:43.154/76.246 Oracle Coherence 3.5.3/465p3 <Info> (thread=Service Thread Pool, member=n/a): Loaded operational configuration from resource "file:C:/projectX82_7712/config/Caching/tangosol-coherence.xml"
[Coherence] 2013-10-29 20:03:43,230 INFO : 2013-10-29 20:03:43.158/76.250 Oracle Coherence 3.5.3/465p3 <Info> (thread=Service Thread Pool, member=n/a): Loaded operational overrides from resource "jar:file:C:/projectX82_7712/common/lib/ext/coherence.jar!/tangosol-coherence-override-dev.xml"
[Coherence] 2013-10-29 20:03:43,230 INFO : 2013-10-29 20:03:43.164/76.256 Oracle Coherence 3.5.3/465p3 <Info> (thread=Service Thread Pool, member=n/a): Loaded operational overrides from file "C:\tangosol-coherence-override.xml"
[Coherence] 2013-10-29 20:03:43,251 INFO : 2013-10-29 20:03:43.250/76.342 Oracle Coherence SE 3.5.3/465p3 <Info> (thread=Service Thread Pool, member=n/a): Remote management is not supported for Standard Edition; disabling remote management
[Coherence] 2013-10-29 20:03:43,282 INFO : 2013-10-29 20:03:43.282/76.374 Oracle Coherence SE 3.5.3/465p3 <Info> (thread=Service Thread Pool, member=n/a): Loaded cache configuration from "file:C:/projectX82_7712/config/Caching/coherence-cache-config.xml"
We also found that when this file was at the root of the disk partition the JVM was launched from, any properties we specified on the command line (eg: -Dtangosol.coherence.localport=24001) were ignored.
Does Coherence have some hard coded preference for the tangosol-coherence-override.xml file at this location, or is there some other explanation for the behavior we are seeing?
Thanks,
Michael