| Author |
Message
|
| mrk |
 Posted: Mon Sep 22, 2008 10:01 am Post subject: Unable to connect MQ Serever from Weblogic server |
 |
|
Novice
Joined: 09 Aug 2007
Posts: 17
|
Hi,
I am very new to weblogic server. But I need to connect to MQserver to get the message.
I am getting below error in weblogic logs.
<BEA-200043> <Bridge "Bridge-xxx" failed to connect to the target destination and will try again in 60 seconds. This could be a temporary condition unless the messages repeat several times
The destination is MQserver.
Could any one help tell me out, what exactly the error telling?
Thanks. |
|
| Back to top |
|
 |
| atheek |
| Posted: Mon Sep 22, 2008 10:33 am Post subject: Re: Unable to connect MQ Serever from Weblogic server |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
| mrk wrote: |
<BEA-200043> <Bridge "Bridge-xxx" failed to connect to the target destination and will try again in 60 seconds. |
Check the target bridge destination. Ensure its up and running and also you have configured a valid target. Look into the stacktrace to get to know why exactly the bridge failed to connect |
|
| Back to top |
|
|
| mrk |
| Posted: Mon Sep 22, 2008 10:44 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007
Posts: 17
|
| Could you please tell me the location of stacktrace |
|
| Back to top |
|
|
| atheek |
| Posted: Mon Sep 22, 2008 10:50 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
| Look into your server logs... |
|
| Back to top |
|
|
| atheek |
| Posted: Mon Sep 22, 2008 10:56 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
Check...
1. The queue manager to which you are connecting is up and running
2. The JNDI names for Target Bridge destination and Connection Factory
is valid
3. If you have used foreign jms to connect to MQ ensure that you have configured the correct details in the jmsadmin setup
4. If you are connecting to MQ in client mode, ensure that a listener is running at the port you have specified in the Connection Factory
5. Check your server/domain logs to get to know more about the reason of failure |
|
| Back to top |
|
|
| mrk |
| Posted: Mon Sep 22, 2008 11:17 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007
Posts: 17
|
Thank you very much for your information.
I will check and let u know if i found any errors.
Thank you. |
|
| Back to top |
|
|
| mrk |
| Posted: Mon Sep 22, 2008 11:22 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007
Posts: 17
|
still i am getting below error in weblogic serer log
2-Sep-2008 20:11:30 o'clock BST> <Debug> <MessagingBridgeRuntime> <BEA-000000> <Bridge Bridge-test Getting target connection>
<22-Sep-2008 20:11:30 o'clock BST> <Info> <MessagingBridge> <BEA-200043> <Bridge "Bridge-test" failed to connect to the target destination and will try again in 60 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: weblogic.jms.bridge.TemporaryResourceException
at weblogic.jms.adapter.JMSBaseConnection.throwTempResourceException(JMSBaseConnection.java:1443)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:391)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:238)
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:1073)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:354)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:302)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:285)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:607)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:279)
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.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
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) |
|
| Back to top |
|
|
| atheek |
| Posted: Mon Sep 22, 2008 11:26 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
| Is this the only exception you are getting in your server logs? Could you see some mq reason codes in the exception? |
|
| Back to top |
|
|
| mrk |
| Posted: Mon Sep 22, 2008 11:29 am Post subject: |
|
|
Novice
Joined: 09 Aug 2007
Posts: 17
|
I am only getting above exception continiously in server log.
Could you pls tell me what is this error.
Why i am not able to connect target distination.
Thank you.. |
|
| Back to top |
|
|
| atheek |
| Posted: Mon Sep 22, 2008 11:45 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
Can't help with this info. You need to enable debugging for the message bridge to capture why exactly its failing
From weblogic FAQ:
| Quote: |
How do I enable debugging for the messaging bridge?
A. You can enable debugging for the messaging bridge using either of the followings methods:
Add the following lines to your WebLogic start script (before the weblogic.Server line):
-Dweblogic.Debug.DebugMessagingBridgeStartup=true
-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
Add the following statements to the ServerDebug entry in your configuration file (config.xml) for the server that the messaging bridge is running on:
DebugMessagingBridgeStartup="true"
DebugMessagingBridgeRuntime="true"
Once debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default. However, if you want them to appear in the Administration Console, add "DumpToConsole" to the statements show above. For example:
-Dweblogic.Debug.DebugMessagingBridgeStartupDumpToConsole=true |
|
|
| Back to top |
|
|
|
|
