LoadBalancer URL in JMS Bridge Destinations

Hi,
This is related to Message Bridge Setup.
Can we use load balancer URL instead of Managed server individual URL(port) in setup of JMS Bridge Destinations(Connection URL)
Say for example like t3://integration.stage.life:5555 instead of regular t3://f3aos.stage.life:7001 URL
Soa_domain-> Services-> Messaging-> Bridges -> JMS Bridge Destinations-> New
Name: SOTOPIC1
Adapter JNDI Name:Adapter JNDI Name
Connection URL: Load balancer URL like like t3://integration.stage.life:5555 instead of regular t3://f3aos.stage.life:7001 URL??
Connection Factory JNDI Name:jms/SOTOPIC_CF
Destination JNDI Name:Destination:jms/SOTOPIC
We tried to give loadbalancer URL in the above configuration and it did not work where as if we regular managed server URL(port) it works?
Is there any additional configuration required for Loadbalancer URL to work?
Thanks

Can anybody please help me?

Similar Messages

  • Weblogic JMS Bridge betwwen WL 11g (10.3.3.0) and ActiveMQ 5.4.2

    Hi,
    I'm getting following warning when I try to connect two JMS Bridge Destinations (source WebLogic and destination ActiveMQ) through a Bridge.
    <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
    But when I test it by sending message WL does not forward that message to destination queue (ActiveMQ).
    When I try to send message individually in WL Queue and MQ Queue from POJO class to test it it works fine.
    Please find the setting details
    JMS Bridge Destination for ActiveMQ
    Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDINoTX
    Classpath: path of activemq-core-5.4.2.jar
    Connection URL: tcp://***.***.***.***:****
    Initial Context Factory: org.apache.activemq.jndi.ActiveMQInitialContextFactory
    Connection Factory JNDI Name: QueueConnectionFactory
    Destination JNDI Name: destination queue
    Destination Type: Queue
    JMS Bridge Destination for WebLogic
    Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDINoTX
    Classpath:
    Connection URL: t3://***.***.***.***:****
    Initial Context Factory: weblogic.jndi.WLInitialContextFactory
    Connection Factory JNDI Name: JNDI name of Connection Factory which is created in JMS module
    Destination JNDI Name: JNDI name of Queue which is created in JMS Module
    Destination Type: Queue
    User Name: given
    Password: given
    Thanks in advance
    Regards
    Amlendu
    Edited by: user7468329 on May 1, 2011 10:01 PM

    Hi,
    There's troubleshooting information in the bridge documentation.
    google: FAQs: WebLogic Messaging Bridge site:oracle.com
    Hope this helps.
    Tom

  • How to Configure Selector For JMS Bridge

    Hi,
    I was trying with Selector option in working with multiple Bridges, here is the scenario i applied.
    Created five Queues ( Q1, Q2, Q3, Q4 and Q5 ) and configured JMS Bridge Destinations having each queue with unique connection factory ( CF1, CF2, CF3, CF4 and CF5 ) and named it as D1, D2, D3, D4 and D5.
    Then created JMS Bridges as JB2 with source as D1 and destination as D2. Similarly JB3 as D1-D3, JB4 as D1-D4 and JB5 as D1-D5.
    And set Sector for each of JB2, JB3, JB4 and JB5 as Two, Three, Four and Five respectively and did restart after the changes.
    Now i am expecting the following scenario to work
    Pushing message to Q1/CF1 having Two in the content of message, hence expecting the message to be delivered to Q2/CF2 through JB2, but the messages is not moved through JB2.
    Similarly, Pushed message to Q1/CF1 having Three in the content of message, hence expecting the message to be delivered to Q3/CF3 through JB3, but the messages is not moved through JB3. Similar behavior for other messages having Four and Five in the message content.
    During the bridge configuration, selected QOS as "Atmost-Once".
    Note: All the configurations were done in same domain and the WL version is 10.3.6.0.*
    The sample message i am pushing to Q1/CF1 say "Two Test Data"* and expecting to reach Queue Q2/CF2
    Regards
    Venkata Madhu
    Edited by: vv**** on Sep 12, 2012 1:05 PM

    Hi Venkata,
    The expected selector syntax is the standard SQL-like JMS syntax. There's an extensive description of the syntax in the javadoc for javax.jms.Message.
    Selectors should normally only reference message header fields and message properties. I don't normally recommend using a selector that is based on message body as this requires using a proprietary WebLogic extension based on "xpath" XML expressions, and can have an large impact on performance. (The performance hit is caused by two factors - the need for the JMS server to unmarshal/decompress/page-in the body in order to get at its contents, and the natural cost of scanning a message body to see if it matches a string.)
    HTH,
    Tom

  • Help: jms bridge failed to put messages into target destination!

    Hi all,
              I created a jms bridge to transfer msgs form one domain(one cluster,hpux) to another domain(one cluster,aix),but it seems that the msg can't arrive at the target destination,below are the main log records:
              ####<2006-11-29 下午09æ—¶19分09秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200033> <Bridge "BillToEaiAckBridgeB1" is obtaining connections to the two adapters.>
              ####<2006-11-29 下午09æ—¶19分09秒 GMT+08:00> <Info> <Common> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-000628> <Created "1" resources for pool "Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA", out of which "1" are available and "0" are unavailable.>
              ####<2006-11-29 下午09æ—¶19分09秒 GMT+08:00> <Info> <Common> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-000628> <Created "1" resources for pool "Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA", out of which "1" are available and "0" are unavailable.>
              ####<2006-11-29 下午09æ—¶19分09秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200032> <Bridge "BillToEaiAckBridgeB1" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.>
              ####<2006-11-29 下午09æ—¶19分09秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200030> <Bridge "BillToEaiAckBridgeB1" is configured to work in "Exactly-once" mode, and it is actually working in "Exactly-once" mode.>
              ####<2006-11-29 下午09æ—¶19分09秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200028> <The bridge "BillToEaiAckBridgeB1" has started transferring messages.>
              ####<2006-11-29 下午09æ—¶20分11秒 GMT+08:00> <Error> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200015> <An error occurred in bridge "BillToEaiAckBridgeB1" during the transfer of messages (weblogic.transaction.RollbackException: SubCoordinator 'eaiServerB1+10.1.31.7:7011+eaiDomain+t3+' not available - with nested exception:
              [javax.transaction.SystemException: SubCoordinator 'eaiServerB1+10.1.31.7:7011+eaiDomain+t3+' not available]).>
              ####<2006-11-29 下午09æ—¶20分11秒 GMT+08:00> <Warning> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200026> <Bridge "BillToEaiAckBridgeB1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.bridge.internal.MessagingBridgeException.)>
              ####<2006-11-29 下午09æ—¶20分12秒 GMT+08:00> <Info> <MessagingBridge> <billeai2> <beSrvB1> <ExecuteThread: '14' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200020> <Bridge "BillToEaiAckBridgeB1" is stopped.>
              The logs told that the target destination is N/A,but didn't tell the detaild reason. Is there anybody who met this problem before and please give me a hand!!! thanks a lot!!

    the domains have to "trust" each other. Make sure to follow the instructions about the "enabled generated credential" in the following doc:
              http://edocs.bea.com/wls/docs81/ConsoleHelp/messaging_bridge.html#1122172

  • Problem using file based JNDI with JMS Bridge, WL 6.1sp3

              I am trying to connect an MQ queue to a Weblogic JMS queue using the JMS bridge,
              WLS6.1sp3. I have the CR081404_61sp3.jar and CR081511_61sp3.jar patches.
              I am having trouble getting the bridge to look up the MQ queue in the file based
              JNDI. According to the log it is trying to use a weblogic.jndi.WLInitialContextFactory
              instead of a com.sun.jndi.fscontext.RefFSContextFactory, which is what it is configured
              to use. I am getting the following error:
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
              Bridge" is getting the connections to the two adapters.>
              <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              RUNTIME! Bridge Provd Messaging Bridge In getConnections: isStopped = false>
              <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              RUNTIME! Bridge Provd Messaging Bridge Getting source connection: sourceConnSpec
              = weblogic.jms.adapter.JMSConnectionSpec@27166f>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
              Principal for Container Managed Security Context.>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
              Principal for Container Managed Security Context.>
              <Sep 29, 2002 12:16:22 PM EDT> <Warning> <Connector> << Weblogic Messaging Bridge
              Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException:
              ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest on createManagedConnection.>
              <Sep 29, 2002 12:16:22 PM EDT> <Error> <Connector> <Error granting connection
              request.>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
              Bridge" failed to connect to the source destination and will try again in 25 seconds.
              (javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
              ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest)>
              <
              The configuration of the bridge, printed out in the log, is:
              <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              STARTUP! Bridge Provd Messaging Bridge's source properties are:
              AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              Classpath=null
              ConnectionFactoryJNDIName = PMS.mqQcf
              ConnectionURL = file:/opt/mqm/java/mq-jndi
              InitialConnectionFactory = com.sun.jndi.fscontext.RefFSContextFactory
              DestinationType = Queue
              DestinationJNDIName = PMS.mqProvdRequest>
              <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              STARTUP! Bridge Provd Messaging Bridge's target properties are:
              AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              Classpath=null
              DestinationType = Queue>
              Am I correct in assuming it should be using the fscontext connection factory?
              Why is it using the weblogic one?
              Jason
              

    CR081511_61sp3.jar patch should fix the problem. Make sure that the
              jar file is picked up. It should be put before other weblogic jar files.
              You should be able to tell if it is picked up by looking at the first
              couple of lines of your server log file.
              Dongbo
              Jason Kriese wrote:
              >
              > I am trying to connect an MQ queue to a Weblogic JMS queue using the JMS bridge,
              > WLS6.1sp3. I have the CR081404_61sp3.jar and CR081511_61sp3.jar patches.
              >
              > I am having trouble getting the bridge to look up the MQ queue in the file based
              > JNDI. According to the log it is trying to use a weblogic.jndi.WLInitialContextFactory
              > instead of a com.sun.jndi.fscontext.RefFSContextFactory, which is what it is configured
              > to use. I am getting the following error:
              >
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
              > Bridge" is getting the connections to the two adapters.>
              > <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              > RUNTIME! Bridge Provd Messaging Bridge In getConnections: isStopped = false>
              > <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              > RUNTIME! Bridge Provd Messaging Bridge Getting source connection: sourceConnSpec
              > = weblogic.jms.adapter.JMSConnectionSpec@27166f>
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
              >
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
              > Principal for Container Managed Security Context.>
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
              >
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
              > Principal for Container Managed Security Context.>
              > <Sep 29, 2002 12:16:22 PM EDT> <Warning> <Connector> << Weblogic Messaging Bridge
              > Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException:
              > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              > url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest on createManagedConnection.>
              >
              > <Sep 29, 2002 12:16:22 PM EDT> <Error> <Connector> <Error granting connection
              > request.>
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
              > Bridge" failed to connect to the source destination and will try again in 25 seconds.
              > (javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
              > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              > url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest)>
              > <
              >
              > The configuration of the bridge, printed out in the log, is:
              >
              > <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              > STARTUP! Bridge Provd Messaging Bridge's source properties are:
              > AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              > Classpath=null
              > ConnectionFactoryJNDIName = PMS.mqQcf
              > ConnectionURL = file:/opt/mqm/java/mq-jndi
              > InitialConnectionFactory = com.sun.jndi.fscontext.RefFSContextFactory
              > DestinationType = Queue
              > DestinationJNDIName = PMS.mqProvdRequest>
              > <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              > STARTUP! Bridge Provd Messaging Bridge's target properties are:
              > AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              > Classpath=null
              > DestinationType = Queue>
              >
              > Am I correct in assuming it should be using the fscontext connection factory?
              > Why is it using the weblogic one?
              >
              > Jason
              

  • JMS Bridge not Working

    Hi,
    I have a weblogic 9.2 running one application.
    I what that application to post messages on a internal JMS queue. That message gets fw to a Weblogic 8 JMS queue.
    To achieve this I created a JMS Bridge with the Weblogic 8 destination, and the Weblogic 9 source.
    When i activate the bridge, i did not see anything on the logs, so i restarted the server.
    Once the server was Up I went to check how many consumers where register on my internal queue, and to my surprise there where none.
    I posted a message to that queue and still nothing. not even on the logs.
    On the source and destination, i put the following:
    Adapter JNDI Name: the XA one
    Classpath: weblogic.jar
    Connection URL: t3://172.16.76.28:8001 on the internal and t3://172.16.76.29:7001 on the external
    weblogic.jndi.WLInitialContextFactory: weblogic.jndi.WLInitialContextFactory
    and the JNDI stuff, user and password.
    I do not see anything in the logs. Any idea?

    I would like to make sure that I understand where you are now.
    1. The bridge is always running on 9.2.
    2. When the bridge is configured to forward messages from local (9.2) to remote (8.1), everything works.
    3. When the bridge is configured to forward messages from remote to local, you run into the SecurityException.
    Is my understanding correct? Where did you see the Exception (on the 9.2 side or the 8.1 side)?
    Are you always using the adapter from the same release as the server that is running the bridge?
    Assuming that you have configured everything correctly, I don't see why remote-to-local case does not work for you. There was an issue similar to what you are seeing in 8.1 GA, which has been fixed in 8.1SP1 and 9.2. You should not see this issue as long as your bridge is running on 9.2 (or 8.1SP1) or later.
    At this point you could try the following:
    1. Change the bridge to run in sync mode (by setting AsyncEnabled to false, the default is true) and see if the problem persists.
    2. Enable domain trust on both the 9.2 and 8.2 domains (see http://edocs.bea.com/wls/docs92/bridge/wls_interop.html#wp1126213 for details).
    3. Run the bridge on 8.1 (using the 8.1 adapter) to forward messages to 9.2. (I know the doc recommends that one should run the bridge on the later version of WebLogic when forwarding between two different releases, but it does not hurt to try as long as your source destination is on the same release are the bridge).
    Thanks,
    Dongbo

  • WLS JMS bridge not forwarding mesages

    Hi All,
    I want to send messages from a queue in the source weblogic domain to the target queue in another weblogic domain. Both the domains are weblogic server. On the source server agile PLM is deployed. For this communication I established JMS bridge and JMS destination on my source server. The resource adpater is deployed and active. But my bridge is not working. Is not forwarding message to the target queue on the target server.
    I inspected the log files. I found the following error
    "<BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://<target_server_ip>:<port>, user name = null) "> "
    Also on the monitoring tab of the JMS bridge initially it was showing message "Failed to look up the source adapter" then I deployed the resource adapter. Now on the monitoring tab its showing the message "Connected to the source" instead of shoing "Fowarding Messages" . can anyone tell me what could be the cause. Please help its really urgetnt!!!
    Can anyone please tell me what can be the issue?
    Thanks in Advance!!

    Could you please provide the way you used the connection factory?
    I am concerned about *(InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://<target_server_ip>:<port>, user name = null) "> "*
    Please check.
    Thanks,
    Jeets

  • JMS bridge communication not working

    Hi,
    I am working on an application, Ap1, which uses Toplink as an ORM layer and also makes use of Toplink cache. The problem is that the database that this application uses
    is also used by another app, Ap2. So I need somehow to refresh Toplink cache of Ap1 when a database update is triggered by Ap2, otherwhise Ap1 will work with out of date data.
    The solution that I found is to use JMS for the communication between the 2 aps and it should work like this:
    - when Ap2 make a database update, it will add a message in a JMS topic that a MDB deployed on Ap1 listens to. And so the MDB will remove the entity from the cache.
    The thing is that A1 and A2 are deployed on different Weblogic servers so I need to have a remote JMS communication between the 2 servers.
    Ap1 is deployed on WLS1 (Weblogic 12C).
    Ap2 is deployed on WLS2 (Weblogic 11C).
    As solutions I tried to use a JMS bridge.
    on the WLS1 side I have created:
    - a JMS server, JmsServer-0
    - a JMS module, JmsModule
    - a local topic included in JmsModule and targeted to JmsServer-0
    - a ConnectionFactory included in JmsModule and targeted to JmsServer-0 (not sure if it is needed)
    - a JMS bridge with source and target configured OK (Bridge is in Active state)
    The outcome is that when Ap2 updates the database, I can see the message in Ap2 JMS server, but I can't see it in Ap1 JMS server even if the JMS bridge appears to be created OK, has state Active.
    I don't know why the message doesn't reach A1 JMS server and I don't know how to debug this problem. I am looking in the Jms Server, monitorring tab. Is there any other place Where I can get some useful info?
    I also tried using a JMS foreign server, but I had the same problem.
    Thanks for any suggestion!

    First of all, you can configure the MDB on WLS server1 to receive messages from a JMS destination that is running on WLS server2. You just need to provide the URL of the remote server.
    If you prefer using the messaging bridge, you can debug your bridge by turning on the bridge debugging flags.
    -Dweblogic.Debug.DebugMessagingBridgeStartup=true
    -Dweblogic.Debug.DebugMessagingBridgeRuntime=true
    -Dweblogic.Debug.DebugMessagingBridgeRuntimeVerbose=true
    Hope this helps.
    Dongbo

  • JMS Bridge from WLS to OAS not working; automatic redirection to JMS Port

    We have setup a JMS Bridge inbetween Weblogic Server 10.3.0 and Oracle App Server 10.1.3. In our test environment it is working fine. But, in LIVE, we are facing a problem. Firewall is there inbetween OAS and WLS.
    1. OAS Admin port 6003, is blocked by firewall. So, from outside environment we can't connect to this port.
    2. OAS Port 12401 (RMI Port) is not-blocked
    3. OAS Port 12601 (JMS Port) is blocked by firewall
    4. We created credential "JMS_USER" while configuring QueueConnFactory at OAS end and used it while setting up WLS JMS Bridge
    We are using ormi://172.24.255.59:12401/default as Provider URL from Weblogic while creating JMS Bridge.
    Problem
    ========
    While connecting from WLS we are getting the following error from WLS end:
    javax.jms.JMSException: Unable to create a connection to "apgst366/172.24.255.59:12,601" as user "JMS_USER".
         at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1050)
         at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1130)
         at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:132)
         at com.evermind.server.jms.EvermindQueueConnection.<init>(EvermindQueueConnection.java:71)
    Question
    =========
    1) We are requesting for 12401; then why the JMS Port 12601 is being referred?
    2) Is there any automatic redirection from OAS end?
    3) Will unblocking the 12601 port by Firewall help?
    Please help me, as this has become a burning issue for us.
    Thanks in advance.

    Can anybody please help me?

  • When to use a JMS Bridge and when to use a Proxy

    Hi,
    We currently are running an OSB with most connections coming in via MQ to a JMS queue. We've been asked to implement a JMS Bridge.
    Wen using a messaging bridge to a foreign provider, the documentation recommends using the Foreign JMS option to simplify the creation of bridge destinations anyway.
    The key difference with using the bridge, is that you remove responsibility for the network transfer of messages from OSB's proxy and give it to the bridge. However, this now means that the messages are stored in WebLogic JMS with all the implications that brings. Is that really what you want? Isn't the whole point of MQ to be your reliable messaging service and not to use WebLogic JMS instead/as well?
    But the Solutions design team mention
    Without bridge
    MQ >--------Receive -------->---------Send ---------> JMS
    | ....... Transaction 1 ....| .....Transaction 2 ......|
    With bridge
    MQ >--------Receive -------->---------Send ---------> JMS
    | ....... ............Transaction 1 .......... ......|
    Is this true, so we have to use a bridge?

    I think your solution design team is wrong..
    MQ --> OSB Proxy Receive ---> OSB Proxy Send --> JMS will be a single XA transaction.
    An OSB proxy is preferred in this case for the following reasons:
    1. Don't use bridge for receiving messages . Bridge should be used rather for sending messages to non highly available remote messaing providers. Even for this case weblogic recommends SAF .
    2. Whatever the savings on transaction as mentioned by your design team doesn't appears to be correct.
    3. Weblogic messaging bridge appears to be a buggy product. You will have to apply a couple of patches to make the bridge to work as expected. It will take some time to stabilise it in a production environment. Weblogic's EJB container is much stable and with MDB's it would be less prone to bugs. This is from my personal experience. Others might have a different experience.
    4. You can leverage the out of box monitoring facilities provided by OSB. This can give you stats of how many messages were transferred between MQ and JMS, average & max response time etc.

  • AQ JMS Bridge in WebLogic 9.2

    I have configured a JMS Bridge that has source target as an AQ(which is referred to by a local weblogic jndi name - followed the robert patric framework) and the destination as a JMS queue. I can see the error logs prointed on the adminserver.logs when the bridge is started and the error is printed on and on.
    error log:
    ####<May 25, 2010 1:51:19 PM CDT> <Info> <MessagingBridge> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274813479568> <BEA-200033> <Bridge "AQ_2_JMS_WLBridge" is obtaining connections to the two adapters.>
    ####<May 25, 2010 1:51:19 PM CDT> <Trace> <eis/jms/WLSConnectionFactoryJNDIXA> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1274813479569> <000000> <<May 25, 2010 1:51:19 PM CDT> Info: AQ_2_JMS_WLBridge : Source connection created to AIA_OSM_OUT_QUEUE>
    ####<May 25, 2010 1:51:19 PM CDT> <Trace> <eis/jms/WLSConnectionFactoryJNDIXA> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1274813479613> <000000> <<May 25, 2010 1:51:19 PM CDT> Info: AQ_2_JMS_WLBridge : Connection started to AIA_OSM_OUT_QUEUE>
    ####<May 25, 2010 1:51:19 PM CDT> <Info> <Common> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274813479614> <BEA-000628> <Created "1" resources for pool "eis/jms/WLSConnectionFactoryJNDIXA", out of which "1" are available and "0" are unavailable.>
    ####<May 25, 2010 1:51:19 PM CDT> <Trace> <eis/jms/WLSConnectionFactoryJNDIXA> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1274813479615> <000000> <<May 25, 2010 1:51:19 PM CDT> Info: null : Target connection created to oracle.communications.ordermanagement.WebServiceQueue>
    ####<May 25, 2010 1:51:19 PM CDT> <Trace> <eis/jms/WLSConnectionFactoryJNDIXA> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1274813479617> <000000> <<May 25, 2010 1:51:19 PM CDT> Info: null : Connection started to oracle.communications.ordermanagement.WebServiceQueue>
    ####<May 25, 2010 1:51:19 PM CDT> <Info> <Common> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274813479618> <BEA-000628> <Created "1" resources for pool "eis/jms/WLSConnectionFactoryJNDIXA", out of which "1" are available and "0" are unavailable.>
    ####<May 25, 2010 1:51:19 PM CDT> <Info> <MessagingBridge> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274813479618> <BEA-200032> <Bridge "AQ_2_JMS_WLBridge" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.>
    ####<May 25, 2010 1:51:19 PM CDT> <Info> <MessagingBridge> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274813479618> <BEA-200030> <Bridge "AQ_2_JMS_WLBridge" is configured to work in "Exactly-once" mode, and it is actually working in "Exactly-once" mode.>
    ####<May 25, 2010 1:51:19 PM CDT> <Info> <MessagingBridge> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274813479618> <BEA-200028> <The bridge "AQ_2_JMS_WLBridge" has started transferring messages.>
    ####<May 25, 2010 1:51:19 PM CDT> <Trace> <eis/jms/WLSConnectionFactoryJNDIXA> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1274813479618> <000000> <<May 25, 2010 1:51:19 PM CDT> Error: AQ_2_JMS_WLBridge : Failed to create consumer AIA_OSM_OUT_QUEUE>
    ####<May 25, 2010 1:51:19 PM CDT> <Trace> <eis/jms/WLSConnectionFactoryJNDIXA> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1274813479619> <000000> <<May 25, 2010 1:51:19 PM CDT> Info: AQ_2_JMS_WLBridge : Connection closed to AIA_OSM_OUT_QUEUE>
    ####<May 25, 2010 1:51:19 PM CDT> <Warning> <MessagingBridge> <hostname_replaced> <osmdev03> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274813479619> <BEA-200026> <Bridge "AQ_2_JMS_WLBridge" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was javax.resource.ResourceException: Error setting message listener.)>
    ####<May 25, 2010 1:51:19 PM CDT> <Trace> <eis/jms/WLSConnectionFactoryJNDIXA> <hostname_replaced> <osmdev03> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1274813479621> <000000> <<May 25, 2010 1:51:19 PM CDT> Info: null : Connection closed to oracle.communications.ordermanagement.WebServiceQueue>
    ####<May 25, 2010 1:51:19 PM CDT> <Info> <MessagingBridge> <hostname_replaced> <osmdev03> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274813479621> <BEA-200020> <Bridge "AQ_2_JMS_WLBridge" is stopped.>
    Thanks
    Matt

    Hi Kapil,
              WebLogic JMS doesn't distinguish between "incoming" and "outgoing" queues - they're both application queues as far as WebLogic is concerned. Either queue can be paused/resumed.
              You might interesting in knowing that WL also supports pausing/resuming MDBs both administratively and automatically on failure. For information, see "Configuring Suspension of Message Delivery During JMS Resource Outages" in the MDB developer guide.
              Tom

  • Message Bridge Destination points to old IP, after failover with HA pair

    Hi
    Weblogic Version in use is 7.0sp7
    We have this Messaging Bridge configured, between two instances of Weblogic server (Each weblogic server exists on Different Weblogic domains)
    Both the weblogic servers run on the same machine.
    So we have configured the message bridge destination with localhost, instead of an IP or DNS name in it.. viz.
    t3://localhost:8001
    t3://localhost:8020 respectively
    where 8001 and 8020 are the listen ports of the respective weblogic servers.
    This machine is a HA pair, controlled by vcs cluster server.
    Which means when we failover from one node to another of the HA pair, the transition(which also involves the IP change from node A to node B) should be ideally transparent to weblogic.
    But when it comes to these messaging bridge destinations
    The Messaging bridge resolves the localhost in the Message Bridge destination to the old node IP, after the failover is done using vcs cluster server.
    To me it looks like weblogic is caching the IP details somewhere and probably reusing it, unaware of the fact that the IP of the machine has changed after the failover.
    I tried configuring the message bridge destination with addresses like t3://<DNSname>:8001 and 8020 respectively. But stiil it tries to connect to the IP of the old node only.
    I did come across this patch in Weblogic 7.0 sp5, which is pretty close to the issue that i am encountering..
    CR126201 In a multiple-server domain, if a Managed Server was rebooted to use a different address or port
    number, the JTA subsystem failed to update the address information. This would cause the
    following exception when the changed server was rebooted:
    javax.naming.CommunicationException. Root exception is
    java.net.ConnectException: t3://ip_address:port_number:
    Destination unreachable;
    nested exception is: java.net.ConnectException: Connection
    refused; No available router to destination
    Would really appreciate if someone can help with this issue.
    Regards
    Azad

    I'm not quite sure what the correct solution might be, but a possible work-around might be to hard-code the two addresses directly into the bridge URL. For example: t3://host:7010,host:7020. WebLogic will try each address in turn, starting from the first one until one succeeds or all fail.
    Another solution might be to configure an "external listen address" on each server. This is the address that "reconnectable" external clients (such as EJBs or a bridge ) will use for reconnect in place of the server's actual listen address.
    Tom

  • JMS Bridge in WL 8.1

    Like many other organizations, we too are in the process of planning a
              migration to WL 8.1. One of the major objectives is to throw away a lot of
              proprietary code and leverage the features available in WL 8.1. One of the
              many home grown tools we have as part of our WL 6.1 implementation is the
              JMS Bridge. The home grown JMS bridge is used to connect to MQ for sending
              events to our fulfillment engines in the legacy environments. Since the
              bridge is used extensively in several of our mission critical apps, I'd like
              to start with it and leverage the WL bridge that is known to smoothly
              integrate with MQ while offering high availability on the Enterprise.
              Now here's a set of challenges that I'd like to overcome with BEA's help.
              Our JMS bridge does some additional tasks like logging message context info
              to a message monitoring table, archiving messages to a file system and many
              more things. We'd love to see the WL JMS Bridge give us the ability to
              define callbacks like beforeReceive and afterReceive that we can define in
              our MDBs to do such tasks. These callbacks would be scoped within the same
              transaction that the onMessage participates in. I'm not sure if the EJB
              spec provides for that and is probably a question for the EBJ gurus (which
              is why I am posting this in the EJB forum as well). But from a JMS spec and
              BEA roadmap perspective, I'd like to know if there are any plans to give us
              this nice feature. If not, are there any technical challenges that would
              make this difficult to consider ?
              

              Adarsh Dattani wrote:
              > You mean intercepting the message as it is produced ? Sure, that might
              > work.
              > I am assuming, from an implementation standpoint the intercepts would work
              > like servlet filters.
              > Would these intercepts participate in the producer's transaction ?
              > Can the intercepts be hooked into the bridge as it produces to the remote
              > destination ?
              We are working in this area, but I'm not sure what the exact
              direction is. Please work through product management
              if you want to get into the details (as you are already doing).
              > Thanks Tom,
              > Adarsh
              >
              >
              > "Tom Barnes" <[email protected]> wrote in message
              > news:[email protected]...
              >
              >>Hi Adarsh,
              >>
              >>This is the first request we've had of this type, and such a feature
              >>would involve significant effort. As a thought, how about
              >>intercepting the produce rather than the receive?
              >>
              >>Tom
              >>
              >>
              >>Adarsh Dattani wrote:
              >>
              >>>Like many other organizations, we too are in the process of planning a
              >>>migration to WL 8.1. One of the major objectives is to throw away a
              >
              > lot of
              >
              >>>proprietary code and leverage the features available in WL 8.1. One of
              >
              > the
              >
              >>>many home grown tools we have as part of our WL 6.1 implementation is
              >
              > the
              >
              >>>JMS Bridge. The home grown JMS bridge is used to connect to MQ for
              >
              > sending
              >
              >>>events to our fulfillment engines in the legacy environments. Since the
              >>>bridge is used extensively in several of our mission critical apps, I'd
              >
              > like
              >
              >>>to start with it and leverage the WL bridge that is known to smoothly
              >>>integrate with MQ while offering high availability on the Enterprise.
              >>>Now here's a set of challenges that I'd like to overcome with BEA's
              >
              > help.
              >
              >>>Our JMS bridge does some additional tasks like logging message context
              >
              > info
              >
              >>>to a message monitoring table, archiving messages to a file system and
              >
              > many
              >
              >>>more things. We'd love to see the WL JMS Bridge give us the ability to
              >>>define callbacks like beforeReceive and afterReceive that we can define
              >
              > in
              >
              >>>our MDBs to do such tasks. These callbacks would be scoped within the
              >
              > same
              >
              >>>transaction that the onMessage participates in. I'm not sure if the EJB
              >>>spec provides for that and is probably a question for the EBJ gurus
              >
              > (which
              >
              >>>is why I am posting this in the EJB forum as well). But from a JMS spec
              >
              > and
              >
              >>>BEA roadmap perspective, I'd like to know if there are any plans to give
              >
              > us
              >
              >>>this nice feature. If not, are there any technical challenges that
              >
              > would
              >
              >>>make this difficult to consider ?
              >>>
              >>>
              >>
              >
              >
              

  • Problems in Sending Data through JMS Bridge - WLS 10.3 to WLS 11g

    I have a scenario where I need to send data from a queue configured on WLS 10.3 to WLS 11g. I am using OSB on WLS 10.3.
    What I have done is
    1. Created a JMS Based BS in OSB which sends data to jms://localhost:7001/ConnFactoryJNDI/QueueJNDI
    2. Created a JMS Bridge on WLS 10.3
    3. Source Destination has been configured as the one mentioned above.
    4. Target Destination has been configured to a queue on WLS 11g.
    When i execute the JMS Based BS in OSB, data is being written to the Source Queue directly. I am not sure of the JMS Bridge functionality but I assume that once data is written to the Source Destination, that data will be automatically pushed on the target destination.
    I have configured a JDBC store for the target queue but I no table is created with the data sent from the source.
    M i missing something here?

    I think this question belongs to weblogic server, but as far as I know bridge should be created always at higher version. means, you should create bridge at 11g and try to pull/drop data from 10g. To check any errors in bridge, check the server log and make sure status of bridge is "forwarding messages"
    Regards,
    Anuj

  • Foreign server or JMS Bridge?

    Weblogic 11g
    WebsphereMQ 7
    Good morning,
    I have a question regarding JMS architecture.
    We’re going to deploy a new app using JMS but all the messaging architecture will be on WebshereMQ.
    Our middleware team recommends us to create a foreign server to communicate with MQ.
    So my question is quite simple, why using a Foregin server instead of a JMS Bridge?
    I’d have used the latter as it aims to communicated with other Message Oriented Middleware.
    Thanks for your wise advices

    You can find more information about integrating with a remote or foreign JMS provider at
    http://docs.oracle.com/cd/E17904_01/web.1111/e13727/interop.htm#i1009767
    This doc discusses a number of approaches and best practices for each of them.
    The messaging bridge does introduce an extra hop; messages are put into a local destination and then forwarded to the final destination. This is useful when the remote destination is not highly available. The bridge will take the messages even when remote destination is not available and then forward them with build-in retry logic when the remote destination becomes available.
    If the remote destination is highly available, foreign JMS server is preferable since it directly access the final destination without an extra hop.
    Hope this helps.
    Dongbo

Maybe you are looking for