Creating a MDB and Distributed Queue in Clustered env in weblogic 9.2

I have created 3 managed servers and all these managed servers are in the cluster.
          Now i create JMS module for this cluster and create the Connection factory 'QUEUE_CF_8' and distributed Queue 'DIS_QUEUE_8' targeting to the cluster.
          I create a MDB and JMS client and deploy them in the cluster.JMS client sends the message to the distributed queue and MDB is listening to the distributed queue
          When i deploy the MDB , it is deploys perfectly . But when i run the client it fails with the following exception
          [java] javax.naming.NameNotFoundException: Unable to resolve 'QUEUE_CF_8'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'QUEUE_CF_8'. Resolved '']; remaining name 'QUEUE_CF_8'
          When i view the JNDI tree for all the managed servers , i can see the Connection factory and the distributed queue.
          Also i deploy the MDB to the cluster and no submoduletargets are specified.
          Let me know what is that iam missing.

<?xml version='1.0' encoding='UTF-8'?>
          <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
          <connection-factory name="Queue_CF_8">
          <sub-deployment-name>Server_group_4</sub-deployment-name>
          <jndi-name>QUEUE_CF_8</jndi-name>
          <security-params>
          <attach-jmsx-user-id>false</attach-jmsx-user-id>
          </security-params>
          </connection-factory>
          <uniform-distributed-queue name="DIS_QUEUE_8">
          <sub-deployment-name>Server_group_4</sub-deployment-name>
          <jndi-name>DIS_QUEUE_8</jndi-name>
          <load-balancing-policy>Round-Robin</load-balancing-policy>
          </uniform-distributed-queue>
          </weblogic-jms>
          But the problem was with the clustering.
          Thanks for your time..

