This discussion is archived
8 Replies Latest reply: Oct 23, 2013 9:59 AM by Leo_TA RSS

Unable to start Coherence Server using 3.7.1

LSV Newbie
Currently Being Moderated

We were running our Coherence grid using 3.6. it was working fine. We just updated the server to use 3.7.1 and our server is not starting with below error. Any suggestions ?

 

 

2013-10-03 07:39:38,460 [Logger@1247017815 3.7.1.0] INFO  Coherence  - 2013-10-03 07:39:38.459/0.734 Oracle Coherence GE 3.7.1.0 <Info> (thread=main, member=n/a): Loaded cache configuration from "file:/test/stand/coherence/target/classes/test/coherence/grid/config/coherence-server-one.xml"; this document does not refer to any schema definition and has not been validated.

2013-10-03 07:39:38,619 [Logger@1247017815 3.7.1.0] INFO  Coherence  - 2013-10-03 07:39:38.618/0.893 Oracle Coherence GE 3.7.1.0 <Info> (thread=main, member=n/a): Loaded cache configuration from "jar:file:/test/stand/coherence/lib/coherence.jar!/coherence-cache-config.xml"

2013-10-03 07:39:38,664 [Logger@1247017815 3.7.1.0] INFO  Coherence  - 2013-10-03 07:39:38.664/0.939 Oracle Coherence GE 3.7.1.0 <Info> (thread=main, member=n/a): WARNING: Failed to load Coherence cache-config.dtd. Provided configuration XML element names will not be validated. Class:com.oracle.coherence.environment.extensible.namespaces.CoherenceNamespaceContentHandler

 

 

Thanks

  • 1. Re: Unable to start Coherence Server using 3.7.1
    Jonathan.Knight Expert
    Currently Being Moderated

    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

     

    JK

  • 2. Re: Unable to start Coherence Server using 3.7.1
    LSV Newbie
    Currently Being Moderated

    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+.

     

    functorpattern

    messagingpattern

    processingpattern

    commandpattern

    coherence-common

    pushreplicationpattern

     

    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.

  • 3. Re: Unable to start Coherence Server using 3.7.1
    LSV Newbie
    Currently Being Moderated

    Please find the jar versions i used

     

    coherence-commandpattern-2.8.5.39174

    coherence-common-2.3.0.39174

    coherence-functorpattern-1.5.5.39174

    coherence-messagingpattern-2.8.6.39174

    coherence-processingpattern-1.4.4.39174

    coherence-pushreplicationpattern-4.0.7.40024

  • 4. Re: Unable to start Coherence Server using 3.7.1
    LSV Newbie
    Currently Being Moderated

    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.

  • 5. Re: Unable to start Coherence Server using 3.7.1
    LSV Newbie
    Currently Being Moderated

    Can someone help me out...

  • 6. Re: Unable to start Coherence Server using 3.7.1
    Jonathan.Knight Expert
    Currently Being Moderated

    Hi

     

    Post a copy of your coherence-server-one.xml file

     

    JK

  • 7. Re: Unable to start Coherence Server using 3.7.1
    LSV Newbie
    Currently Being Moderated

    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.net.URLClassLoader$1.run(URLClassLoader.java:366)

            at java.net.URLClassLoader$1.run(URLClassLoader.java:355)

            at java.security.AccessController.doPrivileged(Native Method)

            at java.net.URLClassLoader.findClass(URLClassLoader.java:354)

            at java.lang.ClassLoader.loadClass(ClassLoader.java:423)

            at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)

            at java.lang.ClassLoader.loadClass(ClassLoader.java:356)

            at java.lang.Class.forName0(Native Method)

            at java.lang.Class.forName(Class.java:188)

            at com.tangosol.util.ExternalizableHelper.loadClass(ExternalizableHelper.java:3165)

            at com.oracle.coherence.environment.extensible.DefaultConfigurationContext$Scope.establishNamespaceContentHandlerFor(DefaultConfigurationContext.java:1124)

            ... 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.

     

    from

     

                    <yy:publisher>

                        <yy:publisher-name> ... </yy:publisher-name>

                        <yy:publisher-scheme>

                            <yy:remote-cluster-publisher-scheme>

                                <yy:remote-invocation-service-name> .... </yy:remote-invocation-service-name>

                                <yy:remote-publisher-scheme>

                                    <yy:local-cache-publisher-scheme>

                                        <yy:target-cache-name> ... </yy:target-cache-name>

                                     </yy:local-cache-publisher-scheme>

                                </yy:remote-publisher-scheme>

                            </yy:remote-cluster-publisher-scheme>

                        </yy:publisher-scheme>

                    </yy:publisher>

     

      to

     

                        <yy:distribution-channels>

                            <yy:distribution-channel>

                                <yy:channel-name> ... </yy:channel-name>

                                <yy:channel-scheme>

                                    <yy:remote-cluster-channel-scheme>

                                        <yy:remote-invocation-service-name> ... </yy:remote-invocation-service-name>

                                        <yy:remote-channel-scheme>

                                            <yy:local-cache-channel-scheme>

                                                <yy:target-cache-name> .... </yy:target-cache-name>

                                            </yy:local-cache-channel-scheme>

                                        </yy:remote-channel-scheme>

                                    </yy:remote-cluster-channel-scheme>

                                </yy:channel-scheme>

                            </yy:distribution-channel>

                        </yy:distribution-channels>

                    </yy:distributor>

     

    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 ?

  • 8. Re: Unable to start Coherence Server using 3.7.1
    Leo_TA Newbie
    Currently Being Moderated

    Hi ,

     

    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:

    3.7.1: http://docs.oracle.com/cd/E24290_01/coh.371/e22623/technotes.htm#sthref8

    3.7.0: http://docs.oracle.com/cd/E18686_01/coh.37/e21505/toc.htm

     

    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.

     

    Regards,

    Leo_TA

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points