JMS Distributed Destinations as proxy service endpoints

We have a cluster of 2 ALSB servers with a proxy service deployed
listening on a JMS queue which is a distributed destination (DD) on a
WLS 8.1 system.
The JMS DD is spread across 4 JMS servers and 4 JVM's.
When ALSB starts up - we only get consumers on 2 of the 4 DD members,
which makes sense as a JMS proxy service is essentially an MDB, and this
is normal MDB/distributed destination behaviour - it will bind to the
queue member where it first makes the connection to the JVM.
How do I make sure my messages are consumed from all 4 DD queue members?
There is a JMS option to forward messages to queues with consumers if no
consumers exist - is that the way to do it?
Someone must have come across this before and I'd be grateful for any
advice.
Also - how do you reduce the consumers on the JMS queue - seems to
default to 16. Perhaps you don't.
Thanks,
Pete

Meghan Pietila wrote:
Update: I see your exchange with Tom over on the JMS forum, Pete. We just switched everything to WLS 9.2, so maybe the ALSB internal extension will work for us. It's not working by default, so possibly it's something that must be activated... I'll follow up with BEA.
http://forums.bea.com/thread.jspa?threadID=570001317
I'd still like to hear what you end up working with, if you don't mind sharing once it's running. :)
MeghanI only have 8.1 as an option - a JMS proxy service is essentially an
MDB, and if you deploy an MDB in the same way, it will only bind to a
single destination, so it's actually behaving as I would expect.
The forward delay on the queue probably won't be an issue for us, as
we're not talking about high volumes and large messages, but for some
sites there will be alot of moving around queues, access jms filestore
etc which you could do without.
I reckon the trick is (as Tom mentioned) to bind to individual
distributed queue members from the proxy service somehow.
I'll let you know what I find out.
Pete

