Unable to create a JMS Message bridge between Weblogic 12c and Weblogic 8.1

Hi,
I am unable to successfully create a Message Bridge between Weblogic 12.1.1.0 and Weblogic 8.1. The error message being received is:
eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://localhost:8001, user name = System) ">
The error on the monitoring tab is WARN: failed to connect to target.
Both domains are deployed on one box for testing purposes. The bridge itself is deployed on Weblogic 12c. The areas of config that may be of interest are:
<server>
<name>AdminServer</name>
<listen-address></listen-address>
</server>
<messaging-bridge>
<name>Bridge</name>
<target>AdminServer</target>
<source-destination>JMSBridgeSource12c</source-destination>
<target-destination>JMSBridgeTarget81</target-destination>
<selector>Test</selector>
<quality-of-service>Exactly-once</quality-of-service>
<qos-degradation-allowed>false</qos-degradation-allowed>
<durability-enabled>true</durability-enabled>
<idle-time-maximum>60</idle-time-maximum>
<async-enabled>true</async-enabled>
<started>true</started>
<preserve-msg-property>false</preserve-msg-property>
</messaging-bridge>
<app-deployment>
<name>jms-xa-adp</name>
<target>AdminServer</target>
<module-type>rar</module-type>
<source-path>D:\ORACLE~3\WLSERV~1.1\server\lib\jms-xa-adp.rar</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<jms-bridge-destination>
<name>JMSBridgeSource12c</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
<user-name>System</user-name>
<user-password-encrypted>{AES}nfFzhs+0J/O2Cenf0g4zDsDyvIKENMF7cZ5sAVUehX0=</user-password-encrypted>
<classpath></classpath>
<connection-factory-jndi-name>JMSConnectionFactory12c</connection-factory-jndi-name>
<connection-url>t3://localhost:7001</connection-url>
<destination-jndi-name>JMSQueue12c</destination-jndi-name>
</jms-bridge-destination>
<jms-bridge-destination>
<name>JMSBridgeTarget81</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
<user-name>System</user-name>
<user-password-encrypted>{AES}eBkO46cHvtrzEraOMIOdXow6WvEAtA4NCUDTQ4mC+9w=</user-password-encrypted>
<classpath></classpath>
<connection-factory-jndi-name>JMSConnectionFactory81</connection-factory-jndi-name>
<connection-url>t3://localhost:8001</connection-url>
<destination-jndi-name>JMSQueue81</destination-jndi-name>
</jms-bridge-destination>
I have enforced global trust between the two domains. I have disabled the guest user on the 8.1 domain but can’t see where to do this on 12c.
Any suggestions would be much appreciated.
Regards
John
Edited by: 958336 on 13-Sep-2012 03:11

Thanks for the recommendation. Unfortunately it did not help solve the problem.
I have managed to get a JMS bridge working between 12c and 8.1 by including the 8.1 weblogic.jar on the classpath. This setup was using eis.jms.WLSConnectionFactoryJNDINoTX.
After trying to use the adapter that supports transactions, WLSConnectionFactoryJNDIXA I received the following error:
java.lang.IllegalStateException: can only be called from server
Is this because the Weblogic 12c server now views the 8.1 server as being foreign?

