CUMP 8.5; Should Director Fail-Over Cause Audio Conf Be Discon?
We have a two region CUMP 8.5.5.14 global deployment with WebEx Type II deployment, which we are now piloting. We have a primary Director in one region and a backup Director in another. During fail-over testing in which we establish an audio/web meeting (using the primary Director to setup the call), and we force a failover of the primary Director (by disconnecting network connection(s). After approximately 5 minutes, the audio conference is disconnected. Callers can call back in, but I’m trying to understand whether this Director failover behavior is expected, where the audio conference would be disconnected. Otherwise , failover to backup Director does appear to be operating OK.
Thanks.
Hi Michael,
That is expected behavior.
http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace/8_5/english/administration/topology_management.html#wpxref82514
Configuring Meeting Director Nodes
Your first node is automatically configured as the Primary Meeting Director node. The second node you add to your system is automatically configured as the Secondary Meeting Director node. If your Primary Meeting Director node fails, your Secondary Meeting Director node becomes the active Meeting Director. Any conferences currently running on the system are interrupted but attendants can dial back in immediately.
-Dejan
Similar Messages
-
Stateful bean not failing over
I have a cluster of two servers and a Admin server. Both servers are running NT
4 sp6 and WLS6 sp1.
When I stop one of the servers, the client does n't automatically failover to
the other server, instead it fails unable to contact server that has failed.
My bean is configured to have its home clusterable and is a stateful bean. My
client holds onto the remote interface, and makes calls through this. If Server
B fails then it should automatically fail over to server A.
I have tested my multicast address and all seems to be working fine between servers,
my stateless bean work well, load balancing between servers nicely.
Does anybody have any ideas, regarding what could be causing the stateful bean
remote interface not to be providing failover info.
Also is it true that you can have only one JMS destination queue/topic per cluster..The
JMS cluster targeting doesn't work at the moment, so you need to deploy to individual
servers?
Thanks
Did you enable stateful session bean replication in the
weblogic-ejb-jar.xml?
-- Rob
Wayne Highland wrote:
>
> I have a cluster of two servers and a Admin server. Both servers are running NT
> 4 sp6 and WLS6 sp1.
> When I stop one of the servers, the client does n't automatically failover to
> the other server, instead it fails unable to contact server that has failed.
>
> My bean is configured to have its home clusterable and is a stateful bean. My
> client holds onto the remote interface, and makes calls through this. If Server
> B fails then it should automatically fail over to server A.
>
> I have tested my multicast address and all seems to be working fine between servers,
> my stateless bean work well, load balancing between servers nicely.
>
> Does anybody have any ideas, regarding what could be causing the stateful bean
> remote interface not to be providing failover info.
>
> Also is it true that you can have only one JMS destination queue/topic per cluster..The
> JMS cluster targeting doesn't work at the moment, so you need to deploy to individual
> servers?
>
> Thanks
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com
-
Sun Directory Proxy 5.2 fail over?
How do i set up DIR Proxy to fail over on the proxy end. I understand if a directory goes down, but what is the proxy goes down. How to i assure that the client will fail over to another proxy?
There are at least three options, in order of least to most desirable:
1. Have the client maintain a failover list of proxy servers. If it is unable to contact the first server in its local list, have it try the next server.
Pros: No additional network complexity or cost.
Cons: May not be possible unless you have access to client code; if proxy server addresses change or additional proxies are added, all clients configurations must be updated.
2. Use round-robin DNS. Point the client to the round robin address and let DNS determine which proxy server should be contacted.
Pros: Easy to implement on client side; load balances traffic equally across your proxy servers.
Cons: A proxy server failure will cause your clients to fail 1/nth of the time (where n is the number of proxy servers in the RR configuration).
3. Use an IP load balancing device (such as a Cisco Distributed Director or F5 BigIP) and have all clients point to the virtual IP of that device.
Pros: Automatically takes failed proxy servers out of the pool; additional load balancing configurations can be maintained on the hardware load balancing device. If you have redundant load balancers, a client should nearly always be able to connect.
Cons: Additional cost and network complexity -
SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur
Hi All,
I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
advice in the end was to post a question here.
SQL Server Nodes, 2014 (12.0.2480.0)
1 Share witness (on separate subnet)
1 Cluster
1 Listener
I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
a small table and hit execute.
The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
Availability DB is 200Mb and is not actively used. The nodes are synchronised.
SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
Questions:
1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
Msg 983, Level 14, State 1, Line 2
Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
00001090.00002128::2015/02/25-03:05:08.255 INFO [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:10.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:11.888 INFO [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
00001090.00002698::2015/02/25-03:05:11.889 INFO [GUM] Node 2: Processing RequestLock 2:49
00001090.00002128::2015/02/25-03:05:11.890 INFO [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
00001090.00002698::2015/02/25-03:05:11.890 INFO [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
00001090.00002128::2015/02/25-03:05:12.890 INFO [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:15.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:16.988 INFO [GUM] Node 2: Processing RequestLock 1:28
Thanks in advance.
KeeganHi Keegan,
From these event log , what I can see is "Sending request Netname" wasted the time .
Could you please tell us the network configuration of that cluster nodes ?
If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
https://support.microsoft.com/kb/258750?wa=wsignin1.0
After that please test again .
Best Regards,
Elton JI
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] . -
OCR and voting disks on ASM, problems in case of fail-over instances
Hi everybody
in case at your site you :
- have an 11.2 fail-over cluster using Grid Infrastructure (CRS, OCR, voting disks),
where you have yourself created additional CRS resources to handle single-node db instances,
their listener, their disks and so on (which are started only on one node at a time,
can fail from that node and restart to another);
- have put OCR and voting disks into an ASM diskgroup (as strongly suggested by Oracle);
then you might have problems (as we had) because you might:
- reach max number of diskgroups handled by an ASM instance (63 only, above which you get ORA-15068);
- experiment delays (especially in case of multipath), find fake CRS resources, etc.
whenever you dismount disks from one node and mount to another;
So (if both conditions are true) you might be interested in this story,
then please keep reading on for the boring details.
One step backward (I'll try to keep it simple).
Oracle Grid Infrastructure is mainly used by RAC db instances,
which means that any db you create usually has one instance started on each node,
and all instances access read / write the same disks from each node.
So, ASM instance on each node will mount diskgroups in Shared Mode,
because the same diskgroups are mounted also by other ASM instances on the other nodes.
ASM instances have a spfile parameter CLUSTER_DATABASE=true (and this parameter implies
that every diskgroup is mounted in Shared Mode, among other things).
In this context, it is quite obvious that Oracle strongly recommends to put OCR and voting disks
inside ASM: this (usually called CRS_DATA) will become diskgroup number 1
and ASM instances will mount it before CRS starts.
Then, additional diskgroup will be added by users, for DATA, REDO, FRA etc of each RAC db,
and will be mounted later when a RAC db instance starts on the specific node.
In case of fail-over cluster, where instances are not RAC type and there is
only one instance running (on one of the nodes) at any time for each db, it is different.
All diskgroups of db instances don't need to be mounted in Shared Mode,
because they are used by one instance only at a time
(on the contrary, they should be mounted in Exclusive Mode).
Yet, if you follow Oracle advice and put OCR and voting inside ASM, then:
- at installation OUI will start ASM instance on each node with CLUSTER_DATABASE=true;
- the first diskgroup, which contains OCR and votings, will be mounted Shared Mode;
- all other diskgroups, used by each db instance, will be mounted Shared Mode, too,
even if you'll take care that they'll be mounted by one ASM instance at a time.
At our site, for our three-nodes cluster, this fact has two consequences.
One conseguence is that we hit ORA-15068 limit (max 63 diskgroups) earlier than expected:
- none ot the instances on this cluster are Production (only Test, Dev, etc);
- we planned to have usually 10 instances on each node, each of them with 3 diskgroups (DATA, REDO, FRA),
so 30 diskgroups each node, for a total of 90 diskgroups (30 instances) on the cluster;
- in case one node failed, surviving two should get resources of the failing node,
in the worst case: one node with 60 diskgroups (20 instances), the other one with 30 diskgroups (10 instances)
- in case two nodes failed, the only node survived should not be able to mount additional diskgroups
(because of limit of max 63 diskgroup mounted by an ASM instance), so all other would remain unmounted
and their db instances stopped (they are not Production instances);
But it didn't worked, since ASM has parameter CLUSTER_DATABASE=true, so you cannot mount 90 diskgroups,
you can mount 62 globally (once a diskgroup is mounted on one node, it is given a number between 2 and 63,
and other diskgroups mounted on other nodes cannot reuse that number).
So as a matter of fact we can mount only 21 diskgroups (about 7 instances) on each node.
The second conseguence is that, every time our CRS handmade scripts dismount diskgroups
from one node and mount it to another, there are delays in the range of seconds (especially with multipath).
Also we found inside CRS log that, whenever we mounted diskgroups (on one node only), then
behind the scenes were created on the fly additional fake resources
of type ora*.dg, maybe to accomodate the fact that on other nodes those diskgroups were left unmounted
(once again, instances are single-node here, and not RAC type).
That's all.
Did anyone go into similar problems?
We opened a SR to Oracle asking about what options do we have here, and we are disappointed by their answer.
Regards
OscarHi Klaas-Jan
- best practises require that also online redolog files are in a separate diskgroup, in case of ASM logical corruption (we are a little bit paranoid): in case DATA dg gets corrupted, you can restore Full backup plus Archived RedoLog plus Online Redolog (otherwise you will stop at the latest Archived).
So we have 3 diskgroups for each db instance: DATA, REDO, FRA.
- in case of fail-over cluster (active-passive), Oracle provide some templates of CRS scripts (in $CRS_HOME/crs/crs/public) that you edit and change at your will, also you might create additionale scripts in case of additional resources you might need (Oracle Agents, backups agent, file systems, monitoring tools, etc)
About our problem, the only solution is to move OCR and voting disks from ASM and change pfile af all ASM instance (parameter CLUSTER_DATABASE from true to false ).
Oracle aswers were a litlle bit odd:
- first they told us to use Grid Standalone (without CRS, OCR, voting at all), but we told them that we needed a Fail-over solution
- then they told us to use RAC Single Node, which actually has some better features, in csae of planned fail-over it might be able to migreate
client sessions without causing a reconnect (for SELECTs only, not in case of a running transaction), but we already have a few fail-over cluster, we cannot change them all
So we plan to move OCR and voting disks into block devices (we think that the other solution, which needs a Shared File System, will take longer).
Thanks Marko for pointing us to OCFS2 pros / cons.
We asked Oracle a confirmation that it supported, they said yes but it is discouraged (and also, doesn't work with OUI nor ASMCA).
Anyway that's the simplest approach, this is a non-Prod cluster, we'll start here and if everthing is fine, after a while we'll do it also on Prod ones.
- Note 605828.1, paragraph 5, Configuring non-raw multipath devices for Oracle Clusterware 11g (11.1.0, 11.2.0) on RHEL5/OL5
- Note 428681.1: OCR / Vote disk Maintenance Operations: (ADD/REMOVE/REPLACE/MOVE)
-"Grid Infrastructure Install on Linux", paragraph 3.1.6, Table 3-2
Oscar -
Failing over Oracle connections in a pool
Hi,
This message is probably a bit out of context (I've already posted
it to the JDBC group). I post here as well, since I guess it's
the place where people have the most experience with clustering
and HA. Original posting below...
Could you please tell me whether, yes or no, connections to an
Oracle database should fail over (when the database fails over
to another machine)? I use Oracle's Transparent Application Failover
(configured via Net8) with Weblogic 6 on Linux and Oracle 8.1.7
on Solaris/SPARC.
If this doesn't work in my configuration, is there any configuration
where it should work? (Another version of Oracle, WLS, OS, ...)
When I try TAF using the PetStore application, I get exceptions
related to no being connected to the database.
If TAF doesn't work with WebLogic, is there a way to work around
the problem? Can I catch these exceptions and renew the connections
in the pool? Or, what else is possible...?
I'd appreciate any help. I'd like to demonstrate our HA product
with WLS. If it doesn't work, I'll turn to iPlanet instead. Pity,
I really like WLS!
Thanks in advance for any help or advice!
Regards, Frank Olsen
Hi (Frank ;-)
I got carried away a bit too fast...
Some more testing shows that it doesn't work in all cases:
- when someone is trying to check out the shopping cart when the
the database fails (and fails over), I get exceptions once the
databses has restarted on the backup node
- the exceptions are related to some transactions being rolled
back and Oracle stating that it couldn't safely replay the transactions
- browsing the categories still works fine
- all access to the shopping cart and sign-in/sign-out causes time-outs
and exceptions
Any ideas what may cause this problem, please?
Regards,
Frank Olsen
"Frank Olsen" <[email protected]> wrote:
>
>Hi,
>
>TAF worked with WLS 6 on NT with the Oracle 8.1.7 client!
>
>Has anyone tested it on Solaris/SPARC?
>
>Regards,
>Frank Olsen
>
>
>
>"Frank Olsen" <[email protected]> wrote:
>>
>>Hi,
>>
>>Most of my question below is still valid (in particular
>>concerning
>>whether TAF should work with WLS on some or all platforms
>>and
>>versions).
>>
>>However, when I tested TAF with the Oracle client (sqlplus)
>>there
>>also was no failover of the (one) connection. I then
>checked
>>the
>>`V$SESSION' view and the colums related to failover showed
>>that
>>TAF was not correctly configured. Strange because I copied
>>the
>>`tnsnames.ora' parameters from the Oracle documentation
>>for TAF.
>>
>>Has anyone managed to configure and use TAF, with or
>without
>>WLS?!
>>
>>Thanks in advance for your help!
>>
>>Regards,
>>Frank Olsen
>>
>>
>>"Frank Olsen" <[email protected]> wrote:
>>>
>>>Hi,
>>>
>>>This message is probably a bit out of context (I've
>already
>>>posted
>>>it to the JDBC group). I post here as well, since I
>guess
>>>it's
>>>the place where people have the most experience with
>>clustering
>>>and HA. Original posting below...
>>>
>>>----
>>>
>>>Could you please tell me whether, yes or no, connections
>>>to an
>>>Oracle database should fail over (when the database
>fails
>>>over
>>>to another machine)? I use Oracle's Transparent Application
>>>Failover
>>>(configured via Net8) with Weblogic 6 on Linux and Oracle
>>>8.1.7
>>>on Solaris/SPARC.
>>>
>>>If this doesn't work in my configuration, is there any
>>>configuration
>>>where it should work? (Another version of Oracle,
>WLS,
>>>OS, ...)
>>>
>>>
>>>When I try TAF using the PetStore application, I get
>>exceptions
>>>related to no being connected to the database.
>>>
>>>If TAF doesn't work with WebLogic, is there a way to
>>work
>>>around
>>>the problem? Can I catch these exceptions and renew
>the
>>>connections
>>>in the pool? Or, what else is possible...?
>>>
>>>I'd appreciate any help. I'd like to demonstrate our
>>HA
>>>product
>>>with WLS. If it doesn't work, I'll turn to iPlanet instead.
>>>Pity,
>>>I really like WLS!
>>>
>>>Thanks in advance for any help or advice!
>>>
>>>Regards, Frank Olsen
>>>
>>
>
-
Is my installation of SQL Server Fail Over cluster correct?
I made a 2 node SQL Server 2012 fail over cluster but having some problems during installation so I wanted to know if the steps below I performed are correct.
Hardware
Node1 192.168.1.10
Node2 192.168.1.11
Added following entries in DNS
cluster.domain.local 192.168.1.12 (for Windows Cluster)
msdtc.domain.local 192.168.1.13 (for MSDTC)
sql.domain.local 192.168.1.14 (for SQL Server Cluster)
Cluster Storage
Disk1 (for Quorum)
Disk2 (for MSDTC
Disk3 (for SQL Server)
Now comes the installation. I am performing all these steps as DOMAIN ADMIN.
1. First I installed clustering role on both nodes
2. Then I ran fail over validation wizard on Node1 adding both nodes which went fine (there were some warnings)
3. Then I made a Windows Cluster on Node1 using these two nodes. I gave the name and IP to this cluster which I wrote above i.e. cluster.domain.local 192.168.1.12
4. Cluster was created and boths nodes are UP.
Now I want to ask a question here. Is it best practice to perform the above operation using DOMAIN ADMIN? Or if I use a standard domain user account with local admin rights, will it work? If not then exactly what rights are required to perform this operation.
5. Then I installed "Application Server" role on both Node1 and Node2 and also added "Distributed Transaction" feature
6. Then I right clicked on Windows Cluster I created and added a new role/feature which is "DTC"
7. I gave it the same name which I wrote above i.e. msdtc.domain.local 192.168.1.13
8. MSDTC was created but when it tried to UP its service, it threw an error. Upon investigation it turns out the Windows Cluster cluster.domain.local doesn't have proper rights to created some objects in AD. I didn't know what rights to give so I gave it full
permission and after that when I created MSDTC again, the service went up fine.
So I want to know what rights does cluster.domain.com require to make MSDTC?
Am I doing good so far?Hello,
>>Then I made a Windows Cluster on Node1 using these two nodes. I gave the name and IP to this cluster which I wrote above i.e. cluster.domain.local 192.168.1.10
Hello I suppose this IP was physical node IP windows cluster IP was 192.168.1.12 I suppose yo must have given this IP as windows cluster IP.10 and 11 are physical nodes in Cluster but 12 is Cluster IP .Correct me if I am wrong.
Did you do failover and failback to check whether cluster is configured correctly or not ,If not please do it .
>>Then I ran fail over validation wizard on Node1 adding both nodes which went fine (there were some warnings)
Please remove warnings also ,it might cause issue.Not sure its correct every time but make sure cluster validation should be free of error and warning.
>>Now I want to ask a question here. Is it best practice to perform the above operation using DOMAIN ADMIN?
You can do it with domain admin account as this is required to create Cluster NAme object(CNO) in domain and local account might not have that right so I would say its ok.
>>I gave it the same name which I wrote above i.e. msdtc.domain.local
192.168.1.11
again this IP is node 2 IP how can you give it to MSDTC.Use below link for reference
http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
SQL 2005 cluster rejects SQL logins when in failed over state
When SQL 2005 SP4 on Windows 2003 server cluster is failed over from Server_A to Server_B, it rejects all SQL Server logins. domain logins are OK. The message is "user is not associated with a trusted server connection", then the IP of the
client. This is error 18452. Anyone know how to fix this? They should work fine from both servers. We think this started just after installing SP4.
DaveKHello,
The connection string is good, you're definitely using sql auth.
LoginMode on Server_B is REG_DWORD 0x00000001 (1) LoginMode on Server_A is REG_DWORD 0x00000002 (2) Looks like you are on to something. I will schedule another test failover. I assume a 2 is mixed mode? If so, why would SQL allow two different modes
on each side of a cluster?
You definitely have a registry replication issue, or at the very least a registry that isn't in sync with the cluster. This could happen for various reasons, none of which we'll probably find out about now, but never the less...
A good test would be to set it to windows only on Node A, wait a minute and then set it to Windows Auth and see if that replicates the registry setting across nodes correctly - this is actually the windows level and doesn't have anything to do with SQL Server.
SQL Server reads this value from the registry and it is not stored inside any databases (read, nothing stored in the master database) as such it's a per machine setting. Since it's not set correctly on Node B, when SQL server starts up it correctly reads
that registry key and acts on it as it should. The culprit isn't SQL Server, it's Windows Clustering.
Hopefully this makes a little more sense now. You can actually just edit the registry setting to match Node A and fail over to B, everything should work correctly. It doesn't help you with a root cause analysis which definitely needs to be done as who knows
what else may not be correctly in sync.
Sean Gallardy | Blog |
Twitter -
WLS6.1sp1 stateful EJB problem = load-balancing and fail over
I have three problem
1. I have 2 clustered server. my weblogic-ejb-jar.xml is here
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>DBStatefulEJB</ejb-name>
<stateful-session-descriptor>
<stateful-session-cache>
<max-beans-in-cache>100</max-beans-in-cache>
<idle-timeout-seconds>120</idle-timeout-seconds>
</stateful-session-cache>
<stateful-session-clustering>
<home-is-clusterable>true</home-is-clusterable>
<home-load-algorithm>RoundRobin</home-load-algorithm>
<home-call-router-class-name>common.QARouter</home-call-router-class-name>
<replication-type>InMemory</replication-type>
</stateful-session-clustering>
</stateful-session-descriptor>
<jndi-name>com.daou.EJBS.solutions.DBStatefulBean</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
when i use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
and deploy this ejb, exception cause
<Warning> <Dispatcher> <RuntimeException thrown b
y rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '2903098842
594628659S:203.231.15.167:[5001,5001,5002,5002,5001,5002,-1]:mydomain:cluster1',
oid: '9', implementation: 'weblogic.jndi.internal.RootNamingNode@5f39bc''
java.lang.IllegalArgumentException: Failed to instantiate weblogic.rmi.cluster.B
asicReplicaHandler due to java.lang.reflect.InvocationTargetException
at weblogic.rmi.cluster.ReplicaAwareInfo.instantiate(ReplicaAwareInfo.ja
va:185)
at weblogic.rmi.cluster.ReplicaAwareInfo.getReplicaHandler(ReplicaAwareI
nfo.java:105)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.initialize(ReplicaAwareRem
oteRef.java:79)
at weblogic.rmi.cluster.ClusterableRemoteRef.initialize(ClusterableRemot
eRef.java:28)
at weblogic.rmi.cluster.ClusterableRemoteObject.initializeRef(Clusterabl
eRemoteObject.java:255)
at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemote
Object.java:149)
at weblogic.jndi.internal.BasicNamingNode.rebindHere(BasicNamingNode.jav
a:392)
at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.j
ava:142)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
2)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
9)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
9)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
9)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
9)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
So do i must use it or not???
2. When i don't use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
, there's no exception
but load balancing does not happen. According to the document , there's must load
balancing when i call home.create() method.
my client program goes here
DBStateful the_ejb1 = (DBStateful) PortableRemoteObject.narrow(home.create(),
DBStateful.class);
DBStateful the_ejb2 = (DBStateful) PortableRemoteObject.narrow(home.create(3),
DBStateful.class);
the result is like that
the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@4695a6)/397
the_ejb2 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@acf6e)/398
or
the_ejb1 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@252fdf)/380
the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@6a0252)/381
I think the result should be like under one... isn't it??
the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@4695a6)/397
the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@6a0252)/381
In this case i think the_ejb1 and the_ejb2 must have instance in different cluster
server
but they go to one server .
3. If i don't use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>",
"<replication-type>InMemory</replication-type>" then load balancing happen but
there's no fail-over
So how can i get load-balancing and fail over together??
I have three problem
1. I have 2 clustered server. my weblogic-ejb-jar.xml is here
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>DBStatefulEJB</ejb-name>
<stateful-session-descriptor>
<stateful-session-cache>
<max-beans-in-cache>100</max-beans-in-cache>
<idle-timeout-seconds>120</idle-timeout-seconds>
</stateful-session-cache>
<stateful-session-clustering>
<home-is-clusterable>true</home-is-clusterable>
<home-load-algorithm>RoundRobin</home-load-algorithm>
<home-call-router-class-name>common.QARouter</home-call-router-class-name>
<replication-type>InMemory</replication-type>
</stateful-session-clustering>
</stateful-session-descriptor>
<jndi-name>com.daou.EJBS.solutions.DBStatefulBean</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
when i use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
and deploy this ejb, exception cause
<Warning> <Dispatcher> <RuntimeException thrown b
y rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '2903098842
594628659S:203.231.15.167:[5001,5001,5002,5002,5001,5002,-1]:mydomain:cluster1',
oid: '9', implementation: 'weblogic.jndi.internal.RootNamingNode@5f39bc''
java.lang.IllegalArgumentException: Failed to instantiate weblogic.rmi.cluster.B
asicReplicaHandler due to java.lang.reflect.InvocationTargetException
at weblogic.rmi.cluster.ReplicaAwareInfo.instantiate(ReplicaAwareInfo.ja
va:185)
at weblogic.rmi.cluster.ReplicaAwareInfo.getReplicaHandler(ReplicaAwareI
nfo.java:105)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.initialize(ReplicaAwareRem
oteRef.java:79)
at weblogic.rmi.cluster.ClusterableRemoteRef.initialize(ClusterableRemot
eRef.java:28)
at weblogic.rmi.cluster.ClusterableRemoteObject.initializeRef(Clusterabl
eRemoteObject.java:255)
at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemote
Object.java:149)
at weblogic.jndi.internal.BasicNamingNode.rebindHere(BasicNamingNode.jav
a:392)
at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.j
ava:142)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
2)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
9)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
9)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
9)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
9)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
So do i must use it or not???
2. When i don't use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
, there's no exception
but load balancing does not happen. According to the document , there's must load
balancing when i call home.create() method.
my client program goes here
DBStateful the_ejb1 = (DBStateful) PortableRemoteObject.narrow(home.create(),
DBStateful.class);
DBStateful the_ejb2 = (DBStateful) PortableRemoteObject.narrow(home.create(3),
DBStateful.class);
the result is like that
the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@4695a6)/397
the_ejb2 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@acf6e)/398
or
the_ejb1 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@252fdf)/380
the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@6a0252)/381
I think the result should be like under one... isn't it??
the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@4695a6)/397
the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
daryReplicaHandler@6a0252)/381
In this case i think the_ejb1 and the_ejb2 must have instance in different cluster
server
but they go to one server .
3. If i don't use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>",
"<replication-type>InMemory</replication-type>" then load balancing happen but
there's no fail-over
So how can i get load-balancing and fail over together??
-
Http cluster servlet not failing over when no answer received from server
I am using weblogic 510 sp9. I have a weblogic server proxying all requests to
a weblogic cluster using the httpclusterservlet.
When I kill the weblogic process servicing my request, I see the next request
get failed over to the secondary server and all my session information has been
replicated. In short I see the behavior I expect.
r.troon
However, when I either disconnect the primary server from the network or just
switch this server off, I just get a message back
to the browser - "unable to connect to servers".
I don't really understand why the behaviour should be different . I would expect
both to failover in the same manner. Does the cluster servlet only handle tcp
reset failures?
Has anybody else experience this or have any ideas.
Thanks
I think I might have found the answer......
The AD objects for the clusters had been moved from the Computers OU into a newly created OU. I'm suspecting that the cluster node computer objects didn't have perms to the cluster object within that OU and that was causing the issue. I know I've seen cluster
object issues before when moving to a new OU.
All has started working again for the moment so I now just need to investigate what permissions I need on the new OU so that I can move the cluster object in. -
3 node cluster with 1 vInstance. vInstance can not to fail-over to one specific node.
I have a 3 node cluster all running Windows Server 2008 R2. Roughly once a month I see my vInstance become degraded and attempt to fail-over. Everything is good as long as it fail-over to SQL01 or SQL02. However if it attempts to fail-over to SQL03, it does
not come online
Quick resolution is to move it manually to SQL01 or SQL02. What could be causing it to fail every time on SQL03.
A couple points:
I did not build the environment.
I am not a DBA.
I only have general knowledge of SQL clustering.
I always get two EVENT ID's: 1069
Cluster resource 'SQL Server (VSQL04)' in clustered service or application 'SQL Server (VSQL04)' failed.
and then
EVENT ID 1205
The Cluster service failed to bring clustered service or application 'SQL Server (VSQL04)' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Where should I begin to look for issues?Here is the cluster event prior to offline state. I will have to go check the cluster log.
The Cluster service failed to bring clustered service or application 'SQL Server (VSQL04)' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
i do not think this helps.. it just says..a resource in offline state.. you need to dig more and see which one it is and why it did not come banck on ..it should be mentioned in the log and\or event viewer.
Hope it Helps!! -
Weblogic 11g Fail over Cluster
Hi,
I'm Using WebLogic Server 11g (10.3.6). I have installed ATG and Commerce reference store in same machine with weblogic.(Endeca Has Separate server). In addition to i have oracle DB server and apache server.
I did following things.
*I have configure one physical machine (WM1) with Web Logic Domain. Other physical machine (WM2) i installed weblogic.
*I configured ATG and Commerce reference store in WM1.(Using cim.sh)
*and Configured Endeca app for WM1.
*I am using weblogic for production environment. I Created 3 Managed servers according to cim.sh production.publishing and staging.
I want to Create fail-over Cluster with WM1 and WM2.
Now is it possible to create fail over cluster?
Please give me instructions ,suggestions or guide to configure cluster for this environments.
Thanks
Nish.Try to see the cluster log information, you should see an event that describes the error that causes the cluster reource to fail.
Regards, Samir Farhat Infrastructure and Virtualization Consultant || Virtualization, Cloud, Azure ? Follow and Ask here https://buildwindows.wordpress.com -
Load Balance Network Cards and Fail over services
Hi,
Im looking at setting up 2 MAC server each with basic services (ie AFP, Open Driectory, software updates and DHCP)
Both servers are less then 12 months old and are both attached with GB ports to the RAID where all the user data is stored.
My questions is how to I setup the 2 network interface cards to act as one and load balance the traffic accross both interfaces?
also I was wondering if it was possible to fail over AFP services, so if one server went down the other would pickup file services where it left off?
I know how to fail over OD and the other services dont matter to much.
Thanks in advance for your assistanceMy questions is how to I setup the 2 network interface cards to act as one and load balance the traffic accross both interfaces?
This is simple link aggregation in System Preferences -> Network
Click the + button at the bottom and choose new Link Aggregate. Choose the existing interfaces (presumably en0 and en1) and you're set.
Note that this requires support in the switch the server is connected to (it needs to support LACP), and that you will bounce your network connection when you set this up (so don't do it when the server is actively servicing clients)
also I was wondering if it was possible to fail over AFP services, so if one server went down the other would pickup file services where it left off?
It's possible, but you need to be very careful with regards to data integrity. For example, typically each server is going to have a local directory (or directories) that are shared. If Server A fails and Server B takes over, how do you intend to ensure that Server B's data is up-to-date, especially with regard to files that might have been in use at the time?
It's a tricky problem to solve without putting the data on a shared storage device using something like XSAN to manage arbitration, and now you could be talking serious $$$s.
I'd recommend looking closely at your file serving needs and work out if it's necessary, or whether you could get by with dividing the load across servers (e.g. some sharepoints are on one server, other sharepoints on the other) so that only a subset of your users are impacted should one server fail.
File synchronization/replication is a major issue (read $$$$$) for a lot of companies. -
Cisco ISE 1.1.1.268 Giving error (Report Generation failed. Cause: Null)
I have this issue and I would be very thankful if someone has the answer for this. When I am trying to access Operation > Report > Catalog > Posture > Posture Detail Assessment & clicking on any posture session detail icon. I am getting following attached errors.
1. Report Generation failed. Cause: Null
2. Cannot execute the statement.
Does anyone knows how to get rid of this error & to get access of posture detail.
ThanksThe error message means that Active Directory server Reject the authentication attempt
as for some reasons the user account got locked.I guess, You should ask your AD Team to check in the AD
Event Logs why did the user account got locked.
Under Even Viewers, You can find it out
Regards
Minakshi (Do rate the helpful posts) -
Hi all,
1. I setup a pool with three Front End servers (FQDN of pool is pool.site1.sip96x2.com and it's pointed to IP address of three Front End servers). Everything works fine. But When I disable network interface on FE1 and FE2, the Lync clients are disconnected.
I haven't understood clearly how the Lync clients failed over in a pool? Please clarify to me.
2. I have two central site (Root site and Primary site, they have different domain sip96x2.com and site1.sip96x2.com). The simple URL dialin is pointed to Front End server at Root site. So if the link between Root site and Primary site is down, how can the
users at Primary site connect to dialin URL?
3. In building topology for Front End pool, I checked Override FQDN internal web service and the FQDN is "poolint.site1.sip96x2.com". I created three A records "poolint.site1.sip96x2.com" and pointed to three IP addresses of Front End
servers. Is it right?
Thanks so much!Ah ok, well first thing if I am reading this correctly, pool pairing Standard with Enterprise is not supported. You should only pair Standard with Standard and Enterprise with Enterprise (even though topology builder won't stop you) Take a look here for
support scenarios http://technet.microsoft.com/en-us/library/jj204697.aspx
To deal with the simple URLs in the event of failover you need to add them using Powershell. Take a look at this article which explains and gives an example: http://blogs.perficient.com/microsoft/2012/01/configuring-simple-urls-for-multiple-lync-pools/
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)
Maybe you are looking for
-
BSI Tax Factory Upgrade 8.0 to 9.0
Hi BSI, We are upgrading our BSI tax Factory from 8.0 to 9.0. We are running: Windows 2008 R2 SQL Server version 10.50.1777 I'm able to connect to the database using login TF90 through SQL Server Management Studio, the ODBC Data Source Administrator
-
How do I determine the interrupt detection sequences for an HP 82350A PCI GPIB card?
I am trying to install an HP 82350A PCI GPIB card in CentOS 6.4. I have installed NI-VISA 5.4. I tinkered around and found driverwizard in /usr/local/bin. It creates an ini file to control the PCI GPIB card. I had somehow succeeded in detecting the c
-
I'm using Aperture with my MacBook Pro and a second display. I have designated the external monitor as the secondary viewer and have Aperture secondary viewer control set to Alternate. This works great for viewing the selected image large but croppin
-
Read Timeout on non-blocking sockets
Hi, I was wondering if there is a way to specify a read timeout (like setSoTimeout for synchronous sockets) when using a non-blocking socket. I'd like to have the select() method return is a sockets timeout expires, puting in the selected key set the
-
Add photo to Profile Photo & Avatar
Hi Can anyone tell me how if possible to add a photo to my Profile Photo & Avatar? Thanks