Similar Messages

  • Error Destination in JMS Transport Configuration page (Proxy Services)

    Hi, Can anybody provides me the sample of Error Destination in JMS Transport Configuration page (Proxy Services) .I need to know the format. I am using "jms://<host:port[,host:port]*/factoryJndiName/destJndiName>", but it does not work.
    From Oracle webstie, http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html, the detail description of Error Destination is " In this field you can configure the name of the target destination for the messages, which have reached the maximum number of retry count. "

    Can you provide the JNDI name of the error destination alone there ?

  • Does jms distributed queue support automatic service migration?

    As the migration document of Weblogic mentioned, the jms distributed queue can be manually migrated, but the document doesn't talk about automatic migration of jms distributed queue. Does jms distributed queue support automatic service migration? Anybody can help me? Thanks a lot.

    When you look at configuring JMS, you do something like:
    Create a JMS server that will contain one or more JMS destinations and will live on a particular server instance.
    Next you create a JMS module and target it to a cluster. Within the module you create a distributed queue (destination).
    Note that it is the JMS server which is the so-called pinned service. For pinned services you can configure migratable targets
    the way you want it (http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/config.html#1056368)

  • How to specify the JMS Client ID in Proxy Service of OSB 11.1.1.5 version ?

    Hi All,
    I am looking for an option to set the JMS clientID for a JMS Proxy services in OSB. Can this feature available in OSB 11.1.1.5 version?
    Thank you,
    Ram.

    These links will helpful for you.
    http://jdevadf.oracle.com/adf-richclient-demo/docs/tagdoc/af_train.html
    http://download.oracle.com/docs/cd/E15523_01/apirefs.1111/e12419/tagdoc/af_train.html

  • JMS distributed destination

    In Bea's WLS 7.0 JMS: "Looking up Distributed Topics" and "Deploying Message-Drive
    Beans on a Distributed Topic" :
    http://e-docs.bea.com/wls/docs70/jms/implement.html#1260828
    This sound like each message(topic) gets sent to all members of a distributed
    topic.
    Then in the same doc for LB, a couple paragraphs down we have a conflict explaination:
    "In the round-robin algorithm, WebLogic JMS maintains an ordering of physical
    destinations within the distributed destination. The messaging load is distributed
    across the physical destinations one at a time in the order that they are defined
    in the WebLogic Server configuration (config.xml) file. "
    If a topcs sent to a distributed topic will be sent to all physical destinations,
    why we need LB here. Or the LB is applied to distributed Queue only.
    Please comments.
    THX.
    -John

    Rob,
    Not a expert I must admit, but the link provided by you states "A distributed destination is a set of destinations (queues or topics) that are accessible as a single, logical destination to a client. A distributed destination has the following characteristics:
    It is referenced by its own JNDI name."
    You can actually configure JMS adapters using JNDI so I think this should be possible. More info here,
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
    Do let us know if this helps and works!
    Regards
    Bhavesh

  • JMS Distributed Destination Topic - how to avoid MDB to recieve duplicates

    HELP!!
              I have spent a lot of time looking for an option to move jms on a cluster, finally I can do this using distributed destination, I have two memmbers(Topic) in the distributed destination topic, but when both of them are active, the Message Driven Bean which is deployed on cluster recieves 2 messages instead of 1, anyone please help me to change this to have only one message instead of 2 !!!!!

    Make it a Queue or don't deploy the MDB to the cluster. You are seeing
              expected behavior. I have the same situation with a Topic and I deploy my
              MDB to one node in the cluster and have it configured to consume the local
              physical Topic.
              Bill
              "Manav Sehgal" <[email protected]> wrote in message
              news:18024883.1107530318601.JavaMail.root@jserv5...
              > HELP!!
              > I have spent a lot of time looking for an option to move jms on a
              > cluster, finally I can do this using distributed destination, I have two
              > memmbers(Topic) in the distributed destination topic, but when both of
              > them are active, the Message Driven Bean which is deployed on cluster
              > recieves 2 messages instead of 1, anyone please help me to change this to
              > have only one message instead of 2 !!!!!
              

  • How i can implement in 6.0 the JMS Distributed Destination feature of 7.0 ?

              Hi all,
              Peace,
              Juan Alonso.
              

    Hi Juan,
              Check out the jms performance whitepaper posted on dev2dev, or find
              attached to post:
              http://newsgroups.bea.com/cgi-bin/dnewsweb?utag=&group=weblogic.developer.interest.jms&xrelated=9372&cmd_thread_last.x=42&cmd_thread_last.y=8
              It contains a section on emulating 7.0 distributed queues in 6.1.
              Also check out the newsgroup thread on "Approximating Distributed Queues
              In 6.1".
              http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jms&item=9415&utag=
              It extends the above whitepaper to cover topics...
              I think you may need 6.1, an easy upgrade from 6.0.
              Tom
              Juan Alonso wrote:
              > Hi all,
              >
              > Peace,
              >
              > Juan Alonso.
              

  • Distributed destination with MQ as Foreign Provider

    Hi
              Messages arrive in a set of clustered MQ Series Queues. MDBs process the messages (We use MQ as the Foreign JMS Provider). Can I set up a distributed destination (JMS Queues) in WebLogic and use those clustered MQ queues as the Foreign Provider ? I would like the MQ Series clustering to provide the redundancy/availability of the MQ Series system and the JMS distributed destination to provide high availability for the MDBs that are hosted in a set of clustered WebLogic server instances.
              Thanks

    Hi          > Messages arrive in a set of clustered MQ Series
              > Queues. MDBs process the messages (We use MQ as the
              > Foreign JMS Provider). Can I set up a distributed
              > destination (JMS Queues) in WebLogic and use those
              > clustered MQ queues as the Foreign Provider ?
              No. WL distributed destinations consist only of a set of physical WL destinations. The WL distributed destination code does not support non-WL destinations.
              > I would
              > like the MQ Series clustering to provide the
              > redundancy/availability of the MQ Series system and
              > the JMS distributed destination to provide high
              > availability for the MDBs that are hosted in a set of
              > clustered WebLogic server instances.
              If MQ Series exposes its distributed destination via the standard JMS API, then the MDBs will automatically run as MQ distributed dest clients. This is a function of MQ, not WL -- WL MDBs simply use the standard JMS API of the vendor's supplied client to get their messages.
              But note that WL MDBs use a single connection per MDB pool/deployment. Some clustering implementations (MQ?) require using multiple connections...
              >
              > Thanks

  • Multiple Proxy Services for single JMS endpoint

    Hi Forum,
    OSB Proxy services do not allow to have the same endpoint. I have defined 2 proxy services to look into one JMS queue. But it does not allow to do this.
    I want to fetch messages from the same queue by more than one Proxy (parallel execution to empty the queue faster). How can I do that?
    Thanks in advance..
    CK

    OSB/JMS by design are of little use here. For parallel execution to empty the queue faster we can
    1) use distributed Q in cluster and multiple proxies can process on the distributed Q.
    Manoj

  • OSB Proxy Service remote Endpoint URI

    Hi,
    I have configured a new Proxy Service in OSB where the endpoint URI points to a JMS Queue on a remote Weblogic Server. But when I look at the OSB server's log, it is showing the following WARNING message: *'Please ensure the destination is available at the JNDI name QUEUE_JNDI_NAME.'*. Is there any other information that the OSB Server requires in order to consume messages from a remote server's queue other that its endpoint URI?
    Thanks in advance for any advise on this.

    The problem was that the endpoint URI had two ip:port endpoints (i.e. jms://192.168.1.1:7001,192.168.1.1:7003/...) and the 2nd ip:port endpoint didn't have any information about the queue. So for now, I've removed the 2nd ip:port from the URI and will include it again once the admin for that server sets up the queue within it correctly.
    Cheers.

  • Publishing message to JMS Queue on Weblogic from OSB proxy service

    Hi,
    1. I have created a JMS module: testModule and a JMS queue: testQueue in the weblogic admin console.
    2. Created a business service with the above queue as endpoint.
    3. Created a proxy service which publishes the message to the queue using the business service. I have used Publish activity to publish the message to the business service.
    When i run the proxy service with the request message, then, no error is coming but, in the admin console when i click on JMS module->testModule->testQueue->Monitoring tab, i see nothing. There are no entries in the table so, how can i check if the message is properly published to the queue or not.
    The queue is not listened by any service for consuming the messages.
    Kindly help me in figuring out this issue.
    Thanks in advance.

    If the destination was a topic, the behavior would be expected. Messages only stays on a topic and are delivered to consumers if there are consumers or durable subscribers.
    Did you check the server logs and see if there are any exceptions or warnings?
    You can also turn on jms debugging by adding the following to your server startup script.
    -Dweblogic.debug.DebugJMSFrontEnd=true
    -Dweblogic.debug.DebugJMSBackEnd=true
    The debugging messages wiill show up in the server log.

  • Report and Alert don't executed in the error handler with a JMS proxy service

    Hi,
    I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
    My error handler contains two main elements :
    - a Report action
    - an Alert with a JMS destination defined
    When the business service failed the message remain in the queue. It's the expected behavior.
    The problem is :
    - the report is missing
    - the alert is raised but missing in the JMS destination defined in the Alert setting.
    I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
    Unfortunately the message don't remain in the JMS queue.
    What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
    I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
    This solution is not convenient and I hope another solution is possible.

    Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
    wiki article on preparing your workgroup environment may require you to visit each machine individually.
    For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
    on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
    but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
    As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
    Please remember to click "Mark as Answer" on the post that helps you, and to click
    "Unmark as Answer" if a marked post does not actually answer your question. Please
    VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

  • Proxy Service listening a JMS Queue

    HI all,
    I have a simple question.
    I have an web application that write a message into a JMS Queue.
    I wanna know if when a message arrives into a JMSQueue an ESB proxy can listen this queue, get the message and afterwards process it.
    Thanks and Regards!

    Hi,
    In ALSB 2.6 its very much possible. Create a proxy Service (Any XML Service) configure your endpoint to the queue. provide correct Url, Connection factory JNDI and queue JNDI to the endpoint.
    Hope this helps you.
    ~Anup

  • Regarding JMS-Queue/Topic in Proxy and Business service in OSB

    Hi
    I have one query regarding to the JMS-Queue/Topic.
    I am published the message to the JMS-Queue/Topic.
    ----My Business-service configuration is---
    General----Any xml
    Tranport--jms://localhost:7001/MyConnectionFactory/RequestQueue
    Response--None
    I call this Business-service in proxy-service of Routing message was published successfully to thee Queue.
    I try to dequeue the message from that queue for this
    --- I take another proxy with---
    General----Any xml
    Tranport--jms://localhost:7001/MyConnectionFactory/RequestQueue
    In meassage flow
    Routing--second busines-service)
    --- Second business-service configuration is---
    General----Any xml
    Tranport-File (C://temp)
    Issue is when I publish the message to Queue,the message is also found in the file  i.e C:temp. I don't now why  this come to the file.*
    Any suggestions
    Thanks
    Mani

    Either I did not get an idea, but in your JMS proxy you are routing to File :)
    If you don't want file, why route to 2nd BS ?

  • What is the endpoint URI of a proxy service?

    Hello, I want to create a SOAP client that will access an ALSB-hosted proxy service, but I don't know the URL needed to get to the web service.
    Within ALSB's console, I can easily test the proxy web service but don't know how to access it externally.
    On the Proxy Service's configuration page, in the Transport section, the endpoint URI is given as "/default/DoubleItExternalProxy", but when I try to access the wsdl at that uri via:
    http://localhost:7001/default/DoubleItExternalProxy?wsdl, I get this message:
    Error 500--Internal Server Error
    This service is not associated to a wsdl
    Although I believe the service must be associated to a WSDL--I have it based on a business service that has its own WSDL. Does anyone know what the browser URL needs to be to get to the WSDL? Using JAX-WS, I need the WSDL to generate the JAX-WS/JAXB artifacts for my SOAP client.
    Thanks,
    Glen

    Hi Glen
    You will need to associate your proxy service with a WSDL when you create it (Unfortunetly it can't be changed from Any SOAP to WSDL afterwards).
    The proxy does not use the wsdl from the any business services it calls in case there are multiple.
    Ryan

Maybe you are looking for