Setting up in-memory replication in WLS5.1

          Hi,
          How do you set up in-memory replication in WLS5.1? I mean what the weblogic.properties
          and what are it's values?
          Thanx
          

Put it in the cluster level properties file. What service pack are you using? I would recommend you use the latest (SP11)
          with WLS 5.1.
          Kailu wrote:
          > Hi,
          >
          > I've set up the following properties(in the server level properties, should they
          > be set up in the cluster level properties?)
          >
          > weblogic.httpd.clustering.enable=true
          > weblogic.httpd.session.persistence=true
          > weblogic.httpd.session.persistentStoreType=replicated
          >
          > and I'm getting the following error(does it have anything do with the settings
          > in the weblogic.policy file?)
          >
          > Mon Mar 18 10:07:55 CST 2002:<I> <ServletContext-General> session: init
          > Mon Mar 18 10:07:55 CST 2002:<E> <ServletContext-General> Servlet failed with
          > Exception
          > java.lang.SecurityException:
          > at java.lang.Throwable.fillInStackTrace(Native Method)
          > at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
          > at weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
          > at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
          > at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(Compiled Code)
          > at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(Compiled
          > Code)
          > at weblogic.jndi.Environment.getContext(Compiled Code)
          > at weblogic.jndi.Environment.getInitialContext(Compiled Code)
          > at weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:363)
          > at weblogic.cluster.replication.ReplicationManager.createSecondary(Compiled
          > Code)
          > at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:617)
          > at weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
          > at weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
          > at weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:349)
          > at weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1307)
          > at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1199)
          > at examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
          > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
          > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
          > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
          > at weblogic.kernel.ExecuteThread.run(Compiled Code)
          >
          > "Kailu" <[email protected]> wrote:
          > >
          > >Hi,
          > >
          > >How do you set up in-memory replication in WLS5.1? I mean what the weblogic.properties
          > >and what are it's values?
          > >
          > >Thanx
          Rajesh Mirchandani
          Developer Relations Engineer
          BEA Support
          

