JMS bridge from Tibco to WLS 8.1(sp4) problems

We have a WLS that contains a MDB for receiving messages from another system. When messages are received on the Tibco topic and are try to be delivered to the WLS, we get the exception below.
          However, if we change the MDB to connect directly to the topic in the other WLS (the publisher), the message is received fine. Also, when using the Tibco bridge, if we use a simple command-line client to place a simple text-based message on the message topic, it is delivered to our server just fine.
          Is this an authentication related issue? If so, then why does it work when the WLS servers are linked directly, but not when Tibco server is being used as bridge between them?
          The publisher of the message is running on Linux, and the subscriber on Windows/XP. The Tibco server on Solaris and is v4.2.
          Thanks,
          Craig
          <Nov 1, 2005 4:11:02 PM MST> <Warning> <MessagingBridge> <BEA-200026> <Bridge "MyMessaging Bridge" 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 java.lang.Exception
          : javax.resource.ResourceException: Error sending message
          at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
          at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
          at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
          at $Proxy8.send(Unknown Source)
          at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
          at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
          at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
          at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
          at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
          at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
          at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
          -------------- Linked Exception ------------
          javax.resource.ResourceException: Error creating producer or sending message
          at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1339
          at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:719)
          at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
          at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:647)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
          at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:644)
          at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
          at $Proxy8.send(Unknown Source)
          at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1258)
          at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1181)
          at weblogic.jms.adapter.JMSBaseConnection$27.run(JMSBaseConnection.java:1943)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
          at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1939)
          at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:3567)
          at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1963)
          at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:3098)
          .)>

Similar Messages

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?

JMS Bridge from 10MP1 to 92MP3

My bridge is on a local server 10MP1, the bridge destination source is a queue on the same server and the target is on the 92MP3 one and also on the localhost.
I get the following issue:
<< eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">>
Everything is ok when i try from a 92MP3 to another 92MP3, from a 10MP1 to a 10MP1 and even from a 92MP3 to a 10MP1 (whith the bridge on the 92MP3)
Is anyone ever tried to make such a connection ?
thanks in advance for your help.

I found where was the problem, when creating a jms bridge with these two versions you must have different names for your jmsServer, your target managed server, you domain and as much as possible for all the resources implied in the bridge configuration.

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

JMS adapter could not receive message from Tibco EMS topic

I'm trying to consume message from tibco EMS topic using Oracle SOA JMS adapter. Can anyone please let me know the steps to do this. Appreciate your help.
Thanks,
SB

Increase Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..

Need help to connect tibco jms queues from OSB

Hi,
We have a requirement in our project "to connect tibco JMS Queues from OSB".
The Queres are created by some othes in remote system, they provided us the details to connect the Queue. the detail are:
Queue Name :EXT_WEALTHHUB.TO_EXT.SYNC.REQ
Jndi Factory :SSLQueueConnectionFactory
and hostName , PORT
Credentails are provided.
We entered the same details in Business service in transport page by choosing 'jms' as protocol and EndpointURI as.
"jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.REQ"
And we created a service account to maintain the credentials and browsed the same at service account in the business service.
In JMS Transport Page we selected
Response Queue : One for all Request URI's
Response Pattern : JMS CorrelaltionID
Response UI :jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.RESP
when we are trying to establish a connection with the above queue getting
javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: er.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
     at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
     at weblogic.jms.common.CDS$1.run(CDS.java:436)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: in.checkLoginSuccess(Login.java:131)
     at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:403)
     at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
     at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1777)
     at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1417)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:437)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:198)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl$2.run(MessageDrivenBeanInfoImpl.java:748)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.doPrivilagedAction(MessageDrivenBeanInfoImpl.java:2238)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
     at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
     at weblogic.jms.common.CDS$1.run(CDS.java:436)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:532)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:158)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentM
Any pointers on how to resolve the above issue will be a greate help to us.
Thanks in Advance

Wrong forum, please ask this on dedicated weblogic or soa forums

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

WLS JMS bridge not working

Hi All,
I have been looking for a solution for the last two days and this is my third post regarding JMS bridge. I configured ome JMS bridge which initially ,on the monitoring tab, was giving information "Failed to look uo 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 "Forwarding Messages" . can anyone tell me what could be thw cause. Please help its really urgetnt!!!

Can anybody please help me?

JMS Bridge is not starting up in Weblogic10

Hi,
I am new to Weblogic10 and I configured the JMS server and JMS bridge to send and receive the messages from MQ queues. When starting the weblogic server I am continuously getting error like,
<21-Mar-2009 07:24:08 o'clock GMT> <Error> <MessagingBridge> <blx25ao01> <aadev100-01> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1237620248164> <BEA-200044> <The following exception has occurred:
java.lang.AbstractMethodError: getTransactionSupport
at weblogic.jms.bridge.internal.MessagingBridge.startInternal(MessagingBridge.java:615)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1030)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
Could you please help me what is the route cause for the above exception.

Hi,
Please remove the UME inconsistencies as advised in note 818947.
Once done restart the server and JMS Provider service should start. Please update back regarding the result.
Thanks & Regards,
Vijith

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

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 Bridges not showing the right status

I am using the weblogic 9.2 MP3 on production servers with around 300 managed servers in 7 clusters. There are around 1200 queues and 2500 JMS bridges connecting the queues to internal and external world.
The JMS bridges on my system doesn't reflect the right status. Sometimes, it shows INACTIVE/Failed status but still keep forwarding the messages.
Different bridge status and description that I can see:
Inactive     Stopped by the administrator.
Active     Forwarding messages.
Inactive     WARN: failed to connect to the target.
Active     Connected to the source.
Also,
I see lots of warnings in the logs as follows...
####<5/03/2013 10:33:33 AM EST> <Warning> <MessagingBridge> <HOSTNAME> <MS NAME> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362440013003> <BEA-200026> <Bridge "BRIDGE NAME" 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.)>
<27/01/2013 05:52:07 AM EST> <Warning> <Connector> <BEA-190024> << eis/jms/WLSConnectionFactoryJNDIXA > Error making initial connections for pool. Reason: javax.resource.ResourceException: Adapter internal error -- connectionFactory object is not instanceof ConnectionFactory>
Any help on the issue will be appreciated...
Thanks

what does emctl status dbconsole show?
Hi All,
I have installed 10g in Win 2000. Enterprise manager
was working fine after installation. I restarted the
Oracle Service (DB Service, TNS, iSQL, DBControl)
from services in Control Panel. Database is up and
working fine but the Enterprise Manager is not
working. When I am trying to use the EM through
Internet Explorer, it is not asking for any login and
showing as database as down. I am able to connect to
DB from client PC. Please advice.

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

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

JMS bridge from Tibco to WLS 8.1(sp4) problems

Similar Messages

Maybe you are looking for