CM 7.0 cluster licensing

We have to build a CM 7.0 cluster based on MCS-7835-H2 servers consisting of the following components:
- One Publisher Server
- Four active Subscribers
- Two redundant Subscribers;
- Two TFTP Servers.
The total number of MCS-7835-H2 servers is 9.
How many node licenses (LIC-CM7.0-7835=) is required in this configuration?

Hi ,
Just to add a touch to the great tips from David and Java (+5 points each guys!) I always thought the answer would be 7 but Chris corrected me in this recent thread and the answer in this instance is 9 Node Licenses will be required;
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Telephony&topicID=.ee6c829&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cc2ab2c/1#selected_message
Hope this helps!
Rob

Similar Messages

WebLogic Cluster License Question

We are currently testing WebLogic 5.1 clustering in our dev environment. I have 4 instances of the clusters running on the same machine but under different IP addresses. I have separate license files under individual license directories under each server under a directory called mycluster. the license file in each of these directories pertain to the ip address for each cluster. However, when I attempt to start the individual servers I receive an error stating that my license file does not contain the multicast ip address, and not the individual server ip's. Help.


          Unless using evaluation cluster license, you have to separate those
          4 licenses to different location if binding with 4 ip. Your 4 WL
          startup scripts must specify the same multicast address in order
          to communicate other clustered nodes.
          Brian
          "Aruna" <[email protected]> wrote:
          >
          >Hi Shawn
          > You need a multicast ip address for cluster
          >to work,
          >caz all the servers running in the cluster communicate
          >with each
          >other through assigned multicast ip, so contact your sys
          >admin
          >for setting up a multicast ip address. More over you may
          >don't
          >have to replicate license files to different directory
          >for different
          >servers, if the license is for clustering. The license
          >can be for
          >primary ip of the system with license for "ClusterII"
          >component.
          >
          >
          >
          >shawn ayers <[email protected]> wrote:
          >>We are currently testing WebLogic 5.1 clustering in our
          >>dev environment. I have 4 instances of the clusters
          >>running on the same machine but under different IP addresses.
          >> I have separate license files under individual license
          >>directories under each server under a directory called
          >>mycluster. the license file in each of these directories
          >>pertain to the ip address for each cluster. However,
          >>when I attempt to start the individual servers I receive
          >>an error stating that my license file does not contain
          >>the multicast ip address, and not the individual server
          >>ip's. Help.
          >

Cluster License weblogic 10

Do I need a cluster license if I'm runnning a cluster for testing and evaluation purpose?

Kai Niklas wrote:
          > Do I need a cluster license if I'm runnning a cluster for testing and evaluation purpose?
          You don't need any special cluster license. You can use default one.
          Remember only about 5 connections limitation per single server.
          Best Regards,
          Karol Muszynski

8.1 SP1 cluster license ?

Hi,
          I have free Weblogic 8.1 SP1 developer edition with one year license
          (download).
          Is this license clustered enabled ? (my HttpProxyServlet doesn't work as
          intended - traffic goes only to one server)
          Thanks.


the traffic goes to only one node probably because of stickyness of the session. try to use a new browser and see if the call lands on a different node. If not check you cluster configuration and make sure the application is deployed properly to the cluster.

Oracle EE cluster licensing

Hi,
I'd have to create a cluster with two servers. Each server is equipped with two processors (i.e. two filled sockets) which are intel quad core.
My question is: assuming that the minimum named user license number is 25, how many 25-user package shall I buy at the minimum?
25? (= the cluster counts as a unique sytem)
50? (= 25 x node)
100 (= 25 x node x processors_each_node)
Thanks in advance
Ciao

Hi,
Here you will find your answer (look the examples):
- http://www.oracle.com/corporate/pricing/sig.pdf
Cheers,
Francisco Munoz Alvarez
http://www.oraclenz.com

