Messaging Bridge status using WLST

Hi,
I am trying to build a WLST script which tells the state of n number of messaging bridges that I have on AdminServer.
connect('uname','pswd','t3://localhost:7001');
serverRuntime();
bd= cmo.getMessagingBridgeRuntime();
print bd.getName()
print bd.getState();
I am having issues in finding the mbean instance, error is as follows
AttributeError: getMessagingBridgeRuntime
would be of great help if you already have this script which is working or help me in solving this.
I am using weblogic 10.3.1

It can be done using weblogic.Admin utility, below is the script...you can modify this according to requirement...
java weblogic.Admin -url t3://$admURL -username weblogic -password $admpasswd GET -pretty -type MessagingBridgeRuntime -mbean $domain:ServerRuntime=$mserver,Name=$bridge,Type=MessagingBridgeRuntime,Location=$mserver -property Description -property Name -property State | grep -v MBeanName

Similar Messages

How to monitor Message Bridge runtime using WLST

Hi Readers,
I would like to monitor Message Bridge runtime on weblogic 8.1 using WLST script.
Can anybody tell if there is any possibility? Is there a MBEAN avaialble for Messaging Bridge.?
Edited by: user13254842 on 09-Sep-2010 23:17

Hi,
I don't recall whether the console provides a way to monitor the bridge, or whether the MessagingBridgeRuntimeMBean hangs off of some parent mbean, but you can obtain arbitrary mbeans using standard JMX query calls.
Some scratch code that I have:
private static MBeanServerConnection getConnection(
    String urlStr,
    String username,
    String password,
    String mbeanServer
) throws Exception {
    // This code implicitly requires weblogic classes to be in the classpath
    // in order to run efficiently, but its possible to get it to work without
    // any WL at all.   See
    //   http://e-docs.bea.com/wls/docs90/jmx/accessWLS.html#1118690
    // The code could be changed to automatically detect if WL is in
    // the classpath, and switch to "iiop" mode if it isn't.
    URI url = new URI(urlStr);
    Hashtable h = new Hashtable();
    h.put(Context.SECURITY_PRINCIPAL, username);
    h.put(Context.SECURITY_CREDENTIALS, password);
    h.put(
      JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,
      JMX_PROTOCOL_PROVIDER
    JMXServiceURL serviceURL = new JMXServiceURL(
       url.getScheme(), url.getHost(), url.getPort(), JMX_JNDI_ROOT + mbeanServe
    JMXConnector connector = JMXConnectorFactory.connect(serviceURL, h);
    return connector.getMBeanServerConnection();
conn = getConnection(url, user, pass, "weblogic.management.mbeanservers.domainruntime")
String type = "JMSServerRuntime";    // not sure may need to add "MBean" or strip off "Runtime", bridge = "MessagingBridgeRuntime"
Set xxx =    conn.queryMBeans(new ObjectName("*:Type=" + type + ",*"), null);Hope this helps,
Tom
Edited by: TomB on Jun 10, 2009 2:57 PM

How to find the NodeManager Status using WLST

Hi All,
can anyone please let me know how to find the nodemanager status using wlst, the nodemanager status whether it is 'Reachable' or not.
Thank you.

Hi Bob,
As James pointed, we faced the same. We could not find any mbean to find the Node Manager Stat that we can monitor from Weblogic console.
The best I can suggest, use the below WLST command after connecting to 'Node Manager:
nm()
Currently connected to Node Manager to monitor the domain xxxdomain.Grep for 'connected to Node Manager to monitor the domain <Your WLS domain name>' and if successfull, your node manager is UP & Connected other wise not 'Reachable'.
Regards,
qumar

Unable to Connect to SUN MQ using Messaging Bridge from Weblogic

Hello
          I am trying to connect to Sun MQ Queueu from weblogic using a messaging bridge. I get the following error message
          <Warning> <Connector> <BEA-190032> << Weblogic Mes
          saging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocati
          onException of javax.resource.ResourceException: Failed to start the connection
          on createManagedConnection.>
          Please looks at my configuration and see if I am missing something.
          I had configured the following:
          1. Source JMS Bridge Destination with
          the following (
          Adapter JNDIname = eis/jms/WLSConnectionFactoryJNDIXA ,
          connection url = file:///c:/temp (Sun MQ File based Store ,
          Initial Conext Fac = com.sun.jndi.fscontext.RefFSContextFactory,
          sun mq Connection fac Jndi name,
          sun mq destination jndi name
          2. Target JMS Bridge Destination
          ( Corresponding weblogic configuration)
          3. Messaging Bridge which uses the above two JMS Bridges.
          4. Also included fscontext.jar from Sun MQ Library into weblogic server classpath.
          Looks like the weblogic is able to get the intial context, but is unable to make connection to the SUN MQ Queue.
          Any help would be appreciated.
          skaturu

Sister f*cking brother bbw picpost teen titans hentai, brother sister f*ck teen ... Dad fucking daughter pics gallery brother fu*king. Pics of teens fuckin

When restarting server after a crash, Messaging bridges are not starting

Hi,
We have Messaging bridge configured with Exactly-Once QOS to read messages from IBM Websphere MQ to Weblogic distributed Queue. We are using Weblogic 10gR3.
1. We killed the weblogic server which was reading message from source destination(IBM MQ). We did this to check whether any message is lost when a server crashes.
2. Then we restarted the weblogic application server and checked the weblogic messaging bridge status.
3. The messaging bridge was not started properly and the following Exception was thrown.
####<Apr 22, 2010 4:09:11 PM BST> <Error> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-056A9014D88E2BE368B7> <> <12312323333> <BEA-200015> <An error occurred in bridge "BRIDGE" during the transfer of messages (javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:941)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:630)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1116)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:438)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy87.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1427)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
.).>
####<Apr 22, 2010 4:09:11 PM BST> <Warning> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948951881> <BEA-200026> <Bridge "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 weblogic.jms.bridge.internal.MessagingBridgeException.)>
####<Apr 22, 2010 4:09:12 PM BST> <Info> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948952726> <BEA-200020> <Bridge "BRIDGE" is stopped.>
Please give your suggestions to fix this issue.
Thanks!
Edited by: user11340353 on 28-Apr-2010 06:34

Hi,
*The server was started in warning mode and the JTA was declared unhealthy. I saw 2 transaction alive for more than 2000 seconds which is uncommon.
*The resource adaptor was started properly.
*We are using file store. But will it make a difference?
Thanks!

JMS Bridge status

Hi,
I am trying to find out the bridge status using the below wlst script. But failed to execute it.
Please help me.
connect(weblogic,'weblogic','t3://localhost:7001')
servers = domainRuntimeService.getServerRuntimes();
if (len(servers) > 0):
     for server in servers:
     messagingBridgeRuntime = server.getMessagingBridgeRuntime;
          messageBridges = messageBrigdeRuntime.getMessageBridges();
          for messageBridge in messageBridges:
               destinations = messageBridges.getDestinations();
               for destination in destinations:
                    print ' BridgeName          ' , destination.getName()
                    print ' State ' , destination.getState()

Hi Dongbo,
Even i am also facing the same issue. when i checked the serverRuntime(), i am unable to find the MessagingBridgeRuntime. Please find the below serverRuntime() when i executed it.
wls:/sampledomain/serverConfig> serverRuntime()
Location changed to serverRuntime tree. This is a read-only tree with ServerRuntimeMBean as the root.
For more help, use help(serverRuntime)
wls:/sampledomain/serverRuntime> ls()
dr-- ApplicationRuntimes
dr-- ClusterRuntime
dr-- ConnectorServiceRuntime
dr-- DefaultExecuteQueueRuntime
dr-- EntityCacheCumulativeRuntime
dr-- EntityCacheCurrentStateRuntime
dr-- EntityCacheHistoricalRuntime
dr-- ExecuteQueueRuntimes
dr-- JDBCServiceRuntime
dr-- JMSRuntime
dr-- JTARuntime
dr-- JVMRuntime
dr-- JoltRuntime
dr-- LibraryRuntimes
dr-- LogBroadcasterRuntime
dr-- LogRuntime
dr-- MANReplicationRuntime
dr-- MailSessionRuntimes
dr-- MaxThreadsConstraintRuntimes
dr-- MinThreadsConstraintRuntimes
dr-- PathServiceRuntime
dr-- PersistentStoreRuntimes
dr-- RequestClassRuntimes
dr-- SAFRuntime
dr-- ServerChannelRuntimes
dr-- ServerSecurityRuntime
dr-- ServerServices
dr-- ThreadPoolRuntime
dr-- TimerRuntime
dr-- WANReplicationRuntime
dr-- WLDFRuntime
dr-- WLECConnectionServiceRuntime
dr-- WTCRuntime
dr-- WebServerRuntimes
dr-- WorkManagerRuntimes
But in serverConfig(), i found the MessageBridges. Please find the below serverConfig() when i executed it.
wls:/sampledomain/serverConfig> ls()
dr-- AppDeployments
dr-- BridgeDestinations
dr-- Clusters
dr-- CustomResources
dr-- DeploymentConfiguration
dr-- Deployments
dr-- EmbeddedLDAP
dr-- ErrorHandlings
dr-- FileStores
dr-- InternalAppDeployments
dr-- InternalLibraries
dr-- JDBCDataSourceFactories
dr-- JDBCStores
dr-- JDBCSystemResources
dr-- JMSBridgeDestinations
dr-- JMSInteropModules
dr-- JMSServers
dr-- JMSSystemResources
dr-- JMX
dr-- JTA
dr-- JoltConnectionPools
dr-- Libraries
dr-- Log
dr-- LogFilters
dr-- Machines
dr-- MailSessions
dr--   MessagingBridges
dr-- RemoteSAFContexts
dr-- SAFAgents
dr-- SNMPAgent
dr-- Security
dr-- SecurityConfiguration
dr-- SelfTuning
dr-- Servers
dr-- ShutdownClasses
dr-- SingletonServices
dr-- StartupClasses
dr-- SystemResources
dr-- Targets
dr-- VirtualHosts
dr-- WLDFSystemResources
dr-- WLECConnectionPools
dr-- WSReliableDeliveryPolicies
dr-- WTCServers
dr-- WebAppContainer
dr-- WebserviceSecurities
dr-- XMLEntityCaches
dr-- XMLRegistries
wls:/sampledomain/serverConfig> cd('MessagingBridges')
wls:/sampledomain/serverConfig/MessagingBridges> ls()
dr--   com.jms.bridge.sample.in
wls:/sampledomain/serverConfig/MessagingBridges> cd('com.jms.bridge.sample.in')
wls:/sampledomain/serverConfig/MessagingBridges/com.jms.bridge.sample.in> ls()
dr-- SourceDestination
dr-- TargetDestination
dr-- Targets
-r-- AsyncEnabled true
-r-- BatchInterval -1
-r-- BatchSize 10
-r-- DeploymentOrder 1000
-r-- DurabilityEnabled true
-r-- IdleTimeMaximum 60
-r-- Name com.jms.bridge.sample.in
-r-- Notes null
-r-- PreserveMsgProperty true
-r-- QOSDegradationAllowed true
-r-- QualityOfService Exactly-once
-r-- ReconnectDelayIncrease 5
-r-- ReconnectDelayMaximum 60
-r-- ReconnectDelayMinimum 15
-r-- Selector
-r-- Started true
-r-- TransactionTimeout 30
-r-- Type MessagingBridge
-r-x freezeCurrentValue Void : String(attributeName)
-r-x isSet Boolean : String(propertyName)
-r-x unSet Void : String(propertyName)
wls:/sampledomain/serverConfig/MessagingBridges/com.jms.bridge.sample.in>
wls:/sampledomain/serverConfig/MessagingBridges/com.jms.bridge.sample.in> cmo.getName()
*'com.jms.bridge.sample.in'*
wls:/sampledomain/serverConfig/MessagingBridges/com.jms.bridge.sample.in> cmo.getType()
*'MessagingBridge'*
wls:/sampledomain/serverConfig/MessagingBridges/com.jms.bridge.sample.in> cmo.getState()
Traceback (innermost last):
File "<console>", line 1, in ?
AttributeError: getState
Using the MessagingBridges i am able to find the name of the bridge and its type except the state as shown above.
I need to find the bridge status through the WLST script only. Let me know is there any possibility in this.
Regards,
Siva Prasad Reddy
+91 9550887963

WLST: How to find 'active' messaging bridges using WLST

I am a beginner in WLST. However has gone through the WLST reference of online and offline commands also have understood the MBean Data model to some extent. I want to get the runtime MBean of a messaging bridge to know its state whether it is active or inactive for weblogic 10.3.3. Please advice with right direction to go ahead on this. Early response would be appreciated.
Requirement is to view the runtime status of bridges through a script and start/stop as needed.

This will probably help you a little on the way
servers = domainRuntimeService.getServerRuntimes();
if (len(servers) > 0):
for server in servers:
    jmsRuntime = server.getJMSRuntime();
      connections = jmsRuntime.getConnections();
      for connection in connections:
           print(connection.getHostAddress());
    jmsServers = jmsRuntime.getJMSServers();
    for jmsServer in jmsServers:
      destinations = jmsServer.getDestinations();The runtime mbeans are listed here: http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13951/core/index.html
In particular the MessagingBridgeRuntimeMBean would be of interest to you.

Using Messaging Bridge with Distributed Destinations

I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
          * WLS Server1:
          * JMS Server1:
          * inbound queue
          * outbound queue
          * JMS Server2:
          * inbound queue
          * outbound queue
          * WLS Server 2:
          * JMS Server3:
          * inbound queue
          * outbound queue
          A distributed destination is configured for the inbound and outbound queues.
          Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
          Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
          Any suggestions?


Hi Rob,
          Consumers on distributed destinations are always pinned
          to a single physical destination on creation. Only
          producers can round-robin each message. When a
          distributed destination is used as a source destination,
          you will need to configure a bridge per distributed
          destination. Alternatively, you can enable
          forwarding between the physical queues, which automatically
          forwards messages from physical queues with
          no consumers to physical queues that have consumers
          (but the extra hop impacts performance). For more information,
          consult the JMS documentation.
          Tom
          Rob McArthur wrote:
          > I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
          > * WLS Server1:
          > * JMS Server1:
          > * inbound queue
          > * outbound queue
          > * JMS Server2:
          > * inbound queue
          > * outbound queue
          > * WLS Server 2:
          > * JMS Server3:
          > * inbound queue
          > * outbound queue
          >
          > A distributed destination is configured for the inbound and outbound queues.
          >
          > Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
          >
          > Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
          >
          > Any suggestions?
          >
          >

Supress message in status bar when using Call Transaction

Hi,
I have designed a RF program and I am using a BDC program to call LT11 transaction for confirming TO.
As this was a Flowrack storage type we will assign Source HU during TO confirmation. So I went for a BDC.
But after confirmation I am getting a Status message TO XXX confirmed in the status bar which is also displayed in the RF Screen for every line item confirmed. I want to supress this message.
I am getting this message in the messtab table as well by using Call Transaction. So how can I supress this message in Status bar.
Please let me know for more information.
Thanks,
Manoj.

>
kaka79 wrote:
> I have designed a RF program and I am using a BDC program to call LT11 transaction for confirming TO.
> But after confirmation I am getting a Status message TO XXX confirmed in the status bar which is also displayed in the RF Screen for every line item confirmed. I want to supress this message.
> I am getting this message in the messtab table as well by using Call Transaction. So how can I supress this message in Status bar.
The CTU (CALL TRANSACTION ... USING ...) captures and stores all the messages into the message internal table (... MESSAGES INTO itab ...), but they are not displayed. So, if one of them appears in the status bar, it's because there is an additional MESSAGE ... statement in the program using the CTU. So look at it and add a condition before the MESSAGE statement to not output this exact message (click the message on status bar to get the message number, or debug the program to get it from the message internal table).

Message bridge exception when using bridging to MQ

          hi ... was wondering if anyone could suggest what might be causing this.
          I have a weblogic 8.1 queue bridged to a MQ5.3 queue. I was successfully able
          to put messages (using the container to handle the XA) into the weblogic Q and
          have the bridge successfully pass the msg onto the MQ Q. However I have started
          getting the following error msgs on random occasions.(and the bridge is not able
          to transfer the msgs across). Any suggestions as to what might be causing this?
          Please let me know if you need any additional info.
          thanks,
          Rajat
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200033> <Bridge "JeInputBridge"
          is obta
          ining connections to the two adapters.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200032> <Bridge "JeInputBridge"
          is conf
          igured to disallow degradation of its quality of service in cases where the configured
          quality of se
          rvice is unreachable.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200030> <Bridge "JeInputBridge"
          is conf
          igured to work in "Exactly-once" mode, and it is actually working in "Exactly-once"
          mode.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200028> <The bridge
          "JeInputBridge" has
          started transferring messages.>
          <Nov 14, 2003 11:10:08 AM EST> <Error> <MessagingBridge> <BEA-200015> <An error
          occurred in bridge "
          JeInputBridge" during the transfer of messages (javax.resource.ResourceException:
          Exception during e
          nListResource).>
          <Nov 14, 2003 11:10:08 AM EST> <Warning> <MessagingBridge> <BEA-200026> <Bridge
          "JeInputBridge" enco
          untered some problems in one of its adapters or underlying systems. It stopped
          transferring messages
          and will try to reconnect to the adapters shortly. (The exception caught was
          weblogic.jms.bridge.in
          ternal.MessagingBridgeException.)>
          <Nov 14, 2003 11:10:09 AM EST> <Info> <MessagingBridge> <BEA-200020> <Bridge "JeInputBridge"
          is stop
          ped.>


I suggest that you contact BEA Customer Support so that somebody can spend more time working
          directly with you and solving the problem.
          Sorry for not being able to help you more.
          Dongbo
          Rajat wrote:
          > hi Dongbo ... i checked the MQ error logs and found the followign error:
          >
          > ----- amqccita.c : 2758 -------------------------------------------------------
          > 11/17/03 10:33:24 AM
          > AMQ9208: Error on receive from host AHEWVTBHALLRA1-1 (169.242.174.24).
          >
          > EXPLANATION:
          > An error occurred receiving data from AHEWVTBHALLRA1-1 (169.242.174.24) over
          > TCP/IP. This may be due to a communications failure.
          > ACTION:
          > The return code from the TCP/IP (read) call was 131 (X'83'). Record these
          > values and tell the systems administrator.
          >
          > I did a test and found out that the error above is logged when i shut down the
          > WLS and NOT when i get the message bridge exception. The MQ system Admin feels
          > that there is bug in WLS as shuttting down WLS should gracefully terminate the
          > MQ connection and not throw any exceptions on MQ. So looks like this another thing
          > i would need your help on. Any other suggestions on what to do regarding the message
          > bridge exception ?
          >
          > Thanks,
          > Rajat
          >
          > Dongbo Xiao <[email protected]> wrote:
          > >Hi Rajat,
          > >Did you look at the log or tracing on the MQSeries side as I suggested?
          > >If you don't see any suspicious error messages on the MQSeries side,
          > >I would suggest that
          > >you contact the BEA Customer Support.
          > >Thanks,
          > >Dongbo
          > >
          > >Rajat wrote:
          > >
          > >> hi Dongbo,
          > >>
          > >> The problem occurs regardless of whether i stop the bridge and restart
          > >it. As
          > >> mentioned earlier, this problem does not occur all the time. This morning
          > >i started
          > >> up WLS and the it was giving the error. I then stopped it and restarted
          > >WLS ...it
          > >> started working fine. I then stopped the bridge and restarted the bridge..and
          > >> the errror happened. I then stopped the WLS and restarted it ...and
          > >the problem
          > >> was still there.... i then stopped and restarted WLS and everything
          > >started working
          > >> fine. On one occasion a few days ago... the bridge was working fine..and
          > >then
          > >> all of a sudden started giving this error...and after a while it started
          > >working
          > >> again. Pls suggest next steps.
          > >>
          > >> Thanks,
          > >> Rajat
          > >>
          > >> Dongbo Xiao <[email protected]> wrote:
          > >> >
          > >> >Hi Rajat,
          > >> >
          > >> >I have looked at your log file after Tom bought to me attention of
          > >the
          > >> >problem you are
          > >> >having.
          > >> >The error message regarding the adapter at the startup
          > >> >(NoSuchMethodException) is not a problem. It is just an info message.
          > >> >I also noticed that the Input bridge had been stopped and restarted
          > >before
          > >> >the error
          > >> >occurred. Did you get the same error if you did not stop and restart
          > >> >the bridge?
          > >> >Looks like the connection was somehow closed on the MQSeries side
          > >after
          > >> >the bridge
          > >> >established a connection to it but before the bridge sent any message
          > >> >over.
          > >> >If the problem only occurs after you stop and restart the bridge,
          > >it
          > >> >more likely is
          > >> >a bug on the WLS side. Otherwise, I would suggest that you check
          > >the
          > >> >log (or tracing)
          > >> >of the queue manager on the MQSeries side and see if you can spot
          > >some
          > >> >problem on the
          > >> >MQSeries side.
          > >> >
          > >> >Thanks,
          > >> >Dongbo
          > >> >
          > >> >Rajat wrote:
          > >> >
          > >> >> hi Tom... i looked over the FAQs but did not spot anything that
          > >i was
          > >> >doing wrong.
          > >> >> I have attatched the stack trace with the JMS debugging. (Sorry
          > >for
          > >> >the large
          > >> >> file... but i spotted some failure msgs regarding the adapter at
          > >startup
          > >> >and i
          > >> >> would like you to take a look ..). I have two bridges setup...
          > >> >> - JeInputBridge - connects weblogic Q to MQ Q
          > >> >> - JeReplyBridge - connects MQ Q to weblogic Q
          > >> >>
          > >> >> I am using the eis.jms.WLSConnectionFactoryJNDIXA adapter and am
          > >using
          > >> >the QOS
          > >> >> = "Exactly-Once"
          > >> >>
          > >> >> The weird thing is that the JeReplyBridge has never shown this error....
          > >> >but the
          > >> >> JeInput bridge sometimes works fine... then starts giving the error.
          > >> >On occassions,
          > >> >> it will keep trying and eventually start working... and sometimes
          > >i
          > >> >have to restart
          > >> >> the weblogic server several times before it starts working.
          > >> >>
          > >> >> Any suggestions/advice will be much appreciated.
          > >> >> Thanks,
          > >> >> Rajat
          > >> >>
          > >> >> Tom Barnes <[email protected]> wrote:
          > >> >> >The information below is too generic to interpret. Were stack
          > >traces
          > >> >> >printed out? Anyhow, I suggest that your start with the
          > >> >> >7.0 messaging bridge FAQ (it also applies to 8.1) to get
          > >> >> >more information about how to diagnose bridge issues:
          > >> >> >
          > >> >> >http://edocs.bea.com/wls/docs70/faq/msgbridge.html
          > >> >> >
          > >> >> >Rajat wrote:
          > >> >> >
          > >> >> >> hi ... was wondering if anyone could suggest what might be causing
          > >> >> >this.
          > >> >> >>
          > >> >> >> I have a weblogic 8.1 queue bridged to a MQ5.3 queue. I was successfully
          > >> >> >able
          > >> >> >> to put messages (using the container to handle the XA) into the
          > >> >weblogic
          > >> >> >Q and
          > >> >> >> have the bridge successfully pass the msg onto the MQ Q. However
          > >> >I
          > >> >> >have started
          > >> >> >> getting the following error msgs on random occasions.(and the
          > >bridge
          > >> >> >is not able
          > >> >> >> to transfer the msgs across). Any suggestions as to what might
          > >be
          > >> >causing
          > >> >> >this?
          > >> >> >> Please let me know if you need any additional info.
          > >> >> >>
          > >> >> >> thanks,
          > >> >> >> Rajat
          > >> >> >>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200033>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is obta
          > >> >> >> ining connections to the two adapters.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200032>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is conf
          > >> >> >> igured to disallow degradation of its quality of service in cases
          > >> >where
          > >> >> >the configured
          > >> >> >> quality of se
          > >> >> >> rvice is unreachable.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200030>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is conf
          > >> >> >> igured to work in "Exactly-once" mode, and it is actually working
          > >> >in
          > >> >> >"Exactly-once"
          > >> >> >> mode.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200028>
          > >> >> ><The bridge
          > >> >> >> "JeInputBridge" has
          > >> >> >> started transferring messages.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Error> <MessagingBridge> <BEA-200015>
          > >> >> ><An error
          > >> >> >> occurred in bridge "
          > >> >> >> JeInputBridge" during the transfer of messages (javax.resource.ResourceException:
          > >> >> >> Exception during e
          > >> >> >> nListResource).>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Warning> <MessagingBridge> <BEA-200026>
          > >> >> ><Bridge
          > >> >> >> "JeInputBridge" enco
          > >> >> >> untered some problems in one of its adapters or underlying systems.
          > >> >> >It stopped
          > >> >> >> transferring messages
          > >> >> >> and will try to reconnect to the adapters shortly. (The exception
          > >> >> >caught was
          > >> >> >> weblogic.jms.bridge.in
          > >> >> >> ternal.MessagingBridgeException.)>
          > >> >> >> <Nov 14, 2003 11:10:09 AM EST> <Info> <MessagingBridge> <BEA-200020>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is stop
          > >> >> >> ped.>
          > >> >> >
          > >> >>
          > >> >> ------------------------------------------------------------------------
          > >> >> Name: myserver.log
          > >> >> myserver.log Type: Text Document (application/x-unknown-content-type-txtfile)
          > >> >> Encoding: base64
          > >> >
          > >

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.

Messaging Bridge with MQ using SSL

Hi everybody,
I'm using JMS messaging bridge to transfer messages from WLS 10.3.6 running on a Solaris machine to remote WebSphere MQ 7 running on an AIX machine. Weblogic reads the configuration of remote MQ from a text file, called .bindings, created using the MQ JMSAdmin tool. The file defines a connection factory with the IP address, port, queue and queue manager name and other important definitions of the remote MQ.
The thing is that the bridge starts pretty well and transfer messages normally, but I need to change the configuration to use SSL. To do it I just added the parameter SSLCIPHERSUITE(SSL_RSA_WITH_RC4_128_MD5) and thought it was enough to achieve the goal.
<May 12, 2014 3:05:45 PM BRT> <Debug> <MessagingBridgeRuntimeVerbose> <BEA-000000> <Exception:
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
Wondering the error could be relatedo to an SSL exception, I enabled the SSL debugging (-Dssl.debug=true) to the managed server, but there were no evidences of an SSL handshake of Weblogic and MQ, so there is no SSL communication between the peers.
Does anybody know if this kind of communication is feasible? What may I be missing here?
Tks!

Hi everybody,
I'm using JMS messaging bridge to transfer messages from WLS 10.3.6 running on a Solaris machine to remote WebSphere MQ 7 running on an AIX machine. Weblogic reads the configuration of remote MQ from a text file, called .bindings, created using the MQ JMSAdmin tool. The file defines a connection factory with the IP address, port, queue and queue manager name and other important definitions of the remote MQ.
The thing is that the bridge starts pretty well and transfer messages normally, but I need to change the configuration to use SSL. To do it I just added the parameter SSLCIPHERSUITE(SSL_RSA_WITH_RC4_128_MD5) and thought it was enough to achieve the goal.
<May 12, 2014 3:05:45 PM BRT> <Debug> <MessagingBridgeRuntimeVerbose> <BEA-000000> <Exception:
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
Wondering the error could be relatedo to an SSL exception, I enabled the SSL debugging (-Dssl.debug=true) to the managed server, but there were no evidences of an SSL handshake of Weblogic and MQ, so there is no SSL communication between the peers.
Does anybody know if this kind of communication is feasible? What may I be missing here?
Tks!

Possible to use a message bridge for access to message copies?

I'd like to be able to consume copies of messages that go across a queue so that they can be validated during testing.
I've been unable to find any mechanisms for authenticated message monitoring which exists in other JMS brokers such as TIBCO EMS and so I'm going down the route of seeing whether a message bridge could help me. My thinking is that I can bridge from QueueA onto TopicA - where the message stays on QueueA and a copy is sent to Topic A which can be safely consumed by the testing tool
First question - is this a workable solution, ie does the message sent to QueueA stay on QueueA until is is consumed normally, or is the message forwarded to the bridged TopicA thus removing the original message?
Second question - I've tried to get a bridge working but encounter an error when trying to use it. The monitoring tab shows the bridge is up OK but I get the exception below in the admin console
<11-Oct-2010 13:55:12 o'clock BST> <Warning> <MessagingBridge> <BEA-200026> <Bridge "Bridge-0" 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 sending message.)>
Any help and advice appreciated
Stuart

One approach is to use a topic; producers send to the topic and both of your application consumer and your auditing consumer consume from the topic. If you have multiple application consumers, you could have a bridge to forward the messages from the topic to a queue and your applications consumers can consume from the queue, while your auditing consumer consumes from the topic.
There is a message life cycle logging capability in WLS JMS, which may be helpful. It can be enabled on a per destination basis. It logs an event in a file when a message is produced, consumed, removed, expired and etc. However the message body is not available in the log. The details can be found at
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/troubleshoot.htm#i1128815

How to list total number of message in specific Topic/queue using wlst comm

Hi All,
Message queue
How to list total number of message in specific Topic/queue using wlst command

aaaah sorry, I didn't notice you were looking for a SPECIFIC topic, bad me
then do something like
<pre>
connect('weblogic','weblogic','t3://localhost:8001')
servers = domainRuntimeService.getServerRuntimes();
if (len(servers) > 0):
for server in servers:
jmsRuntime = server.getJMSRuntime();
jmsServers = jmsRuntime.getJMSServers();
for jmsServer in jmsServers:
destinations = jmsServer.getDestinations();
for destination in destinations:
if destination.getName() == 'YOURQUEUE':
print "Destination ", destination.getName(), " MessageCount ", destination.getMessagesCurrentCount()
</pre>
of course performance-wise this is a terrible script because you loop on all destinations, I am sure there is a way to lookup a specific destination, but I am too lazy to investigate....

WL 7 Message Bridges using the selector.

We are trying to use a WL7 Message Bridge to bring select messages from WL6.
          We are trying to implement the Selector part of the Bridge. Does anyone
          know if this functionality actually works? And if it does work is the format
          of the Selector the same as in a MDB message-selector part of the
          ejb-jar.xml file?
          Thanks,
          John


          As far as we know, the selector part of the bridge works.
          The format of the selector is the same as JMS selector defined
          in JMS specification, which is the same as in MDB message-selector
          element of ejb-jar.xml file.
          Dongbo
          John Favre wrote:
          >
          > We are trying to use a WL7 Message Bridge to bring select messages from WL6.
          > We are trying to implement the Selector part of the Bridge. Does anyone
          > know if this functionality actually works? And if it does work is the format
          > of the Selector the same as in a MDB message-selector part of the
          > ejb-jar.xml file?
          >
          > Thanks,
          > John

Messaging Bridge status using WLST

Similar Messages

Maybe you are looking for