JNDI when clustering

 

Hi Don ,
          All the manager servers in a cluster send heartbeat messages to each other
          using multicast adress) after a certain time period ( i.e every 10 sec ) ,
          at that time it updates their local JNDI tree .
          When we do clustering and a new object object get bound to a cluster then
          that object's JNDI will be replicated to all the server's in the cluster .
          Thanks and regards
          Johnny
          "Don Ferguson" <[email protected]> wrote in message
          news:[email protected]...
          > We are using ip-multicast to propogate the JNDI information to other
          > servers in the cluster. I believe the update is sent immediately
          > (rather than batched and refreshed periodically) but I'm not sure what
          > the propogation delay.
          >
          > matt wrote:
          > >
          > > Selvan,
          > > My understanding is that by default all objects registered to JNDI will
          be
          > > clustered unless you specify a "do not cluster" property in the
          > > properties file. The exact property can be found in the API doc for
          JNDI.
          > > Sunil
          > >
          > > Selvan Ramasamy <[email protected]> wrote in message
          > > news:[email protected]...
          > > > Hello,
          > > >
          > > > If I do cluster few servers then what about the objects I bind them in
          the
          > > > JNDI.
          > > > how frequently these JNDI get reflected to all the cluster servers.
          > > > I am going to do some caching for my clients by binding some java
          > > classes
          > > > in the JNDI.
          > > >
          > > > I think that I am not clear about JNDI bindings with cluster.
          > > >
          > > > Please help me out what exactly happens when do clustering and a new
          > > object
          > > > get bound in the JNDI.
          > > >
          > > > Thanks
          > > > /selvan
          > > >
          > > > Selvan Ramasamy
          > > > Captura Software Inc
          > > >
          > > >
          > > >
          

