Messaging bridge freezing?

          I posted a week ago regarding some mdb's freezing. we haven't gotten a thread dump
          yet but hope to after hours. I wanted to post some more information that's come
          to light about the problem..
          we have a messaging bridge that is linking destinations between our weblogic 7.0
          sp2 instance and a weblogic 5.1 instance. we've noticed that when messaging traffic
          is freezing (we're using the same connection factory for all of these messages
          and for the messaging bridge -- OTHER jms traffic which uses a different connection
          factory is getting through fine), when we untarget the messaging bridge and do
          a netstat -a we see that the connection to the 5.1 instance is still ESTABLISHED
          even though the bridge has been undeployed. it does not go away even after an
          hour or so. The last time we tried this, the admin console locked up.
          Again, we're dealing with very little amounts of traffic, so I doubt that it is
          load related (and in fact happens after several days of inactivity)
          Thanks
          

          can you post the section of the config.xml which is relevant to Message Bridge
          and its destinations ?
          Dips
          "weblogic user" <[email protected]> wrote:
          >
          >here's a stack trace from when we tried to undeploy the bridge:
          >
          >java.lang.NullPointerException
          > at weblogic.jms.adapter51.JMSBaseConnection.recover(JMSBaseConnection.ja
          >va:1330)
          > at weblogic.jms.adapter51.JMSConnectionHandle.recover(JMSConnectionHandl
          >e.java:176)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.connector.common.internal.ConnectionWrapper.invoke(Connectio
          >nWrapper.java:101)
          > at $Proxy111.recover(Unknown Source)
          > at weblogic.jms.bridge.internal.MessagingBridge.cleanup(MessagingBridge.
          >java:1039)
          > at weblogic.jms.bridge.internal.MessagingBridge.shutdown(MessagingBridge
          >.java:1662)
          > at weblogic.jms.BridgeService.removeMessagingBridge(BridgeService.java:3
          >74)
          > at weblogic.jms.BridgeService.removeBridge(BridgeService.java:669)
          > at weblogic.jms.BridgeService.removeDeployment(BridgeService.java:593)
          > at weblogic.management.mbeans.custom.DeploymentTarget.removeDeployment(D
          >eploymentTarget.java:432)
          > at weblogic.management.mbeans.custom.DeploymentTarget.removeDeployment(D
          >eploymentTarget.java:177)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          >eanImpl.java:732)
          > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          >.java:714)
          > at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          >ionMBeanImpl.java:417)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          >57)
          > at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          >25)
          > at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
          >ServerImpl.java:952)
          > at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unkn
          >own Source)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
          > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
          > at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
          >eManager.java:821)
          > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          >a:308)
          >
          >
          >
          >
          