WL Cluster License

          You might know WL clsuter license is different from basic WL, because it binds ip address to start up the service. If i have 2 cpu(s) on 2 machines each (total 4), how many license i need? If i want to run 2 WL instances to bind 2 ip(s) on one machine (2 cpu), how many license i need to purchase?
          Your comment is appreciated.


You only need to BUY one license for each machine as it doesn't matter what your bind address is.
          However, you have to pay on a PER CPU basis. So we will charge the customer for 4 CPUs
          Actually this type of questions can be best answered by your sales rep.
          Kumar
          Brian Lin wrote:
          > You might know WL clsuter license is different from basic WL, because it binds ip address to start up the service. If i have 2 cpu(s) on 2 machines each (total 4), how many license i need? If i want to run 2 WL instances to bind 2 ip(s) on one machine (2 cpu), how many license i need to purchase?
          >
          > Your comment is appreciated.

JMS cluster license

In our environment, we are not using any JMS clustering functionality so we don't have JMS clustering module in license file. I am not sure what configuration causes following errors. Has anybody experience this?
          Thanks
          Nalin


I'm assuming that you have no other WL servers/clusters/domains running.
          Is that correct?
          I wonder if there is a JNDI name conflict occurring. The only
          thing unique in the supplied config that I noticed right away is that
          some JNDI names with "weblogic." - the same subcontext as is
          used for weblogic supplied internal JNDI objects. Try changing these
          to something else. If that doesn't work, try specifying
          the JNDI names that have no subcontexts (no "." or "/" in them)
          to see if that narrows down the problem.
          Nalin Patel wrote:
          > We are running on weblogic 8.1+sp1. Here I am attaching config.xml and the error
          > message.
          >
          > <Dec 16, 2003 9:42:06 AM CST> <Warning> <EJB> <BEA-010096> <The Message-Driven
          > EJB: Gearbox2AuditMessageDrivenBean is unable to connect to the JMS destination:
          > weblogic.coke.jms.gearbox2AuditLogQueue. Connection failed after 2 attempts. The
          > MDB will attempt to reconnect every 10 seconds. This log message will repeat every
          > 600 seconds until the condition clears.>
          > <Dec 16, 2003 9:42:06 AM CST> <Warning> <EJB> <BEA-010061> <The Message-Driven
          > EJB: Gearbox2AuditMessageDrivenBean is unable to connect to the JMS destination:
          > weblogic.coke.jms.gearbox2AuditLogQueue. The Error was:
          > [EJB:010196]'weblogic.jms.common.JMSException: Error creating session' Linked
          > exception = 'weblogic.jms.dispatcher.DispatcherException: Could not register a
          > HeartbeatMonitorListener for [weblogic.jms.dispatcher.DispatcherImpl@1eda64e]
          > for PPDSD'
          > weblogic.jms.common.JMSException: Error creating session
          > at weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:792)
          > at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1031)
          > at weblogic.jms.frontend.FESession.invoke(FESession.java:2527)
          > at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:609)
          > at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:153)
          > at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1768)
          > at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1615)
          > at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1454)
          > at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1594)
          > at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1806)
          > at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1072)
          > at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:958)
          > at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
          > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
          > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
          > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
          > at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
          > Caused by: weblogic.jms.dispatcher.DispatcherException: Could not register a HeartbeatMonitorListener
          > for [weblogic.jms.dispatcher.DispatcherImpl@1eda64e] for PPDSD
          > at weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:306)
          > at weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:354)
          > at weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:790)
          > ... 19 more
          > Caused by: weblogic.rmi.extensions.server.HeartbeatMonitorUnavailableException:
          > Could not register a HeartbeatMonitorListener for [weblogic.jms.dispatcher.DispatcherImpl@1eda64e]
          > at weblogic.rmi.extensions.server.HeartbeatMonitor.addHeartbeatMonitorListener(HeartbeatMonitor.java:86)
          > at weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:302)
          > ... 21 more
          >
          >
          > ------------------------------------------------------------------------
          >
          > <?xml version="1.0" encoding="UTF-8"?>
          > <Domain ConfigurationVersion="8.1.0.0" Name="transora">
          > <Server ListenAddress="" ListenPort="6503" Name="PPDSD"
          > NativeIOEnabled="true" ServerVersion="8.1.0.0">
          > <SSL Enabled="false" HostnameVerificationIgnored="false"
          > IdentityAndTrustLocations="KeyStores" ListenPort="6504" Name="PPDSD"/>
          > </Server>
          > <Security Name="transora"
          > PasswordPolicy="wl_default_password_policy"
          > Realm="wl_default_realm" RealmSetup="true"/>
          > <EmbeddedLDAP
          > Credential="{3DES}v9YfT6Xuo/BcMjtN4CeyB7Ckyo7fp6UpNnHXzlORWPE=" Name="transora"/>
          > <SecurityConfiguration
          > Credential="{3DES}Cdod1CQutgBQqhjnqcr2JEUNaYnUHX/gJ1DtsSCdYrQMm3Ymh0E+4893pxSqnqLUEN/9cH6Cpj/+Sxh3htbjG2+vTcXgS79y"
          > Name="transora" RealmBootStrapVersion="1"/>
          > <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          > <FileRealm Name="wl_default_file_realm"/>
          > <PasswordPolicy Name="wl_default_password_policy"/>
          > <JDBCConnectionPool CapacityIncrement="5"
          > DriverName="oracle.jdbc.driver.OracleDriver"
          > InitialCapacity="20" MaxCapacity="50"
          > Name="gearbox2ConnectionPool"
          > Password="{3DES}ZlGVp4ZkrWcErz3XA5YnvQ=="
          > Properties="user=gearbox2;dll=ocijdbc8;protocol=thin"
          > Targets="PPDSD" TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@qadb01:1521:PPDSD"/>
          > <JDBCDataSource JNDIName="gearbox2.datasource"
          > Name="gearbox2DataSource" PoolName="gearbox2ConnectionPool" Targets="PPDSD"/>
          > <JDBCTxDataSource JNDIName="gearbox2.tx.datasource"
          > Name="gearbox2TxDataSource" PoolName="gearbox2ConnectionPool" Targets="PPDSD"/>
          > <JMSConnectionFactory
          > JNDIName="weblogic.coke.jms.QueueConnectionFactory"
          > Name="Gearbox2JMSFactory" Targets="PPDSD"/>
          > <JMSFileStore
          > Directory="/opt/dsd/preprod/gui/wlserver8.1/weblogic81/transora/applications/dsd/jmsstore" Name="cokeStore"/>
          > <Application Deployed="true" Name="gearbox2"
          > Path="/opt/dsd/preprod/gui/wlserver8.1/weblogic81/transora/applications/dsd/bin/gearbox2.ear"
          > StagingMode="nostage" TwoPhase="true">
          > <WebAppComponent Name="gearbox2" Targets="PPDSD" URI="gearbox2.war"/>
          > <EJBComponent Name="gearbox2-ejb.jar" Targets="PPDSD" URI="gearbox2-ejb.jar"/>
          > </Application>
          > <JMSServer Name="cokeJMSServer" Store="cokeStore" Targets="PPDSD">
          > <JMSQueue CreationTime="1064337589006"
          > JNDIName="weblogic.coke.jms.gearbox2AuditLogQueue"
          > Name="Gearbox2JMSQueue" StoreEnabled="default"/>
          > </JMSServer>
          > </Domain>
          >