Similar Messages

  • In memory replication problems when I bring up a new server

              I've got in memory replication set up for 6.1. It works fine if I have 2 servers
              up and 1 goes down.
              However, if I have 1 server up and a bring a second server up, the sessions blow
              out.
              E.g. I've got server A and server B.
              Both are up, both have sessions. As new sessions come in, they are replicated over
              to the other server.
              now I bring server B down. All sessions on B fail over to A.
              so far so good.
              However when I bring server A back up some of the sessions fail as soon as the server
              is back up.
              Is this a configuration issue, is this a know problem?
              This worked fine in weblogic 5.1. In 5.1 when I brought an instance back up, everything
              worked fine.
              

              It turns out the problem was caused by using an old version of the Apache Plugin.
              This problem occurred while using the 5.1 apache plugin with WLS 6.1.
              Once we realized we were using the wrong plugin and swithced to the 6.1 plugin, the
              problem went away.
              

  • In memory replication doesn't seem to work

    We have set up a Cluster with 2 servers. Our Proxy server is NES. We can
              see the round robin working but each time we are accessing the session,
              the same cookie gets overriden (the browser receives the WebLogicSession
              cookie from the weblogic servers) .... Loosing all the information..
              Is this a WebLogic bug ?
              Olivier
              [olivier.vcf]
              

    I don't think it goes in the xml file. It should be in weblogic.properties file
              weblogic.httpd.session.cookie.name=foo
              -- Prasad
              John wrote:
              > Could you tell me how I can set up the cookie in web.xml to override the WeblogicSession cookie?
              >
              > "Yogi Mudras" <[email protected]> wrote:
              > >Is SP6 out yet ?
              > >
              > >
              > >"Olivier Brand" <[email protected]> wrote in message
              > >news:[email protected]...
              > >> BEA told me that the Session bug will be fixed in SP7.
              > >>
              > >> Otherwise, the in-memory replication is working fine. During our stress
              > >test, we got
              > >> some exceptions.
              > >>
              > >> When we are using in-memory replicaiton, should all the objects put in the
              > >HttpSession
              > >> be Serializable ? My guess is that they have to be.
              > >>
              > >> Olivier
              > >>
              > >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(Compiled
              > >> Code)
              > >> at
              > >>
              > >weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession
              > >(Compiled
              > >> Code)
              > >> at
              > >>
              > >weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
              > >teSessions(Compiled
              > >>
              > >> Code)
              > >> at
              > >>
              > >weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
              > >Compiled
              > >> Code)
              > >> at
              > >> weblogic.time.common.internal.ScheduledTrigger.executeLocally(Compiled
              > >> Code)
              > >> at
              > >> weblogic.time.common.internal.ScheduledTrigger.execute(Compiled Code)
              > >> at weblogic.time.server.ScheduledTrigger.execute(Compiled Code)
              > >> at weblogic.kernel.ExecuteThread.run(Compiled Code)
              > >>
              > >> weblogic.cluster.replication.NotFoundException: remove unable to find
              > >> object 7173403347807782043
              > >> at java.lang.Throwable.fillInStackTrace(Native Method)
              > >> at java.lang.Throwable.fillInStackTrace(Compiled Code)
              > >> at weblogic.rmi.extensions.AbstractRequest.sendReceive(Compiled
              > >> Code)
              > >> at
              > >> weblogic.cluster.replication.ReplicationManager_WLStub.remove(Compiled
              > >> Code)
              > >> at
              > >> weblogic.cluster.replication.ReplicationManager.unregister(Compiled
              > >> Code)
              > >> at
              > >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(Compiled
              > >> Code)
              > >> at
              > >>
              > >weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession
              > >(Compiled
              > >> Code)
              > >> at
              > >>
              > >weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
              > >teSessions(Compiled
              > >>
              > >> Code)
              > >> at
              > >>
              > >weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
              > >Compiled
              > >> Code)
              > >> at
              > >> weblogic.time.common.internal.ScheduledTrigger.executeLocally(Compiled
              > >> Code)
              > >>
              > >> Prasad Peddada wrote:
              > >>
              > >> > Olivier Brand wrote:
              > >> >
              > >> > > In fact, nothing is impossible since there is a HUGE bug in WebLogic
              > >and the
              > >> > > sessions. This bug has been (and still is) filed under the following
              > >number:
              > >> > > CR033896.
              > >> > > I have noticed that if you have two different web app, if you contact
              > >a
              > >> > > servlet in app 1 and a servlet in app 2 (2 different contexts), the
              > >same
              > >> > > cookie: WebLogicSession, is being overriden !!
              > >> > > The workaround is to override in the web.xml the name of the session.
              > >> >
              > >> > Do you have problems even with the suggested workaround?
              > >> >
              > >> > > I got the sticky load balancing back in placing the CookieName
              > >argument in the
              > >> > > NES proxy (app1 and app2). This way the proxy can identify what
              > >application
              > >> > > server to contact depending on the requestor's cookie.
              > >> > >
              > >> > > I am still noticing the loss of the session when using the failover:
              > >> > >
              > >> > > I stop app server A, app1 is switched to app server B but recreate the
              > >same
              > >> > > cookie with a different value. I thought that in-memory replication
              > >was...
              > >> > > replicating. Does it mean that only the DB persistency (or file system
              > >if
              > >> > > using NFS of course) can work in a failover scenario ?
              > >> >
              > >> > When you failover to server B the cookie will change. The behavior is
              > >correct, but
              > >> > do you see loss of session data. Is it possible to post the cookies
              > >before and
              > >> > after failover.
              > >> >
              > >> > - Prasad
              > >> >
              > >> > >
              > >> > > Olivier
              > >> > >
              > >> > > Prasad Peddada wrote:
              > >> > >
              > >> > > > Olivier Brand wrote:
              > >> > > >
              > >> > > > > We have set up a Cluster with 2 servers. Our Proxy server is NES.
              > >We can
              > >> > > > > see the round robin working but each time we are accessing the
              > >session,
              > >> > > > > the same cookie gets overriden (the browser receives the
              > >WebLogicSession
              > >> > > > > cookie from the weblogic servers) .... Loosing all the
              > >information..
              > >> > > >
              > >> > > > What do you mean by overriden? That's not possible. Could you post
              > >the two
              > >> > > > sessions ids.
              > >> > > >
              > >> > > > - Prasad
              > >> > > >
              > >> > > > >
              > >> > > > > Is this a WebLogic bug ?
              > >> > > > >
              > >> > > > > Olivier
              > >> >
              > >> > --
              > >> > Cheers
              > >> >
              > >> > - Prasad
              > >>
              > >
              > >
              

  • Evaluation license for ejb-in-memory-replication!!!

              Hi,
              Has anyone tried using in-memory replication for a stateful-session bean in the evaluation
              copy of WebLogic 6.0 ? I have a simple stateful session bean with <replication-type>InMemory</replication-type>
              set in weblogic-ejb-jar.xml. But when I try to generate a deployable jar file, I
              get the following message,
              % java weblogic.ejbc -compiler jikes std_simple_stateful.jar simple_stateful.jar
              Couldn't find a license for in-memory replication of EJB's, this feature is disabled
              <Jan 31, 2001 1:40:21 PM EST> <Info> <EJB> <Couldn't find a license for in-memory
              replication of EJB's, this feature is disabled>
              The license file seems to have the product enabled.
              any suggestions ???
              thanx in advance
              -Ram
              [email protected]
              

    Make sure the license is in ejbc's classpath.
              We fixed this for SP1 to make it so ejbc will always compile regardless
              of your license. The actual license check occurs when you deploy the
              bean.
              -- Rob
              Ram Munjuluri wrote:
              >
              > Hi,
              >
              > Has anyone tried using in-memory replication for a stateful-session bean in the evaluation
              > copy of WebLogic 6.0 ? I have a simple stateful session bean with <replication-type>InMemory</replication-type>
              > set in weblogic-ejb-jar.xml. But when I try to generate a deployable jar file, I
              > get the following message,
              >
              > % java weblogic.ejbc -compiler jikes std_simple_stateful.jar simple_stateful.jar
              > Couldn't find a license for in-memory replication of EJB's, this feature is disabled
              > <Jan 31, 2001 1:40:21 PM EST> <Info> <EJB> <Couldn't find a license for in-memory
              > replication of EJB's, this feature is disabled>
              >
              > The license file seems to have the product enabled.
              >
              > any suggestions ???
              >
              > thanx in advance
              > -Ram
              > [email protected]
              Coming Soon: Building J2EE Applications & BEA WebLogic Server
              by Michael Girdley, Rob Woollen, and Sandra Emerson
              http://learnweblogic.com
              

  • NullPointerException when doing in-memory-replication

    I am clustering two WLS instance sitting behind a WLS NSAPI proxy on one
              multi-home NT box, but when I tried to use in memory replication with adding
              the the following three properties:
              weblogic.httpd.clustering.enable=true
              weblogic.httpd.session.persistence=true
              weblogic.httpd.session.persistentStoreType=replicated
              I got the exception below. if I removed the session.persistence and
              session.persistentStoreType properties, the request will go through and both
              instance can serve request, but I lost the session information in fail over.
              Any hints will be appreciated!
              Qingxiang
              java.lang.NullPointerException
              at
              weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R
              eplicatedSession.java:339)
              at
              weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi
              onContext.java:322)
              at
              weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp
              l.java:1104)
              at
              weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
              ava:1007)
              at
              weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
              ava:981)
              at
              weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47)
              at
              weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64)
              at
              weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31)
              at jsp_servlet.index._jspService(index.java:105)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :123)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              :141)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:744)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              l.java:692)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              Manager.java:251)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
              at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

    I forgot to add that I am running WLS5.1 with sp3.
              "Qingxiang Ke" <[email protected]> wrote in message
              news:[email protected]...
              > I am clustering two WLS instance sitting behind a WLS NSAPI proxy on one
              > multi-home NT box, but when I tried to use in memory replication with
              adding
              > the the following three properties:
              >
              > weblogic.httpd.clustering.enable=true
              > weblogic.httpd.session.persistence=true
              > weblogic.httpd.session.persistentStoreType=replicated
              >
              > I got the exception below. if I removed the session.persistence and
              > session.persistentStoreType properties, the request will go through and
              both
              > instance can serve request, but I lost the session information in fail
              over.
              >
              > Any hints will be appreciated!
              >
              > Qingxiang
              >
              > java.lang.NullPointerException
              > at
              >
              weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R
              > eplicatedSession.java:339)
              > at
              >
              weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi
              > onContext.java:322)
              > at
              >
              weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp
              > l.java:1104)
              > at
              >
              weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
              > ava:1007)
              > at
              >
              weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
              > ava:981)
              > at
              > weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47)
              > at
              > weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64)
              > at
              > weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31)
              > at jsp_servlet.index._jspService(index.java:105)
              > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
              > at
              >
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :123)
              > at
              >
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
              > :141)
              > at
              >
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              > l.java:744)
              > at
              >
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
              > l.java:692)
              > at
              >
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
              > Manager.java:251)
              >
              > at
              >
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
              > at
              > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              >
              >
              

  • In-memory replication and no. of sessions - clarification

              a small question/clarification
              Lets say we have 2 servers in cluster with in-memory repication. Let say maximum RAM for jvm heap can use is 1.5GB.
              I understand that HTTP Session Data is stored in heap (am i wrong?).
              Now lets say if we set weblogic.httpd.session.cacheEntries=1024 (default).
              The documentation says...
              weblogic.httpd.session.cacheEntries=x
              Where x limits the number of cached sessions at any time. If you are expecting high volumes of simultaneous active sessions, you do not want these sessions to soak up the RAM of your server since this may cause performance problems swapping to and from virtual memory. When the cache is full, the least recently used sessions are stored in the persistent store and recalled automatically when required. If you do not use persistence, this property is ignored, and there is no soft limit to the number of sessions allowed in main memory. By default, the number of cached sessions is 1024. The minimum is 16, and maximum is Integer.MAX_VALUE. An empty session uses less than 100 bytes, but will grow as data is added to it.
              If lets say 1025 user comes in what happens in followin scenario
              1. no heap memory available:
              Does is throw out of memory exception or what does it do to accomodate new user?
              Does swapping occur for HTTP data on the heap? (or am i talking nonsense?)
              2. heap memory available:
              What does the following mean for in-memory replication?
              When the cache is full, the least recently used sessions are stored in the persistent store and recalled automatically when required.
              thanks in advance
              

    shivu wrote:
              > a small question/clarification
              >
              > Lets say we have 2 servers in cluster with in-memory repication. Let say maximum RAM for jvm heap can use is 1.5GB.
              Dont' allocate 1GB for heap. Try not to allocate more than 512 MB.
              > I understand that HTTP Session Data is stored in heap (am i wrong?).
              >
              > Now lets say if we set weblogic.httpd.session.cacheEntries=1024 (default).
              >
              > The documentation says...
              > -----------
              > weblogic.httpd.session.cacheEntries=x
              > Where x limits the number of cached sessions at any time. If you are expecting high volumes of simultaneous active sessions, you do not want these sessions to soak up the RAM of your server since this may cause performance problems swapping to and from virtual memory. When the cache is full, the least recently used sessions are stored in the persistent store and recalled automatically when required. If you do not use persistence, this property is ignored, and there is no soft limit to the number of sessions allowed in main memory. By default, the number of cached sessions is 1024. The minimum is 16, and maximum is Integer.MAX_VALUE. An empty session uses less than 100 bytes, but will grow as data is added to it.
              > ------------
              >
              > If lets say 1025 user comes in what happens in followin scenario
              >
              > 1. no heap memory available:Does is throw out of memory exception or what does it do to accomodate new user?
              > Does swapping occur for HTTP data on the heap? (or am i talking nonsense?)
              If you are out of memory you are out of luck.
              >
              > 2. heap memory available:
              >
              > What does the following mean for in-memory replication?
              > -----
              > When the cache is full, the least recently used sessions are stored in the persistent store and recalled automatically when required.
              > ----
              Hmm. I don't think there is any hard limit with in memory replication. But I would check and let you know.
              >
              > thanks in advance
              Cheers
              - Prasad
              

  • In memory replication

    i'm trying to run my db application in memory, with no writing to disk what so ever.
    i have the DB_PRIVATE, DB_LOG_INMEMORY and DB_TXN_NOSYNC flags set for my environment, and the DB_MPOOL_NOFILE flag set for all my DBs.
    when i added replication to my application, log files are suddenly written to disk.
    what do i need to do in order to avoid this?
    thanks :-)

    You should be able to get rid of the on-disk log files by refraining from setting DB_TXN_NOSYNC. However, replication uses a couple of extra files that are always stored on disk, so you won't be able to achieve literally "no writing to disk whatsoever".
    Alan Bram
    Oracle

  • Problems with WebLogic in-memory replication

    We are using Netscape Server 4.0 with the WebLogic 4.51sp7 proxy connecting
              to 2 clustered machines. We'd like to use the in-memory replication, but
              whenever we set up our weblogic.properties file like the description in the
              "Setting up a WebLogic Cluster" document, we get an error. The following
              are the settings we are setting:
              weblogic.httpd.clustering.enable=true
              weblogic.httpd.session.persistence=true
              webloigc.httpd.session.persistentStoreType=replicated
              We get the error when we try to start up any of the servers in the cluster.
              The following is the error:
              Unable to initialize server: java.lang.NullPointerException
              fatal initialization exception
              java.lang.NullPointerException
              at weblogic.t3.srvr.HttpServer.start(Compiled Code)
              at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
              at weblogic.t3.srvr.T3Srvr.main(Compiled Code)
              at weblogic.Server.startServerDynamically(Compiled Code)
              at weblogic.Server.main(Compiled Code)
              Any information anyone has out there would be greatly appreciated!
              

    Actually, it is just the weblogic.httpd.clustering.enable=true that causes
              problems. When I remove it, it starts up just fine, but I don't think it is
              using the in-memory replication. It is throwing the exception near the end
              of the start up procedure, just after loading the EJBs. Lately, it hasn't
              even been throwing the exception, it just hangs. The last lines we see are:
              74 EJBs were deployed using .ser files.
              0 EJBs were deployed using .jar files
              It is at this point that it either throws the exception or hangs. We do
              have clustering licenses for all the machines in the cluster. We are using
              the default multicastAddress (237.0.0.1) so I was not explicitly setting it.
              Now, I am and it doesn't seem to make any difference.
              Any ideas?
              John
              "Mike Benham" <[email protected]> wrote in message
              news:[email protected]...
              >
              > So just setting those listed properties causes an NPE? If you remove
              > just those properties, you don't get an NPE? At what point in the
              > startup procedure is that exception thrown? Although it shouldn't
              > result in that error, are you sure that you have a clustering license?
              > You also need to set the multicast address to use for your cluster:
              > weblogic.cluster.multicastAddress=IP.
              >
              > - Mike
              >
              >
              > John Peters wrote:
              > >
              > > We are using Netscape Server 4.0 with the WebLogic 4.51sp7 proxy
              connecting
              > > to 2 clustered machines. We'd like to use the in-memory replication,
              but
              > > whenever we set up our weblogic.properties file like the description in
              the
              > > "Setting up a WebLogic Cluster" document, we get an error. The
              following
              > > are the settings we are setting:
              > >
              > > weblogic.httpd.clustering.enable=true
              > > weblogic.httpd.session.persistence=true
              > > webloigc.httpd.session.persistentStoreType=replicated
              > >
              > > We get the error when we try to start up any of the servers in the
              cluster.
              > > The following is the error:
              > >
              > > Unable to initialize server: java.lang.NullPointerException
              > > fatal initialization exception
              > > java.lang.NullPointerException
              > > at weblogic.t3.srvr.HttpServer.start(Compiled Code)
              > > at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
              > > at weblogic.t3.srvr.T3Srvr.main(Compiled Code)
              > > at weblogic.Server.startServerDynamically(Compiled Code)
              > > at weblogic.Server.main(Compiled Code)
              > >
              > > Any information anyone has out there would be greatly appreciated!
              

  • In memory replication not working

    We are using Weblogic 4.5.1 SP5 (I know that is an old service pack -
              but this is in a production system and it usually takes a guarantee that
              a change will fix a bug before being allowed).
              We are clustering two weblogic servers.
              In our test systems everything works great.
              In our production systems, failover works, but not in memory
              replication. With the replication debugging output turned on I see the
              following output:
              <WebLogicServer> WebLogic Server started
              <RJVM> Creating connection to 10.100.35.90/10.100.35.80 ...
              (I should point out that this RJVM message only appears on one of the
              servers, appears whether or not the other server is running, and
              10.100.35.80 is not the IP address of the other server nor of this
              server.)
              (Note, it never prints the typical <RepMan>Adding XXXXXX to the cluster)
              When a user connects and a session is created, we see the following:
              <RepMan>Unable to create secondary for XXXXXXX
              <RepMan>Registered XXXXXX
              <RepMan>Get Secondary JVMID returning null for XXXXXXX
              <RepMan>updateSecondary called on unpaired primary
              <RepMan>lookup found for XXXXXX
              The second server never outputs any new information.
              It's not the code, this works in test, and we have poured over the
              configuration, and all configuration files look correct.
              The MulticastTest also works in the production system.
              Any ideas?
              

              Looks like they are not in cluster..
              double check the configuration and check in weblogic console whether you see both servers under the cluster name...
              Robert Antonucci <[email protected]> wrote:
              >We are using Weblogic 4.5.1 SP5 (I know that is an old service pack -
              >but this is in a production system and it usually takes a guarantee that
              >a change will fix a bug before being allowed).
              >
              >We are clustering two weblogic servers.
              >In our test systems everything works great.
              >In our production systems, failover works, but not in memory
              >replication. With the replication debugging output turned on I see the
              >following output:
              >
              ><WebLogicServer> WebLogic Server started
              ><RJVM> Creating connection to 10.100.35.90/10.100.35.80 ...
              >(I should point out that this RJVM message only appears on one of the
              >servers, appears whether or not the other server is running, and
              >10.100.35.80 is not the IP address of the other server nor of this
              >server.)
              >(Note, it never prints the typical <RepMan>Adding XXXXXX to the cluster)
              >
              >When a user connects and a session is created, we see the following:
              >
              ><RepMan>Unable to create secondary for XXXXXXX
              ><RepMan>Registered XXXXXX
              ><RepMan>Get Secondary JVMID returning null for XXXXXXX
              ><RepMan>updateSecondary called on unpaired primary
              ><RepMan>lookup found for XXXXXX
              >
              >The second server never outputs any new information.
              >
              >It's not the code, this works in test, and we have poured over the
              >configuration, and all configuration files look correct.
              >The MulticastTest also works in the production system.
              >
              >Any ideas?
              >
              

  • Set maximum server memory by using sql scripts

    Dear all
    How to set maximum server memory by using sql scripts in sql server 2014? Thx a lot
    Best regards,
    Wallace

    You can use
    sys.Sp_Configure to set max server memory
    Here are some recommendation for Max Server memory based on RAM size
    GB
    MB
    Recommended Setting
    Command
    16
    16384
    14745
    EXEC sys.sp_configure 'max server memory (MB)', '14745'; RECONFIGURE;
    32
    32768
    29491
    EXEC sys.sp_configure 'max server memory (MB)', '29491'; RECONFIGURE;
    64
    65536
    58982
    EXEC sys.sp_configure 'max server memory (MB)', '58982'; RECONFIGURE;
    128
    131072
    117964
    EXEC sys.sp_configure 'max server memory (MB)', '117964'; RECONFIGURE;
    256
    262144
    235929
    EXEC sys.sp_configure 'max server memory (MB)', '235929'; RECONFIGURE;
    512
    524288
    471859
    EXEC sys.sp_configure 'max server memory (MB)', '471859'; RECONFIGURE;
    1024
    1048576
    943718
    EXEC sys.sp_configure 'max server memory (MB)', '943718'; RECONFIGURE;
    2048
    2097152
    1887436
    EXEC sys.sp_configure 'max server memory (MB)', '1887436'; RECONFIGURE;
    4096
    4194304
    3774873
    EXEC sys.sp_configure'max server memory (MB)', '3774873'; RECONFIGURE;
    Hope this will help
    Glad to help! Please remember to accept the answer if you found it helpful. It will be useful for future readers having same issue.

  • Nokia C2-03 Set Password for Memory Card

    Hi All,
    I m using C2-03, I found an option to set password on memory card.
    Apps and Games > Memory Card > Mem. card opt. > Set password
    for my privacy I set a password but the Memory card still opens without asking. Can anyone plz inform me how do I secure my private data using password?
    Thanks,
    Khaild.
    Solved!
    Go to Solution.

    It will continue to open up without the password. The password will only be asked if you insert the memory card in a different phone and it is only required once. It will keep opening up normally from the next time.
    That password isn't there to keep your memory card protected inside your phone but instead to keep others from using your memory card. As long as the password is there, the phone can't be used on any other phone or even on a PC through card reader.

  • How do I set-up my memory amount for max speed for FCP and Motion

    Hey all, I have a Dual 2.3 G5 with (8 Gigs) Ram. I'm working with a new client. I want to set up my memory or whatever else to provide MAXIMUM processing power for FCP and MOTION. Does anyone have any recommended settings. I've maxed-our RAM. My card is (ATI Radeon 9600-128MB of VRAM)
    Is there a setting in FCP that allows more processing power to be applied to that application ?
    Appreciate any replies

    Most of FCP's speed in performing functions is directly related to processor speed. The only way to increase performance would be to use a Mac with faster processors. Performance is also related to data throughput, so if you're working with high data rate video formats, a fast RAID and/or SATA (or eSATA) media storage solution would help.
    The exception to FCP performance is when rendering/processing FX Plugs; they are dependent on the power of the graphics card.
    Motion is mostly dependent on the power of the graphics card.
    There is no way that I'm aware of that you can speed up RAM. Having the extra RAM will just mean that you can successfully work with more applications open at the same time.
    -DH

  • How much does in-memory replication boost txn rates?

    I posted the note below on the weblogic.developer.interest.clustering" list.
              As a supplement to that question, I'm wondering how much of a boost to
              transaction rates that anyone sees from using in-memory replication with
              WebLogic?
              =====================
              How many peak/average transactions per second is anyone pushing through
              WebLogic? With what response time? On what version of WebLogic? With what
              sort of a configuration?
              If you don't have transactions per second, any other measures of performance
              and scalability would be interesting.
              Randy Heffner
              Giga Information Group
              

              Mike -
              Thanks for the reply -- I phrased my question poorly. What I intended was
              this:
              - Compared to saving context to disk (so that it is accessible across
              servers in a cluster), how much does in-memory replication boost transaction
              throughput rates?
              I'm just wondering if anyone has measured the difference in their
              environment.
              Randy
              "Mike Reiche" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Boost transaction rates? No - it degrades transaction rates. Replicating
              data is
              > extra work.
              >
              > Mike
              >
              > "Randy Heffner" <[email protected]> wrote:
              > >I posted the note below on the weblogic.developer.interest.clustering"
              > >list.
              > >As a supplement to that question, I'm wondering how much of a boost to
              > >transaction rates that anyone sees from using in-memory replication with
              > >WebLogic?
              > >
              > >=====================
              > >How many peak/average transactions per second is anyone pushing through
              > >WebLogic? With what response time? On what version of WebLogic? With
              > >what
              > >sort of a configuration?
              > >
              > >If you don't have transactions per second, any other measures of
              performance
              > >and scalability would be interesting.
              > >
              > >Randy Heffner
              > >Giga Information Group
              > >
              > >
              > >
              > >
              >
              

  • 3rd party distributed SW load balancing with In-Memory Replication

              Hi,
              Could someone please comment on the feasibility of the following setup?
              I've started testing replication with a software load balancing product. This
              product lets all nodes receive all packets and uses a kernel-level filter
              to let only one node at the time receive it. Since there's minimum 1 heartbeat
              between the nodes, there are several NICs in each node.
              At the moment it seems like it doesn't work: - I use the SessionServlet - with
              a 2-node cluster I first have the 2 nodes up and I access it with a single client:
              .the LB is configured to be sticky wrt. source IP address, so the same node gets
              all the traffic - when I stop the node receiving the traffic the other node takes
              over (I changed the colours of SessionServlet) . however, the counter restarts
              at zero
              From what I read of the in-memory replication documentation I thought that it
              might work also with a distributed software load balancing cluster. Any comments
              on the feasability of this?
              Is there a way to debug replication (in WLS6SP1)? I don't see any replication
              messages in the logs, so I'm not even sure that it works at all. - I do get a
              message about "Clustering Services startting" when I start the examples server
              on each node - is there anything tto look for in the console to make sure that
              things are working? - the evaluation license for WLS6SP1 on NT seems to support
              In-Memory Replication and Cluster. However, I've also seen a Cluster-II somewhere:
              is that needed?
              Thanks for your attention!
              Regards, Frank Olsen
              

    We are considering Resonate as one of the software load balancer. We haven't certified
              them yet. I have no idea how long its going to take.
              As a base rule if the SWLB can do the load balancing and maintain stickyness that is fine
              with us as long as it doesn't modify the cookie or the URL if URL rewriting is enabled.
              Having said that if you run into problems we won't be able to support you since it is not
              certified.
              -- Prasad
              Frank Olsen wrote:
              > Prasad Peddada <[email protected]> wrote:
              > >Frank Olsen wrote:
              > >
              > >> Hi,
              > >>
              > > We don't support any 3rd party software load balancers.
              >
              > Does that mean that there are technical reasones why it won't work, or just that
              > you haven't tested it?
              >
              > > As >I said before I am thinking your configuration is >incorrect if n-memory
              > replication is not working. I would >strongly suggest you look at webapp deployment
              > descriptor and >then the config.xml file.
              >
              > OK.
              >
              > >Also doing sticky based on source ip address is not good. You >should do it based
              > on passive cookie persistence or active >cookie persistence (with cookie insert,
              > a new one).
              > >
              >
              > I agree that various source-based sticky options (IP, port; network) are not the
              > best solution. In our current implementation we can't do this because the SW load
              > balancer is based on filtering IP packets on the driver level.
              >
              > Currently I'm more interested in understanding whether it can our SW load balancer
              > can work with your replication at all?
              >
              > What makes me think that it could work is that in WLS6.0 a session failed over
              > to any cluster node can recover the replicated session.
              >
              > Can there be a problem with the cookies?
              > - are the P/S for replication put in the cookie by the node itself or by the proxy/HW
              > load balancer?
              >
              > >
              > >The options are -Dweblogic.debug.DebugReplication=true and
              > >-Dweblogic.debug.DebugReplicationDetails=true
              > >
              >
              > Great, thanks!
              >
              > Regards,
              > Frank Olsen
              

  • What's the recommended setting for "Process memory usage" ("process virtual" in UI) for a 64-bit host on a 64-bit OS?

    Hi gurus
    In resource based throttling, what's the recommended setting for "Process memory usage" ("process virtual" in the resource based throttling tab of the UI) for a 64-bit host
    on a 64-bit Windows OS?
    According to MS (http://msdn.microsoft.com/en-us/library/ee308808(v=bts.10).aspx):
    "By default, the
    Process memory usage throttling threshold is set to 25. If this value is exceeded and the BizTalk process memory usage is more than 300 MB, a throttling condition may occur. On a 32-bit
    server, you can increase the Process memory usage value to 50. On a 64-bit server, you can increase this value to 100. This allows for more memory consumption by the BizTalk process before throttling
    occurs."
    Does this mean that 100 is the recommended setting for a 64-bit host on a 64-bit Windows?
    Thanks
    Michael Brandt Lassen

    Hi Michael,
    Recommended setting is the default setting which is 25 .dot.
    If your situation is abnormal and you see message delivery throttling state to “4” when the following performance counters are high or if you expect any of you integration
    process could have impact on following counters, then you can consider the suggestion by Microsoft. Don’t change the default setting.
    High process memory
    Process memory usage (MB)
    Process memory usage threshold (MB)
    You can see these counters under “BizTalk:MessageAgent”
    You can gauge these performance counter and its maximum values if have done any regression/performance testing in your test servers. If you have seen these counters having
    high values and causing throttling, then you can update the Process memory usage.
    Or unexpectedly you’re process high throughput messages in production which is causing these counters to go high and cause throttling, then up can update the Process memory
    usage.
    The above two cases where I know my expected process usage (by doing performance testing) or suddenly my production server processing has gone high due to unexpected business
    hike (or any reasons) which caused throttling, then do changes to default throttling setting.
    Just changing the default setting without actual reason could have adverse effect where you end up allocating 
    more processing capacities but the actual message processing message usage ever is low means you end up investing in underutilised resources.
    Regards,
    M.R.Ashwin Prabhu
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Maybe you are looking for

  • How can I change the menu bar in a Quicktime video?

    My cousin and I are starting a video network and we want to create custom menu bars for our videos. We know about watermarks on the videos themselves, but I've seen some videos have custom menu bar titles irrespective of the file names and I was wond

  • Why does Safari crash every time I attempt to download

    Every time I try to download skype or an alternate browser such as Chrome, the download progresses up to about 13mb then freezes, the spinning wheel of sadness appears and safari closes. I get the following error report. Any help would be amazing, th

  • Object variable not set error in SAP-VB Connect.

    This is the coding part i have used for connecting SAP and VB for creating the Sales Order in SAP. But it gives the error in the line oheader.Value("DOC_TYPE") = Text1(0) as Object variable or With block variable not set. What could be the reason, pl

  • Shutting down with certain applications.

    My computer keeps shutting down when I open Adobe and other video programs. We were at the Apple Store Sat. and the tech did his business and said we would be good to g. We were until we realized none of our applications were still there. When we dow

  • Connect to MKS Alta 1480 Device Net Mass Flow Controller

    I have a MKS Alta 1480 mass flow controller (MFC), MFC Manual, Labview 8.2 and NI PCI-CAN card.  I know have the MFC wired correctly because I can operate it using another program on the PC that used the deviceNet interface.  I want to talk to it via