Similar Messages

  • Bridge freezes when renaming files

    When I rename certain files or folders, Bridge freezes on this message:
    Updating the cache for items within the folder recursively...
    It doesn't happen with all files or folders, but I haven't been able to determine a pattern. I've also had issues with the previews associated with some files (I just get a gray box), so I'm thinking it's obviously a cache issue. I've cleared the cache multiple times with no success. Any ideas?
    I'm running OSX 10.6.7 (which brought with it lovely bug in PDFs with PostScript-flavored OpenType fonts), which might be an issue. I'm also using Dropbox 0.7.110, with three other users...there are a whole lot of files in Dropbox that constantly update, so I can see how that might affect it to.

    localproductions wrote:
    …wonder what else it could be...
    It could be Time Machine, Spotblight, Dropbox… especially the obnoxious, intrusive Time Machine.
    Chris Cox, a top Adobe engineer who has been writing Photoshop code for some 15 years, recently wrote:
    http://forums.adobe.com/message/3732888#3732888
    The players:   Photoshop, Bridge, Dropbox, Time Machine, Spotlight, Finder
    Photoshop
    creates a temp file, writes to the temp file, and renames the temp to
    replace the original file, plus gets stat on the files.
    Bridge only reads the file, and writes to it's database.
    Finder gets attributes on the file in the normal folders.
    Dropbox
    gets stat on the files from 2 different processes (Dropbox,
    dbfseventsd), even outside it's directory, even in temporary
    directories.
    Spotlight (mdworker, mds) gets stat, and reads the
    files, even in temporary directories, sometimes while the file is still
    being written.
    Time Machine (backupd) gets stats, reads the files, and sometimes sets attributes on the files, even in temporary directories.
    Photoshop, Bridge and Finder are acting as expected.
    While Dropbox and Spotlight are doing some excess work, they don't seem to cause file modifications.
    But
    Time Machine is doing things wrong and causing file modifications, plus
    would fit with the "have the file open a long time" symptom.
    and
    on my own system I've confirmed that Dropbox and dbfseventsd will get stats on files outside the Dropbox folder.
    Dropbox has some bugs to fix.
    Wo Tai Lao Le
    我太老了

  • Bridge freezes online - works offline

    bridge freezes right after getting startet and remains in this stage
    but once I disconnect from the internet it does work perfectly
    - and freezes again as I connect to the internet
    (LR & PH are doing fine !! - PC, Win7)
    Does anyone know how to fix this?

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

  • Bridge Freeze

    Bridge opens with a message "Bridge encountered a problem and is unable to read the cache. Please try purging the central cache in Cache Preferences to correct the situation."  When I attempt to purge the cache, Bridge freezes.

    See post #6 of this thread.  http://forums.adobe.com/message/5223112

  • 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?
              >
              >
              

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

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

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

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

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

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

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

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

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

  • Error occured in Messaging bridge in weblogic to MQ Series

    Hi,
    I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
    <Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
    ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
    locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
    --Please give me the suggestion to fix this.
    Thanks in Advance,
    Sureshkannan Nagarajan

    Hi,
    I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
    <Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
    ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
    locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
    --Please give me the suggestion to fix this.
    Thanks in Advance,
    Sureshkannan Nagarajan

  • Error occured in Message Bridging in Weblogic to MQ Server

    Hi,
    I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
    <Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
    ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
    locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
    --Please give me the suggestion to fix this.
    Thanks in Advance,
    Sureshkannan Nagarajan

    Hello Priya
    If u r loading thru flat file
    1. Check the correct path in infopackage
    2. Check if it is opened,if it is then close it and run package again
    If loading thru R/3
    1. Check DS is not opened in change mode
    2. Check if RSA3 is able to extract data...if it is then check in RSA7 and chk IDOC status...
    3. Are you running init..then make sure no document is posted in R/3 side...
    Thanks
    Tripple k

  • Message Bridge between WLS 6.1 sp3 and MQSeries 5.2

              Hi,
              I'm really struggling with getting the Message Bridge working with Weblogic 6.1
              sp3 and MQSeries 5.2. Currently I have both installed on the same Windows 2000
              machine. First I'll pose some questions that I have, then I discuss the error
              I'm getting. Here are my questions:
              1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml. Within the
              ra.xml deployment descriptor there are config-properties for ConnectionURL, InitialContextFactory,
              ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue is the source
              jms destination bridge and my weblogic queue is the target jms destination bridge,
              what values do I set for the listed config-properties? I can't seem to find any
              documentation on what these values should be. Am I missing something? Do these
              values even have to be set?
              2. When I go to install a Weblogic instance to a different physical machine what
              has to be installed in terms of MQSeries? So I'll have MQSeries on physical machineA
              and Weblogic on a different physical machineB. I want machineA to forward all
              messages placed on a MQSeries Queue to forward them to machineB where the weblogic
              Queue resides. Does machineB also have to contain an MQSeries installation?
              Or can I just grab the necessary libraries and jar files and place them on the
              Weblogic machineB so they can be included?
              3. Is it correct that if I distribute Weblogic onto one physical server and MQSeries
              onto a different physical server that I cannot use Exactly-once quality of service?
              Other notes:
              1. I have the following patches installed for Weblogic 6.1 sp3:
              CR081404_610sp3.jar
              CR081511_61sp3.jar
              2. Here is the commands I used to create my ConnectionFactory and Queue within
              MQSeries:
              def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
              def q(MQTestQueue) qmanager(QM_jeff) queue(default)
              Okay...here is my error:
              <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred in bridge
              "Messaging Bridge" during transferring messages (java.lang.Exception: java.lang.
              reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
              javax.resource.ResourceException: Error creating consumer or receiving message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
              at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
              at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
              at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
              at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
              at $Proxy82.receive(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
              at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
              at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
              Has anyone see this error before? Here is part of my ra.xml file....I just put
              these entries in to see what happens:
              <config-property>
              <config-property-name>ConnectionURL</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>InitialContextFactory</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>ConnectionFactoryJNDI</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>MQTestConnectionFactory</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>DestinationJNDI</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>MQTestQueue</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>DestinationType</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value></config-property-value>
              </config-property>
              <config-property>
              <config-property-name>AdapterType</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>XATransaction</config-property-value>
              </config-property>
              Here is a snip of my config.xml:
              <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              Name="Messaging Bridge" QualityOfService="Atmost-once"
              SourceDestination="Source JMS Bridge Destination"
              TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              <JMSBridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              ConnectionFactoryJNDIName="MQTestConnectionFactory"
              ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              Name="Source JMS Bridge Destination"/>
              <JMSBridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              ConnectionURL="t3://localhost:7001"
              DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              InitialContextFactory="weblogic.jndi.WLInitialContextFactory" Name="Target
              JMS Bridge Destination"/>
              Any help would be greatly appreciated. Thank you in advance for your help.
              Sincerely,
              Jeff
              

              I tried your suggestion and it worked!! The only thing is, it
              makes the deployment of the resource adapter a little more
              complicated. Now my customers are going to have to edit their
              config.xml, instead of just dropping in the appropriate rar into
              the applications directory. But one nice side affect of placing
              the rar's in a different directory is it makes the Message
              Bridge a little more stable. I was finding it to be very
              unstable. One time I would startup my Application Server and
              everything was fine, then I would shutdown. The next time I
              started it up, I would get exceptions. I have yet to see that
              behavior with this new configuration.
              Thanks again for all of your help, it is greatly appreciated!!
              Jeff
              Dongbo Xiao <[email protected]> wrote:
              >Looks like that somehow you have the adapter deployed
              >multiple times, may not be intended. The cause is that
              >everything in the application directory will be automatically
              >deployed and all of them are added to the config.xml. During
              >the next boot, those appear in the config.xml will be deployed and
              >everything in the application directory too. As a result, the adapters
              >are deployed twice. The complain about runtime mbean not found may
              >mean the one that is overridden by the new one.
              >
              >The work around is not to put your adapters in the application
              >directory, instead, put them in a different directory and point to
              >the directory in your config.xml.
              >
              >Dongbo
              >Jeff wrote:
              >>
              >> One more thing...
              >> I noticed that the exception specified that it couldn't find
              >> mydomain:Location=myserver,Name=jms-xa-
              >> adp_Pool_1,ServerRuntime=myserver,Type=ConnectorConnectionPoolRun
              >> time MBean, but what's interesting that if I run the following
              >> java weblogic.Admin GET -type ConnectorConnectionPoolRuntime -
              >> property ActiveConnectionsCurrentCount -url
              >> http://localhost:7001 -username xxxx -password xxxx I get the
              >> following output:
              >>
              >> {MBeanName="mydomain:Location=myserver,Name=jms-xa-
              >> adp_Pool_3,ServerRuntime=myse
              >> rver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCurren
              >> tCount=0}}
              >> {MBeanName="mydomain:Location=myserver,Name=jms-notran-
              >> adp_Pool_2,ServerRuntime=
              >> myserver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCu
              >> rrentCount=0}}
              >>
              >> So from that...it looks like the MBean is there. Any ideas why it
              >is not being
              >> found?
              >>
              >> Thanks,
              >>
              >> Jeff
              >>
              >> "Jeff" <[email protected]> wrote:
              >> >
              >> >
              >> >
              >> >Thank you very much!!
              >> >
              >> >I tried your suggestions and created a general Queue Connection Factory
              >> >within
              >> >MQSeries. Then I setup my MQSeries JMS Bridge Destination to use
              >the
              >> >jms-notrans-adp.rar
              >> >resource adapter. With this configuration, I can send messages to
              >MQSeries
              >> >and
              >> >they get forwarded to Weblogic.
              >> >
              >> >But, if I create a XAQueueConnectionFactory within MQSeries I cannot
              >> >get the bridge
              >> >working at all. I realize that MQSeries has a bug with Transactions
              >> >and remote
              >> >servers, but I have MQSeries and Weblogic running on the same machine.
              >> > I thought
              >> >I could setup an XAConnectionFactory in MQSeries, set the MQSeries
              >JMS
              >> >Bridge
              >> >Destination to use the jms-xa-adp.rar and specify Exactly-once QOS
              >and
              >> >it should
              >> >work? I tried it and it didn't work. ( see attachment for weblogic.log
              >> >showing
              >> >exception ).
              >> >
              >> >Here is my config.xml:
              >> > <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              >> > Name="Request Messaging Bridge" QOSDegradationAllowed="true"
              >> > QualityOfService="Exactly-once"
              >> > SourceDestination="Source JMS Bridge Destination"
              >> > TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              >> > <JMSBridgeDestination
              >> > ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              >> > ConnectionURL="t3://localhost:7001"
              >> > DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              >Name="Target
              >> >JMS Bridge Destination"/>
              >> > <JMSBridgeDestination
              >> > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> > ConnectionFactoryJNDIName="MQTestConnectionFactory"
              >> > ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              >> > DestinationJNDIName="MQTestQueue"
              >> > InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              >> >Name="Source
              >> >JMS Bridge Destination"/>
              >> >
              >> >Again, thank you very much for your response. It helped me a great
              >deal.
              >> > Any
              >> >thoughts on the above problem please foward them along.
              >> >
              >> >Oh...and to answer the question posed to me, yes the CR081511_61sp3.jar
              >> >file is
              >> >dated 8/13/2002
              >> >
              >> >
              >> >Sincerely,
              >> >
              >> >Jeff
              >> >
              >> >Dongbo Xiao <[email protected]> wrote:
              >> >>Please see my comments inline.
              >> >>
              >> >>
              >> >>Jeff wrote:
              >> >>>
              >> >>> Hi,
              >> >>> I'm really struggling with getting the Message Bridge working with
              >> >>Weblogic 6.1
              >> >>> sp3 and MQSeries 5.2. Currently I have both installed on the same
              >> >>Windows 2000
              >> >>> machine. First I'll pose some questions that I have, then I discuss
              >> >>the error
              >> >>> I'm getting. Here are my questions:
              >> >>>
              >> >>> 1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml.
              >> >> Within the
              >> >>> ra.xml deployment descriptor there are config-properties for ConnectionURL,
              >> >>InitialContextFactory,
              >> >>> ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue
              >> >is
              >> >>the source
              >> >>> jms destination bridge and my weblogic queue is the target jms
              >destination
              >> >>bridge,
              >> >>> what values do I set for the listed config-properties? I can't
              >seem
              >> >>to find any
              >> >>> documentation on what these values should be. Am I missing something?
              >> >> Do these
              >> >>> values even have to be set?
              >> >>>
              >> >>
              >> >>You DON'T have to do anything to the adapter deployment descriptor
              >> >>files.
              >> >>The values given there for the listed config-properties are just
              >default
              >> >>values.
              >> >>The values configured in JMSBridgeDestination instances are the values
              >> >>used to
              >> >>override the default values in the dd file.
              >> >>
              >> >>> 2. When I go to install a Weblogic instance to a different physical
              >> >>machine what
              >> >>> has to be installed in terms of MQSeries? So I'll have MQSeries
              >on
              >> >>physical machineA
              >> >>> and Weblogic on a different physical machineB. I want machineA
              >to
              >> >>forward all
              >> >>> messages placed on a MQSeries Queue to forward them to machineB
              >where
              >> >>the weblogic
              >> >>> Queue resides. Does machineB also have to contain an MQSeries
              >installation?
              >> >>> Or can I just grab the necessary libraries and jar files and place
              >> >>them on the
              >> >>> Weblogic machineB so they can be included?
              >> >>>
              >> >>
              >> >>You don't have to install MQSeries on the machine that the WebLogic
              >> >>server is running. You need the necessary libraries and jar files
              >> >>though.
              >> >>
              >> >>> 3. Is it correct that if I distribute Weblogic onto one physical
              >server
              >> >>and MQSeries
              >> >>> onto a different physical server that I cannot use Exactly-once
              >quality
              >> >>of service?
              >> >>>
              >> >>
              >> >>That is correct and it is a MQSeries transaction limitation.
              >> >>
              >> >>> Other notes:
              >> >>> 1. I have the following patches installed for Weblogic 6.1 sp3:
              >> >>> CR081404_610sp3.jar
              >> >>> CR081511_61sp3.jar
              >> >>>
              >> >>
              >> >>What version of CR081511_61sp3.jar you have? You need the one dated
              >> >on
              >> >>8/13/2002.
              >> >>
              >> >>> 2. Here is the commands I used to create my ConnectionFactory
              >and
              >> >>Queue within
              >> >>> MQSeries:
              >> >>> def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
              >> >>> def q(MQTestQueue) qmanager(QM_jeff) queue(default)
              >> >>>
              >> >>
              >> >>The only possible error I see here is that you create a xaqcf while
              >> >your
              >> >>bridge
              >> >>is configured to have "Atmost-once" QOS. The bridge adapter will
              >create
              >> >>XASession
              >> >>if the connection factory is xa because it knows nothing about QOS
              >of
              >> >>the bridge.
              >> >>As I said, there is a limitation in MQSeries transactions, which
              >prevent
              >> >>the
              >> >>transaction to happen between remote servers. Although the bridge
              >does
              >> >>not
              >> >>start the the transaction in your case, but MQSeries xa connection
              >> >>factory may
              >> >>throw error when it detects the other side is remote. Having said
              >that,
              >> >>I am not
              >> >>completely sure this is the problem caused the bridge to fail. I
              >suggest
              >> >>you use
              >> >>a non-xa connection factory on the MQSeries side and see if the problem
              >> >>goes away.
              >> >>
              >> >>> Okay...here is my error:
              >> >>>
              >> >>> <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred
              >> >>in bridge
              >> >>> "Messaging Bridge" during transferring messages (java.lang.Exception:
              >> >>java.lang.
              >> >>> reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
              >> >>> javax.resource.ResourceException: Error creating consumer or receiving
              >> >>message
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
              >> >>> at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
              >> >>> at java.lang.reflect.Method.invoke(Native Method)
              >> >>> at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
              >> >>> at $Proxy82.receive(Unknown Source)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
              >> >>>
              >> >>
              >> >>The latest patch CR081511_61sp3.jar (dated on 8/13/2002) will expose
              >> >>more error
              >> >>information.
              >> >>
              >> >>> Has anyone see this error before? Here is part of my ra.xml file....I
              >> >>just put
              >> >>> these entries in to see what happens:
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>ConnectionURL</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>InitialContextFactory</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>ConnectionFactoryJNDI</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>MQTestConnectionFactory</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>DestinationJNDI</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>MQTestQueue</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>DestinationType</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value></config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>AdapterType</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>XATransaction</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>
              >> >>As I said earlier, you are not supposed to change the adapter dd
              >file.
              >> >>
              >> >>
              >> >>> Here is a snip of my config.xml:
              >> >>>
              >> >>> <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              >> >>> Name="Messaging Bridge" QualityOfService="Atmost-once"
              >> >>> SourceDestination="Source JMS Bridge Destination"
              >> >>> TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              >> >>> <JMSBridgeDestination
              >> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> >>> ConnectionFactoryJNDIName="MQTestConnectionFactory"
              >> >>> ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              >> >>> DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              >> >>> Name="Source JMS Bridge Destination"/>
              >> >>>
              >> >>> <JMSBridgeDestination
              >> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> >>> ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              >> >>> ConnectionURL="t3://localhost:7001"
              >> >>> DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              >> >>> InitialContextFactory="weblogic.jndi.WLInitialContextFactory"
              >Name="Target
              >> >>> JMS Bridge Destination"/>
              >> >>>
              >> >>
              >> >>Your configuration of the bridge and bridge destinations look fine.
              >> >
              >> >>The last thing is that you have to put MQSeries stuff in your CLASSPATH
              >> >>and PATH for starting the WebLogic server that the bridge is running
              >> >>on.
              >> >>
              >> >>You can also turn on debug for more information.
              >> >>-Dweblogic.Debug.DebugMessagingBridgeStartup=true
              >> >>-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
              >> >>
              >> >>
              >> >>Thanks,
              >> >>Dongbo
              >> >
              

  • Messaging bridge with JBoss

    Hi
              I am trying to configure a messaging bridge between weblogic 8.1 sp4 and jboss-4.0.2 on my local machine.
              I have the bridge working for the following configuration:
              Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDINoTX
              Connection URL: jboss server URL with port
              Initial Context Factory: org.jnp.interfaces.NamingContextFactory
              Connection Factory JNDI Name: ConnectionFactory
              Destination JNDI Name: queue/testQueue
              and these jar's are in my weblogic class path:
              [jboss_home]/client/jboss-common-client.jar
              [jboss_home]/client/jbossmq-client.jar
              [jboss_home]/client/jboss-system-client.jar
              [jboss_home]/client/jboss-transaction-client.jar
              [jboss_home]/client/jnp-client.jar
              [jboss_home]/lib/concurrent.jar
              [jboss_home]/client/log4j.jar
              I have also deployed connector module jms-notran-adp.rar on my weblogic server.
              I am using "Duplicate-okay" Quality Of Service and the bridge functions correctly.:^O
              Now when I try to configure the bridge so that I can use "Exactly-once" Quality Of Service I use the following configuration:
              Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDIXA
              Connection URL: jboss server URL with port
              Initial Context Factory: org.jnp.interfaces.NamingContextFactory
              Connection Factory JNDI Name: XAConnectionFactory
              Destination JNDI Name: queue/testQueue
              and add these jar's in my weblogic class path:
              [jboss_home]/client/jboss-common-client.jar
              [jboss_home]/client/jbossmq-client.jar
              [jboss_home]/client/jboss-system-client.jar
              [jboss_home]/client/jboss-transaction-client.jar
              [jboss_home]/client/jnp-client.jar
              [jboss_home]/lib/concurrent.jar
              [jboss_home]/client/log4j.jar
              I also deployed the connector module jms-xa-adp.rar on my weblogic server.
              The connection factory that I use for the weblogic destination is also "XA enabled".
              The problem which I have is that no messages are transferred via the bridge and following error is printed out from the server :_|:
              <2005/08/15 12:20:22 PM> <Error> <Connector> <BEA-190091> <Call to implementation of ManagedConnection.getXAResource in resource adapter with jndiName = eis/jms/WLSConnectionFactoryJNDIXA failed: java.lang.IllegalStateException: can only be called from server>
              Could you please assist.
              Thanks in advance

    Hi,
              I am trying to do configure a bridge between weblogic 7.0 SP4 and JBOSS 4.0.3 SP1.
              I have set the classpath as mentioned but I am getting an error
              ####<Apr 11, 2006 2:02:34 PM CEST> <Debug> <MessagingBridge> <DNI6> <dni6testser
              ver> <ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <200006> <M
              essaging Bridge Debugging RUNTIME! Bridge WebOSSTEST Getting target connection>
              ####<Apr 11, 2006 2:02:34 PM CEST> <Warning> <Connector> <DNI6> <dni6testserver>
              <ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <190032> << Web
              logic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > Resourc
              eAllocationException of javax.resource.ResourceException: Failed to start the co
              nnection on createManagedConnection.>
              ####<Apr 11, 2006 2:02:34 PM CEST> <Info> <MessagingBridge> <DNI6> <dni6testserv
              er> <ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <200043> <Br
              idge "WebOSSTEST" failed to connect to the target destination and will try again
              in 60 seconds. (java.lang.Exception: javax.resource.spi.ResourceAllocationExcep
              tion: CreateManagedConnection Error: Failed to start the connection
              at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
              ctionPool.java:1009)
              at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
              ctionPool.java:1769)
              at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
              n(ConnectionPoolManager.java:191)
              at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
              ection(ConnectionManagerImpl.java:25)
              at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMS
              BaseConnectionFactory.java:126)
              at weblogic.jms.bridge.internal.MessagingBridge.getConnections(Messaging
              Bridge.java:764)
              at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
              java:930)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
              -------------- Linked Exception ------------
              javax.resource.ResourceException: Failed to start the connection
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBase
              Connection.java:1273)
              at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnectio
              n.java:357)
              at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:2
              29)
              at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnect
              ion(JMSManagedConnectionFactory.java:190)
              at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
              ctionPool.java:1002)
              at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
              ctionPool.java:1769)
              at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
              n(ConnectionPoolManager.java:191)
              at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
              ection(ConnectionManagerImpl.java:25)
              Does anyone have a solution

  • Weblogic Message Bridge Producing Duplicate JMS Messages

    We have a message bridge that we use to integrate with TIBCO. The message bridge is deployed on a WL cluster. We see duplicate JMS messages produced by the bridge when it is deployed on the cluster. We don't see this behavior when only one ManagedServer in the cluster is active,.
    TIBCO version: 4.4.3 V5
    WLS: 10.3.3 with patch for bug BUG8732539 (BQC6)
    java -version
    java version "1.6.0_17"
    Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
    Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2121-linux-x86_64, compiled mode)
    We are also seeing a lot of exceptions related to
    <May 27, 2011 4:11:57 PM PDT> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
    However the bridge is active. We are monitoring the message-out count on TIBCO and we observed that we see duplicates whenever there a message is re-delivered. We opened a case with Oracle support and they suggested patch 10258751 which didn't help. The next suggestion was a patch for "Bug 11852771 - [WLS10.3.2]MISSING AND DUPLICATE IN JMS QUEUE MESSAGE MONITORING" but I don't think it will help since our JMS consumers are getting duplicate messages and this is not just a UI issue.
    Here is the message behavior when we send a single message:
    Timelines
    11:34:17 --> Message sent to TIBCO EMS queue
    11:34:17 --> WL MS3 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
    11:34:17 --> WL MS1 says it got the message and committed the transaction
    11:34:17 --> Message is visible in the JMS queue in the admin console
    11:34:17 --> TIBCO EMS has still not received an ACK from WL for the message
    11:34:31 --> TIBCO EMS resends the same JMS message to WL
    11:34:31 --> WL MS2 says it got the message and committed the transaction
    11:34:31 --> WL MS1 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
    11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are two messages in the JMS queue)
    11:34:31 --> TIBCO EMS has still not received an ACK from WL for the message
    11:34:54 --> TIBCO EMS resends the same JMS message to WL
    11:34:31 --> WL MS4 says it got the message and committed the transaction
    11:34:31 --> WL MS2 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
    11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are three messages in the JMS queue)
    11:34:31 --> TIBCO EMS receives an ACK from WL for the message
    MS04
    ####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
    JMS Message Class: TextMessage
    JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
    JMSCorrelationID: null
    JMSDeliveryMode: PERSISTENT
    JMSDestination: Queue[SourceQueue1]
    JMSExpiration: 0
    JMSPriority: 4
    JMSRedelivered: true
    JMSReplyTo: null
    JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
    JMSType: null
    Transaction Id: BEA1-6A59E8FE76C4FC4CA149
    <?xml version="1.0" encoding="UTF-8"?>
    <commands ...
    >
    ####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <MS04> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
    JMS Message Class: TextMessage
    Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
    New JMS MessageID: ID:<193654.1306521294611.0>
    <?xml version="1.0" encoding="UTF-8"?>
    <commands ...
    >
    MS03
    ####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257342> <BEA-000000> <Bridge MessageBridge1 Successfully got connection to the target destination>
    ####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1: both source and target adapters support XA = true>
    ####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 supportsMDBTX = false supportsXA = true async = true>
    ####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 WorkMode = Exactly-once>
    ####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntimeVerbose> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 Entering processMessages() ------ >
    ####<May 27, 2011 11:34:17 AM PDT> <Error> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-3AA29116A4CA622834EA> <> <1306521257343> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: 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:948)
    at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
    at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
    at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
    at $Proxy62.receive(Unknown Source)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
    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)
    at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:200)
    at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
    at $Proxy62.receive(Unknown Source)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
    at $Proxy62.receive(Unknown Source)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
    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: 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:948)
    at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
    at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
    at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
    at $Proxy62.receive(Unknown Source)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
    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)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
    at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
    ... 8 more
    ).>
    ####<May 27, 2011 11:34:17 AM PDT> <Warning> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257344> <BEA-200026> <Bridge "MessageBridge1" 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: MessagingBridgeException: Messaging bridge operation failed
    .)>
    MS02
    ####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271386> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
    JMS Message Class: TextMessage
    JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
    JMSCorrelationID: null
    JMSDeliveryMode: PERSISTENT
    JMSDestination: Queue[SourceQueue1]
    JMSExpiration: 0
    JMSPriority: 4
    JMSRedelivered: true
    JMSReplyTo: null
    JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
    JMSType: null
    Transaction Id: BEA1-679AF074F381152F047C
    <?xml version="1.0" encoding="UTF-8"?>
    <commands ...
    >
    ####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271392> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
    JMS Message Class: TextMessage
    Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
    New JMS MessageID: ID:<196075.1306521271386.0>
    <?xml version="1.0" encoding="UTF-8"?>
    <commands ...
    >
    ####<May 27, 2011 11:34:54 AM PDT> <Error> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
    javax.transaction.xa.XAException
    at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
    at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
    at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
    at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.NullPointerException
    at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
    ... 14 more
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:225)
    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
    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: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
    javax.transaction.xa.XAException
    at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
    at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
    at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
    at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.NullPointerException
    at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
    ... 14 more
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    ... 2 more
    ).>
    ####<May 27, 2011 11:34:54 AM PDT> <Warning> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200026> <Bridge "MessageBridge1" 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: MessagingBridgeException: Messaging bridge operation failed
    MS01
    ####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257536> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
    JMS Message Class: TextMessage
    JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
    JMSCorrelationID: null
    JMSDeliveryMode: PERSISTENT
    JMSDestination: Queue[SourceQueue1]
    JMSExpiration: 0
    JMSPriority: 4
    JMSRedelivered: false
    JMSReplyTo: null
    JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
    JMSType: null
    Transaction Id: BEA1-72BC818FE2BB8C2655C6
    <?xml version="1.0" encoding="UTF-8"?>
    <commands ...
    >
    ####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257542> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
    JMS Message Class: TextMessage
    Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
    New JMS MessageID: ID:<195581.1306521257536.0>
    <?xml version="1.0" encoding="UTF-8"?>
    <commands ...
    >
    ####<May 27, 2011 11:34:31 AM PDT> <Error> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
    javax.transaction.xa.XAException
    at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
    at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
    at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
    at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.NullPointerException
    at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
    ... 14 more
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
    javax.transaction.xa.XAException
    at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
    at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
    at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
    at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.NullPointerException
    at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
    ... 14 more
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
    at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    ... 1 more
    ).>
    ####<May 27, 2011 11:34:31 AM PDT> <Warning> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200026> <Bridge "MessageBridge1" 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: MessagingBridgeException: Messaging bridge operation failed
    .)>

    @Tom, thanks for your hints and sorry for my delayed response. Here are my answers to your queries…
    -- Does messaging work, without any exceptions, when only one bridge is active?
    It works fine when only one node of the cluster is active. -- I'm not familiar with Tibco monitoring, but I suspect that the "message-out count on TIBCO" stat doesn't always imply that there's a duplicate message. It could mean that an initial message delivery attempt failed, it's transaction rolled back, and the message was redelivered. Redelivery after a failure is normal - the original delivered message, if one actually made it onto a WebLogic queue, should be discarded by WebLogic when its failed transaction eventually rolls back (before its ever handed to a consumer application).
    You are absolutely right. The mismatch in count was due to redelivery attempts. We could see that as soon as we turned on trace in TIBCO-- The posted stack traces look like they may be JVM stdout/stderr scrapes, which are often automatically truncated, for example, see the "... 8 more" listed at the bottom of one of the stack traces below. There might be more information in the full stack trace for the "Resource manager is unavailable" exception. Full traces are logged in each WebLogic Server's log files.
    I tried redirecting the output and even set "stdout Stack Trace Depth:" to -1 but I am not albe to see the complete trace.-- The setTransactionTimeout NullPointerException error message looks like it is collateral damage from the original reported "Resource manager is unavailable" exception that's thrown earlier during the enlistResource() step. If you are truly getting duplicates, then I think this is a clue that the bridge is somehow (stupidly) trying to proceed with forwarding the message despite the fact that there's no current transaction on the thread...

    I have a case open with Oracle support and we have extensive debugging turned on. Here is what the engineer came back with. There is an issue with XA transactions in JCA adapter when it talks to third party providers like TIBCO. Since the resource names are not unique across the cluster, a XA transaction is started on multiple nodes in the cluster for the same message. All transactions abort but the message is persisted and TIBCO redelivers the message since the connection is severed when the transaction aborts. We were able to reproduce this scenario at will with our setup and Oracle was able to reproduce the issue too. 