Scale-limited License and Cluster Testing

To Whom It May Concern:
I'm in the process of installing WLS 8.1 SP4 on 4 machines to try to learn how to setup a cluster. I'm using the installation CD that I received from the System Administration class. I realize that this CD installs BEA with a Scale-limited license.
I'm a little confused over the capibility of this license. Here's how your documentation describes it:
"Enables you to run a single WebLogic Server instance with a server capacity limited to approximately 3 percent of the full capacity of a production server with a production license. Restricts server capacity by limiting concurrent socket connections to a maximum of three connections. Requests for a fourth socket connection are blocked until a socket becomes free."
What confuses me is where it says a "single" server. Does this mean that I can't test clustering across multiple machines or does this mean that I can only run 1 instance of WLS on any machine? I understand the limitations concerning capacity and connections, that's understandable... I have no intention of running anything "production" wise with this license, I just want to become use to being an administrator... I recall in the class that we could've (we ended up not) clustered to another users machine, so I figured I could do this... Please help. Thanks :)
Anthony

Kai Niklas wrote:
          > Do I need a cluster license if I'm runnning a cluster for testing and evaluation purpose?
          You don't need any special cluster license. You can use default one.
          Remember only about 5 connections limitation per single server.
          Best Regards,
          Karol Muszynski

