Bi publisher cluster on weblogic 10.3

I'm trying to setup a BI publisher cluster on weblogic server. I managed to do it on on one physical machine. I deployed war application as an exploded archive and selected "I will make the deployment accessible from the following location C:\apps\xmlpsever.war", and in xmlp-server-config.xml I setup repository as "C:\apps\xmlpsever.war\home\repository\XMLP", and everything works fine.
When I try to do same thing, just that my weblogic machines are different physycal machines I have a problem. If I deploy an application in a war package it doesn't work, and if i deploy it as an exploded archive (like said in Bi publisher Installation Guide) it copies the application to all physical machines but application doesn't deploy well because of BI publisher repository path. I tried to put a repository in one folder, share that folder and then map it to X: on every machine, it doesn't help.
Thank you for any help regarding how to configure publisher repository, XMLDB or any solution?

your cluster is unicast or multicast? if you are using unicast, I would suggest switching to multicast and see if the problem still occurs.
keep us posted.

Similar Messages

  • BI Publisher Cluster Deployment Issue

    Hi All,
    I have installed BI Publisher in two nodes A and B (stand alone basic). During scheduler configuration, I have checked cluster option. A load balancer has been configured to point to these two nodes.The data source is file system and location is on network file server.
    I have a java program that call BI Publisher webservice and submit the job for scheduling. The java program points to load balancer ip. Currently I am facing two issues as below:
    1. When I call BI Publisher webservice to schedule the job, I can see that the job is scheduled through one node only
    2. Processing the scheduled job (report generation is distributed into two nodes. But this distribution is not even. If I shedule 5 jobs, Node A is executing one job while the other node executes reamining 4 jobs. Thus I have noticed that Node A remains idle after completing the job till the other node completes the report generation
    Do I need to do make any changes/ perform additional configuration so that the job is distributed among the nodes evenly.
    Your help will be highlu appreciated
    Thanks
    Angshuman

    First, make sure you've got enough machine resources as BIEE11g is resources hungry.
    Next, after installation you should have icons to start BIEE11g (try windows version as it is easier to start up).
    Run the startBIEE11g script and it will take some minutes, be patient. Once you get all processes running
    then you can try to login.
    Take a look at my post:
    http://oraclebiblog.blogspot.com/2010/11/starting-and-stopping-biee-from-command.html
    Good luck
    regards
    Jorge

  • Round Robin was not happening for my cluster with WebLogic Proxy Plugin

              Hi,
              I configured my cluster with software load balancer, HTTPClusterServlet. By default,
              it is load balancing with Round Robin Algorithm. That means one HTTP request
              goes to server1, and the other HTTP request goes to server2. However, it is not
              what I can see no matter for the requests in one HTTP session or not.
              Say I open two browser, and log into my application with two different users,
              one is "cyang", the other is "xpression". Then the HTTP request (for servlet/jsp)
              from two browsers always go to the same server1, server2 is not invoked at all.
              I did see one time, with only one session (one browser with "xPression" user log
              in), the most requests go to server1, suddenly I am brough into log in page, then
              I noticed that the request for "xPression" moved to server2 although server1 is
              still alive. Therefore, at most, I can say it is "Random", rather than "Round
              Robin".
              What is the real meaning for HTTP servlet/jsp load balancing algorithm? Does
              Round Robin mean request go to each server in turns? Does it have to be different
              session or it can be within one session?
              

    It should be sticky. If not, then bug / config error.
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "Carole Yang" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Thanks. Yeh, with two kind of browsers, I do see the request goes to
              different
              > servers.
              >
              > That goes back to the original question. Does "Round Robin" here fall
              into the
              > scope of a HTTP session. However, that is not always true for my tests.
              Sometimes,
              > HTTP request just randomly goes to another server while in the same HTTP
              session.
              > It is not sticky to one particular server during one session.
              >
              >
              >
              > --Carole
              >
              >
              > "Cameron Purdy" <[email protected]> wrote:
              > >Has to be different sessions to go to different machines.
              > >
              > >Best way to test is to run one session in IE and the other in Mozilla
              > >or
              > >Netscape.
              > >
              > >Peace,
              > >
              > >Cameron Purdy
              > >Tangosol, Inc.
              > >http://www.tangosol.com/coherence.jsp
              > >Tangosol Coherence: Clustered Replicated Cache for Weblogic
              > >
              > >
              > >"Carole Yang" <[email protected]> wrote in message
              > >news:[email protected]...
              > >>
              > >> Hi,
              > >>
              > >> I configured my cluster with software load balancer,
              HTTPClusterServlet.
              > >By default,
              > >> it is load balancing with Round Robin Algorithm. That means one HTTP
              > >request
              > >> goes to server1, and the other HTTP request goes to server2. However,
              > >it
              > >is not
              > >> what I can see no matter for the requests in one HTTP session or not.
              > >>
              > >> Say I open two browser, and log into my application with two different
              > >users,
              > >> one is "cyang", the other is "xpression". Then the HTTP request (for
              > >servlet/jsp)
              > >> from two browsers always go to the same server1, server2 is not invoked
              > >at
              > >all.
              > >>
              > >> I did see one time, with only one session (one browser with "xPression"
              > >user log
              > >> in), the most requests go to server1, suddenly I am brough into log
              > >in
              > >page, then
              > >> I noticed that the request for "xPression" moved to server2 although
              > >server1 is
              > >> still alive. Therefore, at most, I can say it is "Random", rather
              > >than
              > >"Round
              > >> Robin".
              > >>
              > >> What is the real meaning for HTTP servlet/jsp load balancing algorithm?
              > >Does
              > >> Round Robin mean request go to each server in turns? Does it have
              > >to be
              > >different
              > >> session or it can be within one session?
              > >
              > >
              >
              

  • Inconsistent message publishing times through weblogic JMS client

    Hi,
    We have a weblogic JMS application which we are deploying in a clustered weblogic enviornment. We are using distributed queues/topics with file store. We have both JMS cliient and server running on separate weblogic clusters. Most of the times it will take about 10 milli seconds to push the message into queue, but 1 in 50 messages takes about anywhere between 0.2 sec to 6 secs. Recently for three days it just took 10 msec for all the messages throught these three days and then started behaving erratically again. I am not able to really figure out why there is lot of deviation in the publishing times. When I monitor both my client and server through admin consiole, I don't see any stuck threads, heap size is normal, cpu load is normal, no problems with network. Please help me to figure out the root cause for abnormal publishing times.
    Regards
    Koti

    Could you check if there are JVM garbage collections during some the publishing times.
    In particular check if there are any full garbage collection occuring when you notice such a deviation in the publishing time.

  • Java publishing framework using Weblogic personalization

    Hi All, Has anyone used the Weblogic personalization server/portal or
    a different Weblogic product as a publishing framework.
    We want to design a publishing system in which we can quickly create
    templates for new type of content on the website, and provide an
    interface for entering the data to the admins. The data can then be
    presented using XML/XSL transformation, and the source can either be a
    database or static XML file.
    Cocoon does provide a framework that comes close to our requirements,
    but as we are using weblogic it might be worth expoling if a
    commercial product can be used for such a framework.
    I am sure many people have a need to post content on the site and use
    a variety of mechanisms to use it.
    Also, can the Portal product be used to generate portlets which can be
    placed on multiple pages. We are looking at 500+ pages in our site,
    with 100+ portlets.
    I can give more specific details if needed. Any help is appreciated.
    Please feel free to also email at [email protected]
    Thanks, Yogi.

    1) http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=4
    2)Make sure you add your JDBC drivers to the beginning of CLASSPATH in either setDomainenv.cmd or setEnv.cmd
    3)What really helped was BEA support and playing with BEA's JDBC example that shows how to create and deploy and use a data source.
    http://dev2dev.bea.com/codelibrary/code/examples_jdbc.jsp

  • Rejoining a cluster in WebLogic 5.1

              Sorry, I haven't had a chance to test this out, so here is a dumb
              question - once a server goes down in a cluster, I know the failure
              is detected by the peers and the server list is modified accordingly
              but what happens when the failed server comes back up and WebLogic
              is started again? Can it successfully join the already up and running
              cluster?
              Thanks
              Satish
              

              Yes
              "Satish Nallur" <[email protected]> wrote:
              >
              >Sorry, I haven't had a chance to test this out, so here
              >is a dumb
              >question - once a server goes down in a cluster, I know
              >the failure
              >is detected by the peers and the server list is modified
              >accordingly
              >but what happens when the failed server comes back up
              >and WebLogic
              >is started again? Can it successfully join the already
              >up and running
              >cluster?
              >
              >Thanks
              >Satish
              

  • OS/hw based failover cluster for WebLogic Server 9.2 Standard Edition

    Hi
    Is it possible to run WebLogic Server 9.2 SE on OS/hardware based cluster?
    I want to get an simple failover environment on a cluster of 2 nodes (active-passive).
    Oracle Database can be run in such scenario with one license with a limit of up time for passive instance.
    Is it the same with WLS licences?
    Regards
    WD

    The problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
    Regards,
    tom
    Edited by: TomB on Sep 17, 2010 2:33 PM

  • JMSClientExceptions:055053 -WebLogic10 Cluster - Remote WebLogic JMS - Help

    All,
    We are using a foreign JMS provider from WeLogic 10 cluster to connect to the Remote WebLogic JMS Server. We are getting below error while posting the data to the queue. Any help , ideas as to why this is occuring please?
    / Error
    Error during connection/session creation:weblogic.jms.common.JMSException: [*JMSClientExceptions:055053*]Error creating connection to the server: java.rmi.UnmarshalException: failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is: java.io.StreamCorruptedException|portal
    Thanks a lot for your help.

    All
    The issue popped up gain. Below is the full stack trace. I confirmed that we are using the t3 URL to connect to remote JMS server (which is Weblogic 10 /JMS). Appreciate any insights help to resolve this issue.
    // Stack Trace
    weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: java.rmi.UnmarshalException:
    failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is:
    java.io.StreamCorruptedException
    at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:253)
    at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
    at weblogic.jms.client.JMSConnectionFactory.createQueueConnection(JMSConnectionFactory.java:165)
    at com.juniper.core.mdb.MessageSender.initSession(MessageSender.java:79)
    at com.juniper.core.mdb.MessageSender.<init>(MessageSender.java:64)
    at com.juniper.core.mdb.MDBHelper.processMessage(MDBHelper.java:98)
    at com.juniper.core.mdb.BaseMDB.onMessage(BaseMDB.java:35)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
    at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:3964)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    Caused by: java.rmi.UnmarshalException: failed to unmarshal class weblogic.jms.client.JMSConnection; nested exception is:
    java.io.StreamCorruptedException
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:229)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
    at weblogic.jms.frontend.FEConnectionFactoryImpl_1001_WLStub.connectionCreate(Unknown Source)
    at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:244)
    ... 15 more
    Caused by: java.io.StreamCorruptedException
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
    at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
    at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
    at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
    at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:227)
    ... 19 more
    Thanks
    Edited by: user3285437 on May 4, 2009 9:26 AM

  • Issue when publishing application on Weblogic 12c

    Hi everybody,
    I am facing a strange issue with my web application when I try to deploy it on the web server (for information, I am working with Eclipse). I am saying that it is strange because it is not happening all the time (most of the time it is happening after a refresh of project sources to integrate changes made by other developers of the team). The second part why it is strange is because it is giving an error message that doesn't make sense for me as the class ApplicationServlet mentioned is present in my project and has no annotations inside.
    Below is the error message :
    weblogic.application.ModuleException: [HTTP:101371]There was a failure when processing annotations for application C:\workspaces\.metadata\.plugins\org.eclipse.core.resources\.projects\sample-app\beadep\sample_domain\sample-app. Ensure that the annotations are valid. The error is com.toto.sample.application.ApplicationServlet
    And this is the stack trace :
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
        at oracle.eclipse.tools.weblogic.server.internal.DeploymentProgressListener.watch(DeploymentProgressListener.java:190)
        at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:506)
        at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1466)
        at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:898)
        at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:686)
        at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:539)
        at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
        at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3153)
        at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
    Caused by: weblogic.application.ModuleException: [HTTP:101371]There was a failure when processing annotations for application C:\workspaces\.metadata\.plugins\org.eclipse.core.resources\.projects\sample-app\beadep\sample_domain\sample-app. Ensure that the annotations are valid. The error is com.toto.sample.application.ApplicationServlet
        at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:732)
        at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
        at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
        at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
        at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:167)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
        at weblogic.application.internal.flow.ModuleStateDriver.prepare(ModuleStateDriver.java:38)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:139)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:55)
        at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:706)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:237)
        at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:48)
        at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
        at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:96)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:229)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
        at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: java.lang.ClassNotFoundException: com.toto.sample.application.ApplicationServlet
        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
        at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
        at weblogic.servlet.internal.AnnotationProcessingManager.processServlets(AnnotationProcessingManager.java:214)
        at weblogic.servlet.internal.AnnotationProcessingManager.processAnnotationsInWebXml(AnnotationProcessingManager.java:201)
        at weblogic.servlet.internal.AnnotationProcessingManager.processAnnotations(AnnotationProcessingManager.java:105)
        at weblogic.servlet.internal.AnnotationProcessingManager.processAnnotations(AnnotationProcessingManager.java:81)
        at weblogic.servlet.internal.WebAppModule.processAnnotations(WebAppModule.java:1828)
        at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:717)
    To be honest I don't really know what is causing this and how I can solve it. I would appreciate if somebody can help me on this.
    Thanks in advance    

    Well, under Filters --> Char Restrictions & Default Values, I have the chars arranged in a particular order. But on the portal, under the 'Free Chars' tab, I still see them arranged in alphabetical order. So, my query seems to have no effect on how the FCs are being displayed on the portal.
    Can I change something in the web template? Or is this a portal property?
    Regards.

  • Error when setting up cluster in weblogic 10.3.6

    Hi All,
    We are trying to set up a cluster with 2 managed servers in WLS 10.3.6. The issue is that we do not manage to deploy our application on the managed server as when we start the managed servesr we have the following error message :
    javax.naming.NameNotFoundException: While trying to lookup 'ouaf.servicebean' didn't find subcontext 'ouaf'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'ouaf.servicebean' didn't find subcontext 'ouaf'. Resolved '']; remaining name 'ouaf/servicebean'
    Unfotunately, we are failing to resolve this issue. Any help would be greatly appreciated !!!
    Many thanks.

    HI,
    Just try to clear tmp and cache once a see if you still face same problem.
    If not please put the complete error stack to verify what exactly going on there.
    Regards,
    Kal

  • Cluster License weblogic 10

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

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

  • Weblogic JMS Cluster

    Hi,
              I have a 6.1 cluster that has a JMS server A and a JMS Server B
              deployed and running on each of the managed nodes. As destination I
              created a topic with the same name for each JMS Server. The connection
              factories I deployed to the cluster only.
              My problem is, when I start the second managed server, I get the
              following error:
              <Error> <Cluster> <Conflict start: You tried to bind an object under
              the name
              com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
              have bound
              from 169.59.5.26 is non clusterable and you have tried to bind more
              than once
              from two or more servers. Such objects can only deployed from one
              server.>
              When I understand correctly, this happens because the JNDI tree gets
              distributed to all nodes of the cluster, so there would be two object
              with the same name. How do I solve this situation? Do I have the
              specify different names for topics in different JMSServer running in a
              cluster? How would the load balancing work?
              Please help. Thanks in advance
              Juerg
              

    Tom,
              Thanks for your help so far, I installed the patch and got things
              working. However I still have some open points where you might be able
              to help.
              Let's assume I don't have these smart forwarders and I have four
              topics per JMSServer deployed to two managed nodes. Connection
              factories deployed to the cluster. When I connect N publishers
              through the cluster, messages from one publisher end up in the
              appropriate topic on nodeA, messages from another publisher end up in
              the appropriate topic on nodeB. Now when I connect a durable
              subscriber via the cluster I only get messages from topics from one of
              the managed nodes, right? (This is exactly what I am seeing in my
              tests) Connecting durable subscribers to each managed node is not
              possible because of JNDI (throws exception like
              InstanceAlreadyExists). How would I connect a subscriber so that it
              subscribes to the right topics on the right node ( one the works with
              the previously described publisher)?
              All this leads me to the conclusion, that without the forwarders, a
              JMS cluster with Weblogic 6.1 is not so powerful, it basically does
              just load balacing.
              Is this correct or am I missing something important here?
              Thanks a lot and have a nice weekend
              Juerg
              Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
              > Juerg Staub wrote:
              > > Tom,
              > >
              > > Thanks a lot. Bascially I did everything right, just need the patch.
              > >
              > > In the other hand I'd like to know what the benefits of the smart
              > > forwarders would be. When I understand correctly, every message would
              > > be forwarded to the appropriate topic in the different JMS servers.
              > > What would that bring in the case of a failure(one node of a cluster
              > > goes down)? As far as I can see, I still would need to 're-establish'
              > > the connection factory, topic session, topic and publisher in order to
              > > publish messages again?
              > >
              >
              > Yep. I think we are on the same page:
              >
              > The "smart-forwarders" would do what the 7.0 distributed topic
              > forwarders do for you. They would forward messages bound to
              > a particular physical topic to all instances of the topic.
              > This can be implemented via a durable subscription on a
              > member topic by each remote member topic's host.
              > MDBs could be used to service the durable subscription,
              > as they already have the reconnect logic built in.
              > (Durable subscriptions are used if you wish to guard against
              > lost messages). The forwarders
              > need to change a property on the message to indicate
              > that the message is already forwarded, and forward
              > only messages that have'nt been forwarded (to prevent
              > endless loops!).
              >
              >
              > > Thanks
              > >
              > > Juerg
              > >
              > > Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
              > >
              > >>I suggest you read the "emulating 7.0 distributed destinations"
              > >>section of the JMS performance white-paper available on dev2dev.bea.com.
              > >>You will need to apply the referenced enhancement patch on top of SP3 to
              > >>disable JNDI replication (or update to 6.1SP4).
              > >>
              > >>If you need to create a true distributed topic, you will also need to
              > >>write your own "smart-forwarders" to forward messages
              > >>between the different physical instances of the topic. Or simply
              > >>use WL JMS 7.0 (the upgrade from 6.1 is straight-forward).
              > >>
              > >>Tom
              > >>
              > >>Juerg Staub wrote:
              > >>
              > >>>Hi,
              > >>>
              > >>>I have a 6.1 cluster that has a JMS server A and a JMS Server B
              > >>>deployed and running on each of the managed nodes. As destination I
              > >>>created a topic with the same name for each JMS Server. The connection
              > >>>factories I deployed to the cluster only.
              > >>>
              > >>>My problem is, when I start the second managed server, I get the
              > >>>following error:
              > >>>
              > >>><Error> <Cluster> <Conflict start: You tried to bind an object under
              > >>>the name
              > >>>com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
              > >>>have bound
              > >>>from 169.59.5.26 is non clusterable and you have tried to bind more
              > >>>than once
              > >>>from two or more servers. Such objects can only deployed from one
              > >>>server.>
              > >>>
              > >>>
              > >>>When I understand correctly, this happens because the JNDI tree gets
              > >>>distributed to all nodes of the cluster, so there would be two object
              > >>>with the same name. How do I solve this situation? Do I have the
              > >>>specify different names for topics in different JMSServer running in a
              > >>>cluster? How would the load balancing work?
              > >>>
              > >>>
              > >>>Please help. Thanks in advance
              > >>>
              > >>>Juerg
              > >>
              

  • Weblogic - Fusion Middleware Cluster - Clarification - 11g

    Hello All,
    I've checked the forum and would need just a little clarification regarding weblogic cluster & fusion Middleware + Load Balancing.
    My current Setup is:
    ==============
    1 APP Server: Runs Fusion Middleware 11g Forms and Reports + Weblogic + OHS (windows 2008R2)
    1 DB Server: Standalone database 11gR2 installation (windows 2008R2)
    I've been asked to add a new app server and setup load balancing between the two app servers in order to split the incoming forms & reports requests.
    What do I do? Do I install the new app server like the first one and just add it to an existing domain(clustering)? Is there a difference between fusion middleware clustering and weblogic clustering (as in database RAC - the whole idea being failover 24/7 no single point of failure?)
    I would appreciate any assistance, and need not great detail, just need to make sense of the whole thing.
    I'm already on with the following document: [http://docs.oracle.com/cd/E21764_01/web.1111/e13709/toc.htm]
    Thanks in advance
    Jan S.

    Hi Jan
    You are almost there. I would like to clarify some points for you.
    1. You already have WLS + Forms/Reports and of course Backend RCU Database that has all the meta data for Forms/Reports. This RCU database is on single server Oracle database.
    I've been asked to add a new app server and setup load balancing between the two app servers in order to split the incoming forms & reports requests.
    2. The first question for above requirement is, do you need the new Server on the same Existing physical box or a different remote physical box. If on the same physical box (which I doubt), then there is NO need to install any new software like WLS, Forms/Reports etc. All you do is create a new Managed Server and add it to your existing Domain. NOW, do you currently have a Clustered Domain. If you, all you do is add this new server to that cluster. If not, then you need to add a New cluster and add your old and this NEW managed server to that Cluster. If your existing domain is only single server and is very recent, I would prefer create a brand new Cluster domain with Different Port numbers (you can change port numbers anytime later also). Then add/create one or two managed servers.
    3. If you are give a new physical box for this new managed server, then YES, you do need to install exactly SAME version of Weblogic Server and same version of Forms/Reports server on this new machine. Then create a Cluster Domain with 2 managed servers. One managed server on first box where you will have Admin Server + Managed Server 1. Then run pack command. Go to other machine. Run unpack command to create second Managed Server. Now you got 2 managed servers in a Single Clustered Domain.
    4. Now comes the Load Balancing Part. Never ever expose the individual managed server host and port and WebApp urls for any Clustered Domain. Instead install Apache Http Web App Server which I guess is same as Oracle Http Server. Oracle renamed it (there is no need for this, but it may be company policy). Anyhow all you do is, just install Apache Web Server. Copy some .dll (.so on linux) files to this apache installation. Then update httpd.conf file or weblogic.conf file with details of clustered weblogic domain managed servers host, port, url patterns etc.
    5. All the External Requests will now go to Apache Web Server like http://apachehost:apacheport/xxxUrl. This Apache will take care of LOAD Balancing, Failover etc and based on input url pattern will redirect requests to back end cluster of weblogic managed servers.
    6. The backend RCU database that has Metadata for Forms/Reports NEED NOT be Clustered. If you really have extremely heavy data, then you can have Oracle RAC database. Have multiple DB Nodes in RAC. For each Node, create a DataSource in Weblogic conolse and finally one master Multi Data Soiurce that uses all these single Datasources. But very rarely you really need RAC or clustered database for RCU. So for now, just go with single non-clustered Database that has RCU Schemas.
    In conclusion, even though you have Forms/Reports, just follow the standard normal Weblogic Clustered domain Architecture for your requirement. All clustering is at application server level and nothing to do with any Oracles softwares like SOA/BPM, Forms/Report, BI etc etc.
    Thanks
    Ravi Jegga

  • Multiple open db connections in a weblogic cluster

    we have created a cluster in weblogic with oracle database.
    Whenever we are starting the cluster (managed servers), there are a lot of connections are opening in database (around 150 in database). Although we have set max capacity of cgDataSource, cgDataSourcenoXA and wlsjmsreportDS as 20. So ideally there should not be more than 60 connections open at any point of time.
    We are using OSB 10gR3 in Linux 64 bit platform.

    The max capacity for a data source is per node in the cluster (if it's targeted to the cluster).
    So if you have 3 data sources, with max capacity of 20 each and two nodes in your cluster you should have around 3*20*2 = 120 connections.
    Of course at startup WebLogic only creates the number of connections specified in the initial capacity.

  • Eclipse + Oracle WebLogic Server Tools - stuck during publishing

    Hello,
    I'm experiencing a problem publishing to my application server in Eclipse, and would very much appreciate any help given.
    Server: WebLogic 10gR3
    Eclipse: Ganymede JEE SR2
    Oracle WebLogic Server Tools: 1.2.0.200907171310
    OS: Windows XP 32 bit
    JVM: Sun 6u13
    In my workspace:
    - Several Java projects
    - Several EJB projects
    - Several web projects
    - One connector project
    - One EAR project, referencing all other projects as its JEE modules
    - One WebLogic server in my "Servers" view, defined to deploy my EAR project
    Summary of my problem:
    Sometimes, and it seems pretty random, when starting the server - the "Publishing to Oracle WebLogic server" operation would never stop (can be seen in the "Progress" view). As a result, Eclipse is essentially stuck, as all other operations, such as saving a file etc', would not be performed since they would be waiting for the publish operation to complete.
    I did notice that a trigger for this is a deployment failure, such as a badly-defined application-module-datasource, or a failed startup task, but I have also experienced this with a good deployment as well.
    I am, literally, clueless. I have tried the new Galileo but it's too buggy, had some weird phenomenons there, and I have also tried the OEPE Galileo preview and got some weird phenomenons there as well.
    Again, your help would be very much appreciated.
    Thanks in advance,
    Amnon Grossman
    ECI Telecom

    Amnon,
    Try the Eclipse forum:
    Enterprise Pack for Eclipse
    Also, the 11g Eclipse 3.5 support is out of Preview/Beta mode and you should be able to open support tickets on it:
    http://forums.oracle.com/forums/ann.jspa?annID=1116

Maybe you are looking for