-- Can you check the state of the message on the WebLogic Q? The fact that a message is shown on the WL console doesn't necessarily mean that the state of the message is visible (it could be waiting for the transaction to commit - something that apparently never happens). On the console: Services -> Messaging -> JMS Modules -> [module name] -> [destination name].

    Our consumer was getting duplicate messages. This confirms that the console was not giving us incorrect information. The console showed that 2/3/4 messages were in "current" state when we expected only one message.
-- Make sure that the bridge's Tibco destination is a Tibco queue not a Tibco topic (it's happened).

    Yeah we made sure it was a Queue.
-- Can you post your bridge and destination stanzas from your config.xml? 

    Will try to do this shortly but have to strip out lot of information.
-- I vaguely recall that there was a problem with untyped connection factories in Tibco at one point (not sure). You might want to try changing the Tibco configuration to spin-up "XA Queue Connection Factory" instead of just an "XA Connection Factory" (plus modify the bridge configuration accordingly).

    We tried this but it didn't eliminate this issue. One thing we did notice however was that the number of rollbacks were greatly reduced.

    Here is the workaround that Oracle is suggesting: Create pinned destinations and assign it to a distributed queue. This will keep the transactions local and hence eliminate the duplicate transactions and rollback. We tried it and it eliminated the dups issue. However I discovered another bug during my testing. Our cluster messaging mode is "Unicast" and message forwarding from zero consumer queues to queues with consumers fails. We have four/five nodes in the cluster and two consumer threads. I observed that the zero consumer queues always forward to one queue in the cluster that has consumers. The forwarding stalls when I bring down the node that has consumers. Again, we were able to reproduce this issue at will and Oracle has acknowledged that it is a bug. They've reported that Unicast fails without any warning whereas Multicast fails with a warning in the log. We have observed this message forwarding stalling even with UDQs.
    I have another case open for an issue where our message bridges that transfer messages from TIBCO to WLS stalls after sometime. The status is shown as active but it is not doing anything. The server instance shows stuck threads trying to roll back a message. TIBCO logs indicate that it is receiving a request to rollback a transaction but it is not finding the transaction to rollback. The only way to recover from this condition is to restart the cluster. I am fairly confident that he root case for this issue is again the XA transaction issue. I changed our UDQ to pinned destination in one environment and we are no longer seeing dups or bridge stalling there. Hopefully Oracle can resolve the message forwarding issue.Thanks again….

  • JMS Messaging Bridge WLS8.1

              Hello All,
              I am trying to hook up 2 Queues as source and target destinations for the WLS8.1
              Messaging Bridge[MB] functionality.
              So when I send a message to Q1[source destination], the MB forwards the message
              to Q2[target destination].
              I have 1 MDB deployed and listening on Q2.
              I verify the messages received via the admin console in wls8.1 as well as the
              MDB I have deployed.
              Thus, the MB works.
              However, when I deploy a MDB on Q1 as well, the message is lost(not forwaded to
              Q1 by the MB).
              Assuming that the source destination is of type Queue, and this behaviour is expected,
              I went to test with a Topic as source destination for the MB and a Queue as the
              target destination for the MB.
              However, I failed to receive any messages in the dest[Q2] via the MB.
              This is with / without a MDB listening on the Topic[source destination].
              One MDB is always listening on the Queue[target destination].
              MB does not work.............
              Can anyone help ?
              TIA.
              

    There is no native code specific to this use case, except
              perhaps for IBM code, and I know of no issues.
              Raja wrote:
              > I have tested Messaging Bridge(jms-xa-adp.rar),Foreign JMS provider in WLS8.1-SP1
              > on windows NT m/c.Can any body tell me whether there will any problem while setting
              > up and running the same test on Solaris.
              >
              > Thanks in advance,
              > Raja
              

  • WLS 8.1 SP5 Message bridge doesn't refresh connection after idle time out

    Hi,
    I am seeing in the log after enabling the debug flags that message bridge intermittently stops refreshing the connection without logging further info and causing a production failure.Bridge is forwarding the message from WLS 8.1..5 DQ to the remote MQ 6.0 queue.
    Below is the snippet which doesn't come in the log which suggests that bridge stops refreshing the connection.
    <BEA-200027> <Bridge "CASLDNSenderBridge" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.>
    The above message does appear everytime but intermittently it stops and the messages put after this leading to the exceptions.The bridge has been configured in asynchronous mode and the idle time out is configured as 60 secs.
    Can somebody please let me know if there is any known issue with 8.1 SP5 where message bridge stops refreshing connection intermittently or how to debug this further.

    I would normally suggest raising the issue with support, but I recall hearing that 8.1 is nearing the end of its support cycle, so I'm not sure that's an option for you. Other options:
    - try upgrading to a newer SP, or better yet, a new version of WebLogic
    - try changing to synchronous forwarding
    - examine thread dumps from when the bridge appears to be stalled
    - post the exception that bridge is throwing when it tries to connect
    - try patching MQ (the problem could be on the MQ side, and perhaps an older version of the bridge may not be fully capable of handling all of MQs minor quirks)
    - write a program to (A) detect inactivity on the src destination, and (B) somehow restart the bridge and/or all of WL when this occurs
    Tom