Error when running weblogic 10 in cluster

I am testing out weblogic 10 and when I run it with a single managed server and an admin server then everything works fine. When I run it in a cluster with a valid test cluster license, I get the following error. Does anyone know what the cause of this error is and how to fix it? Thanks for the help.
          <Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
          java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
          java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
          at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
          at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
          at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
          at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
          at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
          at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
          at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
          at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
          at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
          at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
          at weblogic.security.service.SecurityManager.runAs(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
          at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
          at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
          at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
          at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
          at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
          at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
          at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
          at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
          at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
          at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
          at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
          at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
          at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
          at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
          at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
          at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
          >

We solved this by increasing the number of open files, by adding the following in the /etc/security/limits.conf
* soft nofile 50000
* hard nofile 50000

How to setup weblogic cluster in 6.1 SP4

          Hi All,
          I have a Licensed weblogic in my solaris servers. I need to test weblogic clustering
          . How can i simulate weblogic clustering is there is any easy steps to do that
          and what should i do in order to make my EJB`s cluster aware. And some ppl say
          that i need to take a seperate weblogic cluster license other than the weblogic
          license.Kindly help me in proceeding further
          Thanks in advance
          Bala.J


Hi
I have same problem at beforetime.
You can do follow:
Step 1:
copy rt.jar form JDK 1.2.1\jre\lib\jar
to J2EE1.2.1\lib\system\
Step 2:
Set J2ee_classpath = c:\j2ee1.2.1\lib\system\rt.jar
Step 3:
Restart computer and J2ee
You can try it
Help can help you
David

Error received when running weblogic in cluster

I am trying out clusters to see what the benefit would be to our application but I keep getting an error in the background. I have obtained a test cluster license and it is loading it up on startup. Does anyone know what this error is or how to fix it? Thanks for the help.
<Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>

I am trying out clusters to see what the benefit would be to our application but I keep getting an error in the background. I have obtained a test cluster license and it is loading it up on startup. Does anyone know what this error is or how to fix it? Thanks for the help.
<Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>

Cluster-related error for remote client

          Hello,
          I am getting the following error when running a remote stand-alone client that attempts to access an entity bean that is running within WLS6.1sp2:
          java.lang.NullPointerException
          at weblogic.rmi.cluster.WeightBasedReplicaHandler.chooseReplica(WeightBasedReplicaHandler.java:65)
          at weblogic.rmi.cluster.BasicReplicaHandler.loadBalance(BasicReplicaHandler.java:258)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:223)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy1.findByPrimaryKey(Unknown Source)
          at ProductClient.main(ProductClient.java:40)
          We are not using clustering. The standalone client is using "copied" jars such as weblogic.jar on a win2000 pc. The error happens whether we run WLS on unix or on win2000.
          Any thoughts on how to avoid this problem?
          Thanks for any help,
          Clint Prouty
          DST Systems


As i mentioned earlier NPE is our problem.
          Pls try SP3 and if that doesn't solve, follow up with support.
          Kumar
          Clint Prouty wrote:
          > Hi Rajesh,
          >
          > Yes I do have the clustering license key in my license.bea file.
          > The error happens even if the client is running on the same
          > win200O PC as WLS. The error I listed comes from the client program, so I am
          > not sure how the license would come into play.
          >
          > Thanks,
          >
          > Clint
          >
          > Rajesh Mirchandani <[email protected]> wrote:
          >
          >>Do you have a clustering license key in your license.bea file ? It seems
          >>that we are looking for the cluster license even though you are not
          >>using clustering.
          >>
          >>Put the key in and see if it helps.
          >>
          >>Kumar Allamraju wrote:
          >>
          >>
          >>>you should report this problem to [email protected]
          >>>
          >>>I'm not sure if it's a known issue in SP2 and fixed in SP3. It's worth
          >>>trying SP3.
          >>>
          >>>--
          >>>Kumar
          >>>
          >>>Clint Prouty wrote:
          >>>
          >>>
          >>>>Hello,
          >>>>
          >>>>I am getting the following error when running a remote stand-alone
          >>>>
          >>client that attempts to access an entity bean that is running within
          >>WLS6.1sp2:
          >>
          >>>>java.lang.NullPointerException
          >>>> at weblogic.rmi.cluster.WeightBasedReplicaHandler.chooseReplica(WeightBasedReplicaHandler.java:65)
          >>>> at weblogic.rmi.cluster.BasicReplicaHandler.loadBalance(BasicReplicaHandler.java:258)
          >>>> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:223)
          >>>> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          >>>> at $Proxy1.findByPrimaryKey(Unknown Source)
          >>>> at ProductClient.main(ProductClient.java:40)
          >>>>
          >>>>We are not using clustering. The standalone client is using "copied"
          >>>>
          >>jars such as weblogic.jar on a win2000 pc. The error happens whether
          >>we run WLS on unix or on win2000.
          >>
          >>>>Any thoughts on how to avoid this problem?
          >>>>
          >>>>Thanks for any help,
          >>>>
          >>>>Clint Prouty
          >>>>DST Systems
          >>>>
          >>>>
          >>--
          >>Rajesh Mirchandani
          >>Developer Relations Engineer
          >>BEA Support
          >>
          >>
          >>
          >

Rich media session Licenses

I have 80 rich media session licenses for jabber guest deployement
2 expressway-c
2 expressway-e
if i install 20 licenses in each expressway how it will work
Please explain

Maybe easier to understand, to say that it will utilize 2 RMS (or traversal call licenses if it would be a VCS).
One on the -E and one on the -C.
So only the ones which are active in a call will utilize licenses.
(here "each expressway" would be 4 licenses, which is not what happens ;-)
In this JG deployment it makes sense to distribute licenses 50:50 in between the -E and the -C.
Expressway does not really know a model like "active/standby". (ok you could put
one of each cluster into maintenance mode, but thats in general not what you want to do).
I tried to find out a bit more how expressway clustering should behave regards jabber
guest, but I did not really find anything, looks like its just RR A records, ...
Within a cluster licenses are shared, so the -E or -C cluster can have allover 40 calls and
as Patrick wrote it does not directly matter how they are distributed.
With 4 expressways I would distribute 20 licenses on each peer, so also 50:50 on peer1 and peer2.

Licensing -Security Contexts on ASA5585-X

All,
I have a customer with 2 ASA 5585-X and they are looking at running a total of 20 Security contexts in failover mode on these two firewalls. From a licensing perspective, Can I get 10 security contexts on each of these firewalls and that gives me a cumulative context number of 20.I am not sure though if I will be able to run all 20 contexts in failover mode on both firewalls.
This is the document I am reading but not very clear.
http://www.cisco.com/en/US/docs/security/asa/asa90/license/license_management/license.html#wp1345944
Thanks

Hi,
If you want to split the 20 Security Contexts between 2 differents ASAs then you are looking at configuring a Active/Active Failover environment.
If you want all Security Contexts to be Active only on one physical ASA at a time (while the other is there to take over when the main one fails) then you are looking at configuring a Active/Standby Failover enviroment.
So in other words
Each units 10 Security Context license will be combined between the units
You can either use 20 Security Contexs on a single physical unit at a time in Active/Standby
OR you can divide the 20 Security Contexts between the 2 Physical ASAs in Active/ActiveFor example 10 Active in ASA1 and 10 Active in ASA2
Also heres a partial quote from the Cisco document
Failover License Requirements and Exceptions
Failover units do not require the same license on each unit.
Older versions of ASA software required that the licenses match on each unit. Starting with Version 8.3(1), you no longer need to install identical licenses. Typically, you buy a license only for the primary unit; for Active/Standby failover, the secondary unit inherits the primary license when it becomes active. If you have licenses on both units, they combine into a single running failover cluster license. How Failover or ASA Cluster Licenses Combine
For failover pairs or ASA clusters, the licenses on each unit are combined into a single running cluster license. If you buy separate licenses for each unit, then the combined license uses the following rules: For example, for failover: You have two ASA 5540 ASAs, one with 20 contexts and the other with 10 contexts; the combined license allows 30 contexts. For Active/Active failover, the contexts are divided between the two units. One unit can use 18 contexts and the other unit can use 12 contexts, for example, for a total of 30.
- Jouni

DNS & License configuration

Hi,
Please help me with the following problems.
See my company have two public IP address: 200.200.200.1 and
200.200.200.2, one domain name: mycompany.com. These two public
addresses are mapped into two private addresses (192.168.0.1 and
192.168.0.2) via NAT(network address translator) respectively.
The two servers are clustered.
The problems are:
1) Should I add two entries in ISP's DNS configuration file?
mycluster IN A 200.200.200.1 (maybe 192.168.0.1 is wrong)
mycluster IN A 200.200.200.2
2) In my two weblogic servers, what should the IP addresses bound
in the cluster licenses be? 200.200.200.X or 192.168.0.X?
(The servers runs on privates IP address. That is, the two
servers are in a internal network segment. )
What should I do?
Internet
|
ISP's network
| |
My private network Other companies' network
Andy

Hi Andy
First of all, you should have a proxy server to support clusters. Its
always a good idea to have proxy servers. To setup proxy servers refer to
the weblogic site and search for NSAPI or ISAPI. Once you have done that,
you can give the address of the proxy server to the DNS. Anyone from the
outside will be able to connect to the proxy server and you will need only
one entry in the named.conf file.
Your proxy server should have 2 NICs one connecting to the outside and one
connecting to the inside. In this case, you will need to specify the
internal IPs in the cluster license file. Only the proxy server will know
where the cluster is. The proxy server will transmit all requests via the
internal NIC.
Hope this does the trick
Sudhakar
"Andy Ping" <[email protected]> wrote in message
news:[email protected]..
Hi,
Please help me with the following problems.
See my company have two public IP address: 200.200.200.1 and
200.200.200.2, one domain name: mycompany.com. These two public
addresses are mapped into two private addresses (192.168.0.1 and
192.168.0.2) via NAT(network address translator) respectively.
The two servers are clustered.
The problems are:
1) Should I add two entries in ISP's DNS configuration file?
mycluster IN A 200.200.200.1 (maybe 192.168.0.1 is wrong)
mycluster IN A 200.200.200.2
2) In my two weblogic servers, what should the IP addresses bound
in the cluster licenses be? 200.200.200.X or 192.168.0.X?
(The servers runs on privates IP address. That is, the two
servers are in a internal network segment. )
What should I do?
Internet
|
ISP's network
| |
My private network Other companies' network
Andy

CM 7.0 cluster licensing

Similar Messages

Maybe you are looking for