Exif "subject distance", shows in Bridge 5, gone in Bridge 6

Just made the switch from CS5 to CS6.  The Camera Data (Exif) panel in Bridge 5 gives me the Subject Distance value.  In Bridge 6 that field is not shown.  Under Preferences>Metadata, the Subject Distance field is check in both versions.  What has happened to this datum in Bridge 6?

Curt Y,
Thanks for your response.  I was aware of the thread you reference.  In fact I have implemented the excellent workaround described by Paul Riggott in that thread. 
Nevertheless that thread fails to provide an answer to the original question:  Why is subject distance correctly displayed in Bridge 5 and that field completely absent in Bridge 6.
In my case this is true for both native NEF files and when the same file is converted to DNG. 
It is true for both old and recent files and for files from D700 and D800 cameras. 
In the case of these two cameras, the Subject Distance is found under the Makers Notes but is not found under the Exif data as reported by ExifToolGUI.  This last finding confirms the observation of DLC (reply #4) in the cited thread. 
However if one examines the advanced tab in file info, one finds the following:
In both Bridge 5 and Bridge 6 there is an entry under Exif Properties labeled "Subject Distance"
So the question remains: why is this datum displayed in the Camera Data (Exif) Panel of Bridge 5 but not in Bridge 6?  And what can be done to correct this glitch?
Addendum / Correction
I have just discovered the following:  Older (raw) files which had been previously opened with Bridge 5, regardless if they were edited or not, when now opened in Bridge 6 do show the Subject Distance in the Exif Panel.

Similar Messages

  • Subject Distance in EXIF Data

    Now that LR 2.6 reads EXIF Subject Distance into the catalogue, does anyone know how this information can be added for images that have been imported using previous versions of LR?
    Tony

    Thanks Ian,
    Read Metadata from File isn't the answer since doing this obliterates everything that has been added to the metadata since the original import, but does add the Subject Distance.  I'm using RAW (NEF) files without xmp sidecars.  If I save to xmp and then Read Metadata from File, it works.  I just hoped there might be a simpler way to get the Subject Distance into the catalogue.  I also have many jpg images in my catalogue (before I started shooting raw) and the xmp solution can't be applied to those, although I could save the metadata to the jpg files (I don't really want to do that either).  I originally started with a Nikon D50 and those images have Subject Distance in their Exif data, so the information is there for all my images, I just need an easy way to get it into the catalogue.

  • Where has the preview panel gone is Bridge CS5?

    Today when I opened up Bridge, the preview panel on the right hand side has disappeared. It shows as being selected when I go to the Window Menu but it isn't there. The scroll bar is also missing so I can't view all of the thumbnails. Does anyone have any ideas about why this has happened and how I can return it to it's normal format? Thanks, Michelle.

    Fantastic. Thank you, much appreciated
    Date: Mon, 16 May 2011 02:22:18 -0600
    From: [email protected]
    To: [email protected]
    Subject: Where has the preview panel gone is Bridge CS5?
    No, but you can choose Reset Workspace from the workspace menu to get it back to normal.
    >

  • CS6 Bridge "Not Displaying Subject Distance Information in Exif Data"

    In Bridge CS5 the "Subject Distance" information is displayed for Zoom lenses which report distance information, under the Camera Data (Exif) panel.
    In Bridge CS6 either 64 or 32 bit, no "Subject Distance" information is displayed for the same files, which report this information under CS5 bridge.
    I have checked that the "Subject Distance" is checked and turned on under the preferences section. Not sure if the data is either not being read or just not being displayed.

    Thanks Ian,
    Read Metadata from File isn't the answer since doing this obliterates everything that has been added to the metadata since the original import, but does add the Subject Distance.  I'm using RAW (NEF) files without xmp sidecars.  If I save to xmp and then Read Metadata from File, it works.  I just hoped there might be a simpler way to get the Subject Distance into the catalogue.  I also have many jpg images in my catalogue (before I started shooting raw) and the xmp solution can't be applied to those, although I could save the metadata to the jpg files (I don't really want to do that either).  I originally started with a Nikon D50 and those images have Subject Distance in their Exif data, so the information is there for all my images, I just need an easy way to get it into the catalogue.

  • Lens-to-subject distance in EXIF data

    I'm looking for lens-to-subject distance in my EXIF data (Canon 7D Mk II).  Is it captured?And if so, how do I view it?

    Hi wildimagesfla!
    Thanks for posting.
    The distance between the lens and the subject being focused on is not something that is captured and recorded in the EXIF information.
    Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

  • Camera data subject distance missing in CS6

    This is another strange problem.  I noticed that recent shots with any of 3 Nikon cameras, D3, D4 and D300s lack the distance data in CS6 Bridge.  But older shots do.  I narrowed the change to about June 10, 2012.  Before this they have the subject distance and June 12 pictures and later don't.  It seems that this is the time when I configured or installed CS6 which was a free upgrade after getting CS5.1
    When I open CS5.1 Bridge though, even the most recent shots have subject distance.

    Curt Y,
    Thanks for your response.  I was aware of the thread you reference.  In fact I have implemented the excellent workaround described by Paul Riggott in that thread. 
    Nevertheless that thread fails to provide an answer to the original question:  Why is subject distance correctly displayed in Bridge 5 and that field completely absent in Bridge 6.
    In my case this is true for both native NEF files and when the same file is converted to DNG. 
    It is true for both old and recent files and for files from D700 and D800 cameras. 
    In the case of these two cameras, the Subject Distance is found under the Makers Notes but is not found under the Exif data as reported by ExifToolGUI.  This last finding confirms the observation of DLC (reply #4) in the cited thread. 
    However if one examines the advanced tab in file info, one finds the following:
    In both Bridge 5 and Bridge 6 there is an entry under Exif Properties labeled "Subject Distance"
    So the question remains: why is this datum displayed in the Camera Data (Exif) Panel of Bridge 5 but not in Bridge 6?  And what can be done to correct this glitch?
    Addendum / Correction
    I have just discovered the following:  Older (raw) files which had been previously opened with Bridge 5, regardless if they were edited or not, when now opened in Bridge 6 do show the Subject Distance in the Exif Panel.

  • Display subject distance in Lightroom metadata

    The EXIF data in the Lightroom database includes SubjectDistance but this does not appear in the Metadata windows.  It would be very handy if it was.
    (forgive me if I have overlooked it).
    (note: SubjectDistance is not recorded for all camera/lens combinations, eg 7D and Tamron does not)
    As a further and natural extension, you could then easily calculate and display Depth of Field estimates (Near/Far limits and total DOF)

    Digging deeper ...
    The Lightroom database has a table called AgHarvestedEXIFData, which has columns for aperture, focal length etc but not subject distance.
    There is also a table called agAdditionalMetadata.  This has a column XMP which is xml format EXIF data etc, including <SubjectDistance>
    So the data is in the database but not in the table which is used by the MetaData tab in the Default view option.
    So why does it sometimes show for you?
    The clue is the heading Shooting Info on your screenshot.  I don't get that.  However if I switch though to the EXIF option instead of Default the list of EXIF data fields changes, enough to make me think it is using different code.  I think in some circumstances it is clever enough to extract the data from the XMP field and push it into this form. I picked up a few 'Shooting Info' threads in the forums, bemoaning the loss of this data too.  Why sometimes and not others?  It might be your camera model/lens/focus mode, but possibly did you shoot tethered?
    Here is a sample of some of the XMP data - as you can see there is a lot of useful shooting information available but not accessible!
    <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.2-c020 1.124078, Tue Sep 11 2007 23:21:40        ">
    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""
        xmlns:tiff="http://ns.adobe.com/tiff/1.0/">
       <tiff:Make>Canon</tiff:Make>
       <tiff:Model>Canon EOS 7D</tiff:Model>
       <tiff:Orientation>1</tiff:Orientation>
       <tiff:ImageWidth>5184</tiff:ImageWidth>
       <tiff:ImageLength>3456</tiff:ImageLength>
      </rdf:Description>
      <rdf:Description rdf:about=""
        xmlns:exif="http://ns.adobe.com/exif/1.0/">
       <exif:ExifVersion>0221</exif:ExifVersion>
       <exif:ExposureTime>1/160</exif:ExposureTime>
       <exif:ShutterSpeedValue>7321928/1000000</exif:ShutterSpeedValue>
       <exif:FNumber>5/1</exif:FNumber>
       <exif:ApertureValue>4643856/1000000</exif:ApertureValue>
       <exif:ExposureProgram>3</exif:ExposureProgram>
       <exif:ISOSpeedRatings>
        <rdf:Seq>
         <rdf:li>100</rdf:li>
        </rdf:Seq>
       </exif:ISOSpeedRatings>
       <exif:DateTimeOriginal>2010-12-30T15:56:15.83+13:00</exif:DateTimeOriginal>
       <exif:DateTimeDigitized>2010-12-30T15:56:15.83+13:00</exif:DateTimeDigitized>
       <exif:ExposureBiasValue>0/1</exif:ExposureBiasValue>
       <exif:MaxApertureValue>4625/1000</exif:MaxApertureValue>
       <exif:SubjectDistance>317/100</exif:SubjectDistance>
       <exif:MeteringMode>5</exif:MeteringMode>
       <exif:Flash rdf:parseType="Resource">
        <exif:Fired>False</exif:Fired>
        <exif:Return>0</exif:Return>
        <exif:Mode>2</exif:Mode>
        <exif:Function>False</exif:Function>
        <exif:RedEyeMode>False</exif:RedEyeMode>
       </exif:Flash>
       <exif:FocalLength>70/1</exif:FocalLength>
       <exif:CustomRendered>0</exif:CustomRendered>
       <exif:ExposureMode>0</exif:ExposureMode>
       <exif:WhiteBalance>0</exif:WhiteBalance>
       <exif:SceneCaptureType>0</exif:SceneCaptureType>
       <exif:FocalPlaneXResolution>5184000/907</exif:FocalPlaneXResolution>
       <exif:FocalPlaneYResolution>3456000/595</exif:FocalPlaneYResolution>
       <exif:FocalPlaneResolutionUnit>2</exif:FocalPlaneResolutionUnit>
       <exif:PixelXDimension>5184</exif:PixelXDimension>
       <exif:PixelYDimension>3456</exif:PixelYDimension>
      </rdf:Description>
      <rdf:Description rdf:about=""
        xmlns:xap="http://ns.adobe.com/xap/1.0/">
       <xap:ModifyDate>2010-12-30T15:56:15.83+13:00</xap:ModifyDate>
       <xap:CreateDate>2010-12-30T15:56:15.83+13:00</xap:CreateDate>
       <xap:MetadataDate>2010-12-30T19:48:23.959-13:00</xap:MetadataDate>
       <xap:Rating>2</xap:Rating>
      </rdf:Description>
      <rdf:Description rdf:about=""
        xmlns:dc="http://purl.org/dc/elements/1.1/">
       <dc:creator>
        <rdf:Seq>
         <rdf:li>Paul Willyams</rdf:li>
        </rdf:Seq>
       </dc:creator>
       <dc:rights>
        <rdf:Alt>
         <rdf:li xml:lang="x-default">Copyright Paul Willyams</rdf:li>
        </rdf:Alt>
       </dc:rights>
      </rdf:Description>
      <rdf:Description rdf:about=""
        xmlns:aux="http://ns.adobe.com/exif/1.0/aux/">
       <aux:SerialNumber>670502410</aux:SerialNumber>
       <aux:LensInfo>28/1 135/1 0/0 0/0</aux:LensInfo>
       <aux:Lens>EF28-135mm f/3.5-5.6 IS USM</aux:Lens>
       <aux:LensID>178</aux:LensID>
       <aux:ImageNumber>0</aux:ImageNumber>
      <aux:ApproximateFocusDistance>317/100</aux:ApproximateFocusDistance>
       <aux:FlashCompensation>0/1</aux:FlashCompensation>
       <aux:Firmware>1.1.0</aux:Firmware>
      </rdf:Description>
    etc

  • When I attempt to apply a lens profile in the Develop module the only choices are for the Fujifilm X100/S/T even though in the Library module the EXIF data correctly shows the camera as the X-T1 and the precise lens used to take the picture. How do I get

    When I attempt to apply a lens profile in the Develop module the only choices are for the Fujifilm X100/S/T even though in the Library module the EXIF data correctly shows the camera as the X-T1 and the precise lens used to take the picture. How do I get the right profile available?

    First, the required profile needs to be present. LR 5.4 supports the X-T1 in terms of understanding its Raw format, but will not come with a profile for every lens which can be mounted onto that.
    A profile is made for each specific lens, as mounted on a certain camera. It can also be used with pictures taken on a different (reasonably similar) camera body than the one originally used during profiling. This is subject to the sensor format: you can employ a given lens profile made for full frame, on an image from a crop sensor behind the same lens - but not vice versa.
    Next, the image type needs to correspond to the image type which has been built into the profile: Raw, or non-Raw.
    Lightroom offers only profiles of the right type for the image(s) concerned. There are many more provided for correcting camera Raw, than for correcting camera JPG. That is also the case with additional profiles, e.g. those accessed via the Adobe lens profile downloader utility.
    Finally, in the event that there simply is no profile out there for a given lens, it is not particularly difficult (though a little tedious) for the end user to generate one, using a further Adobe utility which is downloadable as a package, including a range of checkerboard calibration targets, each of which needs to be printed at a stated physical size.

  • Sony: Lens Profile Creator knows the subject distance, ACR does not

    When making a lens profile for a Sony alpha DSLR, lens profile creator identifies the focus distance, and processes each distance accordingly. However, when loaded in ACR (or PS lens correction filter), the software does not display the distance. Why can LPC read the subject distance and ACR cannot?

    function(){return A.apply(null,[this].concat($A(arguments)))}
    el_floz wrote:
    The Creator, however, determines / calculates the subject distance itself.
    Is this a complicated way of saying "God only knows"? 
    In all seriousness, if one program can calculate a piece of info from a file, so could another.  The designers may just not have chosen to dig so deeply into the manufacturer-specific data as to do so.  Or, as appears to be the case here, the information is derived from known subject material in the image itself.
    -Noel

  • 1300 Root-Bridge and Non-Root Bridge setup

    I have two 1300s that I am trying to set up as Root Bridge and Non-Root Bridge, however, everytime i specify one of them as a Non-Root bridge, the radio0 interface becomes disabled. The only option that i am able to pick that enables the radio0 interface is "Access Point", which is what am trying to avoid it being.
    Can anybody help me figure out how to go about this

    A non-root's radio will show as disabled if it cannot find the root AP to associate to. Make sure you have "infrastructure-ssid" configured under the SSID on both the root and non-root bridges. Also depending on code versions you may have to configure the distance command under the radio interface on the root.

  • Does Adobe Photoshop Elements come bundled with Adobe Bridge?  Or is Bridge a separate purchase?

    Does Adobe Photoshop Elements come bundled with Adobe Bridge?  Or is Bridge a separate purchase?

    Apparently there was a change in Elements 9.
    From the PsE forum:
    Bridge is no longer included with PSE. If you buy PSE anywhere except the Mac App Store you get Organizer instead. The app store version doesn't have organizer.
    and from a link therein:
    A lot of Mac folks are unhappy about Adobe’s decision to include Organizer with Elements 9 in place of Adobe Bridge, which came with previous Mac versions. (The Organizer used to be just for Windows.) If you have an older version of PSE that included Bridge, you can still use it with Elements 9…

  • Can Wireless bridge be a transport bridge for another WLAN?

    Can I setup a bridge as a transport bridge between two bridges as following?
    LAN1---B1---B2---B3---LAN2
    ______________\B4---LAN3
    How should I setup for root and non-root in this case?
    Can I do aggregation if I have 2 bridges in location 1 and 2 for redundancy?

    Instead of using the "Assist Me" mode, you will want to use the "Manual Setup" mode to configure both AirPorts for an extended wireless network.
    Dynamic WDS - Extending a Wireless Network Setup
    If practical, place the base stations in near proximity to each other during the setup phase. Once done, move them to their desired locations.
    Open AirPort Utility, and then, select the base station that will connect to the Internet.
    Choose Manual Setup from the Base Station menu, or double-click the base station to open the configuration in a separate window. Enter the base station password if necessary.
    Click AirPort in the toolbar, and then, click Wireless.
    Choose “Create a wireless network” from the Wireless Mode pop-up menu, and then, select the “Allow this network to be extended” checkbox.
    Next, select the base station that will extend this network, and then, choose Manual Setup from the Base Station menu, or double-click the base station to open its configuration in a separate window. Enter the base station password if necessary.
    Choose “Extend a wireless network” from the Wireless Mode pop-up menu, and then, choose the network you want to extend from the Network Name pop-up menu.
    Enter the base station network and base station password if necessary.
    Click Update to update the base station with new network settings.
    (ref: Pages 43-44 of Apple AirPort Networks.)

  • Bridge doesn't Start, Bridge mini is running (PS6)MacPro, i7, OSX 10.7.4

    Bridge doesn't Start, Bridge mini is running (PS6)MacPro, i7, OSX 10.7.4
    Horst Koch, 
    Community Member
    23.05.2012 13:29
    Bridge stürzt immer ab, bzw. startet erst gar nicht, Bridge Mini unter PS 6 läuft
    MacPro, i7, OSX 10.7.4 (Neueinrichtung)
    Adobe reader 10.1 läßt sich nicht starten
    meldung "interner fehler ist aufgetrten"
    Update PS 6 läßt sich nicht installieren
    möchte Zugriff auf eine nicht vorhandne Library/User Datei

    Have you tried resetting preferences by holding down Option key and starting Bridge?  Should get reset window with 3 options.  Choose all 3.

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

  • Root-Bridge and Non-Root Bridge Support

    I was wondering if the ISR Routers (Cisco 1811w) support the root-bridge and non-root-bridge feature. If not is there another device apart from the 1310 and 1410 bridges that support this feature?
    Thank You,
    VT

    Hi VT,
    The ISR AP supports both of these roles;
    Access Point Link Role Flexibility
    Access Point Link Role Flexibility allows access point radios to operate in a combination of radio roles,
    such as access point root, bridge root (with or without clients), bridge nonroot (with or without clients).
    This provides a more flexible deployment scheme to support the various applications requirement. Note
    that the ISR AP does not support access point repeater and WGB.
    Wireless Non-Root Bridge
    The wireless non-root bridge allows the access point radio to operate as the remote node in a point to
    point or point to multi-point network.
    Wireless Root Bridge
    The wireless root bridge role provides support for both point-to-point or point to multi-point bridging.
    http://www.cisco.com/en/US/docs/ios/12_4/12_4x/release/notes/rn1800xj.html
    Hope this helps!
    Rob

Maybe you are looking for