Maybe you are looking for

  • Line graph problem in numbers

    How can I change. the thickness of lines when using the line diagram in numbers. I want to see 3 lines that are relatively close to each other but because they are very thick they overlay each other.

  • Exchange Rate differences in FC. SAP Note: 999974

    Hi All We are having problem in clearing of bank accounts due to balance being incorrect. We implemented SAP Note: 999974 but seems like i am missing something, In User Exit FEB00001 my code is: IF i_febep-fwaer NE ''.   wa_febcl-selfd = 'FM'.   wa_f

  • Applying Support Packs at GRC Access Control 5.3 overall solution level

    Hi All I recently noticed something at a customer, that GRC Access Controls 5.3 launch pad shows a different SP level e.g. version8, while the components, Compliant User Provisioning shown SP10, RAR shown SP12 etc. My questions are; 1. Should SP upda

  • Itunes freezes when I connect 30g 5th generation ipod

    I hope someone can help. I've got a 30g 5th generation ipod which Ive had no problems with until recently but now when I connect it to my laptop itunes opens as normal but then doesn't respond. itunes doesn't appear to recognise my ipod and it is com

  • Layers in Pages ?

    Hello,     I have used Adobe Photoshop CS2 on my G4 in the past, but I was hoping to use Pages, manly to create flyers. I like using layers in Photoshop and I was wondering if there is such a feature in Pages. Pages may call it something different, b