Problems starting a Message Bridge on 8.1sp3

Question

Hi,
          We've been ruuning weblogic server 8.1 sp2 for sometime using a message bridge it has always startted transferring message automatically after a ser ver restart, you see messages such as :
          Oct 12, 2004 10:27:10 AM BST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 16
          1.2.231.193>
          <Oct 12, 2004 10:27:10 AM BST> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to the repository.>
          <Oct 12, 2004 10:27:10 AM BST> <Info> <Configuration Management> <BEA-150007> <The booted configuration ./config.xml has been backed up at
          /qv/dev/capg002b/weblogic/./config.xml.booted.>
          <Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200020> <Bridge "BLS-BLP Messaging Bridge" is stopped.>
          <Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200033> <Bridge "BLS-BLP Messaging Bridge" is obtaining connections to the two adapters.>
          <Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200032> <Bridge "BLS-BLP Messaging Bridge" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.>
          <Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200030> <Bridge "BLS-BLP Messaging Bridge" is configured to work in "Exactly-
          once" mode, and it is actually working in "Exactly-once" mode.>
          <Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200028> <The bridge "BLS-BLP Messaging Bridge" has started transferring messages.>
          <Oct 12, 2004 10:28:09 AM BST> <Info> <MessagingBridge> <BEA-200028> <The bridge "BLS-BLP Messaging Bridge" has started transferring messages.>
          <Oct 12, 2004 10:28:34 AM BST> <Info> <MessagingBridge> <BEA-200028> <The bridge "BLS-BLP Messaging Bridge" has started transferring messages.>
          but with 8.1sp3 the Message Bridge does NOT automatically start transferring messges after a restart and you get messgaes like this :
          <Oct 12, 2004 10:42:24 AM BST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 161.2.231.193>
          <Oct 12, 2004 10:42:24 AM BST> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to the repository.>
          <Oct 12, 2004 10:42:24 AM BST> <Info> <Configuration Management> <BEA-150007> <The booted configuration ./config.xml has been backed up at /qv/dev/capg002b/weblogic/./config.xml.booted.>
          <Oct 12, 2004 10:43:07 AM BST> <Info> <MessagingBridge> <BEA-200020> <Bridge "BLS-BLP Messaging Bridge" is stopped.>
          <Oct 12, 2004 10:43:07 AM BST> <Info> <MessagingBridge> <BEA-200033> <Bridge "BLS-BLP Messaging Bridge" is obtaining connections to the two adapters.>
          <Oct 12, 2004 10:43:07 AM BST> <Info> <MessagingBridge> <BEA-200032> <Bridge "BLS-BLP Messaging Bridge" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.>
          <Oct 12, 2004 10:43:07 AM BST> <Info> <MessagingBridge> <BEA-200030> <Bridge "BLS-BLP Messaging Bridge" is configured to work in "Exactly-once" mode, and it is actually working in "Exactly-once" mode.>
          with sp3 the message transfer needs to be started manually from the browser console.
          So my questing : why is bridge start up not automatic in sp3, bug ? or feature ?
          thanks
          justin

Answer 1

I've got some more info on this, and it gets stranger !!
          Basically I upgraded another system that uses Message Briging to sp3, and miraculuously, the transfer DID start automatically as desired. Very confusing ! so I compared the MessagingBridge stanzas in the config.xml for each system:
          this from the "broken" system where the bridge does not automatically start :
          <MessagingBridge Name="DStoMHMessagingBridge"
          QualityOfService="Exactly-once"
          SourceDestination="DStoMHSourceDestination" Started="true"
          TargetDestination="DStoMHTargetDestination" Targets="datasourceCluster"/>
          and this from the system where the bridge DOES automatically start :
          <MessagingBridge BatchSize="1" Name="BLS-BLP Messaging Bridge"
          SourceDestination="BLS-BLP Bridge Source Destination"
          Started="true"
          TargetDestination="BLS-BLP Bridge Target Destination" Targets="smpd289-bls1"/>
          I noticed that
          QualityOfService="Exactly-once"
          was missing from the working system, so removed it from the broken system. And sure enough the bridge transfer DID start automically, when it had'nt done before. Problem fixed.
          So there are several questions :
          1. Why does the QualityOfService setting have an impact on whether the Bridge starts automatically ?
          2. When you look at the web console on both the working and broken original systems and on the "broken" system with the QualityOfService="Exactly-once" line removered, It still says Exectly-once on the webpage. So Why this miss-match between whats contained in config.xml and whats shown on the webconsole ?