Combined-tier WebLogic Cluster (two clustered instances)

Hi guys,
How can I realise it?
[http://lowerthan60.files.wordpress.com/2010/10/cluster_1.jpg]
Is it right steps?
[http://middlewaremagic.com/weblogic/?p=971]
Load Balancer and main domain working fine between two IP (instances).
Edited by: 867750 on Jun 23, 2011 5:44 AM

          In the case of WL6 and WL7 clustering, if the requests from the same user jump
          around different instances, we experience this kind of session loss problem very
          frequently. I am not sure if this is the same case for WL5. The idea is, find
          a way to make sure the requests from the same use always hit the same instance
          unless it is dwon.
          "Cameron Purdy" <[email protected]> wrote:
          >Are you using cookies or URL encoding?
          >
          >Peace,
          >
          >Cameron Purdy
          >Tangosol, Inc.
          >http://www.tangosol.com/coherence.jsp
          >Tangosol Coherence: Clustered Replicated Cache for Weblogic
          >
          >
          >"Sam Dupont" <[email protected]> wrote in message
          >news:[email protected]..
          >> Any advise on the following problem would be greatly appreciated.
          >>
          >> I am running WebLogic 5.1 (don't know ServicePack offhand) on two
          >instances which are clustered.
          >>
          >> When both instances are up and I redirect from a jsp to a jsp, I lose
          >the
          >httpSession. When either of the instances are down, the httpSession
          >is not
          >lost.
          >>
          >> Has anyone ever seen anything like this or what might be causing it?
          >>
          >> Thanks
          >
          >
          

Similar Messages

  • Migrate a SQL Server 2005 clustered instance

    Hi all,
    I've a 2 node cluster running Windows Server 2003, on the top of the cluster run two clustered instance of SQL Server 2005 Enterprise. The Windows Server 2003 are physical machine and the shared storage is implemented into a FC SAN.
    I want to migrate the 2 clustered instance on a new Windows Server 2008R2 servers that runs on new hardware (so no in-place migration).
    Is there a certified path for migration?

    Hi,
    thank you for the answer, I've just seen that web resource. I'm trying to find something specific for SQL Server, if it exists.
    Can you please explain your requirement. Did you read complete article ? As far as i can read you dont want inplace migration in that case get a new windows boxes and configure windows server cluster its fair simple and easy. Do you want document how to configure
    windows cluster ?
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • SQL Server 2012 - 3 SQL clustered instances - one default/ two named instances - how assign/should assign static ports for named instances

    We have two physical servers hosting 3 SQL 2012 clustered instances, one default instance and two named instances.
    The default instance is using port 1433 and the two named instances are using dynamic port assignment.
    There is discussion about assigning static port numbers to the two named clustered SQL instances.
    What is considered best-practice?  For clustered named instances to have dynamic or static ports?
    Are there any pitfalls to assigning a static port to a named instance that is a cluster?
    Any help is greatly appreciated

    Hi RobinMCBC,
    In SQL server the default instance has a listener which listens on the fixed port which is TCP port 1433. And for the named instance the port on which the SQL server listens is random and is dynamically selected when the named instance of the SQL server
    starts.
    For Standalone instance of the SQL server we can change the dynamic port of the named instance to the static port by using SQL server configuration manager as other post, however, in case of the cluster, when we change the port no. of the named instance
    to the static port using the method described above, the port no. again changes back to the dynamic port after you restart the services. I recommend you changing the Dynamic port of the SQL Server to static port 
    on all the nodes , disabling and enabling the checkpointing to the quorum.
    For more information, you can review the following article about how to change the dynamic port of the SQL Server named instance to an static port in a SQL Server 2005 cluster.
    http://blogs.msdn.com/b/sqlserverfaq/archive/2008/06/02/how-to-change-the-dynamic-port-of-the-sql-server-named-instance-to-an-static-port-in-a-sql-server-2005-cluster.aspx
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Can we have two admin instances while performing Dynamic clustering?

    Can we have two admin instances while performing Dynamic clustering?

    Just referring you to this thread.
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/91f6434f-8a4e-4e53-b185-2f3a493aa134/issue-with-office-365-integration-module?forum=winserveressentials
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • Two SAP Instances in High Availability cluster - SGeSAP - HPUX

    Dear All
    We want to install 2 SAP instances in single host with DB and CI separately. DB and CI will be on High Availabilty Cluster using SGeSAP for HP - Unix. The database is Oracle 10g.
    Does SAP support multiple instance on the same hosts(DB and CI) for HA option.
    Kindly inform
    Regards
    Lakshmi

    Yes it is possible to run two SAP systems on same cluster using SGeSAP.  Normally If there is only one system on the cluster DB is configured on one node and CI is configured on the second node, with fail over in case of a node failure.  In your case if a node fails one node will be running two DB and two CI instances.  You have to size the hardware accordingly.  Just FYI, SGeSAP is licensed per SAP System.

  • Log4j issue with two ears in weblogic cluster

    Hi,
    I am having issue with log4j.I am having 2 ear files say AppA and AppB.I have used log4j(DailyRollingFileAppender) in both so that logs from AppA gets written to a.log and from AppB gets written to b.log.
    This approach is working fine in non-clustered environment(weblogic admin server).
    But when i try the same in a clustered(weblogic cluster) environment the logs from both AppA and AppB gets written to a.log.
    Could you please help me to resolve this issue.

    Include ${weblogic.Name} in your log4j property file thiis will create the log file name with server name
    log4j.appender.TEST_LOGGER.File=/logs/${weblogic.Name}_TEST_LOGGER_LOG.txt
    Do not keep log4j within your ear
    move it to server and include it in your class path of your server.

  • No communication between the two nodes in weblogic cluster

    Hi All,
    We have installed weblogic cluster in our environment(LINUX 64-Redhat.5).On one node admin server ,managed server1,on second node we have managed server2.When we try to deploy application on one node it is not getting reflected in othe node.We have ran datagram test to check communication between 2 node.
    Here we observed that listener and pulisher are picking wrong IPs not the server Ips.
    can any one explain why and what is the problem.
    thanks,
    sudheer.

    Hi Sudheer,
    While performing the datagram test you mention the ports and ip so I am not sure how they are picking wrong ip and port. Follow the instructions to perform the test http://coherence.oracle.com/display/COH35UG/Performing+a+Datagram+Test+for+Network+Performance
    Re the deployments, you need to ensure that multicast is enabled in your environment and both your managed server are in the same subnet otherwise you need to specify WKA for unicast communication. I am assuming that you are building SOA infrastructure as it internally uses Coherence for deploying applications and you can follow the instructions http://download.oracle.com/docs/cd/E15523_01/core.1111/e12036/extend_soa.htm#CHDEAFJH else use the intructions as mentioned here http://download.oracle.com/docs/cd/E17904_01/web.1111/e13709/features.htm
    Hope this helps!
    Cheers,
    NJ

  • Session lost problem in Weblogic cluster and Iplanet proxy

              We have an environment like this
              Iplanet 4.1--> Two Weblogic servers.(WLS 6.1 sp1)
              The Weblogic servers are not really clusterd, but we are using the Weblogic Cluster
              attribute in the obj.conf to configure the proxy (The Weblogic servers are really
              independant servers with the same application deployed).
              This is working fine in our development environment. No problem with session and
              load balancing. Although this architecture is not documented in Weblogic docs,
              I have seen several references to this type of architecture in the web and it
              seems to be working.
              Now we are into our pre-production environment. The same archictecture exists.
              Only the following differences
              1. Both the weblogic servers run on multihomed machines. We have bound the Weblogic
              servers to specific IP addresses using the Listen address option.
              2. The same IP addresses are there in the proxy plug-in conf file.
              3. There is a firewall between the Iplanet and Weblogic.
              Now if only one weblogic is running, the application works fine. The moment we
              turn the other weblogic on, the application starts misbehaving. The session seems
              to get lost and proxy forwards requests randomly.
              What could be the reason?
              Regards
              Anup
              

              Hi
              The problem got solved. There was an older version of libproxy.so in the Iplanet
              proxy
              Regards
              Anup
              Yeshwant Kamat <[email protected]> wrote:
              >Anup,
              >
              >Is there a reason you are not clustering the WLS instances? Remove the
              >firewall in your
              >prod environment and see if that makes a difference.
              >
              >Anup wrote:
              >
              >> Hi Mike
              >> 1. As per the documentation WebLogic Server is set up to handle session
              >tracking
              >> by default. So we are not doing anything special. Since the application
              >works
              >> fine with one Weblogic and multiple clients connecting to it through
              >Iplanet ,
              >> I think there is no problem with Session tracking as such.
              >>
              >> 2.We are using the default cookie name for session (JSESSIONID). So
              >we haven't
              >> done anything extra in the proxy set up or weblogic.xml
              >>
              >> 3. I have watched the cookie that comes on the browser
              >> PAACk3iviDm4ZuMPIbB9TpTTw9slk40IEC02MKjpu14EZ9ayzqaP!-1196227542!gmbpds054!7015!7016.
              >>
              >> gmbpds054 is the DNS name of one of the weblogic servers. So that is
              >also fine.
              >>
              >> What else could be the problem.
              >> Regards
              >> Anup
              >>
              >> "Mike Reiche" <[email protected]> wrote:
              >> >
              >> >If you have session tracking turned on in weblogic, creating a session
              >> >will write
              >> >a cookie back to the browser. iPlanet does sticky load balancing
              >based
              >> >on the
              >> >IP address in this cookie. So -
              >> >
              >> >1) do you have session tracking turned on?
              >> >
              >> >2) is the cookie getting written to your browser?
              >> >
              >> >3) are iPlanet and WebLogic using the same cookie? (same name)
              >> >
              >> >Mike
              >> >
              >> >"Anup Maliyackel" <[email protected]> wrote:
              >> >>
              >> >>We have an environment like this
              >> >>
              >> >>Iplanet 4.1--> Two Weblogic servers.(WLS 6.1 sp1)
              >> >>
              >> >>The Weblogic servers are not really clusterd, but we are using the
              >Weblogic
              >> >>Cluster
              >> >>attribute in the obj.conf to configure the proxy (The Weblogic servers
              >> >>are really
              >> >>independant servers with the same application deployed).
              >> >>
              >> >>This is working fine in our development environment. No problem with
              >> >>session and
              >> >>load balancing. Although this architecture is not documented in Weblogic
              >> >>docs,
              >> >>I have seen several references to this type of architecture in the
              >web
              >> >>and it
              >> >>seems to be working.
              >> >>
              >> >>Now we are into our pre-production environment. The same archictecture
              >> >>exists.
              >> >>Only the following differences
              >> >>1. Both the weblogic servers run on multihomed machines. We have
              >bound
              >> >>the Weblogic
              >> >>servers to specific IP addresses using the Listen address option.
              >> >>
              >> >>2. The same IP addresses are there in the proxy plug-in conf file.
              >> >>
              >> >>3. There is a firewall between the Iplanet and Weblogic.
              >> >>
              >> >>Now if only one weblogic is running, the application works fine.
              >The
              >> >>moment we
              >> >>turn the other weblogic on, the application starts misbehaving. The
              >> >session
              >> >>seems
              >> >>to get lost and proxy forwards requests randomly.
              >> >>
              >> >>What could be the reason?
              >> >>
              >> >>Regards
              >> >>Anup
              >> >
              >
              

  • How to split presentation level and business level using two ATG instances

    Hello All!
    We are investigating possibility of splitting ATG presentation (web store with jsp pages and other presentation components) and business (ATG components such as Pricing, Catalog, etc.) levels. The first idea that we have is simply start two instances of ATG. One instance will serve client requests (presentation level) and communicates with another ATG instance (business level) where all ATG components are situated.
    The main problem is a Nucleus container which is used for accessing all ATG components. And we don't know right solution how to point to a Nucleus container that is situated on a remote ATG instance. Right now we have two ideas how to establish communication between two ATG instances:
    - try to replace local Nucleus container by remote one using RMI;
    - do not replace Nucleus container by implementing some custom filter that can redirect all servlet requests to another ATG instance. In that case we will have two Nucleus containers.
    What do you think about all this? Do you have any other solutions how to solve the task? Maybe we lost something? Can we deploy a cluster of ATG instances that will communicate between each other?
    Thanks in advance.
    Andrey.
    Edited by: 945758 on Jul 11, 2012 7:00 AM

    Yes ATG system can have multiple nodes grouped in one or more clusters managed by load balencer
    If the services you are talking about are inherently ATG services like login, add to cart, checkout then its better to implement it with ATG.
    ATG provides and support both REST and SOAP based Webservice and allows you to expose any ATG component as service thus making it available outside ATG space.
    To be able to manage load better you can split your servers to page serving servers and services oriented servers and place them into multiple clusters.
    Though I haven't seen anyone using this kind of topology so not sure whether it's there is any challenge in setting up this topology.

  • Single sign-on in weblogic cluster?

              I am using wls 7.0 sp1 that form a cluster by two managed servers each at different
              physical machine.
              In front of the servers, a hardware load-balancer providing a virtual ip that
              mapped to the real ip of the 2 machines.
              I deployed a web application to the cluster. The html & jsp files are all protected
              by Form Based Authorization.
              My expectation is, whenever I sign-on to the first managed server, the login credential
              should also be valid for the second managed server.
              But it is not the case.
              My situation is:
              - open brower with url: http://virtual.ip:7001/admin.jsp
              - the load balancer map the request to my first managed server.
              - the response from the first managed server prompt the login page for username
              and password.
              - after POST the information, my target admin.jsp page display properly.
              - when I click the link within the admin.jsp page, eg. http://virtual.address:7001/status.jsp
              there is two possibilities:
              1. the load balancer route the request to the first managed server and everything
              well.
              or
              2. the load balancer route the request to the second managed server and response
              with login page again.
              The second case is definitely not what I expected.
              Question:
              Is it the default behavior of Weblogic cluster on the single sign-on? I think
              my login is against a WLS domain (at least a cluster), not to a specific web server!
              Any comments are welcome.
              

              Note my answer is not directly related to your question, but it might help.
              From my experience to configure WL cluster with hardware load balancer, the session
              stick (layer 7 switch) should be used (either using the session cookie, or ServerID
              cookie). That is, unless one instance is down, all requests from the same session
              are better go to the same server. I ever tried round-robin or random load balance
              policy at hardware load balancer without session stick, and the result was as
              disappointing as you have seen.
              "franky c." <[email protected]> wrote:
              >
              >
              >I am using wls 7.0 sp1 that form a cluster by two managed servers each
              >at different
              >physical machine.
              >In front of the servers, a hardware load-balancer providing a virtual
              >ip that
              >mapped to the real ip of the 2 machines.
              >I deployed a web application to the cluster. The html & jsp files are
              >all protected
              >by Form Based Authorization.
              >
              >My expectation is, whenever I sign-on to the first managed server, the
              >login credential
              >should also be valid for the second managed server.
              >
              >But it is not the case.
              >
              >My situation is:
              >- open brower with url: http://virtual.ip:7001/admin.jsp
              >- the load balancer map the request to my first managed server.
              >- the response from the first managed server prompt the login page for
              >username
              >and password.
              >- after POST the information, my target admin.jsp page display properly.
              >- when I click the link within the admin.jsp page, eg. http://virtual.address:7001/status.jsp
              > there is two possibilities:
              > 1. the load balancer route the request to the first managed server
              >and everything
              >well.
              > or
              > 2. the load balancer route the request to the second managed server
              >and response
              >with login page again.
              >
              >The second case is definitely not what I expected.
              >
              >Question:
              >Is it the default behavior of Weblogic cluster on the single sign-on?
              >I think
              >my login is against a WLS domain (at least a cluster), not to a specific
              >web server!
              >
              >
              >Any comments are welcome.
              >
              >
              

  • Caching read-only data in a weblogic cluster: Need Help

    Hello,
    I'm working on the development of a web site that will be based on a weblogic cluster spread across several weblogic instances running on several unix boxes.
    To avoid frequent hits to the database, I would like hold a huge amount of data in the application's in-memory cache. The idea is to query the database at startup and store the results in memory for the life of the JVM.
    I have three questions around this:
    1. Is it advisable to store this data in the form of read-only entity beans?
    2. If not, what other options do I have?
    3. In some rare cases, a back-end script might change (and commit) data contained in one or two of these 64000 records. What is the best way of propagating these data changes across the cluster?
    Any help in this regard would be greatly appreciated.
    Regards,
    Dipak Jha

    Could somebody please guide me on this?
    Dipak Jha

  • Libproxy sp12 behind a firewaill fails to connect to weblogic cluster

    Two WLS 5.1 SP11 clustering, iPlanet4.1 w/wlproxy plugin, Solaris Box. There is a firewall in between the iPlanet WebServer and the weblogic cluster. The NSAPI proxy plugin ( libproxy.so )connects successfully to one of the weblogic cluster for the first time using the NAT IPs of the cluster m/c maintained in the obj.conf. The Response contains the actual IP of the weblogic cluster m/c which gets updated in the proxy and uses that to connect to the cluster and firewall blocks that as it is not the NAT IP. But this works fine in libproxy of weblogic 6.1 unfortunately this has a problem when the data that gets passed is more than 1000 chars.
              

    shouldn't the connect string look like jdbc:oracle:thin:@MyIP:1521:MySID ?

  • Sizing of WebLogic Cluster Servers

    I have an application that needs to be implemented in BEA WebLogic 5.1 (
    JSP, Servlet, EJB) and deployed on Solaris 8 talking to Oracle
    8.0/Solaris (in clustered environment).
    I am in the process of sizing the application. Following are some of the
    basic sizing information:
    No of users: 6000
    Usage Pattern: High during evenings in US time zone
    Concurrent users: 300
    EJBs types: 200 entity and 50 session beans ( stateless), 4 stateful
    session beans
    State Per User: 2K
    Database Tables: 100
    No of screens: 80
    Data Accessed per User Request: 20K
    Cluster: Yes
    No of Machines in Cluster: 2
    Clustering Type: Recommended 2- tier ( with Web Server on a different
    machine)
    What kind of SUN machine should I be buying?
    I mean, ES 220 or ES 450 ...or a higher end machines? What should be the
    swap space, RAM, no. of processors?
    Any existing documentation or specification will be very valuable.
    Thanks,
    Hari

    Hi,
    First of all weblogic server has ONLY one Admin Sever per Domian which should be used for administrative work, hence we cannot have have a backup of Admin server.
    Weblogic Server Architecture
    Yes, the best way is to use horizontal clustering as shown below where all the managed servers are in a cluster.
    Machine-1
    - Admin Server
    - MS-1
    - MS-3
    Machine-2
    - MS-2
    - MS-4
    HTTP Servers Architecture
    Assuming you would be using Apache HTTP server, hence using weblogic Apache plugin you would be able to communicate with weblogic servers. In hhtpd.conf file you have to load the module and in if-module block you would have to give all the information about the weblogic server which would then try to connect with weblogic servers as well as will load-balance between them.
    For more information check the below link for Apache HTTP server.
    Topic:Installing and Configuring the Apache HTTP Server Plug-In
    http://download.oracle.com/docs/cd/E15051_01/wls/docs103/plugins/apache.html#wp131399
    Topic:General Parameters for Web Server Plug-Ins
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143055
    Hope this helps you.
    Regards,
    Ravish Mody

  • Weblogic cluster for 24x7 environment and a front OHS server

    Hi experts,
    We are going to set up a reliable J2EE application server environment by using clustering webgoic servers on TWO nodes, and a front OHS https server in DMZ for load balancing.
    I am new to weblogic cluster and load balance by OHS. I have visited this forum for Fusion MiddleWare clustering etc. Can some experts share some light on this?
    Will our deployment architecture be able to handle the J2EE applications failover? In other word, we can restart one of Weblogic Managed Servers when a new release of J2EE codes are re-deployed without impacting business end users’s usage?
    Problems we want to solve:
    1. All J2EE applications are available for 24x7 even when new J2EE codes are released and deployed on weblogic Managed Servers ANY TIME, side-by-side deployment and restart a managed server if we need to clean the HTTP cache.
    2. The J2EE applications should be accessed by external and internal users with a Single Access Point, like
    https://apps.company1.com/j2ee1
    https://apps.company2.com/j2ee1
    https://apps.company1.com/j2ee2
    https://apps.company2.com/j2ee2
    All J2EE applications (j2ee1, j2ee2, j2ee3 etc) should be deployed on both of weblogic Servers in a cluster, and pointing to a SAME backend database.
    Can some experts share with us the best practices on components and configurations? Thanks.

    Seems your architecture is like Browser => OHS ( DMZ ) => Weblogic => DB OR Browser => HLB( like bigip ) => OHS ( DMZ ) => Weblogic => DB
    Cluster is the solution for load balancing however if you are using OHS for redirection to weblogic then OHS does the load balancing in round robin way. using cluster in this way has a benefit of in case of any one of your managed server is down the OHS will divert connection request to any one of the active managed server ( you have to turn on dynamic list on at OHS ).
    http://weblogicserveradministration.blogspot.com/2010/10/load-balancing-in-weblogic-server.html
    Failover is something different, if in case any of the any managed server goes down then your user you get the application session from another server but new one, means the the tasks not saved by the users on earlier session will lost. for that yo need to use cluster and then need to enable the session replication. another best option is you can use the coherence web if you are using latest versions of weblogic supporting coherence web. with that you not need to worry on user sessions and you can start any of the managed server anytime without worrying about the user sessions.
    http://weblogicserveradministration.blogspot.com/2010/10/manage-http-session-states-session.html
    http://weblogicserveradministration.blogspot.com/2011/05/oracle-coherence-37-coherenceweb.html
    http://weblogicserveradministration.blogspot.com/2010/11/clustering-part-i.html
    another way is, you can use side by side deployment feature in case you don't want shutdown your application completely, with this, old connections and new requests will goes to old application and once new application activated all new requests will come to new application and once all requests on old application will complete that application will retire automatically.
    Regards
    Mukesh Negi
    http://weblogicserveradministration.blogspot.com

  • StreamCorruptedException when starting Weblogic cluster

    Hi, I have an application running on Weblogic Server 8.1 sp4 in clustered environment. When the cluster is restarted the first server restarts without errors but the second one has the following error message. What does the error message mean? Some messages have disappeared form the JMS queue when the cluster has been restarted. Does this error message have something to do with the disappeared messages?
              <29.9.2006 14:09:17 EEST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster Cluster2 on 237.0.0.6:10603.>
              <29.9.2006 14:09:17 EEST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster2.>
              <29.9.2006 14:09:47 EEST> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server CL2Server2.>
              <29.9.2006 14:09:54 EEST> <Error> <JMS> <BEA-040368> <The following exception has occurred:
              java.io.StreamCorruptedException: Unknown object stream version. 5505025
                   at weblogic.jms.store.BufferDataInputStream.readObject(BufferDataInputStream.java:167)
                   at weblogic.jms.store.JDBCIOStream.doRecoverBodies(JDBCIOStream.java:1024)
                   at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:939)
                   at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:1140)
                   at weblogic.jms.store.JMSStore.recover(JMSStore.java:315)
                   at weblogic.jms.backend.BEStore.open(BEStore.java:264)
                   at weblogic.jms.backend.BEStore.start(BEStore.java:151)
                   at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
                   at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
                   at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
                   at weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
                   at weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
                   at weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
                   at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
                   at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
                   at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
                   at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
                   at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
                   at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
                   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                   at java.lang.reflect.Method.invoke(Method.java:324)
                   at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
                   at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
                   at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
                   at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
                   at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
                   at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
                   at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
                   at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
                   at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
                   at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
                   at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
                   at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
                   at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
                   at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
                   at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
                   at weblogic.Server.main(Server.java:32)

    Make sure that the JMS server isn't attempting to load a store that was created from a later version of WLS. Also, make sure that no two JMS servers share the same database table - otherwise they will corrupt each-other's data. I think the latter is likely the problem.
              Tom

Maybe you are looking for