Similar Messages

  • MQ 6 WLS 9.2 JMS Message Bridge Error

    I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2 collocated on the same server following the BEA example:
              1.Create local queue on MQ
              2.Bind queue using JMSAdmin
              3.Create JMS bridge betwen a source destination using JNDI name in #2 and a local WLS queue.
              Here is the WLS config:
              <messaging-bridge>
              <name>MQ-WLSBridge</name>
              <target>adminServer</target>
              <source-destination>MQ-WLSSource</source-destination>
              <target-destination>MQ-WLSTarget</target-destination>
              <selector></selector>
              <quality-of-service>Exactly-once</quality-of-service>
              <qos-degradation-allowed>true</qos-degradation-allowed>
              <durability-enabled>true</durability-enabled>
              <idle-time-maximum>60</idle-time-maximum>
              <async-enabled>true</async-enabled>
              <started>true</started>
              <preserve-msg-property>false</preserve-msg-property>
              </messaging-bridge>
              <jms-bridge-destination>
              <name>MQ-WLSTarget</name>
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              <classpath></classpath>
              <connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
              <connection-url>t3://localhost:7005</connection-url>
                   <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
              </jms-bridge-destination>
              <jms-bridge-destination>
              <name>MQ-WLSSource</name>
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              <classpath></classpath>
              <connection-factory-jndi-name>QCF</connection-factory-jndi-name>
              <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
              <connection-url>file:///usr/mqm/java/jndi</connection-url>
              <destination-jndi-name>MQMessageQueus</destination-jndi-name>
              </jms-bridge-destination>
              I used a standalone JMS client and was able to connect to the MQ queue using the above JNDI name, factory so the MQ side was set up properly.
              When I start up WLS, I saw that
              <The messaging bridge "MQ-WLSBridge" has been successfully deployed.>
              and the exception:
              <MessagingBridge> <BEA-200042> <Bridge MQ-WLSBridge failed to connect to the source destination and will try again in 20 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: Failed to start the connection
                   at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1458)
                   at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1438)
                   at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:403)
                   at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:242)
                   at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
                   at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
                   at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
                   at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1057)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:346)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:277)
                   at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:606)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:271)
                   at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
                   at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
                   at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
                   at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:92)
                   at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:809)
                   at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1042)
                   at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
                   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
                   at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
              )>
              There is no error in the MQ logs. What is the problem?
              CS

    C S <> wrote:
              > I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2
              > collocated on the same server following the BEA example: 1.Create local
              > queue on MQ 2.Bind queue using JMSAdmin
              > 3.Create JMS bridge betwen a source destination using JNDI name in #2 and
              > a local WLS queue.
              >
              > Here is the WLS config:
              > <messaging-bridge>
              > <name>MQ-WLSBridge</name>
              > <target>adminServer</target>
              > <source-destination>MQ-WLSSource</source-destination>
              > <target-destination>MQ-WLSTarget</target-destination>
              > <selector></selector>
              > <quality-of-service>Exactly-once</quality-of-service>
              > <qos-degradation-allowed>true</qos-degradation-allowed>
              > <durability-enabled>true</durability-enabled>
              > <idle-time-maximum>60</idle-time-maximum>
              > <async-enabled>true</async-enabled>
              > <started>true</started>
              > <preserve-msg-property>false</preserve-msg-property>
              > </messaging-bridge>
              >
              > <jms-bridge-destination>
              > <name>MQ-WLSTarget</name>
              >
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              > <classpath></classpath>
              >
              <connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
              > <connection-url>t3://localhost:7005</connection-url>
              > <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
              > </jms-bridge-destination>
              > <jms-bridge-destination>
              > <name>MQ-WLSSource</name>
              >
              Hello,
              First of all, your classpath doesn't seem to be correct. You need to add the
              MQ jars in the bridge classpath. (DONT use the server classpath for
              this!!!)
              Secondly, enable debugging in Weblogic, which will give you some
              information: -Dweblogic.Debug.DebugMessagingBridgeStartup=true -Dweblogic.Debug.DebugMessagingBridgeRuntime=true -Dweblogic.Debug.DebugMessagingBridgeRuntimeVerbose=true
              IF you have more questions, pls reply also be mail.
              Bart
              Schelstraete Bart
              [email protected]
              http://www.schelstraete.org
              http://www.linkedin.com/in/bschelst

  • Message bridge between two instances

    I am trying to setup messaging bridge between two instances of weblogic server.
    Can the second instance belong to a different domain? If yes how to configure it?

    Yes, you can configure a messaging bridge to work between two WebLogic domains.
    The general instructions of configuring a message bridge, including the bridge instance itself, the bridge destinations and the adapter, can be found at
    http://edocs.bea.com/wls/docs103/bridge/basics.html#wp1168461
    The only extra thing that you may need to take care of for the cross-domain case is to configure cross-domain security as instructed at
    http://edocs.bea.com/wls/docs103/bridge/wls_interop.html#wp1126873
    Regards,
    Dongbo

  • Messaging Bridge Between 2 Weblogic Server

              Hi,
              I would like to create a messaging bridge between two Weblogic Server on two different
              server. One on Windows NT and one on Solaris.
              I have created one queue on NT and one other queue on Solaris, and the corresponding
              JMS Bridge destination for each queue on one server (and the other to test).
              And on one server (and the other to test), I have created a messaging bridge to
              transfert messages from one queue to the other, but I have a message on the Weblogic
              Server.
              javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
              ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              url = http://usv9007.rtc.ch:7001, user name = null, password = null
              at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
              at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
              at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
              at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
              at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
              at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
              at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
              request.>
              Parameter for the distant queue
              Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
              ressources for the ConnectionFactory and the corresponding adapter)
              Connection URL : http://SolarisIP:7001
              InitialContextFactory : weblogic.jndi.WLInitialContextFactory
              ConnectionFactory JNDI Name : myConnectionFactory
              Destination JNDI Name : myQueueSolaris
              Destination Type : Queue
              I don't understand why I have this error, because all the parameters are correct,
              and the http tunneling is activated.
              Could you help me to configure correctly this messaging bridge ???
              Thanks a lot.
              

    Looks like the error occurred on the target destination
              of the bridge. One way to find out if your configuration
              is correct is to use the same parameters (initial context factory,
              url, username and password) to get a connection to the
              target server from a standalone client.
              Dongbo
              Seb wrote:
              >
              > Hi,
              >
              > I would like to create a messaging bridge between two Weblogic Server on two different
              > server. One on Windows NT and one on Solaris.
              >
              > I have created one queue on NT and one other queue on Solaris, and the corresponding
              > JMS Bridge destination for each queue on one server (and the other to test).
              >
              > And on one server (and the other to test), I have created a messaging bridge to
              > transfert messages from one queue to the other, but I have a message on the Weblogic
              > Server.
              >
              > -----------------------------------------------------------------
              > javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
              > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              > url = http://usv9007.rtc.ch:7001, user name = null, password = null
              > at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
              > at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
              > at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
              > at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
              > at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
              > at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
              > at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              > <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
              > request.>
              > -----------------------------------------------------------------
              >
              > Parameter for the distant queue
              >
              > Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
              > ressources for the ConnectionFactory and the corresponding adapter)
              > Connection URL : http://SolarisIP:7001
              > InitialContextFactory : weblogic.jndi.WLInitialContextFactory
              > ConnectionFactory JNDI Name : myConnectionFactory
              > Destination JNDI Name : myQueueSolaris
              > Destination Type : Queue
              >
              > I don't understand why I have this error, because all the parameters are correct,
              > and the http tunneling is activated.
              >
              > Could you help me to configure correctly this messaging bridge ???
              >
              > Thanks a lot.
              

  • When opening Bridge (CS6) I get the following message: "Bridge encountered a problem and is unable to read the cache. Please try purging the central cache in Cache Preferences to correct the situation" I tried and after selecting purge cache it does not a

    When opening Bridge (CS6) I get the following message: "Bridge encountered a problem and is unable to read the cache. Please try purging the central cache in Cache Preferences to correct the situation" I tried and after selecting purge cache it does not allow me to select OK. Also Bridge keeps saying "Building Criteria" with the spinning wheel and nothing happens. I tried uninstalling and reinstalling to no avail. Please help:)

    Maybe a Preferences reset can help:
    Numerous program settings are stored in the Adobe Bridge preferences file, including display, Adobe Photo Downloader, performance, and file-handling options.
    Restoring preferences returns settings to their defaults and can often correct unusual application behavior.
    Press and hold the Ctrl key (Windows) or the Option key (Mac OS) while starting Adobe Bridge.  
    In the Reset Settings dialog box, select one or more of the following options:  
      Reset Preferences 
    Returns preferences to their factory defaults. Some labels and ratings may be lost. Adobe Bridge creates a new preferences file when it starts.
    Purge Entire Thumbnail Cache
    Purging the thumbnail cache can help if Adobe Bridge is not displaying thumbnails properly. Adobe Bridge re-creates the thumbnail cache when it starts.
    Reset Standard Workspaces
    Returns Adobe predefined workspaces to their factory default configurations.
    Click OK, or click Cancel to open Adobe Bridge without resetting preferences.   

  • When opening Bridge I get this message: Bridge encountered a problem and is unable to read the cache. Please try purging the central cache in the cache preferences to correct the situation. I have tried this and still get this message. when I delete image

    When opening Bridge I get this message: Bridge encountered a problem and is unable to read the cash. Please try purging the central cache in the cache preferences to correct this problem. I did this and still get this same message.Also now when deleting images they don't delete till I close and reopen Bridge. What can i do to fix this problem?

    Maybe a Preferences reset can help:
    Numerous program settings are stored in the Adobe Bridge preferences file, including display, Adobe Photo Downloader, performance, and file-handling options.
    Restoring preferences returns settings to their defaults and can often correct unusual application behavior.
    Press and hold the Ctrl key (Windows) or the Option key (Mac OS) while starting Adobe Bridge.  
    In the Reset Settings dialog box, select one or more of the following options:  
      Reset Preferences 
    Returns preferences to their factory defaults. Some labels and ratings may be lost. Adobe Bridge creates a new preferences file when it starts.
    Purge Entire Thumbnail Cache
    Purging the thumbnail cache can help if Adobe Bridge is not displaying thumbnails properly. Adobe Bridge re-creates the thumbnail cache when it starts.
    Reset Standard Workspaces
    Returns Adobe predefined workspaces to their factory default configurations.
    Click OK, or click Cancel to open Adobe Bridge without resetting preferences.   

  • JMS Message Bridge - WLS to MQ

    Hi,
    Subsequent to my last posts on Foreign JMS Server setup (where I had to receive a msg from a remote MQ Queue), now I have a requirement to post messages to an remote MQ Queue for a diff application.
    As a POC, I configured the JMS Message Bridge with bridge source as my local JMS queue and bridge destination as the Remote MQ Queue and it works fine as expected !!
    just have couple of questions on that -
    1. For a long time, I was struggling with this error on server startup
    <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
    Then I realized from the server log that the actual reason was authentication failure in MQ Queue Manager :
    JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager '' with connection mode 'Client' and host name '77.40.190.130'. Please check if the supplied username and password are correct on the QueueManager you are connecting to AND
    JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
    Since this MQ setup is managed by someone else, when they pass on the .binding file after creating queuemanager, queue, etc, Should I also ask them for the username and password for the QM?? I am not sure if this is a part of the .binding file.
    2. Some doubts around the QOS. As I understood, I am using the No-Transaction Adapter. This means I can use QOS as either "Atmost once" or "Duplicate OK". The latter seems to be ok so that I dont lost messages in any case. But I am yet to find out if the other application is ok to handle duplicates.
    But is there a restriction/limitation to use "Exactly Once" ?? I noticed that there is also an XA-Transaction Adapter in WLS. Is it not possible to use that with MQ?
    Thanks in advance.
    best regards,
    Murali

    In your binding file QCF or XAQCF definition , you will see a Channel field since you are using a client mode to connect to the queue manager. This channel is called a Server Connection Channel [ SVRCONN]. At the queue manager side of things, when this SVRCONN is defined, MQ Admin teams tend to define an attribute called MCAUSER. In this setup the userid used for authorisation at queue manager is the following in the below precedence:
    1. If MCAUSER is defined in the channel, that will be the user id and it overrides any security context sent from client application. This user id should have sufficient permissions to connect to queue manager , get , put. The MQ admin teams on certain platforms will be able to get the exact permission that is missed from the queue manager error logs when a 2035 security exception occurs.
    2. If no MCAUSER is defined then the userid passed in the createConnection JMS call will be the user context used.
    I am not exactly sure of the behaviour when no MCAUSER and no user id in createConnection calls, but i think it takes the user of the MQ Listener process which starts the SVRCONN channel instance when a client initiates the connection.
    So for your situation, it will be worth start checking with how the MQ side configuration is. This issue tends to be a very common issue with client applns connecting to qmgr.

  • Significance of async-enabled option of jms-messaging-bridge

    Hi Folks !!
    I have a question regarding JMS-MESSAGING-BRIDGES:
    What difference will async-enabled = true | false will make to the bridge? Which option will be good from performance point of view ?
    Thanks in advance.
    Edited by: 994778 on Mar 19, 2013 7:05 AM

    As you know, the bridge acts as a receiver from the source destination and a sender to the target destination. When async-enabled is set to true, the bridge works as an asynchronous listener to the source destination, while otherwise it acts as a synchronous receiver. In other words, the former is a push mode and the latter is a poll mode. The sync mode does batching while async mode does not. There are a couple of things that you need to consider while determining which mode is better, such as the desired QOS of the bridge, and whether you are bridging between wls destinations or a WLS destination to/from a 3rd party destination. For example, if you requires exactly-once QOS and your source destination is not a WLS JMS destination, you have to use sync mode; actually the bridge internally will switch to sync mode even if you set it to async mode.
    You can find the tuning guide for the messaging bridge at
    http://docs.oracle.com/cd/E17904_01/web.1111/e13814/bridgetuning.htm#g1153237
    Regards,
    Dongbo

  • JMS Messaging Bridge ( communication across domains)

    Following is the Scenario
    We have 2 Weblogic domains, Domain A ( running on port 2000) and Domain B (running on port 3000)
    In Domain A I want to look up a Queue which is in Domain B and send a message on that that Queue.
    So the requirement is to send message from one domain to other domain ( i.e sending message across domains )
    I have read on forum that this is possible using JMS Messaging Bridge.Can any body please guide me or provide some sample code for this.
    Thanks in advance.
    Regards
    ~Yogesh

    Hi
    You can define the same queue in both domains.
    In domain A ( the source ) create the Origin of bridge
    In domain A too ( the source) create the destination of bridge ( pointing to address and port of domain B)
    In domain A create the bridge ( joining source and destination )
    In domain A , deploy the connector ... a .rar file
    Best Regards
    Jin
    PD: this doesn?t affect the code of your app.

  • Using JMS Messaging Bridge in BPEL

    Hi
    I wanted to create a bpel process to put a message on to a JBoss queue on an external system.
    I could see from many forums that JMS Messaging bridge is a suitable option to go ahead. I could create new JMS destinatiosn and a JMS bridge on top of that.
    Can some once help me out with a sample bpel process inidcating how to use the JMS bridge within the bpel prpcess.
    Thanks in advance

    Hi
    You can define the same queue in both domains.
    In domain A ( the source ) create the Origin of bridge
    In domain A too ( the source) create the destination of bridge ( pointing to address and port of domain B)
    In domain A create the bridge ( joining source and destination )
    In domain A , deploy the connector ... a .rar file
    Best Regards
    Jin
    PD: this doesn?t affect the code of your app.

  • JMS Messaging Bridge Problems with WLS 8.1 sp2

              Thank you in advance for your help.
              I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
              Q. I have this working wonderfully in an environment without clustering but once
              I try to deploy to a cluster, I am having two major problems.
              1) When the managed servers are restarted, the messaging bridges immediately complain
              about not being able to find the resource adaptor. After I manually un-target
              the messaging bridge from the cluster and re-target them, they find the resource
              adaptor but cannot connect to the source... which leads to my next problem.
              2) The messaging bridges cannot connect to the source destination whether it is
              an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
              see relative:
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
              Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
              Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
              Bridge.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
              is deployed as a migratable.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
              Bridge as a migratable.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
              source configurations are:
              AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              Classpath=null
              ConnectionURL = file:/e:/private/JNDI/eBusDev02
              DestinationType = Queue
              DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
              InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
              ConnectionFactoryJNDIName = jms.oes.MQ-QCF
              .>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
              target configurations are:
              AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              Classpath=null
              ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
              DestinationType = Queue
              DestinationJNDIName = jms/oes/ADV-REPLYQ
              InitialContextFactory = weblogic.jndi.WLInitialContextFactory
              ConnectionFactoryJNDIName = jms/oes/QCF
              .>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
              is successfully initialized.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
              has been successfully initialized as a migratable.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
              Bridge.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
              has been successfully activated..>
              ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
              <Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
              two adapters.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
              Getting source connection.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
              <Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
              and will try again in 15 seconds. (java.lang.NullPointerException)>
              I know the queues are up and I am pretty sure my MQ client configuration is correct.
              Is there anyway to get more information about the NullPointerException or the
              error being encountered?
              

    Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
              If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
              Tom

  • My bridge is not working normally and keep given me this message : bridge encountered a problem and is unable to read the cache . Please try purging the central cache in cache preferences to correct the situation

    My bridge is not working normally and keep given me this message : bridge encountered a problem and is unable to read the cache . Please try purging the central cache in cache preferences to correct the situation

    And did you then actually purge the cache?
    Please realize that you have given ZERO details.
    BOILERPLATE TEXT:
    Note that this is boilerplate text.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    etc.,
    someone may be able to help you (not necessarily this poster, who is not a Windows user).
    a screen shot of your settings or of the image could be very helpful too.
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

  • Unable to create a new Message  Layout : 500 attempts failed.

    I am getting this error " Unable to create a new Message Layout : 500 attempts failed." when I am trying to add my custom region to seeded Message Layout.

    Is that all the error message you are getting or java error stack is also there? It looks like a custom message as I couldn't find it in fnd messages. DO you have any other custom code on this page or is this a custom page?
    --Shiv                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • HELP with JMS message bridge to MSMQ

              Can anyone offer suggestions on how to obtain/build a JMS messaging bridge to MSMQ.
              I see that WL has a Messaging Bridge but only for certain foreign messaging systems.
              FioranoMQ have a JMS Implementation with a bridge to MSMQ but a complete JMS implementation
              seems overkill and is costly.
              We already have Weblogic's JMS implementation & just want messages to appear on
              a JMS Queue when they are put in a MSMQ queue. A message driven bean will then
              trigger from the JMS queue.
              

    It is rare to hear of MSMQ when it comes to messaging.
              (I guess MSMQ users typically stay in MS world?)
              I suggest building a minimal subset JMS wrapper. Customers
              have had success with this approach with other queuing products.
              If you can implement asynchronous (onMessage) then the same
              wrapper can be used to plug into MDBs as well as into the bridge.
              You might find that there already is open source
              for these wrappers, search the web.
              Take note that interop is what web-services is supposed
              to be all about. You might want to investigate writing
              an MSMQ app that in turn invokes a WebLogic web-service
              that finally enqueues to a WL queue.
              Another possibility is to write an MSMQ app that invokes
              WebLogic's JMS C client to put messages into a JMS
              queue. The JMS C client is due out
              shortly, perhaps this week, perhaps within the next
              few weeks. It will be posted to dev2dev and work
              with 7.0.
              Tom, BEA
              Pete wrote:
              > Can anyone offer suggestions on how to obtain/build a JMS messaging bridge to MSMQ.
              > I see that WL has a Messaging Bridge but only for certain foreign messaging systems.
              >
              >
              > FioranoMQ have a JMS Implementation with a bridge to MSMQ but a complete JMS implementation
              > seems overkill and is costly.
              >
              > We already have Weblogic's JMS implementation & just want messages to appear on
              > a JMS Queue when they are put in a MSMQ queue. A message driven bean will then
              > trigger from the JMS queue.
              

  • Getting error Unable to create a new Message Layout: 500 attempts failed.

    Dear All,
    I am trying to add Form Value item to the Message Component Layout region through personalization.
    I am getting error Unable to create a new Message Layout: 500 attempts failed.
    While I am able to add Message Text Input, Message Lov Input items without any issue.
    Same issue will appear if I add stack layout region.
    The requirement is to add two hidden field to a Oracle supplied Message Component Layout Region( Page /oracle/apps/pa/finplan/webui/UpdateForecastLinePG
    region UpdateResourceAssignmentRN.FinSumFieldsRN)
    Please help me any work around or solution.
    Regards
    Devender Yadav

    Hi Sun,
    Thanks for reply.
    I am just trying to add Form Value item not the Message Layout Bean.
    Jdeveloper is allowing to add the messageLayout bean to messageComponentLayout (I have just tested it). It means OA Framework is facilitating it, it is the personalization Framework which may have restriction.
    Regards
    Devender Yadav

