I have posted a reply to this question where you originally asked it Downloading Coherence 3.7 but just to repeat myself...
I'm not sure that the message you have posted is the cause of your cluster failing to start. All the message says it that the XML configuration will not be validated against a schema or DTD. I would expect there are more error messages or stack traces in your logs.
I see that you are using the Coherence Incubator too - have you made sure that the version of the Incubator you are using is compatible with 3.7.1
Thanks for your Reply JK.
i am not seeing any other error. it keeps on trying to start and stopping in the above line. also, I did upgrade these jars compatible for 3.7.1+.
Onething i noted it, it works when i use 3.6 coherence.jar upgrading (i.e other jars are of 3.7.1 stream) all other dependent jars.
Please find the jar versions i used
I have set log level to 9. still not seeing any error trace.
Can someone please help me out. stuck up with this fa long time.
Can someone help me out...
Post a copy of your coherence-server-one.xml file
Sorry for late reply JK. It was a problem with my coherence-server-one.xml. Some of the xml tags were not supported in the latest Incubator jars. Changing it worked.
I have a quick question.
I got below exception when configuring push replication using coherence INC versiong 10 jars.
Caused by: java.lang.ClassNotFoundException: com.oracle.coherence.patterns.pushreplication.configuration.PushReplicationNamespaceContentHandler
at java.security.AccessController.doPrivileged(Native Method)
at java.lang.Class.forName0(Native Method)
... 12 more
I fixed it by using com.oracle.coherence.patterns.eventdistribution.configuration.EventDistributionNamespaceContentHandler instead of com.oracle.coherence.patterns.pushreplication.configuration.PushReplicationNamespaceContentHandler. Also i changed my push replication configuration from publisher to event distributor.
<yy:publisher-name> ... </yy:publisher-name>
<yy:remote-invocation-service-name> .... </yy:remote-invocation-service-name>
<yy:target-cache-name> ... </yy:target-cache-name>
<yy:channel-name> ... </yy:channel-name>
<yy:remote-invocation-service-name> ... </yy:remote-invocation-service-name>
<yy:target-cache-name> .... </yy:target-cache-name>
I want to know, if publisher configuration is retried in coherence INC 10 jars. If no, can you pls tell me how do i acheive it. If yes, can publisher can be replaced with even distributor ?
How are you doing the upgrade from coherence 3.6 to 3.7.1 ?
The Coherence documentation doesn't have an explicit upgrade guide.
At its simplest level Coherence is simply an API library. If you are using Coherence at that level then you should refer to the Coherence 3.7.1 release notes for details of any changes to the behaviour of the product or its API interfaces:
and assess whether that has any impact on your applications or not.
Since you are upgrading between major versions it is not possible to do a live / rolling upgrade
If you are using Coherence as part of another Oracle Fusion Middleware product, such as Oracle Access Manager, Oracle SOA, Oracle OSB, etc., then the upgrade information for the Oracle product takes precedence over the Coherence documentation.