Similar Messages

  • MDB and Execute Queue

    Hi Folks,
    as we got problems on thread deadlocks using JMS, we decided to define our own thread
    queue to be used by our application. In the documentation it is described, that you
    need to generate all your EJBs with java weblogic.ejbc -dispatchPolicy xyz. By this
    you connect your EJB to the named thread queue, which you will need to add to your
    config.xml.
    What I could find out was, that this works fine for stateful or stateless session
    beans, but it looks like message driven beans do ignore this option.
    So here are my questions:
    Which thread queue is used by message driven beans?
    How can I change the thread queue?
    Many thanks,
    Nicole

    Unfortunately, MDBs do not currently support running on a separate queue. They run on
    the default queue.
    -- Rob
    Nicole wrote:
    Hi Folks,
    as we got problems on thread deadlocks using JMS, we decided to define our own thread
    queue to be used by our application. In the documentation it is described, that you
    need to generate all your EJBs with java weblogic.ejbc -dispatchPolicy xyz. By this
    you connect your EJB to the named thread queue, which you will need to add to your
    config.xml.
    What I could find out was, that this works fine for stateful or stateless session
    beans, but it looks like message driven beans do ignore this option.
    So here are my questions:
    Which thread queue is used by message driven beans?
    How can I change the thread queue?
    Many thanks,
    Nicole

  • MDB and MessageConsumer Queue Questions

    (1) Does a MessageConsumer object, when called on its onMessage() method, provide the same JMS queue processing as a Message Driven Bean (MDB) called on it's onMessage() method? That is, the message remains on the queue until the onMessage() method completes in both cases.
    (2) Does the same apply to a MessageConsumer's receive() method? That is, the message remains on the queue until the next receive is called?
    Thanks

    Unfortunately, MDBs do not currently support running on a separate queue. They run on
    the default queue.
    -- Rob
    Nicole wrote:
    Hi Folks,
    as we got problems on thread deadlocks using JMS, we decided to define our own thread
    queue to be used by our application. In the documentation it is described, that you
    need to generate all your EJBs with java weblogic.ejbc -dispatchPolicy xyz. By this
    you connect your EJB to the named thread queue, which you will need to add to your
    config.xml.
    What I could find out was, that this works fine for stateful or stateless session
    beans, but it looks like message driven beans do ignore this option.
    So here are my questions:
    Which thread queue is used by message driven beans?
    How can I change the thread queue?
    Many thanks,
    Nicole

  • Distributed queue usage with custom queue listeners in cluster

    Hi,
    Can someone help in solving the issue. We have a web application which will create consumers(threads in infinite loop) for an inbound queue(name comes from DB table) and after doing certain process result will be pushed to outbound queue(name comes from DB table).
    When application runs in single managed server(without clustering) every thing works fine.
    If I want to deploy the same application in two managed servers (with are under same cluster) which talks to same DB how to handle above scenario
    1. Create 2 JMS servers one on each managed server(on different machines)
    2. Create queue one for each JMS server
    3. Create distributed queue and add above two queues as members of it
    4. Create connection factory and target it to cluster
    After creating above instrastructure(similar infrastructure will be created for inbound and outbound queue), can I use distributed queue JNDI name to create listeners(threads) to read messages? Or do I need to create listeners for each individual member in the distributed queue?
    I know that while sending message to distributed queue, I can create sender on distributed queue and weblogic automatically takes care of sending the message to appropriate member in the DQ, but how it works for distributed queue?
    Also, want to know how can I access distributed queue? For example, if managed server 1 is accessed by http://10.11.134.24:7001 and managed server 2 is accessed by http://10.11.134.25:7001. which URL I need use in JNDI context provider URL to access distributed queue? can I use any URL will it make any difference?
    Generally for servlets/JSPs we create proxy server to access it through cluster, instead of directly using managed server URLs. But how it works for distributed queue?
    Thanks
    Santhosh
    Edited by: user8676720 on Oct 4, 2011 8:35 AM

              Yes.
              It turns out that if replicate local queue jndi name in cluster is set to false
              the message did not get forward :(
              Dongbo Xiao <[email protected]> wrote:
              >Sorry, the attribute is ForwardDelay, not ForwardPolicy.
              >
              >Dongbo
              >
              >Dongbo Xiao wrote:
              >
              >> Hi Eran,
              >>
              >> Have you set up the ForwardPolicy for the Distributed Queue?
              >> By default, the ForwardPolicy is -1, which turns off the forwarding.
              >>
              >> Dongbo
              >>
              >> eran wrote:
              >>
              >> > Hello,
              >> > I have 2 nodes in cluster each one has a pinned JMS server with a
              >queue QueueA
              >> > and QueueA2
              >> > respectively both mebers in a distributed destination dist_queue.
              >> > There is a consumer on QueueA only (startup class).
              >> > In case of a message sent to QueueA2 a consumer is created for QueueA2
              >automaticly
              >> > (seen in the admin console) out of the blue, and the message do not
              >get forward
              >> > to QueueA where my consumer is listening.
              >> > Monitoring JMS connections of both servers shows only my consumers'
              >connection.
              >> > Our application depends on the forward feature.
              >> > Am I doing something wrong? any ideas?
              >> >
              >> > Thanks.
              >> > Eran
              >
              

  • Queue vs Distributed queue

    Hi Guys,
    Could you please help me resolve some doubts on Regular Queue and Distributed Queues.
    1. What is the basic Difference between regular q and distributed q.
    2. Can we deploy the regular q on clustered weblogic, If yes, how will this be different from deploying a distributed q on cluster.
    Regards

    Hi,
    Queue or Distributed Queue had same set of working design but only one difference is one queue is set for one pinned services where as Distributed queue is targeted to Cluster that means, One distirbuted queue can have multiple queue which are targeted to individual managed server or JMS server.
    I hope you know difference between Uniform distributed queue and Distributed queue.
    Uniform Distributed queue will created its own temporary queue destination on run time where as Distributed queue will required physical queue to assigned with in clustere.
    Hope I address your query.
    Regards,
    Kal

  • Data retrieval from JMS queue using single SOA composite in a clustered env

    Hi,
    I have following situation:
    1) A requester SOA composite (Composite1)is reading data from a File
    2) Mediator is routing data received from Composite1 and writing in a JMS queue.
    3) A provider composite (Composite2) is reading from the JMS queue.
    Both Composite1 and Composite2 is deployed in a clustered environment.
    Problem is Composite2 is not able to read data sequentially from JMS Queue sometime (for example out of 30000 transactions its failing once). Here it's a queue and only one producer and only one consumer is there.
    What may cause this issue? I thought a single producer and single consumer on a queue will guarantee FIFO retrieval . Could you please advise where may be the gap?
    Thanks
    Edited by: user1054373 on Sep 18, 2012 11:29 PM

    Hi,
    I thought a single producer and single consumer on a queue will guarantee FIFO retrieval Java Message Service Specification does not guarantee ordered message delivery when applications use distributed queues...
    Using Weblogic Message Unit-of-Order may solve your issue...
    http://docs.oracle.com/cd/E23943_01/web.1111/e13727/uoo.htm#JMSPG389
    Hope this helps...
    Cheers,
    Vlad

  • JMS for WebLogic Server 9.2. Members of distribute queues

    I don't understand concept of the distributed queues. As far as I understand, distributed queues consist of physical queues. How do I create physical queus for distributed queues ? What is the Members tab for Distributed queue ? If I have non-persistent distributed queu , can I have a distributed q that points to the cluster that doesn't have a JMS ?

    Hi,
    I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
    -Vinod

  • Compare creation of Datasources and JMS Queues : SAP vs (Weblogic/Websphere

    I am used to creating JDBC Datasources and JMS Queues on Weblogic/Websphere thru their Admin applications.
    Can someone compare/contrast that process to that on SAP's netweaver ( either using NWA or Visual Administrator).
    Thanks

    Hi Parag,
    For the process of creating JDBC datasources and JMS resources @ SAP NetWeaver you can refer to the documents here on SDN and help.sap.com, and compare that process for yourself, thus not being influenced by others' biased or unbiased opinions.
    For NetWeaver 04 and 04s these would be:
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm">JDBC Connector Service</a>
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/22/cf4e71c46cdb4da31153be96c5389f/frameset.htm">JMS Connector Service</a>
    For the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/javaee5">Java EE 5 Edition</a>:
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7bb9751d-0e01-0010-febd-c3adce2c408c">Working with Database Tables, DataSources and JMS Resources</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/806e75a0-0e01-0010-2587-fc518de8ac1a">Administration Guide</a> -> section "Application Resources Management" (pages 89-104)
    Hope that helps!
    Your feedback/findings are very welcome!
    -Vladimir

  • How do you change the email address on the auto-created button in a distributed form?

    I created a form and distributed form but its going to the wrong person. It's almost like its using the email address that was used to register the software

    What does that have to do with the PREMIERE PRO video editing software discussed in this forum?
    Provide the name of the program you are using so a Moderator may move this message to the correct program forum

  • Are Connection Factory and JMS Queue supposed to be in JNDI tree

    I have created Connection Factory and JMS Queue. I am expecting to find both in JNDI tree. Where, in the http://localhost:7001/console/consolejndi.portal, could I find them? I mean, in which branch of the JNDI tree?

    Hi,
    You should find them following exactly the way you define their JNDI Names... Make sure you are looking into the JNDI tree for the right managed server... Pay attention into the targets of your connection factory and queue...
    For example, a JNDI name jms.myConnectionFactory (or jms/myConnectionFactory) targeted to soa_server1 will appear under soa_server1 / jms / myConnectionFactory ...
    Hope this helps...
    Cheers,
    Vlad

  • Issue with Distributed Queue and WebLogic Clustering

    Hi, When a message is received by distributed queue, MDB is processing the message on two managed servers. There seems to be issue with clustering and the physical queues present on both the managed servers are receving the message.
    Our environment configuration details are as below:
    One Web logic Cluster with 2 nodes (2 managed web logic servers).
    One MDB deployed on the cluster listening to a queue with JNDI name “xng/jms/CODEventsQueue”
    One Distributed queue with two members on the two nodes of the cluster, and with JNDI name “xng/jms/CODEventsQueue”
    Two members of the distributed queue deployed on two JMS servers, which are separately deployed on each managed server .
    And the distributed queue is deployed on the cluster.
    Any help is appreciated.
    Thanks
    Sampath

    It is not clear to me how you concluded that "both the managed servers are receiving the message". Did you monitor the queues' statistics, or did you see both MDB instances received the same message?
    It looks like that you using a weighted distributed queue. Do the two physical queues that compose the distributed queue have their own JNDI names? If so, what are they?
    Have you tried to use a uniform distributed queue and see if the same behavior shows up?
    You can find more about uniform distributed destination at
    http://edocs.bea.com/wls/docs103/jms/dds.html#wp1313713
    BTW, which WebLogic Server releases are you using? Could you provide the distributed queue configuration?
    Thanks,
    Dongbo

  • Using distributed queues and factories in a weblogic cluster

    Hi all,
    in our environment we have a domain which has two machines. One is running the AdminServer and Node1 and the 2nd machine is running Node2.
    For each Node I have created a JMS Server and a corresponding file store located at each machine.
    I've also created a JMS Module containing our required queues, factories and topics. Queues and Topics are of the Uniform Distributed type.
    I've targeted this module at the cluster and experimented with creating a subdeployment. But from what I recon, since all my resources have default targeting
    enabled, a subdeployment is not required, they target what is targeted by the JMS Module, right?
    However I get an exception when both nodes are up:
    <Nov 4, 2008 11:47:01 AM EET> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member       
    MyJMSModule!MyJMSServer@myTopic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Couldn't connect to weblogic.rjvm.RJVMImpl@187766d - id: '-1415064081927280896S:10.0.0.5:
    [7001,7001,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain        :NodeApp2' connect time: 'Tue Nov 04 11:47:01 EET 2008' - it is likely that the connection has already been shut down; nested exception is:
    5564732         java.rmi.ConnectException: Couldn't connect to weblogic.rjvm.RJVMImpl@187766d - id: '-1415064081927280896S:10.48.92.70:[7001,7001,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp2'
    connect time: 'Tue Nov 04 11:47:01 EET 2008' - it is likely that the connection has already been shut downThe two nodes are up and running and the node managers as well. Is this the correct way to create the queues and topics for a clustered environment?
    Thanks
    Edited by: dvm on Nov 4, 2008 3:12 AM

    I've done the steps but the problem still persists. I don't know if I had this before, but now both machines can't see each other.
    From Node1 logs *.out file:
    <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member MyJMSModule!MyJMSServer2@my_cacheTopic:
    weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException:
    Couldn't connect to weblogic.rjvm.RJVMImpl@62017d - id: '4786464166486913267S:10.48.92.70:[7001,7001,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp2'
    connect time: 'Wed Nov 05 16:03:53 EET 2008' - it is likely that the connection has already been shut down; nested exception is:
    java.rmi.ConnectException: Couldn't connect to weblogic.rjvm.RJVMImpl@62017d - id: '4786464166486913267S:10.48.92.70:[7001,7001,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp2'
    connect time: 'Wed Nov 05 16:03:53 EET 2008' - it is likely that the connection has already been shut downand from Node2 logs *.out file:
    <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member MyJMSModule!MyJMSServer1@my_cacheTopic:
    weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException:
    Couldn't connect to weblogic.rjvm.RJVMImpl@24b64a - id: '-788798942991630857S:10.48.92.69:[7003,7003,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp1'
    connect time: 'Wed Nov 05 16:03:59 EET 2008' - it is likely that the connection has already been shut down; nested exception is:
    java.rmi.ConnectException: Couldn't connect to weblogic.rjvm.RJVMImpl@24b64a - id: '-788798942991630857S:10.48.92.69:[7003,7003,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp1'
    connect time: 'Wed Nov 05 16:03:59 EET 2008' - it is likely that the connection has already been shut downThis happens just after the managed servers have been started with the application previously deployed.

  • Distributed Destinations and Error Queues

              I have a distributed queue - distqueue which is configured with two queue members
              - srvr1q
              and srvr2q. srvr1q is a physical queue destination that is running on JMSServer1
              on one instance in a cluster. srvr2q is a physical queue destination that is running
              on JMSServer2 on another instance in the cluster. I have two errorqueues - srvr1errq
              and srvr2errq - deployed on JMSServer1 and JMSServer2 respectively. I have configured
              the srvr1q to the following:
              Redelivery Delay Override: 10000
              Redelivery Limit: 3
              Error Destination: srvr1errq
              Also the srvr2q is configured to the following:
              Redelivery Delay Override: 10000
              Redelivery Limit: 3
              Error Destination: srvr2errq
              There is an MDB listening to each one of these local queues. The MDB is programmed
              to throw a null pointer exception (to simulate business logic processing failures)
              My expectations are : the message goes to one of the local queues. Null Pointer
              exception is thrown. After 10 seconds the message is resent to the same queue
              with a similar fate. After the third attempt, the message is moved to the error
              queue of the corresponding local queue.
              What I see is the following:
              When I send a message I do see a Null Pointer Exception, but it occurs only once
              and I dont see the message going to the error queue. Since my Load Balancing policy
              is Round-Robin on the distqueue, the local queues receive the message every other
              time with the same result - Null Pointer Exception thrown only once.
              I also have JMSStores configured so the messages are persistent.
              Can someone explain to me what I am doing wrong?
              Thanks.
              

              "Prakash Muthukrishnan" <[email protected]> wrote:
              >
              >Hi Tom
              > Thanks again for the reply. I do use a tx MDB. I have set the transaction-type
              >to Container in the message-driven stanza in ejb-jar.xml. And also the
              >trans-attribute
              >for that EJB in the container-transaction stanza, I have used Required.
              >Do I need
              >to setup anything else ?
              I don't think so.
              > The transaction descriptor element in the weblogic-enterprise-bean
              >stanza in weblogic-ejb-jar.xml for that MDB is empty.
              Not sure what you mean?
              > Am I missing anything
              >else?
              Container & Required is all that is needed
              If you like, post your ejb descriptor xml file, and I'll take a quick
              look to double-check.
              >-Prakash
              >
              >Tom Barnes <[email protected]> wrote:
              >>Hi Prakash,
              >>
              >>A runtime exception should force a rollback for tx MDBs, and
              >>a recover for non-tx MDBs. If you are seeing different
              >>behavior there may be a bug in WL.
              >>
              >>Since MDBs do not log an exception when the app throws
              >>a Runtime exception, I often recommend wrapping the
              >>application code in a try catch anyhow
              >> try {
              >> } catch (Throwable t) {
              >> log
              >> force rollback
              >> }
              >>I think there are plans to provide a configurable that
              >>optionally does something similar in the next release (no guarantees).
              >>(The problem is that some apps throw a runtime on purpose, and
              >>could quickly flood the log if such runtimes were logged per message.)
              >>
              >>Tom
              >>
              >>Prakash Muthukrishnan wrote:
              >>> Tom
              >>> Thanks for the suggestion. Using the setRollbackOnly method did the
              >>trick. This
              >>> brings up
              >>> a related question: What if a run time exception was thrown during
              >>the processing
              >>> in an MDB?
              >>> Is it not retried and ultimately shoved into the error queue?
              >>> Thanks again.
              >>> -Prakash
              >>>
              >>>
              >>> Tom Barnes <[email protected]> wrote:
              >>>
              >>>>Hi Prakash,
              >>>>
              >>>>At first glance, it doesn't seem like your doing anything wrong.
              >>>>Could you post your release and SP level, as well as your config.xml?
              >>>>
              >>>>How many messages did you send through?
              >>>>
              >>>>Note that for transactional MDBs it is best to call "setRollbackOnly"
              >>>>on the EJB context rather than throwing an NPE. This is because
              >>>>throwing a runtime exception forces the MDB to destroy itself and
              >>>>get re-initialized (pretty high overhead). For non-transactional
              >>>>MDBs, throwing a runtime exception is your only option.
              >>>>
              >>>>Tom, BEA
              >>>>
              >>>>Prakash Muthukrishnan wrote:
              >>>>
              >>>>
              >>>>>I have a distributed queue - distqueue which is configured with two
              >>>>
              >>>>queue members
              >>>>
              >>>>>- srvr1q
              >>>>>and srvr2q. srvr1q is a physical queue destination that is running
              >>>>
              >>>>on JMSServer1
              >>>>
              >>>>>on one instance in a cluster. srvr2q is a physical queue destination
              >>>>
              >>>>that is running
              >>>>
              >>>>>on JMSServer2 on another instance in the cluster. I have two errorqueues
              >>>>
              >>>>- srvr1errq
              >>>>
              >>>>>and srvr2errq - deployed on JMSServer1 and JMSServer2 respectively.
              >>>>
              >>>>I have configured
              >>>>
              >>>>>the srvr1q to the following:
              >>>>>
              >>>>>Redelivery Delay Override: 10000
              >>>>>Redelivery Limit: 3
              >>>>>Error Destination: srvr1errq
              >>>>>
              >>>>>Also the srvr2q is configured to the following:
              >>>>>Redelivery Delay Override: 10000
              >>>>>Redelivery Limit: 3
              >>>>>Error Destination: srvr2errq
              >>>>>
              >>>>>There is an MDB listening to each one of these local queues. The
              >MDB
              >>>>
              >>>>is programmed
              >>>>
              >>>>>to throw a null pointer exception (to simulate business logic processing
              >>>>
              >>>>failures)
              >>>>
              >>>>>My expectations are : the message goes to one of the local queues.
              >>>>
              >>>>Null Pointer
              >>>>
              >>>>>exception is thrown. After 10 seconds the message is resent to the
              >>>>
              >>>>same queue
              >>>>
              >>>>>with a similar fate. After the third attempt, the message is moved
              >>>>
              >>>>to the error
              >>>>
              >>>>>queue of the corresponding local queue.
              >>>>>
              >>>>>What I see is the following:
              >>>>>When I send a message I do see a Null Pointer Exception, but it occurs
              >>>>
              >>>>only once
              >>>>
              >>>>>and I dont see the message going to the error queue. Since my Load
              >>>>
              >>>>Balancing policy
              >>>>
              >>>>>is Round-Robin on the distqueue, the local queues receive the message
              >>>>
              >>>>every other
              >>>>
              >>>>>time with the same result - Null Pointer Exception thrown only once.
              >>>>>
              >>>>>I also have JMSStores configured so the messages are persistent.
              >>>>>
              >>>>>Can someone explain to me what I am doing wrong?
              >>>>>Thanks.
              >>>>
              >>>
              >>
              >
              

  • JMSHelper throws 'JMS server is not targetted' creating distributed queue

    I am trying to use the 8.1 weblogic.jms.extensions.JMSHelper to create a distributed queue. The target JMS servers are all migratable servers. When calling method createDistributedQueueAsync() I get a JMSException thrown compaining that the [first] JMS server is not targetted. Looking at the code provided in [http://forums.bea.com/bea/thread.jspa?messageID=200023386] which is based on the JMSHelper class source, the exception may be thrown because the target MBean is of class MigratableTargetMBean, whereas the JMSHelper is expecting class TargetMBean. Yet, the 9.0 documentation (which at least documents it) suggests that MigratableTargetMBean is derived from TargetMBean
              Does anyone have experience of this issue or its resolution, short of crafting the code by hand as per the above-referenced reply?

    Hi,
    Just to remember the configuration: 2 managed servers configured as cluster that should be deployed on 2 different machine.
    Following summary of the tests:
         - node manager + admin server + 1 managed server running on the first machine --> server failed to init with error "Server is not in the majority cluster partition"
         - node manager + admin server + 2 managed servers running on the one machine --> servers are running without errors
         - node manager + admin server + 1 managed server running on the first  machine / node manager runs on the second machine --> server on the first machine runs without errors without the famous error ' Server is not in the majority cluster partition'.
    Bottom line, seems that if the node manager is not running on the remote machine, the cluster is not in a stable state and so the single managed server failed to initialize.
    Is it according the documentation / expectations ?
    Thanks,
    Yaakov

  • MDB connecting to Remote Distributed Queue

    Hi,
    I am trying to deploy a MDB in weblogic 10.0 and this will listen to a Distributed Queue in another weblogic version10 server.
    my MDB code looks like
    @MessageDriven(mappedName = "jms/DMSQueue", activationConfig = {
              @ActivationConfigProperty(propertyName = "initial-context-factory ", propertyValue = "weblogic.jndi.WLInitialContextFactory"),
              @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue = "jms/cf"),
              @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
              @ActivationConfigProperty(propertyName="destination", propertyValue="jms/DMSQueue"),     
              @ActivationConfigProperty(propertyName = "destinationJndiName", propertyValue = "jms/DMSQueue"),          
              @ActivationConfigProperty(propertyName = "providerAdapterJNDI", propertyValue = "java:/RemoteJMSProvider"),
              @ActivationConfigProperty(propertyName = "provider-url", propertyValue = "t3://10.54.115.171:80")          
    public class TestMdb implements MessageListener {
         public void onMessage(Message message) {
              System.out.println("Received Message: " + message);
    if the I configure the bean for a local Queue it works properly.
    But if I provide the url of the remote Queue, it does not get connected.
    my ejb-jar.xml
    contains only
    <enterprise-beans>
    <message-driven>
    <ejb-name>ejbsms</ejb-name>
    <ejb-class>hmil.TestMdb</ejb-class>      
    </message-driven>
    </enterprise-beans>
    I guess we need to provide the security credentials of the remote server and may be missing some thing else.
    Please guide me on what changes required in annotations to get it working
    I prefer to use container independent propertyName
    Edited by: user13583038 on Jan 3, 2011 4:08 AM

    You can try posting JMS related questions to the JMS newsgroup.

Maybe you are looking for

  • Not Able to Uninstall Oracle BPEL and SOA Suite

    Cannot Delete OLITE40.jar file from //product/10.1.3.1/Oracleapps/Mobile/Sdk/BIN

  • How to find and replace the text present in the url

    I have a column of type NCLOB with some text having url's in between as shown below: ======================================================================== This text is for testign purpose.This text is for testign purpose. <A PL/SQL <U PL/SQL </U>

  • Dynamic Playlist for streaming video

    This is my first attempt at building a dynamic playlist for streaming flash video and I'm following the tutorial at "macromedia.com/devnet/flash/articles/video_player.html". I've changed the paths to my FMS and loaded the video files to the applicati

  • DNS Management in OS 10.6.3 Server

    We are currently running Mac OS 10.4.11 server, and we will soon be upgrading to Mac OS 10.6.3 server on a new Xserve, and I have a question about how DNS is managed in Mac OS 10.6.3 server. We run DNS internally only. On our 10.4.11 server, we switc

  • Cannot switch back from windows keyboard setup

    I switched the option and command key in system preferences so the layout would be correct on my windows keyboard but now the keys will not switch back (they say they are switched but do not work that way) Does anyone know how to fix this?