JMS Performance in Weblogic 10 ?

Hi
          In our Production Environment (weblogic 10 MP1).we have 4 managed servers ( App1, App2, app3, App4 )on 4 different physical machines, but we have only 1 JMS server on App2. The JMS Modules is connected to whole cluster and there is 4 single queues "NO DISTRIBUTED QUEUES" & one connection Factory. I know it will be the best if we have 4 managed server with 4 JMS server. But do Distributed Queue configuration will affect the performance? if yes How?
          Also please give any other suggestions as well..
          Thanks in Advnance.

Hi,
          A DQ would improve performance for two reasons:
          (1) The queueing engine's work would be equally divided between four machines rather than only one machine.
          (2) There would be less network overhead - perhaps even none depending on your design. Applications running on App1, App3, and App4 would no longer to make remote requests to "App2" in order to send or receive messages. Instead, they would simply invoke JMS locally. Network overhead can sometimes be the dominant bottleneck in a performance benchmark - so removing the network can potentially be a huge win.
          A DQ also improves high availablity - if App2 is down, messages can still be processes on App1, 3, and 4.
          Tom
          Edited by barnes at 06/12/2008 4:21 PM

Similar Messages

  • WEBLOGIC JMS performance ?

    hi ,
              I tried to find some numbers , about how much messages (in the diffrerent
              categories - ptp or pub/sub) can a weblogic server
              can stand - messages / sec , or some benchmarks,
              but i didn't find any on the web ..
              any one has any idea / link for such benchmark / performance test ???
              I would appriciate any answer !
              thanks!
              

    1) Start with the "WebLogic JMS Performance Guide" white-paper
              on dev2dev.bea.com. This guide has no numbers, but
              it has general guidelines. Performance is not just
              numbers...
              2) General note:
              In 7.0+ JMS file stores, BEA provides 3 disk write policies.
              The default is "cache-flush", as that is transactionally safe
              in all cases. The policy may have a dramatic effect
              on performance. (WL JMS defaults to "cache-flush", IBM MQ
              always uses "direct" - as far as I know, and many smaller
              JMS players default to "disabled".)
              3) The book
              "J2EE Performance Testing with BEA WebLogic Server"
              by Peter Zadrozny, Philip Aston, Ted Osborne
              contains JMS numbers, and a benchmark tool. Keep
              in mind that the numbers here are all "producer
              limited". All the benchmarks are run with
              a single producer, so the numbers often show little
              scaling. (Most apps increase producer counts
              as they scale.)
              Tom, BEA
              Amir Ben-Amots wrote:
              > hi ,
              >
              > I tried to find some numbers , about how much messages (in the diffrerent
              > categories - ptp or pub/sub) can a weblogic server
              > can stand - messages / sec , or some benchmarks,
              >
              > but i didn't find any on the web ..
              >
              > any one has any idea / link for such benchmark / performance test ???
              >
              > I would appriciate any answer !
              >
              > thanks!
              >
              >
              

  • Slow JMS Performance

              Hi,
              I'm using WL7.1 SP2 for a JMS based application. The database is SQLServer 2000,
              and the JMS queues are persistent on this DB.
              A client outside the Weblogic Server connects and fires lots of JMS messages to
              the application. These messages are consumed by a pool of MDB's.
              I don't think it's performing as well as it could.
              For example, if I un-deploy my application, and fire 80,000 JMS messages at the
              server, it takes around 10 minutes to persist these messages to the queues. All
              good so far.
              However, with the application deployed, the same number of messages take around
              3 hours. The messages are consumed and processed as fast as they can be persisted
              to the JMS queue. It's almost as if the messages are being synchronysly put on
              the queue, ie. control is not returned to the client until the message is consumed
              and processed. Unless I'm misunderstanding this, as soon as the messages is successfully
              persisted to the JMS queue, control should be passed back to the client.
              What I'd expect to happen is that the client would take around the same time post
              the messages to the JMS Queue, ie. about 10 minutes - and the Pending Message
              count to increase on the WL Server. Once all 80,000 messages were on the queue,
              the Pending Message count would gradually go down as the messages were processed.
              If I'm misunderstanding the way this works, please let me know. If you need any
              further info, please ask and I'll post the answers.
              Thanks,
              Richard Kenyon
              EDS - UK
              

    No problem.
              Performance is one of my hot-buttons, so I can't help but
              noting that when it comes to queueing, or even asynchronous
              invokes in general, slowing down the requester is often
              goodness. It helps put "back-pressure" on the requesting
              application, and so helps prevent a permanently growing
              request backlog that the slower request handling
              applications could never dig their way out of.
              Tom
              P.S. An updated version of the JMS performance
              guide will be released in the next few weeks. It has
              corrections, adds information about 8.1 features, and
              expands information in a number of areas. I'll post
              a link in the newsgroup when it comes out.
              Richard Kenyon wrote:
              > Thanks Tom,
              >
              > I suspected (and hoped!) that this would be the answer. I just needed
              > clarification that I wasn't being stupid :-)
              >
              > I'll have a look at the Performance guide you mentioned.
              >
              > Thanks,
              > Richard Kenyon
              > EDS - UK
              >
              > "Tom Barnes" <[email protected]> wrote in message
              > news:[email protected]...
              >
              >>When the application is active, it is forcing the server to do
              >>other work as well. In effect you are sharing a limited
              >>resource. Transactions (if applicable), your
              >>application code, your application receives, etc.
              >>In effect, the sender is slowed down because it
              >>is competing with the MDB application for resources.
              >>I suggest you read the JMS Performance
              >>Guide white-paper on dev2dev.bea.com.
              >>
              >>Tom
              >>
              >>Richard Kenyon wrote:
              >>
              >>>Hi,
              >>>
              >>>I'm using WL7.1 SP2 for a JMS based application. The database is
              >>
              > SQLServer 2000,
              >
              >>>and the JMS queues are persistent on this DB.
              >>>
              >>>A client outside the Weblogic Server connects and fires lots of JMS
              >>
              > messages to
              >
              >>>the application. These messages are consumed by a pool of MDB's.
              >>>
              >>>I don't think it's performing as well as it could.
              >>>
              >>>For example, if I un-deploy my application, and fire 80,000 JMS messages
              >>
              > at the
              >
              >>>server, it takes around 10 minutes to persist these messages to the
              >>
              > queues. All
              >
              >>>good so far.
              >>>
              >>>However, with the application deployed, the same number of messages take
              >>
              > around
              >
              >>>3 hours. The messages are consumed and processed as fast as they can be
              >>
              > persisted
              >
              >>>to the JMS queue. It's almost as if the messages are being synchronysly
              >>
              > put on
              >
              >>>the queue, ie. control is not returned to the client until the message
              >>
              > is consumed
              >
              >>>and processed. Unless I'm misunderstanding this, as soon as the messages
              >>
              > is successfully
              >
              >>>persisted to the JMS queue, control should be passed back to the client.
              >>>
              >>>What I'd expect to happen is that the client would take around the same
              >>
              > time post
              >
              >>>the messages to the JMS Queue, ie. about 10 minutes - and the Pending
              >>
              > Message
              >
              >>>count to increase on the WL Server. Once all 80,000 messages were on the
              >>
              > queue,
              >
              >>>the Pending Message count would gradually go down as the messages were
              >>
              > processed.
              >
              >>>If I'm misunderstanding the way this works, please let me know. If you
              >>
              > need any
              >
              >>>further info, please ask and I'll post the answers.
              >>>
              >>>Thanks,
              >>>Richard Kenyon
              >>>EDS - UK
              >>>
              >>
              >
              >
              

  • How to increase the performance of  Weblogic server 7.0?

    How to increase the performance of Weblogic server 7.0 ?
    also, how do i avoid typing the server login and password evertime I start the
    webserver?

    How to increase the performance of Weblogic server 7.0 ?It depends on what is not running fast enough for you.
    also, how do i avoid typing the server login and password evertime I
    start the webserver?In the startWebLogic shell script (.cmd or .sh) add:
    set WLS_USER=weblogic
    set WLS_PW=password
    (Replace "password" with whatever your password is.)
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com/coherence.jsp
    Tangosol Coherence: Clustered Replicated Cache for Weblogic
    "winston" <[email protected]> wrote in message
    news:3fe42d33$[email protected]..
    >

  • Can you specify third party JMS Provider in Weblogic appserver configuration

              Can you specify third party JMS Provider in Weblogic appserver configuration ???
              Only place i know of is that you can specify third party JMS Provider in MDB configuraion.
              DOES Weblogic has some kind of configuration files where you specify JMS Provider
              info (Like you can do that in JBOSS)
              

    You can also specify a third-party JMS provider using the Messaging Bridge,
              which transfers messages from one queue or topic to another.
              And in general, inside WLS you can use any JMS provider you wish anywhere
              that you can also use WLS JMS. In an upcoming release, there will also be
              some support to make foreign JMS providers a little easier to configure.
              But why would you want to use another JMS provider anyway? ;-)
              greg
              "Neeru Munjal" <[email protected]> wrote in message
              news:[email protected]..
              >
              > Can you specify third party JMS Provider in Weblogic appserver
              configuration ???
              >
              > Only place i know of is that you can specify third party JMS Provider in
              MDB configuraion.
              > DOES Weblogic has some kind of configuration files where you specify JMS
              Provider
              > info (Like you can do that in JBOSS)
              

  • JMS users on Weblogic

    Hi All,
    We have created JMS  queue on weblogic server which is file base persistent .
    Now my query is if any external code wants to publish a message into the queue they need user name to connect .
    Which user they can connect other than weblogic user OR what user I can create so that he doesn’t has Admin rights and can publish to Queue.
    Thanks
    AK

    I'm not familiar it, but apparently there's a feature in the security subsystem that allows propagating security information for "L2 Caches" via JMS, and it is this feature that's generating the Warning -- not JMS itself.
    I do not happen to know how this feature works, what kind of JMS configuration it expects, or if the Warning is simply a natural ephemeral part of the boot/initialization process of the security feature that can be ignored.
    You might want to try posting to the "WebLogic Server - Security" newsgroup.
    Tom

  • Foreign JMS QCF and Weblogic Sever Session Pool

              Hi!
              We have Weblogic 6.1 SP2 installation.
              We are trying to use JMS Server session pool and connection consumer configuration
              with MQSeries QCF registered to weblogic JNDI via startup class.
              Upon server startup weblogic is throwing ClassCast exception for QueueConnection.
              It seems weblogic is expecting QueueConnection implementation by weblogic.
              Any suggestions or alternative way of doing it.
              Thanks
              Jay PArikh
              

    Hi Jay,
              Server session pools do not support foreign providers.
              The preferred way to integrate foreign providers is via MDBs or
              via the Messaging Bridge (bridge available in SP3). For a
              comprehensive write-up on integrating foreign providers with
              WL see the whitepaper "Using Foreign JMS Providers with
              WebLogic Server" on dev2dev.bea.com.
              Tom
              Jay Parikh wrote:
              > Hi!
              >
              > We have Weblogic 6.1 SP2 installation.
              >
              > We are trying to use JMS Server session pool and connection consumer configuration
              > with MQSeries QCF registered to weblogic JNDI via startup class.
              >
              > Upon server startup weblogic is throwing ClassCast exception for QueueConnection.
              > It seems weblogic is expecting QueueConnection implementation by weblogic.
              >
              > Any suggestions or alternative way of doing it.
              >
              > Thanks
              > Jay PArikh
              

  • How to configure JMS server in weblogic

    Hi,
    I want to configure JMS server in weblogic.So please send me needful link.
    Regards
    Anup

    Hi Anup,
    1. The first thing you have to do is create a filestore where messages will be stored. Look at the below link for more detailed instructions:
    http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/stores/CreateFileStores.html
    2. Next create a JMS server. Look at the below link for more detailed instructions
    http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_servers/ConfigureJMSServers.html
    3. Now, create a JMS System Module to hold the JMS resources like Queues, Topics, Connection Factory, SAF agents etc..
    http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/modules/ConfigureJMSModules.html
    4. Now, create a resource like connection factory OR queue etc.
    http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/modules/ConfigureJMSModuleResources.html
    For now, lets stick to the basics and create a basic queue using the below documentation unless you exactly know what resource you want to create
    http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/queues/CreateQueues.html
    5. You will also need to create a connection factory to use the resource. See below documentation
    http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_modules/connection_factories/CreateConnectionFactories.html
    Please go through the below JMS architecture diagram as well as documentation that will tell you what JMS on WebLogic is all about in terms of configuration
    http://docs.oracle.com/cd/E23943_01/web.1111/e13738/overview.htm#i1084283
    Arun

  • What is the association between JMS Server and JMS Module in weblogic 10?

    Hi,
    I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
    And I have created a JMS Server and Targetted to the current running server (Admin Server).
    But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
    queue = (Queue) initialContext.lookup("jndi_queue");
    Exception:
    javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
    But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
    How JMS Module and JMS server are associated.
    My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
    Please advice.
    Thanks....

    Hi,
    Once you have JMS servers configured:
    Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
    Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
    Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
    For more information, reference the "best practices" chapter of the JMS configuration guide:
    http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
    I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
    Hope this helps,
    Tom

  • JMS Warning on weblogic startup

    The JMS experts may here know better. Looking hard to resolve this issue relaated to JMS. can anyone help here.
    Re: JMS Warning on weblogic startup

    I'm not familiar it, but apparently there's a feature in the security subsystem that allows propagating security information for "L2 Caches" via JMS, and it is this feature that's generating the Warning -- not JMS itself.
    I do not happen to know how this feature works, what kind of JMS configuration it expects, or if the Warning is simply a natural ephemeral part of the boot/initialization process of the security feature that can be ignored.
    You might want to try posting to the "WebLogic Server - Security" newsgroup.
    Tom

  • JMS Performance

              Hi All,
              i read the BEA WebLogicTM JMS Performance Guide (July 31, 2003) and have some
              questioon:
              http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp
              The only thing that indicates performance in the whole document is page 60 with
              the 3 examples.
              the problem there is that the arithmetic just doesn't work.
              All examples use a 100 Mbit link at 80% efficiency, which gives 10 mbyte/sec.
              Example 1: Messages of length 1Mbyte, 2 operations: (Calculating in IN Kbytes)
              10000/(1000*2) = 5. Bravo !!!
              Example 2: Message length 50kbyte, 10 operations : 10000/(50*10) = 20. (Am i wrong
              ? not 160 as the document says). Out of each 10 operations, 1 is write (send)
              and 9 are receive (read) , so each subscriber gets 2 messages per second, and
              not 18 as the document says.
              Example 3: Message size 50kByte, 2 Operations (because of the Multicast). 10000/(50*2)
              = 100 , and not 800. each subscriber gets 50 per second, and not 89.
              The arithmetic is simple, you can do it on your fingers - no need for excel.
              Can you, Please
              1. Explain the calculations
              2. Supply real life, Measured statistics that DO take into consideration server
              power, Memory constraints and other trivial, but necessary, facts of life...
              Thanks yuval
              

    Well, I must admit I was the primary author, so you will have
              trouble getting additional info. But, heck, I'm game:
              (1) We have literally had dozens of customers not
              realize that the network can be a bottleneck, thus the
              network calculations. Congrats on being one of the majority
              that didn't need this bit of guidance, but please don't look
              down on those that do - they are pretty bright people in
              their own right.
              (2) Memory usage is a function of number of messages,
              usage of queues or topics, and message size. Assuming
              paging is enabled, I think it is fair to be conservative
              and estimate for queues:
              number of messages * .5K = memory used
              This assumes .5K overhead per message - as the guide
              states, WL JMS does not page out message-headers, so
              messages have overhead even when they are paged out.
              (3) This is a performance guide, not a capacity guide, the
              guide was not intended to address capacity.
              As the paper states, there is a reason for this.
              Hard performance statistics are VERY application and
              hardware dependent. To get anything even close to the statistics
              that map to a particular app, run the app. That said, the performance
              book referenced in the guide DOES contain statistics, pretty
              graphs, and even a tool. Keep in mind that the first edition of the
              book never tests using multiple producers - which limits
              scalability, and kind of limits the applicability of some
              of the graphs - but the authors realize this, and are addressing
              the issue in the next addition.
              Tom
              Yuval Avni wrote:
              > Hi All,
              >
              > i read the BEA WebLogicTM JMS Performance Guide (July 31, 2003) and have some
              > questioon:
              > http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp
              > The only thing that indicates performance in the whole document is page 60 with
              > the 3 examples.
              > the problem there is that the arithmetic just doesn't work.
              >
              > All examples use a 100 Mbit link at 80% efficiency, which gives 10 mbyte/sec.
              >
              > Example 1: Messages of length 1Mbyte, 2 operations: (Calculating in IN Kbytes)
              > 10000/(1000*2) = 5. Bravo !!!
              >
              > Example 2: Message length 50kbyte, 10 operations : 10000/(50*10) = 20. (Am i wrong
              > ? not 160 as the document says). Out of each 10 operations, 1 is write (send)
              > and 9 are receive (read) , so each subscriber gets 2 messages per second, and
              > not 18 as the document says.
              >
              > Example 3: Message size 50kByte, 2 Operations (because of the Multicast). 10000/(50*2)
              > = 100 , and not 800. each subscriber gets 50 per second, and not 89.
              >
              > The arithmetic is simple, you can do it on your fingers - no need for excel.
              >
              > Can you, Please
              >
              > 1. Explain the calculations
              > 2. Supply real life, Measured statistics that DO take into consideration server
              > power, Memory constraints and other trivial, but necessary, facts of life...
              >
              > Thanks yuval
              

  • B2B/JMS Performance Tuning

    Hello All,
    We have a use-case in which an SOAP message will be received by OSB proxy service. The 3 step process is described below:
    1. OSB will extract EDIFACT message from request and write it to the SOA JMS queue IE012_IN_Queue.
    2. B2B listeneing channel is configured to listen to IE012_IN_Queue and translate the EDIFACT to XML and send the translated message to another JMS queue IE012_Out_Queue.
    3. BPEL process reads XML message from IE012_Out_Queue and processes it further.
    Under load, we observe that this 3 step process is causing delay and processing is taking more time at one of the 3 points. We are unable to exactly say which one of the 3 steps is taking more time. Can anyone help me in this area ?
    Regards
    Aparna

    Hi Aparna,
    You may refer -
    http://docs.oracle.com/cd/E23943_01/core.1111/e10108/b2b.htm#BGBGHAHF
    Few basic recommendations -
    1. Domain must be running in production mode
    2. Both server and component level logging should be set to error/warning to avoid excessive logging
    3. Monitor DB and make sure that SQL's are performing good (You will need AWR and ASH reports of DB for this. You may take help from any DBA in your org)
    4. SOA must be running in a cluster and all the servers of the cluster must be up and running
    5. Monitor the data-sources (specially SOA datasource) and make sure that enough connections are available to handle the load
    6. Make sure that JTA timeout and XA transaction timeout (set in data-source) are set to a proper value (Weblogic JTA timeout< DataSource XA Transaction Timeout < DB distributed_lock_timeout)
    7. It is recommended to use Exalogic and Oracle RAC DB for high volume production deployments
    I believe that if all above points are taken care of then B2B should be able to process small messages (like 6KB in your case) within few milliseconds. If still you hit a performance issue then better log a SR with support and after screening your system, they may suggest more fine tuning at pain points. Remember that each and every production deployment may be unique because of the requirements and resources available so generic recommendations may not solve the issue completely and hence screening of the specific system will be required to find the pain-points.
    Regards,
    Anuj

  • JMS Performance/Design

    Hi,
    I am new to JMS and J2ee and I need some guidance, if anyone can help me plz.
    I am building a new application where I might have a very large number of clients (hundred of thousands possibly) exchanging messages with a server and between them.
    I was using sockets and serialization to handle that but it was ok for small number of users only.
    so First I need a robust server that can handle a large number of users, since I have a limited budget I was thinking to use JBoss since it's open sourse and free, is this a good choice or is it better to get weblogic or websphere, etc..?
    Every client who logs in can communicate to the server and exchange messages or (objects).
    When a client wants to talk to another client, he does that through the server too of course.
    I am thinking to use JMS (message beans) to exchange messages between the server and clients, or between the clients themselves (synchronously/asynchronously). I need to find what is the best implementation/design that will have the better performance and to avoid bottleneck on the server ?
    should I create a message bean for each client on the server when he logs in to handle the communication between this client and the server and keep it until he logs out?
    or should all clients subscribe to the same message bean (or service) on the server?
    if the client starts a communication with another client, should I open a session for only the 2 of them? or the same bean they are subscribed to will handle that?
    I was thinking to use publisher/subscriber but if there is a huge amount of trafic going on between these clients, how can the server handle all these requests quickly?

    Hi,
    Thank you for the reply.
    I know that the system is not that easy, that's why I am looking for help :)
    The software itself consists of client application and server side application, the comuunication part is similar to yahoo messenger, but a user can be behind a local server/firewall (mainly if it's a company) or use the public server .
    the requirements are the following:
    -The client side application is downloaded from the web-site of our company.
    -The application communicates to our company's server for updates and other services (same way as window updates itself by contacting microsoft server).
    -a corporate might decide to buy/download our server application in order to establish a local secure server rather than being on our public server.
    -The client might be member of the local server of his company (behind a firewall of course) but he also still can communicate to our public server for updates.
    (same way if you have a windows client part of a local server and he still can contact Microsoft for updates)
    -A Client can search the local server or our server for other clients/users and add them to his friends list (like yahoo)
    -The user will be notified (if he likes) when a friend goes online or offline
    -The user can send/receive data from his friends. (the data is not big maybe maximum a couple hundred KB , the worse case is maybe 1/2 MB)
    They told ma about JXTA and I am looking at it, any better ideas ?
    Regards
    George

  • Error in using the JMS Adater using weblogic queue

    I am using weblogic queue in jms adapter to queue the data. i configured the server.xml
         <shared-library name="oracle.weblogic" version="10.1.3">
              <code-source path="D:\product\10.1.3.1\OracleAS_5\jdk\lib\weblogic.jar"/>
         </shared-library>
    I got the following error. Any Suggestions?
    file:/D:/product/10.1.3.1/OracleAS_5/bpel/domains/default/tmp/.bpel_OSM_OrderRequest_2.0_c68a29fd8af11327e1a8892e8de5a6bb.tmp/Sample.wsdl [ Produce_Message_ptt::Produce_Message(orderRequestMessage) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    </summary>
    </part>
    -<part name="detail">
    <detail>
    org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.

    I am able to fix this error by copying "JmsAdapter.jar" to "applib" directory of oc4j_soa.
    I was getting a new error.
    +"Missing class: oracle.tip.adapter.api.TranslationAware+
    +     Dependent class: oracle.tip.adapter.jms.JmsInteractionSpec+
    +     Loader: global.libraries:1.0+
    +     Code-Source: /D:/SOA1013/j2ee/oc4j_soa/applib/JmsAdapter.jar+
    +     Configuration: <code-source> in /D:/SOA1013/j2ee/oc4j_soa/config/server.xml+
    +The missing class is available from the following locations:+
    +     1. Code-Source: /D:/SOA1013/bpel/lib/orabpel.jar (from <code-source> in /D:/SOA1013/j2ee/oc4j_soa/config/server.xml)+
    +     This code-source is available in loader oracle.bpel.common:10.1.3."+
    But managed it to fix it by copying "orabpel.jar" to "applib" directory.
    We need to restart OC4J once we copy the JAR files.
    regards,
    S.Vasanth Kumar.

  • Migration of JMS Queues from Weblogic 10.3 to 12c

    Hi - We are currently planning to move our JMS Queues from existing 10.3 server to 12c and for the same we are looking for some feedback : 
    We need to define a rollback strategy in case our migration to 12c does not work well and we need to revert back to using weblogic 10.3. Are messages sent to weblogic 12c backward compatible with version 10.3? As part of rollback, business would want to drain out any remaining messages from 12c and feed them back to 10.3 queues to allow them for processing. Is this feasible? If yes then, could you please suggest how, If not then could you please suggest a strategy for rollback and process remaining messages in 12c?
    We would also want to know if we can keep the same Database for both 10.3 and 12c JMS persistent stores for the same queues or should we define a completely new DB? With weblogic we can define prefixes for the DB stores which would make queue tables to have different names between 10.3 and 12c for same queues. However we are not sure if there are any other internal tables that JMS creates in the persistent stores DB, not using these prefixes, which would then corrupt the data since both 10.3 and 12c tables would be on the same DB.
    Thanks
    Nitin

    Hello,
    the final release for WLP is 10.3.6, running on WebLogic Server 10.3.6.
    Emmanuel

Maybe you are looking for

  • Archiving Error - Cyclic Redundancy Check

    Hey there, My inbox is full again. I went to archive and I get the below message after the archive is finished: Error while archiving folder "Inbox" in store "[email protected]". The file C:\Users\XXX\AppData\Local\Microsoft\Outlook\[email protected]

  • FaceTime with 3G network

    I manage to FaceTime on "3G" network. I did it with the new iPad (64GB wifi) while connected (via hotspot) to my iPhone 4. The iPhone 4 itself was on 3G network. I guess the iPad 'thinks' it was on wifi, thus enabling the FaceTime. The iPhone's 3G si

  • Team Membership and Students

    Does each team membership have to be for one year or can it be month-to-month?  In the school year the number of students will vary semester to semester.

  • Problems with deploying application to Policy Server 7.2.1 & DSS 7.2.2

    Hiya -<br /><br />I've been using Policy Server 7.0.2 and Document Security Server 7.0.2 to policy protect PDFs.<br /><br />I've recently just installed Policy Server 7.2.1 & DSS 7.2.2 on another machine and am now trying to use the same EJB deployed

  • Comment ouvrir l'IPhone pour insérer la carte SIM

    J'ai commandé L'IPhone 3GS via internet et je ne sais pas comment l'ouvrir pour insérer la carte SIM