Maybe you are looking for

  • New to mac, help!!

    Hey Ive been trying to set up my ichat. I appear to have an account called bonjour, i dont know where it came from, im assuming my mac did it automatically (im completely new to macs!). However, it wont let me add buddies. The whole buddy tab is in g

  • W540 Announced Today

    From http://www.cnbc.com/id/101024541 ThinkPad W540: Lenovo's Most Powerful and Mobile Workstation Ever Featuring the best ThinkPad display ever, the 15.5 inch 3K IPS panel, the W540 answers the demand for a portable, independent software vendor (ISV

  • Recording midi music as a WAV f

    For years I've been using a Soundblaster card and the software I got with it (Midi Orchestrator). Making WAV files, and putting them onto a CD was a simple matter. I recently bought a new computer with Windows XP and on-board sound. I was delighted t

  • Sky+ Anytime and Time Capsule as wireless connector

    Good morning ladies and gentlemen.  I was hoping one of you forumites could help me with an 'idiots guide' to set up a Time capsule to act as wireless connector for my sky+ HD box - if its possible.  I cant seem to find anything to help me anywhere e

  • Audiobook and Games not showing up

    My wife's G4 cube has the latest version of OSX and ITunes but the audiobook and Ipod games categories do not show up under the library like they do on my ibook. Why is that?