WKA Lists
Hmm,
I'm trying to get a new applications working with a WKA list.
To simplify the test case I've reduced the list to :
<socket-address id="17">
<address>10.129.20.128</address>
<port>3000</port>
</socket-address>
<socket-address id="18">
<address>10.129.20.128</address>
<port>3001</port>
</socket-address>
Any thoughts?
Kindest regards,
Andrew.
2008-12-04 11:30:54,829 INFO [Logger@25039388 3.4/405] [Coherence] 2008-12-04 11:30:54.829/0.579 Oracle Coherence EE 3.4/405 <Info> (thread=main, member=n/a): Loaded cache configuration from file "C:\awilson\dev\mrm\config\coherence\cacheConfig.xml"
Exception in thread "main" com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
2008-12-04 11:31:26,313 ERROR [Logger@25039388 3.4/405] [Coherence] 2008-12-04 11:31:26.313/32.063 Oracle Coherence EE 3.4/405 <Error> (thread=main, member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberSet=ServiceMemberSet(
OldestMember=n/a
MemberId/ServiceVersion/ServiceJoined/ServiceLeaving
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/ServiceLeaving
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
Aha, interesting. I tried that and got :
Caused by: java.lang.IllegalArgumentException: unknown user type: com.tangosol.coherence.component.net.management.Connector$Announce
at com.tangosol.io.pof.ConfigurablePofContext.getUserTypeIdentifier(ConfigurablePofContext.java:400)
at com.tangosol.io.pof.ConfigurablePofContext.getUserTypeIdentifier(ConfigurablePofContext.java:389)
at com.tangosol.io.pof.PofBufferWriter.writeObject(PofBufferWriter.java:1432)
at com.tangosol.io.pof.ConfigurablePofContext.serialize(ConfigurablePofContext.java:338)
It looks like that type is not supported for POF.
How do I get round this problem? I guess I could add it to my POF file for now...
Similar Messages
-
Support for virtual IP in WKA list
I am attempting to implement Coherence Grid Edition 3.5.3 Patch 7 . It's running on Sun Java 1.6.06 on a Solaris 5.10 machine (which I will call machine A1) which has an ip address 1.2.3.261. Also, there is a virtual IP address 1.2.3.260 which points to this same machine A1, as well as a hostname that maps to the virtual IP address of the machine A1.
(Note: I have mocked up the IP addresses in this post for security reasons).
I am using WKA due to concerns of the local network admins regarding multicast (debatable, but for now let's please assume I need to go with WKA).
If this production machine A1 develops any problem, we can quickly switch to an alternate machine A2. The alternate machine A2 contains automatically replicated copies of all of our important sub-directories (including the coherence xml configuration files), but it does have a different IP.
During a failure of machine A1, we would shut down machine A1, start up machine A2, and reroute the virtual IP to alternate machine A2's true IP. Machine A2 would be supplied a copy of the file-system that A1 had when A1 was shutdown.
We would seek to not have to edit any configuration files on A2. It is difficult to maintain alternate configuration files using our current replication scheme, and any machine-specific customizations are problematic.
Therefore, we would prefer to list the virtual IP of machines A1 and A2 in the WKA list, rather than the true IP of these machines.
However, when I attempt to list the virtual IP in the WKA list...
<well-known-addresses>
<socket-address id="1">
<address>1.2.3.260</address> <!--virtual ip -->
<port>8088</port>
</socket-address>
</well-known-addresses>
... I get the error below.
2010-09-03 12:01:51.464/1.401 Oracle Coherence GE 3.5.3/465p7 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/a
2010-09-03 12:01:54.760/4.697 Oracle Coherence GE 3.5.3/465p7 <Error> (thread=Cluster, member=n/a): Node myhostname/1.2.3.261:8088 is not allowed to create a new cluster; WKA list: [1.2.3.260:8088]
2010-09-03 12:01:54.760/4.697 Oracle Coherence GE 3.5.3/465p7 <D5> (thread=Cluster, member=n/a): Service Cluster left the cluster
Exception in thread "main" java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_ANNOUNCE)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:38)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:395)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:7)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:27)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:998)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:905)
at com.tangosol.net.DefaultCacheServer.start(DefaultCacheServer.java:139)
at com.tangosol.net.DefaultCacheServer.main(DefaultCacheServer.java:60)
2010-09-03 12:01:54.763/4.700 Oracle Coherence GE 3.5.3/465p7 <Error> (thread=main, member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_ANNOUNCE)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:38)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:395)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
What exactly is being checked here? Does each Coherence instance expect to see it's own IP listed in the WKA list, and refuse to run if it can't find it's own IP on the list?
Is the instance detecting it's own IP via an operating system call, or is there some way I can influence the instance's sense of what IP it is running on?
Is there any advice for supporting this kind of virtual IP scenario?
I have tried listing the hostname with no better success, because the hostname points to the virtual IP, and therefore has the same effect as listing the virtual IP.
As a workaround, I have altered the WKA list to list of the true IPs of both machines...
<well-known-addresses>
<socket-address id="1">
<address>1.2.3.261</address> <!-- A1 -->
<port>8088</port>
</socket-address>
<socket-address id="2">
<address>1.2.3.262</address> <!-- A2 -->
<port>8088</port>
</socket-address>
</well-known-addresses>
... even though both machines will never be up and running at the same time. This workaround avoids the error and the cluster appears to come up. I am not sure if there's any ill effect that at any given time one of these two IPs will never be up and running.
Despite my workaround, true support for virtual IPs would be superior; listing all the true non-virtual IPs in the WKA list means re-editing the list as the hardware changes.
Thanks for any advice!
P.S. I tried the above with Coherence 3.5.2 with the same results.
Edited by: user11114413 on Sep 3, 2010 11:45 AMHi user11114413,
The issue you are seeing actually has little to do with VIP, and more to do with there being multiple IP addresses for us to choose from on your box. For such multi-IP boxes, you'll want to tell us the IP to use, and in your case you want to tell as a VIP. This can be done either by editing your operational configuration file, and including an <address> element within the <unicast-listener> element, or via the tangosol.coherence.localhost system property. For example:
<unicast-listener>
<well-known-addresses>
<socket-address id="1">
<address>1.2.3.260</address> <!--virtual ip -->
<port>8088</port>
</socket-address>
</well-known-addresses>
<address>1.2.3.260</address> <!--virtual ip -->
<port>8088</port>
</unicast-listener>or
java ... -Dtangosol.coherence.localhost=1.2.3.260If you are using the same operational configuration on all nodes in your cluster then the system property approach is likely preferable, and would only be necessary on the two machines sharing the VIP.
As for using VIP or an extended WKA list, the choice is yours, either will work. If you do go the VIP route, it would obviously be a very bad idea to simultaneously use the same VIP and port at the same time from the two machines.
thanks,
Mark
Oracle Coherence -
Coherence clustering between two separate wka clusters
Hi,
I am running Coherence 3.6 in my environment.Off lately I am seeing a weird issue with respect to two separate wka clusters. when I mean separate wka cluster, these are two clusters configured with a distinct wka list.
I try to connect with Coherence cmd line tool to a cluster named "cluster-ABC" which has a wka IP- 10.30.xx.xxx on "host x". Then I come out of this cluster, and connect from the same command prompt window to another host -"host y" which has a same named cluster-"cluster-ABC" but a different wka IP-10.30.yy.yyy. Between the two clusters, the only common factor is the cluster name. Other things such as wka list etc are different.
After some time, I see that nodes from "host y" start joining "host x". this seems to happen only when i connect to two different clusters, from my command line utility. The clusters here are formed using wka in each case. there is no multicast enabled on our setups. This used to never happen with coherence 3.5, where i did similar kind of operations on the cluster.
Is there some kind of reference being held by the utility even after it is disconnected from the second cluster?
Thanks,
ChandiniWe tried out your suggestion on using unique cluster names. I had 2 hosts each running a cluster with a unique cluster name; cluster-A and cluster-B. I had another node on a third host connect to cluster-A using port 8092 and then tried connecting to the cluster-B after changing the cluster name appropriately. But, this time the node was rejected by cluster-A saying that the configurations are different.
On changing the port from 8092 to 8090 and connecting to cluster-B worked just fine. I guess, just having unique cluster names isn't helping. Would this be fixed by the ticket that's been raised?
Is there anything else we could do in the interim to get around the issue? Using different ports might not be a very helpful solution as we've noticed that 3.6 onwards, we need to open up the ports in the firewall of the host where the nodes are running. This wouldn't be too feasible for us.
-Roshan -
Wka vs. multicast error logging
I have been moving our caches from multicast to use wka. Along the way It seems as if the wka seting provides less and/or different logging in the jvm error log.
For example, with multicast enabled, I had a jdom error that was correctly being reported in the error log. Once I enabled wka, the error did not appear even though the problem still existed. It was only switching back to multicast that I again saw the error and was able to correct
If this is true, is there a setting in the tangosol-coherence-override.xml file that will provide the same type if logging the multicast settings seem to produce.
regards,
cj willette
systems engineer
ll bean, freeport maineHi CJ.
I wonder if you had a configuration error in the tangosol-coherence-override.xml when you defined the WKA list. As a result you could have the entire cluster configuration using the default settings instead and as a result not seeing your specific cache configuration.
Could you please send the WKA configuration to support at tangosol.com, so we could verify the correctness of the setup.
Regards,
Gene -
Coherence not using my -Dtangosol.coherence.wka
I would like 29066 to be the "well known" port, but Coherence is using 8088 (the default)
-Dtangosol.coherence.localport=29066
-Dtangosol.coherence.wka=secondary.xxxxxx.com
-Dtangosol.coherence.wka.port=29066
-Dtangosol.coherence.log.level=9
2012-01-19 12:37:27.827/60.284 Oracle Coherence 3.6.0.4 <Info> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded operational configuration from "jar:file:/ucrmv1r1/APPLTOP/fusionapps/oracle_common/modules/oracle.coherence_3.6/coherence.jar!/tangosol-coherence.xml"
2012-01-19 12:37:27.841/60.297 Oracle Coherence 3.6.0.4 <Info> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded operational overrides from "jar:file:/ucrmv1r1/APPLTOP/fusionapps/oracle_common/modules/oracle.coherence_3.6/coherence.jar!/tangosol-coherence-override-dev.xml"
2012-01-19 12:37:27.842/60.298 Oracle Coherence 3.6.0.4 <Info> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded operational overrides from "jar:file:/ucrmv1r1/APPLTOP/fusionapps/soa/soa/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar!/tangosol-coherence-override.xml"
2012-01-19 12:37:27.850/60.306 Oracle Coherence 3.6.0.4 <D5> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Optional configuration override "/custom-mbeans.xml" is not specified
2012-01-19 12:37:27.864/60.320 Oracle Coherence 3.6.0.4 <D6> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded edition data from "jar:file:/ucrmv1r1/APPLTOP/fusionapps/oracle_common/modules/oracle.coherence_3.6/coherence.jar!/coherence-grid.xml"
Oracle Coherence Version 3.6.0.4 Build 19111
Grid Edition: Development mode
Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
[INFO ][memory ][Thu Jan 19 12:37:28 2012][1327005448043][23695] [YC#103] 60.454-60.499: YC 180503KB->184889KB (187744KB), 0.045 s, sum of pauses 44.711 ms, longest pause 44.711 ms.
[INFO ][memory ][Thu Jan 19 12:37:28 2012][1327005448109][23695] [OC#22] 60.500-60.565: OC 184889KB->103717KB (187744KB), 0.065 s, sum of pauses 62.968 ms, longest pause 62.968 ms.
2012-01-19 12:37:28.158/60.614 Oracle Coherence GE 3.6.0.4 <Info> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded cache configuration from "jar:file:/ucrmv1r1/APPLTOP/fusionapps/soa/soa/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar!/soa-coherence-cache-config.xml"
2012-01-19 12:37:28.781/61.237 Oracle Coherence GE 3.6.0.4 <D4> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): TCMP bound to /99.99.30.235:29066 using SystemSocketProvider
2012-01-19 12:37:59.511/91.967 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2012-01-19 12:37:28.789, Address=99.99.30.235:29066, MachineId=58603, Location=site:us.xxxxx.com,machine:slc00vmh,process:23695, Role=WeblogicServer) has been attempting to join the cluster using WKA list [secondary.xxxxx.com/99.99.30.235:>>>>>> 8088 <<<<<<<<] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.
The fabric-runtime.jar!tangosol-coherence-override.xml contains
<well-known-addresses>
<socket-address id="1">
<address system-property="tangosol.coherence.wka1"></address>
<port system-property="tangosol.coherence.wka1.port">8088</port>
</socket-address>
That seems to conflict (i.e. override) with the socket-address id="1" in tangosol-coherence.xml
Edited by: mikereiche on Jan 19, 2012 7:13 PMHi,
Try replacing the properties:
-Dtangosol.coherence.wka=secondary.xxxxxx.com
-Dtangosol.coherence.wka.port=29066-Dtangosol.coherence.wka1=secondary.xxxxxx.com
-Dtangosol.coherence.wka1.port=29066
Cheers,
NJ -
Performance degradation with addition of unicasting option
We have been using the multi-casting protocol for setting up the data grid between the application nodes with the vm arguments as
*-Dtangosol.coherence.clusteraddress=${Broadcast Address} -Dtangosol.coherence.clusterport=${Broadcast port}*
As the certain node in the application was expected in a different sub net and multi-casting was not feasible, we opted for well known addressing with following additional VM arguments setup in the server nodes(all in the same subnet)
*-Dtangosol.coherence.machine=${server_name} -Dtangosol.coherence.wka=${server_ip} -Dtangosol.coherence.localport=${server_port}*
and the following in the remote client node that point to one of the server node like this
*-Dtangosol.coherence.wka=${server_ip} -Dtangosol.coherence.wka.port=${server_port}*
But this deteriorated the performance drastically both in pushing data into the cache and getting events via map listener.
From the coherence logging statements it doesn't seems that multi-casting is getting used atleast with in the server nodes(which are in the same subnet).
Is it feasible to have both uni-casting and multi-casting to coexist? How to verify if it is setup already?
Is performance degradation in well-known addressing is a limitation and expected?Hi Mahesh,
From your description it sounds as if you've configured each node with a wka list just including it self. This would result in N rather then 1 clusters. Your client would then be serviced by the resources of just a single cache server rather then an entire cluster. If this is the case you will see that all nodes are identified as member 1. To setup wka I would suggest using the override file rather then system properties, and place perhaps 10% of your nodes on that list. Then use this exact same file for all nodes. If I've misinyerpreted your configuration please provide additional details.
Thanks,
Mark
Oracle Coherence -
Coherence Error at the time of Starting weblogic Server
Hi ,
I am getting below error at the time of starting Weblogic OSB managed server
We are using osb_cluster1 (Unicast) for osb_server1 managed server.
When Weblogic server try to start the managed server we get following Coherence errors and startup scripts try to point to Oracle Coherence 3.6.0.4.(its mainly happening in starting osb_server1 managed server, this error is not appearing during soa_server1 managed server start)
We don't want to use the coherence at all, we are trying to disable the coherence feature, but hardly getting any success in it, every time during server start-up following error appears.
Let me know if you have any solution to it.
####<Mar 5, 2012 9:18:55.424 AM > <Warning> <Coherence> <sjsj-idm.kuy.co.wo> <osb_server1> <Logger@406289568 3.6.0.4> <<anonymous>> <> <3976a80e38d52337:-f13ff44:135df5aa8b6:-8000-0000000000000007> <1330892335424> <BEA-000000> <Oracle Coherence 3.6.0.4 (member=n/a): This Member(Id=0, Timestamp=2012-03-05 09:18:23.752, Address=11.49.63.33:7880, MachineId=31265, Location=site:kuy.co.wo,machine:deap-idm01,process:10629, Role=OSB-node) has been attempting to join the cluster using WKA list [sjsj-idm.kuy.co.wo/11.49.63.33:9003] for 31 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.>
####<Mar 5, 2012 9:18:55.425 AM > <Warning> <Coherence> <sjsj-idm.kuy.co.wo> <osb_server1> <Logger@406289568 3.6.0.4> <<anonymous>> <> <3976a80e38d52337:-f13ff44:135df5aa8b6:-8000-0000000000000007> <1330892335425> <BEA-000000> <Oracle Coherence 3.6.0.4 (member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond>
####<Mar 5, 2012 9:22:58.769 AM > <Error> <Coherence> <sjsj-idm.kuy.co.wo> <osb_server1> <Logger@406289568 3.6.0.4> <<anonymous>> <> <3976a80e38d52337:-f13ff44:135df5aa8b6:-8000-0000000000000007> <1330892578769> <BEA-000000> <Oracle Coherence 3.6.0.4 (member=n/a): Detected soft timeout) of {WrapperGuardable Guard{Daemon=IpMonitor} Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}}>
####<Mar 5, 2012 9:22:58.770 AM > <Warning> <Coherence> <sjsj-idm.kuy.co.wo> <osb_server1> <Logger@406289568 3.6.0.4> <<anonymous>> <> <3976a80e38d52337:-f13ff44:135df5aa8b6:-8000-0000000000000007> <1330892578770> <BEA-000000> <Oracle Coherence 3.6.0.4 (member=n/a): Attempting recovery of Guard{Daemon=IpMonitor}>
####<Mar 5, 2012 9:23:25.530 AM > <Error> <Coherence> <sjsj-idm.kuy.co.wo> <osb_server1> <Logger@406289568 3.6.0.4> <<anonymous>> <> <3976a80e38d52337:-f13ff44:135df5aa8b6:-8000-0000000000000007> <1330892605530> <BEA-000000> <Oracle Coherence 3.6.0.4 (member=n/a): Failure to join a cluster for 301 seconds; stopping cluster service.>
####<Mar 5, 2012 9:23:25.879 AM > <Error> <Coherence> <sjsj-idm.kuy.co.wo> <osb_server1> <Logger@406289568 3.6.0.4> <<anonymous>> <> <3976a80e38d52337:-f13ff44:135df5aa8b6:-8000-0000000000000007> <1330892605879> <BEA-000000> <Oracle Coherence 3.6.0.4 (member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:637)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:7)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:998)
at com.bea.alsb.coherence.impl.CoherenceProvider.<init>(CoherenceProvider.java:45)
at com.bea.alsb.coherence.impl.CoherenceProviderFactory.newInstance(CoherenceProviderFactory.java:21)
at com.bea.alsb.coherence.init.CoherenceAppListener.preStart(CoherenceAppListener.java:45)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:284)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:614)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)>
Edited by: 858026 on Mar 4, 2012 6:21 PM
Edited by: 858026 on Mar 4, 2012 6:23 PMHi NJ,
In WL console while setting up cluster I have given Messaging
Mode to Unicast,
By default Multicast address and ports comes up
Multicast Address - 239.192.0.0,
Multicast Port- 7001
I have modified the override file but still getting given error logs while server startup and its trying to look for override file in Oracle Coherence 3.6.0.4/coherence.jar
<!DOCTYPE coherence SYSTEM ""coherence.dtd"">
<coherence>
<cluster-config>
<!-- By default, this is using a multicast listener for cluster discovery, etc.
If you wish to use a unicast listener:
- update the entries in /coherence/unicast-listener/well-known-addresses/socket for each member of the cluster
(or specify the corresponding system properties)
- set the /coherence/unicast-listener/address to the host name of this machine
See http://coherence.oracle.com/display/COH35UG/well-known-addresses for more details. -->
<unicast-listener>
<well-known-addresses>
<socket-address id=""1"">
<address system-property=""OSB.coherence.wka1""></address>
<port system-property=""OSB.coherence.wka1.port""></port>
</socket-address>
<socket-address id=""2"">
<address system-property=""OSB.coherence.wka2""></address>
<port system-property=""OSB.coherence.wka2.port""></port>
</socket-address>
<socket-address id=""3"">
<address system-property=""OSB.coherence.wka3""></address>
<port system-property=""OSB.coherence.wka3.port""></port>
</socket-address>
<socket-address id=""4"">
<address system-property=""OSB.coherence.wka4""></address>
<port system-property=""OSB.coherence.wka4.port""></port>
</socket-address>
<socket-address id=""5"">
<address system-property=""OSB.coherence.wka5""></address>
<port system-property=""OSB.coherence.wka5.port""></port>
</socket-address>
<socket-address id=""6"">
<address system-property=""OSB.coherence.wka6""></address>
<port system-property=""OSB.coherence.wka6.port""></port>
</socket-address>
<socket-address id=""7"">
<address system-property=""OSB.coherence.wka7""></address>
<port system-property=""OSB.coherence.wka7.port""></port>
</socket-address>
<socket-address id=""8"">
<address system-property=""OSB.coherence.wka8""></address>
<port system-property=""OSB.coherence.wka8.port""></port>
</socket-address>
<socket-address id=""9"">
<address system-property=""OSB.coherence.wka9""></address>
<port system-property=""OSB.coherence.wka9.port""></port>
</socket-address>
</well-known-addresses>
<address system-property=""OSB.coherence.localhost"">127.0.0.1</address>
<port system-property=""OSB.coherence.localport"">7890</port>
</unicast-listener>
<multicast-listener>
<address system-property=""OSB.coherence.clusteraddress"">239.192.0.0</address>
<port system-property=""OSB.coherence.clusterport"">7001</port>
</multicast-listener>
</cluster-config>
</coherence>
####<Mar 6, 2012 3:00:44.050 PM NZDT> <Notice> <StdErr> <dete-idm01.hnz.co.nz> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330999244050> <BEA-000000> <2012-03-06 15:00:44.015 Oracle Coherence 3.6.0.4 <Info> (thread=[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'): Loaded operational configuration from "zip:/u01/app/oracle/product/OSB11.1.1.4/oracle_common/modules/oracle.coherence_3.6/coherence.jar!/tangosol-coherence.xml">
####<Mar 6, 2012 3:00:44.053 PM NZDT> <Notice> <StdErr> <dete-idm01.hnz.co.nz> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330999244053> <BEA-000000> <2012-03-06 15:00:44.029 Oracle Coherence 3.6.0.4 <Info> (thread=[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'): Loaded operational overrides from "zip:/u01/app/oracle/product/OSB11.1.1.4/oracle_common/modules/oracle.coherence_3.6/coherence.jar!/tangosol-coherence-override-dev.xml">
####<Mar 6, 2012 3:00:44.053 PM NZDT> <Notice> <StdErr> <dete-idm01.hnz.co.nz> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330999244053> <BEA-000000> <2012-03-06 15:00:44.030 Oracle Coherence 3.6.0.4 <Info> (thread=[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'): Loaded operational overrides from "zip:/u01/app/oracle/product/OSB11.1.1.4/user_projects/domains/OSBD/servers/osb_server1/tmp/_WL_user/ALSB Coherence Cache Provider/yannht/APP-INF/lib/com.bea.alsb.coherence-impl.jar!/tangosol-coherence-override.xml">
####<Mar 6, 2012 3:00:44.073 PM NZDT> <Error> <OSB Coherence WebLogic> <dete-idm01.hnz.co.nz> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0ed5cc20267507d3:a44cfd4:135e5bc3642:-8000-0000000000000003> <1330999244073> <BEA-2032481> <Unable to initialize OSB Coherence Cache Provider because there was an error starting Coherence:
com.bea.alsb.coherence.impl.ConfigurationException: Error starting Coherence from cache configuration file /coherence/osb-coherence-cache-config.xml:
(Wrapped) java.lang.reflect.InvocationTargetException
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:269)
at com.tangosol.net.CacheFactory.getServiceConfig(CacheFactory.java:1355)
at com.tangosol.net.CacheFactory.getCacheFactoryBuilderConfig(CacheFactory.java:1231)
at com.tangosol.net.CacheFactory.getCacheFactoryBuilder(CacheFactory.java:593)
at com.bea.alsb.coherence.impl.CoherenceProvider.<init>(CoherenceProvider.java:42)
at com.bea.alsb.coherence.impl.CoherenceProviderFactory.newInstance(CoherenceProviderFactory.java:21)
at com.bea.alsb.coherence.init.CoherenceAppListener.preStart(CoherenceAppListener.java:45)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.tangosol.net.CacheFactory.getServiceConfig(CacheFactory.java:1350)
... 29 more
Caused by: (Wrapped: Failed to apply the element override: /tangosol-coherence-override-dev.xml) (Wrapped: Failed to apply the element override: /tangosol-coherence-override.xml) (Wrapped: Failed to apply the element override: /coherence/osb-coherence-override.xml) (Wrapped) java.io.IOException: Exception occurred during parsing: looking for id=10, found id=1((0,29,13) Name coherence.dtd)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.coherence.component.application.console.Coherence.loadOverrides(Coherence.CDB:83)
at com.tangosol.coherence.component.application.console.Coherence.loadConfiguration(Coherence.CDB:46)
at com.tangosol.coherence.component.application.console.Coherence.getServiceConfig(Coherence.CDB:14)
at com.tangosol.coherence.component.application.console.Coherence.ensureRunningLogger(Coherence.CDB:10)
at com.tangosol.coherence.component.application.console.Coherence.getSafeCluster(Coherence.CDB:14)
at com.tangosol.coherence.component.application.console.Coherence.getServiceConfig(Coherence.CDB:8)
... 34 more
Caused by: (Wrapped: Failed to apply the element override: /tangosol-coherence-override.xml) (Wrapped: Failed to apply the element override: /coherence/osb-coherence-override.xml) (Wrapped) java.io.IOException: Exception occurred during parsing: looking for id=10, found id=1((0,29,13) Name coherence.dtd)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.coherence.component.application.console.Coherence.loadOverrides(Coherence.CDB:83)
at com.tangosol.coherence.component.application.console.Coherence.loadOverrides(Coherence.CDB:64)
... 39 more
Caused by: (Wrapped: Failed to apply the element override: /coherence/osb-coherence-override.xml) (Wrapped) java.io.IOException: Exception occurred during parsing: looking for id=10, found id=1((0,29,13) Name coherence.dtd)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.coherence.component.application.console.Coherence.loadOverrides(Coherence.CDB:83)
at com.tangosol.coherence.component.application.console.Coherence.loadOverrides(Coherence.CDB:64)
... 40 more
Caused by: (Wrapped) java.io.IOException: Exception occurred during parsing: looking for id=10, found id=1((0,29,13) Name coherence.dtd)
at com.tangosol.run.xml.XmlHelper.loadXml(XmlHelper.java:120)
at com.tangosol.run.xml.XmlHelper.loadXml(XmlHelper.java:155)
at com.tangosol.coherence.component.application.console.Coherence.loadOverrides(Coherence.CDB:41)
at com.tangosol.coherence.component.application.console.Coherence.loadOverrides(Coherence.CDB:64)
at com.tangosol.coherence.component.application.console.Coherence.loadOverrides(Coherence.CDB:64)
at com.tangosol.coherence.component.application.console.Coherence.loadConfiguration(Coherence.CDB:46)
at com.tangosol.coherence.component.application.console.Coherence.getServiceConfig(Coherence.CDB:14)
at com.tangosol.coherence.component.application.console.Coherence.ensureRunningLogger(Coherence.CDB:10)
at com.tangosol.coherence.component.application.console.Coherence.getSafeCluster(Coherence.CDB:16)
at com.tangosol.coherence.component.application.console.Coherence.getServiceConfig(Coherence.CDB:8)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.tangosol.net.CacheFactory.getServiceConfig(CacheFactory.java:1350)
at com.tangosol.net.CacheFactory.getCacheFactoryBuilderConfig(CacheFactory.java:1231)
at com.tangosol.net.CacheFactory.getCacheFactoryBuilder(CacheFactory.java:593)
at com.bea.alsb.coherence.impl.CoherenceProvider.<init>(CoherenceProvider.java:42)
at com.bea.alsb.coherence.impl.CoherenceProviderFactory.newInstance(CoherenceProviderFactory.java:21)
at com.bea.alsb.coherence.init.CoherenceAppListener.preStart(CoherenceAppListener.java:45)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:284)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:614)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
... 3 more
Caused by: java.io.IOException: Exception occurred during parsing: looking for id=10, found id=1((0,29,13) Name coherence.dtd)
at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:134)
at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:71)
at com.tangosol.run.xml.SimpleParser.parseXml(SimpleParser.java:84)
at com.tangosol.run.xml.XmlHelper.loadXml(XmlHelper.java:116)
... 43 more
The error can be caused by one of the following:
1) The operational configuration file is invalid (see $DOMAIN_DIR$/config/osb/coherence/osb-coherence-override.xml)
2) The cache configuration file is invalid (see $DOMAIN_DIR$/config/osb/coherence/osb-coherence-cache-config.xml)> -
OAM 11g 11.1.1.5 BP02 server not starting
I am getting this error, anyone had this issue and got it resolved?
[2012-05-25T10:18:59.951-06:00] [oam_server1] [ERROR] [] [Coherence] [tid: Logger@454179738 3.5.3/465p2] [userId: <anonymous>] [ecid: 11d1def534ea1be0:658dea01:13784cb045d:-8000-0000000000000002,0] [APP: oam_server] 2012-05-25 10:18:59.948/40.750 Oracle Coherence GE 3.5.3/465p2 <Error> (thread=Cluster, member=n/a): Node /10.7.1.28:9097 is not allowed to create a new cluster; WKA list: [apollo.cde.state.co.us/127.0.0.1:9095]
[2012-05-25T10:18:59.963-06:00] [oam_server1] [ERROR] [] [Coherence] [tid: Logger@454179738 3.5.3/465p2] [userId: <anonymous>] [ecid: 11d1def534ea1be0:658dea01:13784cb045d:-8000-0000000000000002,0] [APP: oam_server] 2012-05-25 10:18:59.961/40.763 Oracle Coherence GE 3.5.3/465p2 <Error> (thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_ANNOUNCE)[[
I am not sure about what cluster its talking about. I do not have a cluster. Its just one OAM server.
Edited by: PKG on Jul 13, 2012 9:53 AMI changed the port as per the doc 1384844.1 and I still get the same problem.
-
Doubt regarding Operational Config Params
Hi,
I am running a coherence cluster and in my tangosol-coherence-override.xml file :
1. While configuring WKA I am not able to use any other port other than 8088. Any way I can specify my own port.
2. And my replicated cache errors while starting up when I configure it using the services tag.Hi user1945969,
1. When you say that you can only use port 8080 when configuring WKA, do you mean this is the only port you can specify in the WKA list or the only port you can use for your cache server?
First, you can confifure WKA in your tangosol-coherence-override.xml like this
<unicast-listener>
<well-known-addresses>
<socket-address>
<address>hostname</address>
<address>1234</address>
</socket-address>
<socket-address>
<address>hostname</address>
<address>5678</address>
</socket-address>
</well-known-addresses>
</unicast-listener>You just repeat the <socket-address> sections for however many host/port combinations you want in your list.
2. You really should not need to do anything with the services section in your overrides file - in fact your tangosol-coherence-override.xml does not need to have a services section. All the settings for the services are configured in your cache configuration file. I think this was pointed out in your other post.
JK -
Does Solaris 10 support cisco Virtual Port Channels over IP?
Does anyone know if Solaris 10 support cisco Virtual Port Channels open IP?
Hi user11114413,
The issue you are seeing actually has little to do with VIP, and more to do with there being multiple IP addresses for us to choose from on your box. For such multi-IP boxes, you'll want to tell us the IP to use, and in your case you want to tell as a VIP. This can be done either by editing your operational configuration file, and including an <address> element within the <unicast-listener> element, or via the tangosol.coherence.localhost system property. For example:
<unicast-listener>
<well-known-addresses>
<socket-address id="1">
<address>1.2.3.260</address> <!--virtual ip -->
<port>8088</port>
</socket-address>
</well-known-addresses>
<address>1.2.3.260</address> <!--virtual ip -->
<port>8088</port>
</unicast-listener>or
java ... -Dtangosol.coherence.localhost=1.2.3.260If you are using the same operational configuration on all nodes in your cluster then the system property approach is likely preferable, and would only be necessary on the two machines sharing the VIP.
As for using VIP or an extended WKA list, the choice is yours, either will work. If you do go the VIP route, it would obviously be a very bad idea to simultaneously use the same VIP and port at the same time from the two machines.
thanks,
Mark
Oracle Coherence -
Separate OSB installations on same subnet interfere with one another
We currently have 1 OSB cluster installation running with two nodes, and we have set up an additional, single server installation of OSB.
What I've found is that even though I didn't install coherence at all on the single-server installation, the server logs show coherence errors indicating that the single-server installation is trying (but failing) to connect to the clustered installation. How do I turn coherence completely off for the single-server installation?user8784201 wrote:
We currently have 1 OSB cluster installation running with two nodes, and we have set up an additional, single server installation of OSB.
What I've found is that even though I didn't install coherence at all on the single-server installation, the server logs show coherence errors indicating that the single-server installation is trying (but failing) to connect to the clustered installation. How do I turn coherence completely off for the single-server installation?Starting from 11g Release 1 onwards, OSB provides an integrated solution for result caching with Oracle Coherence. In order to make your different installation work in the same subnet you need to modify the Coherence cluster from using multicast to unicast. In order to change from multicast to unicast, modify the osb-coherence-override file located at $DM/config/osb/coherence/osb-coherence-override.xml to either have different multicast ip/port for different installations or include the WKA list (nodes that should form the particular cluster).
Hope this helps!
Cheers,
NJ -
Coherence issues on SOA Cluster
Hi,
Have a 2 Node cluster od soa 11.1.1.5. Have 3 instances of 2 Node cluster running on the same machine. It's basically one for DEV,TST,UAT on the same machine. We have cronjobs that run every night shuts down all the cluster instances and then bring them back up. Recently one of our UAT soa cluster having issues. Both the Nodes come up fine but soa-infra in one node is not getting deployed and is down. I tried to manually start that node but no luck these are the errors I am getting in the Node where soa-infra is down. It's been working fine since recently. Any idea what might be wrong and where to look at. Any help is appreciated.
Inside the console all the servers are up and running but when going to Enterprise Manager it shows soa-infra down and only see one node.
####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <1354165823364> <BEA-000000> <bpel.fatal.conection.max.retry is set to 3<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.360/533.658 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2012-11-28 23:09:52.784, Address=9.9.10.95:8083, MachineId=3944, Location=site:xxorg.com,machine:web1,process:19968, Role=WeblogicServer) has been attempting to join the cluster using WKA list [web2.xxorg.com/8.8.18.85:8083, web1.xxorg.com/9.9.10.95:8083] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.>>
####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <1354165823365> <BEA-000000> <<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.363/533.661 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster that does not respond to join requests; this is usually caused by a network layer failure:
Message "SeniorMemberHeartbeat"
FromMember=Member(Id=1, Timestamp=2012-11-28 21:28:09.017, Address=8.8.18.85:8083, MachineId=3968, Location=site:xxorg.com,machine:web2,process:3396, Role=WeblogicServer)
FromMessageId=0
Internal=false
MessagePartCount=1
PendingCount=0
MessageType=17
ToPollId=0
Poll=null
Packets
[000]=Broadcast{PacketType=0x0DDF00D2, ToId=0, FromId=1, Direction=Incoming, ReceivedMillis=23:10:23.353, MessageType=17, ServiceId=0, MessagePartCount=1, MessagePartIndex=0, Body=0}
Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}
ToMemberSet=null
NotifySent=false
LastRecvTimestamp=none
MemberSet=MemberSet(Size=1, BitSetCount=1, ids=[1])
}>>
<Nov 28, 2012 11:14:53 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:637)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
Truncated. see log file for complete stacktrace
<div class="jive-quote"> </div>
.....As we have 2 physical machines and have DEV (2-node soa cluster), TST (2-node soa cluster), UAT (2-node soa cluster) all running on the same machines and comes up and down for daily DB maintenance everynight. As it the UAT environment any help appreciated in pointing to tle location to debug.
Also have Unicast operation, and use Well-Known Addressing (WKA) configured in Console under server(s)->start tab. But looks like something with coherence that's not working for the cluster to come up and failing.
ThanksThis appears related to bug 9874750. Make sure you retrieve the latest copy of the Install/Upgrade guide from support.oracle.com. Under this bug, the guide was updated to remove some preinstallation steps that were causing the installation to fail
Edited by: rwunderl on Aug 23, 2010 6:08 AM -
Oracle SOA Cluster soa-infra failing, startup coherence issues
Hi,
Have a 2 Node cluster od soa 11.1.1.5. Have 3 instances of 2 Node cluster running on the same machine. It's basically one for DEV,*TST*,*UAT* on the same machine. We have cronjobs that run every night shuts down all the cluster instances and then bring them back up. Recently one of our UAT soa cluster having issues. Both the Nodes come up fine but soa-infra in one node is not getting deployed and is down. I tried to manually start that node but no luck these are the errors I am getting in the Node where soa-infra is down. It's been working fine since recently. Any idea what might be wrong and where to look at. Any help is appreciated.
Inside the console all the servers are up and running but when going to Enterprise Manager it shows soa-infra down and only see one node.
####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <> <> <1354165823364> <BEA-000000> <bpel.fatal.conection.max.retry is set to 3<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.360/533.658 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2012-11-28 23:09:52.784, Address=9.9.10.95:8083, MachineId=3944, Location=site:xxorg.com,machine:web1,process:19968, Role=WeblogicServer) has been attempting to join the cluster using WKA list [web2.xxorg.com/8.8.18.85:8083, web1.xxorg.com/9.9.10.95:8083] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.>>
####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <> <> <1354165823365> <BEA-000000> <<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.363/533.661 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster that does not respond to join requests; this is usually caused by a network layer failure:
Message "SeniorMemberHeartbeat"
FromMember=Member(Id=1, Timestamp=2012-11-28 21:28:09.017, Address=8.8.18.85:8083, MachineId=3968, Location=site:xxorg.com,machine:web2,process:3396, Role=WeblogicServer)
FromMessageId=0
Internal=false
MessagePartCount=1
PendingCount=0
MessageType=17
ToPollId=0
Poll=null
Packets
[000]=Broadcast{PacketType=0x0DDF00D2, ToId=0, FromId=1, Direction=Incoming, ReceivedMillis=23:10:23.353, MessageType=17, ServiceId=0, MessagePartCount=1, MessagePartIndex=0, Body=0}
Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}
ToMemberSet=null
NotifySent=false
LastRecvTimestamp=none
MemberSet=MemberSet(Size=1, BitSetCount=1, ids=[1])
}>>
<Nov 28, 2012 11:14:53 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:637)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
Truncated. see log file for complete stacktrace
>
<anonymous>] [ecid: 0000JhFIXrrEWN0pnwh8iZ1Gi2DE000009,0] [APP: soa-infra] Cluster communication initialization failed. If you are using multicast, please make sure multicast is enabled on your network and that there is no interference on the address in use. Please see the documentation for more details.[[
com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
<Nov 29, 2012 9:20:13 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
)As we have 2 physical machines and have DEV (2-node soa cluster), TST (2-node soa cluster), UAT (2-node soa cluster) all running on the same machines and comes up and down for daily DB maintenance everynight. As it the UAT environment any help appreciated in pointing to tle location to debug.
Also have Unicast operation, and use Well-Known Addressing (WKA) configured in Console under server(s)->start tab. But looks like something with coherence that's not working for the cluster to come up and failing. Here are the unicast coherence settings we have for both servers in the console under Start Server tab as per Oracle EDG
WLS_SOA1
-Dtangosol.coherence.wka1=web1.xxorg.com
-Dtangosol.coherence.wka2=web2.xxorg.com
-Dtangosol.coherence.localhost=web1.xxorg.com
-Dtangosol.coherence.localport=8083
-Dtangosol.coherence.wka1.port=8083
-Dtangosol.coherence.wka2.port=8083
WLS_SOA2
-Dtangosol.coherence.wka1=web1.xxorg.com
-Dtangosol.coherence.wka2=web2.xxorg.com
-Dtangosol.coherence.localhost=web2.xxorg.com
-Dtangosol.coherence.localport=8083
-Dtangosol.coherence.wka1.port=8083
-Dtangosol.coherence.wka2.port=8083ThanksHi,
Have a 2 Node cluster od soa 11.1.1.5. Have 3 instances of 2 Node cluster running on the same machine. It's basically one for DEV,*TST*,*UAT* on the same machine. We have cronjobs that run every night shuts down all the cluster instances and then bring them back up. Recently one of our UAT soa cluster having issues. Both the Nodes come up fine but soa-infra in one node is not getting deployed and is down. I tried to manually start that node but no luck these are the errors I am getting in the Node where soa-infra is down. It's been working fine since recently. Any idea what might be wrong and where to look at. Any help is appreciated.
Inside the console all the servers are up and running but when going to Enterprise Manager it shows soa-infra down and only see one node.
####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <> <> <1354165823364> <BEA-000000> <bpel.fatal.conection.max.retry is set to 3<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.360/533.658 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2012-11-28 23:09:52.784, Address=9.9.10.95:8083, MachineId=3944, Location=site:xxorg.com,machine:web1,process:19968, Role=WeblogicServer) has been attempting to join the cluster using WKA list [web2.xxorg.com/8.8.18.85:8083, web1.xxorg.com/9.9.10.95:8083] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.>>
####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <> <> <1354165823365> <BEA-000000> <<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.363/533.661 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster that does not respond to join requests; this is usually caused by a network layer failure:
Message "SeniorMemberHeartbeat"
FromMember=Member(Id=1, Timestamp=2012-11-28 21:28:09.017, Address=8.8.18.85:8083, MachineId=3968, Location=site:xxorg.com,machine:web2,process:3396, Role=WeblogicServer)
FromMessageId=0
Internal=false
MessagePartCount=1
PendingCount=0
MessageType=17
ToPollId=0
Poll=null
Packets
[000]=Broadcast{PacketType=0x0DDF00D2, ToId=0, FromId=1, Direction=Incoming, ReceivedMillis=23:10:23.353, MessageType=17, ServiceId=0, MessagePartCount=1, MessagePartIndex=0, Body=0}
Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}
ToMemberSet=null
NotifySent=false
LastRecvTimestamp=none
MemberSet=MemberSet(Size=1, BitSetCount=1, ids=[1])
}>>
<Nov 28, 2012 11:14:53 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:637)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
Truncated. see log file for complete stacktrace
>
<anonymous>] [ecid: 0000JhFIXrrEWN0pnwh8iZ1Gi2DE000009,0] [APP: soa-infra] Cluster communication initialization failed. If you are using multicast, please make sure multicast is enabled on your network and that there is no interference on the address in use. Please see the documentation for more details.[[
com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
<Nov 29, 2012 9:20:13 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
)As we have 2 physical machines and have DEV (2-node soa cluster), TST (2-node soa cluster), UAT (2-node soa cluster) all running on the same machines and comes up and down for daily DB maintenance everynight. As it the UAT environment any help appreciated in pointing to tle location to debug.
Also have Unicast operation, and use Well-Known Addressing (WKA) configured in Console under server(s)->start tab. But looks like something with coherence that's not working for the cluster to come up and failing. Here are the unicast coherence settings we have for both servers in the console under Start Server tab as per Oracle EDG
WLS_SOA1
-Dtangosol.coherence.wka1=web1.xxorg.com
-Dtangosol.coherence.wka2=web2.xxorg.com
-Dtangosol.coherence.localhost=web1.xxorg.com
-Dtangosol.coherence.localport=8083
-Dtangosol.coherence.wka1.port=8083
-Dtangosol.coherence.wka2.port=8083
WLS_SOA2
-Dtangosol.coherence.wka1=web1.xxorg.com
-Dtangosol.coherence.wka2=web2.xxorg.com
-Dtangosol.coherence.localhost=web2.xxorg.com
-Dtangosol.coherence.localport=8083
-Dtangosol.coherence.wka1.port=8083
-Dtangosol.coherence.wka2.port=8083Thanks -
Hi,
I am trying to start coherence server on two different machines. I have modified tangosol-coherence-override-dev.xml for include ipaddress to WKA list (Followed the instruction from http://confluence.atlassian.com/display/CONFKB/How+to+Configure+a+Cluster+Without+Multicast+Traffic).
When I start the coherence server on two machines. Both machines coherences servers are not started, It waiting for another node to connect. Got the below error message
2010-12-26 14:16:11.469/280.351 Oracle Coherence GE n/a <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known node s to respond
Exception in thread "main" com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=ServiceMemberSet(
OldestMember=n/a
ActualMemberSet=MemberSet(Size=0, BitSetCount=0
MemberId/ServiceVersion/ServiceJoined/MemberState
Thanks in advance for your help.The request timeout exception occurred while starting a service.
The is a general document on metalink (document 845363.1) which talks about several potential reasons for service timeout.
However I suspect that there is a problem in the WKA configuration, as this error can be seen using an unreachable hostname in the <address> element -
I stopped by WebLogic Server, but the script failed, so I had to kill -9 the startWeblogic.s process and the java process. Now I cannot restart the server. Whenever I try, I get the following error:
<Jan 6, 2015 12:17:48 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY.>
<Jan 6, 2015 12:17:48 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<Jan 6, 2015 12:17:48 PM PST> <Notice> <Log Management> <BEA-170032> <The Server has detected ODL configuration for java.util.logging. The PlatformLoggerLevels attribute configuration on the LogMBean will be ignored.>
<Error>: Failed to write a log message
<Jan 6, 2015 12:18:07 PM PST> <Error> <com.oracle.coherence> <BEA-000000> <2015-01-06 12:18:07.572/40.183 Oracle Coherence GE 12.1.3.0.0 <Error> (thread=Cluster, member=1): StopRunning ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_JOINED), Id=0, Version=12.1.3, OldestMemberId=1} due to unhandled exception: >
Any suggestions for how to resolve this?
Thank you!
DanThanks for the advice. Unfortunately, my coherence is still failing somehow. It is strange because my Admin server was working up until yesterday. In any event, no matter how many domains I create, I still get the following error:
<Logger@1032327427 12.1.3.0.0> <<anonymous>> <> <> <1420656852991> <BEA-000000> <2015-01-07 10:54:12.991/60.973 Oracle Coherence GE 12.1.3.0.0 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2015-01-07 10:53:42.419, Address=<ipaddress>:7202, MachineId=9428, Location=site:,machine:hostname,process:26602,member:AdminServer, Role=WeblogicServer) has been attempting to join the cluster using WKA list [/<ipaddress>:7201] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.>
Thanks again for your hlep,
Daniel
Maybe you are looking for
-
RFC execution process terminates the Java Process
Hi All, we have a RFC which returns large data with export parameter. While executing JCO.client.execute(), java process is getting terminated. I tried to set the more heap size but of no use. It didn't give any OutOfMemory either. The JCO trace fi
-
All of a sudden my Ipod won't turn off. I hold down the button like I use to turn it off, but nothing happens. Can anyone help?
-
Battery For Late 2008 Aluminum MacBook?
Where can I get a genuine Apple battery for my Late 2008 Aluminum MacBook?
-
Why does my html code becomes unreadable overview on the search engine adobe edge code
Hello Why does my html code becomes unreadable overview on the search engine? Everything alligner left, the images no longer appear and the page background template either. I am new in the html code, but I have nothing to change this one and the othe
-
Waiting on MacBook, Can't see or open on iPhone
I have a few problems with outsourcing (iCloud). For one, a lot of documents I wrote, in Text Edit and in Pages, on my MacBook with OS 10.8.5, are labeled as "waiting." On my iPhone with iOS 8.1, in Pages app, I cannot see any of the Pages documents,