Similar Messages

  • Why opening from java the rpt search for a JNDI when it's setup for a DNS ?

    I downloaded CR for eclipse 2.
    All is 'quite' working froma a java app.
    i've only a problem with an 'jndi name search error'. I'll try to explain.
    In the RPT i use a DSN connection to a sql server into a differente machine. When I open directly the rpt, all is working.
    From java code, i'll open the report, but when i try to export  to pdf iit tell me about an error 'jndi name search error', with the name of the DSN connection i setup.
    Why? Why opening rpt all is working, but opening from code NOT is working ?
    What's the difference from two opening methods? Why an .rpt opened from java cannot just open the connection like when opened from cristal report !?
    *My question is: why opening from java the rpt search for a JNDI when it's setup for a DNS connection ?! *

    The .rpt has been originally created from an ancient version of Cristal report. probably the '8'.
    In an italian software called 'Business', the .rpt is populated for printing of invoices and similar docs.
    My society is trying to 'integrate' our software with the .rpt used from our customer.
    So we want simply open .rpt, add a new logo, set the selection for record and save as pdf.
    We so bought Cristal report 2008 (v.12 ), opened the .rpt, saved (so it 's now in a supported version).
    The sql server is located at 10.1.2.40, and is a Microsoft Sql Server.
    In my development pc I've installed Cr 12. I added a User DSN to point to Sql server at 10.1.2.40, at right DB with username and password. Opening from my development machine the .rpt and 'running' it, it display the data. Ok !
    I downloaded CR4 Eclipse 2.
    I open report using the unmanaged sdk. (to access it through file system, not via RAS), Ok.
    I set selection record. Ok.
    I execute .export with 'PDF' for format option and here I get an exception: the JNDI name 'CPR'  is not found. Where CPR is the DSN name setup into .rpt from Cristal Report 2008.
    So, no, i'm not trying to using the designer from Eclipse, but from the full application. But I must use the rpt at runtime to export some rendered records.
    What must I do to do this?
    CR4E only supports java based connections, so it is looking for the JDBC/JNDI name and won't look at the DSN's.
    How Can i setup at runtime a JDBC / JNDI connection ?
    I already have a 'connection' from my code to the sql server, using sqlserver jdbc driver v. 4 from microsoft. And executing query I see the results. So i have right driver, ip, db name, user name and password
    But is there a way to simply tell at runtime to my .rpt to use THIS connection? Or a similar connection...
    Thanks in advance for help provided to us. (we bought a CR license only for this work...)

  • Exception:  Cluster address must be set when clustering is enabled

    Hi,
    I've created a simple web service and deployed to a cluster. When i invoke the WSDL url (http://localhost/webservice/MyService?WSDL) through the browser i get the enclosed exception (listed at the bottom)
    I can easily solve this issue by explicitly stating a cluster address witihin the admin console ( Environment->Clusters->Cluster Address:), however the documentation states that i do not need to do this. ( http://edocs.bea.com/wls/docs100/webserv/setenv.html#wp220521 )
    Can someone clarify that indeed I need to explicitly declare a Cluster Address when deploying and invoking web services within a clustered environment.
    Thanks
    #-Exception as displayed within the browser--
    Error 500--Internal Server Error
    java.lang.IllegalArgumentException: Cluster address must be set when clustering is enabled.
         at weblogic.wsee.server.ServerUtil.getClusterAddress(ServerUtil.java:439)
         at weblogic.wsee.server.ServerUtil.getHTTPServerURL(ServerUtil.java:130)
         at weblogic.wsee.server.servlet.WsdlRequestProcessor.getAddressInfo(WsdlRequestProcessor.java:161)
         at weblogic.wsee.server.servlet.WsdlRequestProcessor.process(WsdlRequestProcessor.java:76)
         at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:257)
         at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

    Hi,
    You will have to specify the address for the cluster to get this work. This was done because if cluster address is not specified, there were other issues that popped up.
    Its works as designed.
    Regards.

  • JNDI and clustering

    All,
              What happens with naming services in a clustered environment?
              Is the naming service dupilcated across all servers in the cluster or
              are they other approaches?
              How is this configured?
              What is the effect on the client when requesting the initial context ina
              clusteerd environment?
              Thanks in advance
              Aaron
              

    Aaron Robinson wrote:
              > All,
              >
              > What happens with naming services in a clustered environment?
              > Is the naming service dupilcated across all servers in the cluster or
              > are they other approaches?
              >
              Anything you bind into the jndi tree will be replicated.
              > How is this configured?
              Nothing to configure. It is automatic when you start servers in a
              cluster.
              > What is the effect on the client when requesting the initial context ina
              > clusteerd environment?
              None.
              >
              > Thanks in advance
              > Aaron
              Cheers
              - Prasad
              

  • Error with JNDI when creating new data source

    Hi :
    This weekend, while adding new applications to the production environment we ran into a problem where the JNDI tree of the new managed servers was unreachable.
    The error message we saw was:
    <1364066840022> <BEA-149231> <Unable to set the activation state to true for the application 'EOI'.
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:349)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    weblogic.common.ResourceException: is already bound
    at weblogic.jdbc.common.internal.RmiDataSource.start(RmiDataSource.java:387)
    at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:136)
    at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:97)
    at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:346)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    We traced the issue to a new data source that was added were we found that along with the the expected jndi name entry in the jdbc xml file, there were two blank entries:
    <jndi-name>weblogic.jdbc.DataSource.EOI</jndi-name>
    <jndi-name></jndi-name>
    <jndi-name></jndi-name>
    The data source was deleted, consoles restarted, the data source recreated and the issue occured again. To get by the issue we had to manually remove the blank tags from the xml file.
    We created 2 new data sources, and it only happened on the one. The same data source each time. Additionally, this issue did not occur when these changes were made in our lower (development, qa) regions.
    The version is the same in all three regions.
    WebLogic Version:     
    WebLogic Server Temporary Patch for 9324911 Wed Feb 03 22:38:01 PST 2010
    WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967
    Is this a known issue? And if so, is there a way to avoid it, other than to start constantly checking the newly created XML files?
    Thank you
    ted

    Yes, this is a common issue and documented in Oracle Docs:
    WebLogic Server: Getting "weblogic.common.ResourceException: is already bound" exception with JDBC JNDI name (Doc ID 1154250.1)
    The only fix is that you need to remove the empty value entries.
    Cheers!!
    AJ

  • How to add an object in JNDI when a server starts?

    I have an integration app. The app contains EJB project. The project contains EJB which reads data from LDAP.
    My first version of EJB contains the following code:
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
    env.put(Context.PROVIDER_URL, strProvider);
    env.put(Context.SECURITY_AUTHENTICATION, strAuth); env.put(Context.SECURITY_PRINCIPAL,strPrincipal); env.put(Context.SECURITY_CREDENTIALS,strCredentials);
    DirContext dirCtx = new InitialDirContext(env); // exception
    All connection properties are hardcoded and it is not a good practice.
    Also I can put those properties into deployment descriptor. But I am going to have some EJBs and each EJB has to have those properties into descriptors. It is not useful.
    My idea: I would like to have whatever object which is called automatically when a server starts; this object creates InitialDirContext and put the context into JNDI. All EJBs lookup the context by a name. But I don't know how to do that.
    And another question: how to change connection properties dynamically? My idea is putting the properties in XML Cache. And my object (which creates InitialDirContext) reads the properties from XML Cache. Can I handle a message that my properties in XML Cache have been changed and in this cases my object reads new properties and calls rebind() to update InitialDirContext?
    Thanks,
    Ivan

    To bind an object into the JNDI tree check the documentation here:
    http://e-docs.bea.com/wls/docs81/jndi/jndi.html#475702
    If this is to be used by all your applications that you deploy on the server check out the startup/shutdown class documentation here:
    http://edocs.bea.com/wls/docs81/ConsoleHelp/startup_shutdown.html
    Cheers
    IV

  • How to achieve session failover when clustering tomcat6

    Hi ,
    I have followed SAP KB 1529429 - How to create a Tomcat cluster with LBR as load balancer and BusinessObjects Enterprise XI 3.1.
    when I am shutting down one tomcat automatically the user is being throwed out of the session.
    Regards,
    Saikrishna

    Gi,
    sure, you can. This task is out of Scope of the SAP BI Product Suite and has to be achieved only on Tomcat Level.
    You wont get any Support from SAP for this.
    Please refer to the official Tomcat Documentation.
    Apache Tomcat 7 (7.0.52) - Clustering/Session Replication HOW-TO
    Regards
    -Seb.

  • Exception when retreiveing list from JNDI when the list updates at the same time.

    Hi
    I get a Exception when i am retreiving a list from the jndi:
    Start server side stack trace:
    com.sun.java.util.collections.ConcurrentModificationException
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at java.lang.RuntimeException.<init>(Compiled Code)
    at
    com.sun.java.util.collections.ConcurrentModificationException.<init>(Concurr
    entModificationException.java:48)
    at com.sun.java.util.collections.HashMap$HashIterator.next(Compiled
    Code)
    at
    weblogic.jndi.toolkit.ReadOnlyMapBasedNamingStore$1.nextElement(Compiled
    Code)
    at weblogic.jndi.toolkit.AbstractNamingEnumeration.next(Compiled
    Code)
    at
    weblogic.jndi.toolkit.AbstractNamingEnumeration.nextElement(Compiled Code)
    at
    weblogic.utils.enumerations.BatchingEnumerationBase.nextBatch(Compiled Code)
    at
    weblogic.utils.enumerations.BatchingEnumerationBase_WLSkel.invoke(BatchingEn
    umerationBase_WLSkel.java:66)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(Compiled
    Code)
    at
    weblogic.rmi.extensions.BasicRequestHandler.handleRequest(Compiled Code)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    at weblogic.kernel.ExecuteThread.run(Compiled Code)
    End server side stack trace
    It says in the documentation of the weblogic server that: if the jndi is
    updated while you are retreiving the list from the server, you will only get
    the old list.
    And that is ok for me. But insted i get this exception that interupts the
    list retreiving. And if i just catch this exception an just continue or
    start again, it comes over and over.
    the code that does this, is like this:
    InitialContext context = new InitialContext(env);
    NamingEnumeration list = context.listBindings("sid");
    Vector copy = new Vector(10000,1000);
    log("Initiating copy of JNDI list!");
    try
    while (list.hasMore())
    copy.addElement(list.next());
    catch (Exception e)
    log("Copying interupted:" + e.toString());
    How can i solve this ?
    Is it a configuration of the server problem ?
    Are ther other ways of retreiving the list ?
    -Ståle Tomten

    Be carefull - you read Object two times, so if you
    have only one object you will get null after second
    reading, and NullPointerException as a result if you
    try to do smth with null.
    Wrong:
    while( inputFromServlet1.readObject() != null)
    Object o = inputFromServlet1.readObject();Previous man example is also wrong because you
    cannot declare anything in while
    Sorry for this one... I certainly must have spent too much time on these fora ;-)
    Thanks for the correction, by the way...
    Correct:
    Object o;
    while( (o = inputFromServlet1.readObject()) != null)
    String str = (String)o;
    System.out.println("Got Object");

  • Lost My CF Administrator When Clustering

    Need some help, please.  I have two identical CF10 enterprise servers set up with IIS7 on Win2008.  Each has 4 CF instances running.  I decided to experiment with clustering as I''ve run previous version of CF as J2EE instance with much success.
    So, on server 1 I registered a remote instance on server 2.  No problem.  I then went into the Cluster Manager and added this remote instance to my existing cluster.  Upon clicking Submit I was greeted by a plain white screen that said only: 503 Server unavailable.  Several refreshes predictably yielded the same thing.
    I restarted the CF instance.  Now I get IIS error 500, IsapiFilterModule when trying to access CF Admin
    I re-ran my web server connector tool.
    I've tried falling back to older server.xml files.
    I'm sure something got screwed up when trying add to my cluster but without a CF Admin I'm not sure how to undo this.
    All other instances and all remote instance on server 2 are fine.  I can access them with no problem.  But, I cannot access my main CFAdmin on Server 1.
    Any help?

    Found my answer a few minutes after posting, thankfully.
    In my CF install directory I found a 'config' folder.  In there I opened the cluster.xml file where I found the cluster config of my server.  I removed the reference to the remote server I had registered and attempted to add to my cluster.  Then I restarted the CF instance and re-ran the web config tool and that fixed it.  Thank God!  Was sweating that one for a while!
    Not sure what happened here because everything is running normally otherwise.  Like I said, I've run multi-instance CF in J2EE mode with much success in the past so this is a disappointment.

  • Problem when clustering with O Cluster

    Dear all ,
    i have the following error when trying to build a clustering model on my data. I used O cluster with the default settings. The strange thing is i have have created a build before for the same data and on the same machine and it worked fine. what could be wrong ? The error description says a memory problem but my settings have not changed since last time.
    here is the complete error desciption
    Server task state: error
    Server task detail:
    ORA-40101: Data Mining System Error ORA-40101: Data Mining System Error ORA-40101: Data Mining System Error ODM_OC_CLUSTERING_MODEL-BUILD_OC.build_ocluster--20010
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
    ORA-06512: at "DMSYS.ODM_OC_CLUSTERING_MODEL", line 122
    ORA-06512: at "DMSYS.ODM_OC_CLUSTERING_MODEL", line 2408
    ORA-40101: Data Mining System Error ODM_OC_CLUSTERING_MODEL-BUILD_OC.ocluster--20010
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
    ORA-06512: at "DMSYS.ODM_OC_CLUSTERING_MODEL", line 122
    ORA-06512: at "DMSYS.ODM_OC_CLUSTERING_MODEL", line 2312
    ORA-06500: PL/SQL: storage error
    ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu call ,pmucalm coll)
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
    ORA-06512: at "DMSYS.ODM_OC_CLUSTERING_MODEL", line 122
    ORA-06512: at "DMSYS.ODM_OC_CLUSTERING_MODEL", line 2408
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
    ORA-06512: at "DMSYS.ODM_OC_CLUSTERING_MODEL", line 122
    ORA-06512: at "DMSYS.ODM_OC_CLUSTERING_MODEL", line 2312
    ORA-06512: at "DMSYS.DBMS_DATA_MINING", line 30--
    Many thanks
    Lamia Abo zaid

    hi ,
    In this scenario u can use the load balancer instead of fail over clustering .
    I would suggest u to create apache proxy for redirect the request for many jboss instance.
    Rgds
    kathir

  • Error when clustering a Connection pool

              We are testing the cluster feature of WebLogic 6.0 Sp2 on MS Win2K Pro and have
              run into a problem trying to cluster the petstoreServer in the Petstore domain
              to a remote machine. I cannot get the Connection pool, called "petstorePool",
              to load on the remote managed server. This is preventing the database from working
              properly on the remote managed server. What can I do to enable the Connection
              Pool to load properly? Below is the boot-up window for the remote managed server.
              Starting Cluster Service ....
              <Jul 13, 2001 8:19:40 AM CDT> <Error> <JDBC Connection Pool> <Cannot startup con
              nection pool "petstorePool" Cannot load driver class: COM.cloudscape.core.JDBCDr
              iver>
              <Jul 13, 2001 8:19:43 AM CDT> <Critical> <WebLogicServer> <Failed to invoke star
              tup class "StartBrowser", java.lang.ClassNotFoundException: com.bea.estore.start
              up.StartBrowser>
              <Jul 13, 2001 8:19:43 AM CDT> <Notice> <WebLogicServer> <ListenThread listening
              on port 7007, ip address 10.10.10.61>
              <Jul 13, 2001 8:19:43 AM CDT> <Notice> <WebLogicServer> <SSLListenThread listeni
              ng on port 7008, ip address 10.10.10.61>
              <Jul 13, 2001 8:19:43 AM CDT> <Notice> <WebLogicServer> <WebLogic Server started
              >
              

    could you post your managed server's start script?
              Make sure Cloudscape's libs are in the classpath.
              Andy Levy wrote:
              > We are testing the cluster feature of WebLogic 6.0 Sp2 on MS Win2K Pro and have
              > run into a problem trying to cluster the petstoreServer in the Petstore domain
              > to a remote machine. I cannot get the Connection pool, called "petstorePool",
              > to load on the remote managed server. This is preventing the database from working
              > properly on the remote managed server. What can I do to enable the Connection
              > Pool to load properly? Below is the boot-up window for the remote managed server.
              >
              > Starting Cluster Service ....
              > <Jul 13, 2001 8:19:40 AM CDT> <Error> <JDBC Connection Pool> <Cannot startup con
              > nection pool "petstorePool" Cannot load driver class: COM.cloudscape.core.JDBCDr
              > iver>
              > <Jul 13, 2001 8:19:43 AM CDT> <Critical> <WebLogicServer> <Failed to invoke star
              > tup class "StartBrowser", java.lang.ClassNotFoundException: com.bea.estore.start
              > up.StartBrowser>
              > <Jul 13, 2001 8:19:43 AM CDT> <Notice> <WebLogicServer> <ListenThread listening
              > on port 7007, ip address 10.10.10.61>
              > <Jul 13, 2001 8:19:43 AM CDT> <Notice> <WebLogicServer> <SSLListenThread listeni
              > ng on port 7008, ip address 10.10.10.61>
              > <Jul 13, 2001 8:19:43 AM CDT> <Notice> <WebLogicServer> <WebLogic Server started
              > >
              

  • Slow performance when clustering wl8.1 throught ms iis

    We have our webserver setup to load balance to multiple weblogic 8.1 instances via IIS. If the IIS service is started and one or more weblogic instances are not then response times are very slow. Once all the weblogic instances (specified in WebLogicCluster= parameter of the iisproxy.ini file) have been brought up, performance is fine. Any help to improve the initial performance and/or explanations of this problem would be greatly appreciated.

    Hi,
              Go through the following link and kindly follow the weblogic perfomance tunning parameters.
              http://e-docs.bea.com/wls/docs81/perform/WLSTuning.html#1104298
              ---Anilkumar kari

  • Weblogic Clustering  - No server found

              Hi folks,
              Occasionaly, when we weblogic ping our servers, we get "No server found" errors.
              In the server weblogic.log files, we don't see much in the way of information other
              than a heartbeat being the last entry usually in the log.
              These errors sometimes correspond with an inability to access the website from a
              browser as well, which obviously is a little difficult to explain to customers/partners.
              According to the weblogic console, garbage collection doesn't appear to be the cause
              of this problem. It's happening roughly every 30 minutes and behaves as it should
              (up to 99% down to 10-20%). The collection occurs instantaneously and doesn't appear
              to correspond to any problems in the servers.
              We have about 1200 java classes, 1100 jsps, ~200 ejb classes that are deployed,
              and 200-300 thousand page views per day.
              We have numerous jobs using the weblogic timers, loading up caches and performing
              other tasks. I'd like to blaim them, but there is no spike in CPU usage and, like
              I said, garbage collection is behaving.
              Session replication is not turned on, however clustering is enabled for failover.
              We're deployed on 2 sun servers, Solaris 2.7, Sun 420 / sparc architecture. We're
              using Jdk 1.2.1._04. We've allocated 1 Gigabyte of ram to each VM on each server.
              We've been battling these issues for over two years now, slowly upgrading with the
              patches. We've tweaked every configuration option about a half dozen times.
              The only two tweaks that I've found to be helpful were reducing from 4 VMs on 2 servers
              to 2 VMs on 2 servers. And changing the connection timeout from 5 minutes to 2
              minutes on the web layer. The first tweak makes sense, the second tweak is very
              mysterious.
              I'd like to upgrade further to later patches, however my developers are telling me
              that we need to use JDK 1.3 because our JSPs are too big for JDK 1.2 and there are
              memory leaks in JDK 1.3.
              The reason the JSPs are too big is because the latest service packs add more code
              to the JSPs, thus creating verify errors from too large code blocks all over the
              place.
              Questions:
              - is there a way to turn off multicasting, jndi, ebj clustering but still have failover?
              - anyone deploying JDK 1.3 on Solaris with weblogic? Are you running into memory
              problems?
              - shall we struggle on or just rewrite everything so it works in resin or some other
              servlet engine, dumping weblogic altogether?
              

    Tim,
              Can you mention the WLS version & SP level?
              BTW, have you ever considered contacting weblogic support?
              This kind of issues are best solved by BEA support or calling
              BEA consultant to your site. ;-)
              Kumar
              Tim Shephard wrote:
              > Hi folks,
              >
              > Occasionaly, when we weblogic ping our servers, we get "No server found" errors.
              >
              > In the server weblogic.log files, we don't see much in the way of information other
              > than a heartbeat being the last entry usually in the log.
              >
              > These errors sometimes correspond with an inability to access the website from a
              > browser as well, which obviously is a little difficult to explain to customers/partners.
              >
              > According to the weblogic console, garbage collection doesn't appear to be the cause
              > of this problem. It's happening roughly every 30 minutes and behaves as it should
              > (up to 99% down to 10-20%). The collection occurs instantaneously and doesn't appear
              > to correspond to any problems in the servers.
              >
              > We have about 1200 java classes, 1100 jsps, ~200 ejb classes that are deployed,
              > and 200-300 thousand page views per day.
              >
              > We have numerous jobs using the weblogic timers, loading up caches and performing
              > other tasks. I'd like to blaim them, but there is no spike in CPU usage and, like
              > I said, garbage collection is behaving.
              >
              > Session replication is not turned on, however clustering is enabled for failover.
              >
              > We're deployed on 2 sun servers, Solaris 2.7, Sun 420 / sparc architecture. We're
              > using Jdk 1.2.1._04. We've allocated 1 Gigabyte of ram to each VM on each server.
              >
              > We've been battling these issues for over two years now, slowly upgrading with the
              > patches. We've tweaked every configuration option about a half dozen times.
              >
              > The only two tweaks that I've found to be helpful were reducing from 4 VMs on 2 servers
              > to 2 VMs on 2 servers. And changing the connection timeout from 5 minutes to 2
              > minutes on the web layer. The first tweak makes sense, the second tweak is very
              > mysterious.
              >
              > I'd like to upgrade further to later patches, however my developers are telling me
              > that we need to use JDK 1.3 because our JSPs are too big for JDK 1.2 and there are
              > memory leaks in JDK 1.3.
              >
              > The reason the JSPs are too big is because the latest service packs add more code
              > to the JSPs, thus creating verify errors from too large code blocks all over the
              > place.
              >
              > Questions:
              >
              > - is there a way to turn off multicasting, jndi, ebj clustering but still have failover?
              > - anyone deploying JDK 1.3 on Solaris with weblogic? Are you running into memory
              > problems?
              >
              > - shall we struggle on or just rewrite everything so it works in resin or some other
              > servlet engine, dumping weblogic altogether?
              >
              

  • Shared singleton across clusters?

              I have a singleton class that I would like to share across
              servers in a cluster. Simply storing it in the session object
              doesn't seem like the solution because user a and user b, each with their own
              copy of this object, could quickly get out of synch. Is there a way for me to
              bind this object to the jndi tree for the entire cluster so that everyone uses
              the same
              object? I know I could keep things in sync by storing the info
              in the database, but the whole reason for this object's existence is to avoid
              unnecessary trips to the database. Thanks!
              

    Hi,
              Is the Coherence Cache ur talking abt useful for the fast reads ???
              We have situation with our application, where we need a distributed cache
              which handles fast reads .. and rite now we r looking for a product or
              implementation which does the same...And this cache is dynamic to some
              extend that the applications can change this cache rarely ..but application
              access this cache very very often.
              Right now without thinking abt cluster with a Single Server we can do this
              easily by using JNDI.. but distributing JNDI across cluster in weblogic have
              there own problems.. as we need to find a way to replicate the tree when
              there is a change to this cache.
              Right now thinking abt wrapping this cache with a Stateful Session Bean and
              I dont have a clue how weblogic will replicate the changes and also abt the
              fail over situations... Do u think is this a good approach or is there any
              other alternative?
              Hope to hear back from u guys..
              Regards and TIA
              Amar Pratap
              "Cameron Purdy" <[email protected]> wrote in message
              news:[email protected]...
              > > I do not think it is a good idea to bind data objects in JNDI
              >
              > It does work for certain cases on Weblogic, but replicated objects can
              > collide in Weblogic's JNDI implementation and the approach is not
              portable.
              >
              > > Moreover singleton objects are for
              > > a single VM and not for a cluster.
              >
              > It is a common requirement for applications that have to scale up to a
              > cluster. These applications typically use a singleton when they aren't
              > clustered, and it can provide immense performance improvements ... but
              when
              > clustering there are relatively few choices for caching across a cluster.
              > Besides our Coherence product, which is a clustered cache, there are
              several
              > options:
              >
              > 1) read-only ejb with JMS invalidation (Seppuku pattern that Dima
              designed)
              > 2) JNDI (may suffer from collision problems)
              > 3) RMI object (single point of failure and requires network traffic)
              >
              > > I would suggest you consider the database
              >
              > That's definitely the choice for transactional data (i.e. you don't want
              to
              > lose it no matter what), but for a cache, you are typically caching the
              data
              > that is in the database ... because the database is high-latency and
              > increasingly expensive as you scale.
              >
              > Applications that rely solely on the database and do not cache suffer
              > terribly when scaling.
              >
              > Peace,
              >
              > --
              > Cameron Purdy
              > Tangosol Inc.
              > Tangosol Coherence: Clustered Coherent Cache for J2EE
              > Information at http://www.tangosol.com/
              >
              >
              > "Rajesh Mirchandani" <[email protected]> wrote in message
              > news:[email protected]...
              > > I do not think it is a good idea to bind data objects in JNDI. They will
              > not be
              > > available to the other servers in the cluster. Moreover singleton
              objects
              > are for
              > > a single VM and not for a cluster. I would suggest you consider the
              > database
              > > approach.
              > >
              > > There are a lot of discussions in this newsgroup. Search for previous
              > postings.
              > >
              > > sdb wrote:
              > >
              > > > I have a singleton class that I would like to share across
              > > > servers in a cluster. Simply storing it in the session object
              > > > doesn't seem like the solution because user a and user b, each with
              > their own
              > > > copy of this object, could quickly get out of synch. Is there a way
              for
              > me to
              > > > bind this object to the jndi tree for the entire cluster so that
              > everyone uses
              > > > the same
              > > > object? I know I could keep things in sync by storing the info
              > > > in the database, but the whole reason for this object's existence is
              to
              > avoid
              > > > unnecessary trips to the database. Thanks!
              > >
              > > --
              > > Rajesh Mirchandani
              > > Developer Relations Engineer
              > > BEA Support
              > >
              > >
              >
              >
              

  • EJB 3.0 local interface JNDI

    Hello
    I found some information that will probably help a lot of people having trouble with local interface not referenced in JNDI.
    You need to delacre each local interface in the web.xml.
         <ejb-local-ref>
              <ejb-ref-name>MappedNameInYourEJB</ejb-ref-name>
              <ejb-ref-type>Session</ejb-ref-type>
    <local> yourLocalInterface
              </local>
         </ejb-local-ref>
    The weird thing about this is you don't need to do it when you use remote interface!! I would have thought Weblogic was smart enough to put your EJB in the JNDI when you declare @local on your interface!!
    Am I wrong with something here?
    When I read the EJB spec, it says you don't need to declare your EJB anywhere when you use annotation....
    If someone have an explanation I would be very happy to read about it!!!!
    Tanx

    Hi,
    In our current impl, we don't bind local business interface impl onto global jndi, this is because adding global JNDI binding for local EJB means every local business interface object must be bound into global JNDI, which will give rise to strange errors when accessing remotely or in different application context.
    On the other hand, you needn't add each local interface in the web.xml, you can use annotation through EJB link, which is the suggested way to use EJB local reference, for example:
    @Stateful(name="AccountManagementBean")
    public class AccountManagementBean
    @EJB(
    name="PersonBeanRef",
    beanName="PersonBean"
    Person person;
    @Stateless(name="PersonBean")
    public class PersonBean implements Person {
    In this example, AccountManagementBean has a local reference of PersonBean, the key is you should use beanName in @EJB, whose value is the ejb name of referenced EJB.

Maybe you are looking for