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

Similar Messages

  • Messaging Bridge on WLS 6.1 sp3

              Hi
              I'm having a problem setting up a messaging bridge on WLS6.1 (sp3)
              The source destination (MQseries -> bridge) uses com.ibm.mq.jms.MQXAQueueConnectionFactory.
              I use a startup class to create JNDI entries for the MQ queue and qmanager.
              The target (bridge -> JMS queue) uses weblogic.jms.client.JMSXAConnectionFactory.
              Both source and target destinations use the eis.jms.WLSConnectionFactoryJNDIXA
              adapter JNDI name.
              When I start the server, I get these 2 messages in the log:
              Warning> <Connector> << Weblogic Messaging Bridge Adapter (Local TX) > Connection
              Pool has been initialized with no connections.>
              <Info> <Connector> << Weblogic Messaging Bridge Adapter (Local TX) > Connection
              Pool initial
              ization has completed successfully.>
              followed by :
              <Info> <MessagingBridge> <Bridge "MQJMSMessaging Bridge" suceesfully found the
              two adapters configured for it.>
              And when I try to monitor the messaging bridge runtime from the console, it shows
              "Found two adapters and about to make connections" but nothing happens after that.
              Any message sent to the MQ queue is not picked up.
              I'm not sure if I'm doing something wrong.
              Any help would be greatly appreciated.
              Vic
              

    Hi Victor,
              First of all, are you running any batches? You need to get the latest bridge
              batch for 6.1sp3 from BEA Customer Support.
              Second, I noticed that you are using XA. I don't know which MQ release you
              are using, but there was a limitaion in the previous MQSeries releases that the queue
              manager has to be collcated with the client (which is the bridg ein our case) in order for XA
              to work. You may want to check that out.
              If the problem persists after you take care of these two issues,
              you could turn on the bridge debug to see what is wrong.
              You probably need to take a look at the bridge FAQ (where you can
              find out how to turn on the debug) at
              http://e-docs.bea.com/wls/docs61/faq/msgbridge.html
              Another useful doc is the white paper on dev2dev for using foreign JMS in WLS.
              http://dev2dev.bea.com/resourcelibrary/whitepapers/jmsproviders.jsp
              Thanks,
              Dongbo
              Victor wrote:
              > Hi
              > I'm having a problem setting up a messaging bridge on WLS6.1 (sp3)
              >
              > The source destination (MQseries -> bridge) uses com.ibm.mq.jms.MQXAQueueConnectionFactory.
              > I use a startup class to create JNDI entries for the MQ queue and qmanager.
              >
              > The target (bridge -> JMS queue) uses weblogic.jms.client.JMSXAConnectionFactory.
              >
              > Both source and target destinations use the eis.jms.WLSConnectionFactoryJNDIXA
              > adapter JNDI name.
              >
              > When I start the server, I get these 2 messages in the log:
              >
              > Warning> <Connector> << Weblogic Messaging Bridge Adapter (Local TX) > Connection
              > Pool has been initialized with no connections.>
              > <Info> <Connector> << Weblogic Messaging Bridge Adapter (Local TX) > Connection
              > Pool initial
              > ization has completed successfully.>
              >
              > followed by :
              > <Info> <MessagingBridge> <Bridge "MQJMSMessaging Bridge" suceesfully found the
              > two adapters configured for it.>
              >
              > And when I try to monitor the messaging bridge runtime from the console, it shows
              > "Found two adapters and about to make connections" but nothing happens after that.
              >
              > Any message sent to the MQ queue is not picked up.
              >
              > I'm not sure if I'm doing something wrong.
              > Any help would be greatly appreciated.
              >
              > Vic
              

  • Unable to create a JMS Message bridge between Weblogic 12c and Weblogic 8.1

    Hi,
    I am unable to successfully create a Message Bridge between Weblogic 12.1.1.0 and Weblogic 8.1. The error message being received is:
    eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://localhost:8001, user name = System) ">
    The error on the monitoring tab is WARN: failed to connect to target.
    Both domains are deployed on one box for testing purposes. The bridge itself is deployed on Weblogic 12c. The areas of config that may be of interest are:
    <server>
    <name>AdminServer</name>
    <listen-address></listen-address>
    </server>
    <messaging-bridge>
    <name>Bridge</name>
    <target>AdminServer</target>
    <source-destination>JMSBridgeSource12c</source-destination>
    <target-destination>JMSBridgeTarget81</target-destination>
    <selector>Test</selector>
    <quality-of-service>Exactly-once</quality-of-service>
    <qos-degradation-allowed>false</qos-degradation-allowed>
    <durability-enabled>true</durability-enabled>
    <idle-time-maximum>60</idle-time-maximum>
    <async-enabled>true</async-enabled>
    <started>true</started>
    <preserve-msg-property>false</preserve-msg-property>
    </messaging-bridge>
    <app-deployment>
    <name>jms-xa-adp</name>
    <target>AdminServer</target>
    <module-type>rar</module-type>
    <source-path>D:\ORACLE~3\WLSERV~1.1\server\lib\jms-xa-adp.rar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <jms-bridge-destination>
    <name>JMSBridgeSource12c</name>
    <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
    <user-name>System</user-name>
    <user-password-encrypted>{AES}nfFzhs+0J/O2Cenf0g4zDsDyvIKENMF7cZ5sAVUehX0=</user-password-encrypted>
    <classpath></classpath>
    <connection-factory-jndi-name>JMSConnectionFactory12c</connection-factory-jndi-name>
    <connection-url>t3://localhost:7001</connection-url>
    <destination-jndi-name>JMSQueue12c</destination-jndi-name>
    </jms-bridge-destination>
    <jms-bridge-destination>
    <name>JMSBridgeTarget81</name>
    <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
    <user-name>System</user-name>
    <user-password-encrypted>{AES}eBkO46cHvtrzEraOMIOdXow6WvEAtA4NCUDTQ4mC+9w=</user-password-encrypted>
    <classpath></classpath>
    <connection-factory-jndi-name>JMSConnectionFactory81</connection-factory-jndi-name>
    <connection-url>t3://localhost:8001</connection-url>
    <destination-jndi-name>JMSQueue81</destination-jndi-name>
    </jms-bridge-destination>
    I have enforced global trust between the two domains. I have disabled the guest user on the 8.1 domain but can’t see where to do this on 12c.
    Any suggestions would be much appreciated.
    Regards
    John
    Edited by: 958336 on 13-Sep-2012 03:11

    Thanks for the recommendation. Unfortunately it did not help solve the problem.
    I have managed to get a JMS bridge working between 12c and 8.1 by including the 8.1 weblogic.jar on the classpath. This setup was using eis.jms.WLSConnectionFactoryJNDINoTX.
    After trying to use the adapter that supports transactions, WLSConnectionFactoryJNDIXA I received the following error:
    java.lang.IllegalStateException: can only be called from server
    Is this because the Weblogic 12c server now views the 8.1 server as being foreign?

  • Message bridge between two instances

    I am trying to setup messaging bridge between two instances of weblogic server.
    Can the second instance belong to a different domain? If yes how to configure it?

    Yes, you can configure a messaging bridge to work between two WebLogic domains.
    The general instructions of configuring a message bridge, including the bridge instance itself, the bridge destinations and the adapter, can be found at
    http://edocs.bea.com/wls/docs103/bridge/basics.html#wp1168461
    The only extra thing that you may need to take care of for the cross-domain case is to configure cross-domain security as instructed at
    http://edocs.bea.com/wls/docs103/bridge/wls_interop.html#wp1126873
    Regards,
    Dongbo

  • WLS 6.1 SP3 and apache plugin

    Hello,
    I have WLS 6.1 SP3 and apache 1.3.26 installed on solaris 8.
    I enabled the weblogic Weblogic Plug-In Enabled for my wls server and
    then I configured my apache server like the following:
    1) I used mod_wl.so that comes with wls under
    \bea\wlserver6.1\lib\solaris
    2) Then I loaded that module using APACHE_HOME/bin/apxs -i -a -n
    weblogic mod_wl.so
    When I load the module I get the following:
    [Thu Jan 15 10:05:53 2004] [warn] Loaded DSO libexec/mod_wl.so uses
    plain Apache 1.3 API, this module might crash under EAPI!
    please recompile it with -DEAPI)
    /usr/apache/bin/apachectl start: httpd started
    I don't understand that message
    3) The following lines were added to httpd.conf:
    LoadModule weblogic_module libexec/mod_wl.so
    AddModule mod_weblogic.c
    4) Then I added the following to the httpd.conf:
    <IfModule mod_weblogic.c>
    WebLogicHost 10.1.10.205(my weblogic IP)
    WebLogicPort 7020 (my weblogic port)
    FileCaching On
    MatchExpression *.jsp
    </IfModule>
    The problem is that the apache server is not able to redirect the jsp
    calls to the WLS server and I'm always getting "The page cannot be
    displayed"
    Any information that might guide me to solve this problem is appreciated
    Itani Mohamed
    SoftSolutions
    Tel: +961.1.90.11.70 ext:141
    Fax: +961.1.90.11.75
    www.softsolutions.fr

    Itani,
    Please try the mod-wl-ssl.so module shipped with weblogic, as this module is compiled with -DEAPI flag

  • Messaging Bridge Between 2 Weblogic Server

              Hi,
              I would like to create a messaging bridge between two Weblogic Server on two different
              server. One on Windows NT and one on Solaris.
              I have created one queue on NT and one other queue on Solaris, and the corresponding
              JMS Bridge destination for each queue on one server (and the other to test).
              And on one server (and the other to test), I have created a messaging bridge to
              transfert messages from one queue to the other, but I have a message on the Weblogic
              Server.
              javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
              ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              url = http://usv9007.rtc.ch:7001, user name = null, password = null
              at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
              at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
              at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
              at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
              at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
              at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
              at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
              request.>
              Parameter for the distant queue
              Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
              ressources for the ConnectionFactory and the corresponding adapter)
              Connection URL : http://SolarisIP:7001
              InitialContextFactory : weblogic.jndi.WLInitialContextFactory
              ConnectionFactory JNDI Name : myConnectionFactory
              Destination JNDI Name : myQueueSolaris
              Destination Type : Queue
              I don't understand why I have this error, because all the parameters are correct,
              and the http tunneling is activated.
              Could you help me to configure correctly this messaging bridge ???
              Thanks a lot.
              

    Looks like the error occurred on the target destination
              of the bridge. One way to find out if your configuration
              is correct is to use the same parameters (initial context factory,
              url, username and password) to get a connection to the
              target server from a standalone client.
              Dongbo
              Seb wrote:
              >
              > Hi,
              >
              > I would like to create a messaging bridge between two Weblogic Server on two different
              > server. One on Windows NT and one on Solaris.
              >
              > I have created one queue on NT and one other queue on Solaris, and the corresponding
              > JMS Bridge destination for each queue on one server (and the other to test).
              >
              > And on one server (and the other to test), I have created a messaging bridge to
              > transfert messages from one queue to the other, but I have a message on the Weblogic
              > Server.
              >
              > -----------------------------------------------------------------
              > javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
              > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              > url = http://usv9007.rtc.ch:7001, user name = null, password = null
              > at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
              > at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
              > at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
              > at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
              > at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
              > at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
              > at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
              > <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
              > request.>
              > -----------------------------------------------------------------
              >
              > Parameter for the distant queue
              >
              > Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
              > ressources for the ConnectionFactory and the corresponding adapter)
              > Connection URL : http://SolarisIP:7001
              > InitialContextFactory : weblogic.jndi.WLInitialContextFactory
              > ConnectionFactory JNDI Name : myConnectionFactory
              > Destination JNDI Name : myQueueSolaris
              > Destination Type : Queue
              >
              > I don't understand why I have this error, because all the parameters are correct,
              > and the http tunneling is activated.
              >
              > Could you help me to configure correctly this messaging bridge ???
              >
              > Thanks a lot.
              

  • Message Bridge in wls 61 sp3

              Hi there,
              i try to install wls61 sp3 for evaluating the messaging bridge and i could not find
              the connectors (jms-xa-adp.rar, jms-notran-adp.rar, jms-notan-adp51.jar)
              the documentation says they sould be in WL_HOME\server\lib, but there are not there
              Where can i find them ?
              Thanks
              Bye
              Sven
              

              1) Ok, i took theese files, but to deploy a connector to a managed server, i have
              to but the jmsadapte.jar-file from the *.rar-file to the classpath of the managed
              server
              2) Starting a managed server with this configuration i get the following error:
              <Jul 11, 2002 4:38:51 PM CEST> <Info> <Connector> <Unable to determine Resource Principal
              for Container Managed Security Context.>
              <Jul 11, 2002 4:38:52 PM CEST> <Warning> <Connector> << Weblogic Messaging Bridge
              Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException: ConnectionFactory:
              jms.connection.BridgeConnectionFactoryXA not found on createManagedConnection.>
              <Jul 11, 2002 4:38:52 PM CEST> <Error> <Connector> << Weblogic Messaging Bridge Adapter
              (XA) > Error making initial connections for pool. Reason: CreateManagedConnection
              Error: ConnectionFactory: jms.connection.BridgeConnectionFactoryXA not found>
              <Jul 11, 2002 4:38:52 PM CEST> <Warning> <Connector> << Weblogic Messaging Bridge
              Adapter (XA) > Connection Pool has been initialized with no connections.>
              So what am i doing wrong ??
              Thanks
              Bye
              Sven
              "Dongbo Xiao" <[email protected]> wrote:
              >After all, the adapters for the Messaging Bridge are missing
              >in the 6.1SP3 package. There is a temporary patch for this on
              >the way. Meanwhile, you can download the adapters from
              >ftp://edownload:[email protected]/pub/downloads/MessagingBridge61.zip
              >
              >Alternatively you can copy the adapters from WL_HOME\server\lib
              >in the 7.0 package into 6.1SP3 installation WL_HOME\lib. If one
              >side of your bridge is WebLogic Server 5.x, you need
              >jms51-interop.jar file as well, which is in the same directory as the
              >adapters.
              >
              >Dongbo
              >
              >"Sven Roesner" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> Hi there,
              >> i try to install wls61 sp3 for evaluating the messaging bridge and i could
              >not find
              >> the connectors (jms-xa-adp.rar, jms-notran-adp.rar, jms-notan-adp51.jar)
              >> the documentation says they sould be in WL_HOME\server\lib, but there
              >are
              >not there
              >> ?!
              >> Where can i find them ?
              >> Thanks
              >> Bye
              >> Sven
              >
              >
              

  • Difference between WLS 6.1 SP2   and SP3

    I have recently tested my application in WLS 6.1 SP3 (who work normally in WLS
    6.1 SP2) , I have problem with my jsp page for merging a jsp in another
    What need I do to correct it ?

    Steven,
    The CGIServlet for WebLogic will not run a CGI that doesn't have an extension.
    Just add and extension to your executable and it should run fine.
    jeff
    "Steven" <[email protected]> wrote:
    Hi all,
    I am currently facing a problem with CGI binaries via CGIServlet on WLS
    6.1
    sp4. The web.xml file has been configured correctly as follows:
    -------- start of web.xml -----------
    <servlet>
    <servlet-name>CGIServlet</servlet-name>
    <servlet-class>weblogic.servlet.CGIServlet</servlet-class>
    <init-param>
    <param-name>cgiDir</param-name>
    <param-value>/web/bea6.1sp2/wlserver6.1/config/ngwapp/applications/NGWWebApp
    /cgi-bin</param-value>
    </init-param>
    <init-param>
    <param-name>*.pl</param-name>
    <param-value>/web/perl5/bin/perl5.00405</param-value>
    </init-param>
    <init-param>
    <param-name>*.cgi</param-name>
    <param-value>/web/perl5/bin/perl5.00405</param-value>
    </init-param>
    </servlet>
    <servlet-mapping>
    <servlet-name>CGIServlet</servlet-name>
    <url-pattern>/cgi-bin/*</url-pattern>
    </servlet-mapping>-------- end of web.xml ---------
    When a call is made to http://.../cgi-bin/dialogserver , this results
    in a
    404-File Not Found error.
    The contents of the cgi-bin directory have not been altered and I did
    not
    face this problem earlier when I was using sp2.
    It only happened after I upgraded to sp4. Can anyone help?
    best rgds,
    steven.

  • WLS 6.1 sp3 and XA and DB2

              Our configuration is:
              WLS 6.1 with sp3 on Solaris and DB2 7.2.7 on AIX running on remote server. Local
              DB2 client is installed on Solaris (LD_LIBRARY_PATH and other DB2 related variables
              are set accordingly).
              In some parts of our system we decided to use message-driven beans to process
              some work off side. In some of them we interact with database and send JMS messages
              to trigger some other MDBs. And we need all these operation to be one unit of
              work. Since we have operation on JMS and DB stores, we were forced to use XA and
              DB2 XA JDBC driver type 2.
              Most of the time things work fine ( always in our dev environment where WLS, DB2
              runs on the same Win2000 box), but rundomly we get JVM to crash on Solaris - like
              once a day or two. We are about to roll out to production but with these crashes
              we are confident about stablity of our app. We found that in most cases (but not
              all) those were related to the situation when DB2 connection were dropped or become
              invalid.
              On BEA website I found the information that WLS does not work in XA mode with
              DB2 7.1, because "APP driver falls back to NET driver". Does this still apply
              to DB2 7.2.7? If yes then I do not understand why Java->JNI call would fall back
              to Java->JNI->Java? Besides on IBM site there is nothing which says that type
              2 driver (so called APP one) requires JDBC client running on the same machine
              as database. If BEA claims that this indeed is the case, then it poses severe
              limitation to XA JDBC driver of IBM. Well, it means it is pretty much useless
              (who runs DB and app server on the same box ?)
              Today we just found new information about additional setting for XA connection
              pools that apply to DB2 and Sybase. For DB2 you need to set KeepXAConnTillTxComplete
              to true in your config.xml. We do not know yet if it is going to make things better
              (any input from BEA?)
              Can we get firm statement answer from BEA whether our configuration is supported
              or if not how we can achieve data/JMS integrity without using DB2 XA driver. Would
              using regular DB2 driver in pseudo-XA mode be a best work around, provided that
              the regular one is stable.
              How precisely WLS behave when it needs to orchestrate distributed transaction
              using pseudo-XA JDBC driver and fully-XA JMS server? In second phase does it first
              as DB to commit and if it succeeds it commits JMS, otherwise it rollbacks everything?
              We are very anxious to get our questions answered please.
              Thanks,
              Waldek
              

    Look for sometime around November. No exact date.
    Eric
    "Dominic Tulley" <[email protected]> wrote in message
    news:[email protected]..
    Thanks Eric,
    you know what I'm going to ask next right?
    Any ideas when SP4 comes out?
    Cheers,
    -Dominic
    "Eric Gross" <[email protected]> wrote in message
    news:[email protected]..
    The next version of Apache that we will support will be 2.0.42/2.0.43
    and
    the module for that will be included in the next Service Pack for6.1(SP4)
    and 7.0(SP2).
    The problem with Apache 2 is that when a new release comes out a newmodule
    needs to be compiled. Most of the time. For 2.0.42/2.0.43 this is notthe
    case.
    Regards,
    Eric
    "Dominic Tulley" <[email protected]> wrote in
    message
    news:3da3f246$[email protected]..
    I'm trying to set this up (initially just apache in front of a single
    WLS
    server but ultimately I want to put it in front of a cluster).
    I've installed Apache 2.0.40.
    I've copied the mod_wl_20.so file into the apache modules folder.
    I've edited the httpd.conf file and added the line:
    LoadModule weblogic_module modules/mod_wl_20.so
    When I run apache -t to check the configuration I get the following:
    C:\Program Files\Apache Group\Apache2\bin>apache -t
    Syntax error on line 173 of C:/Program Files/Apache
    Group/Apache2/conf/httpd.conf:
    Cannot load C:/Program Files/Apache Group/Apache2/modules/mod_wl_20.sointo
    server: The specified procedure could not be found.
    So what's going on here?
    Looking at previous postings it sounds like there's an issue with
    versions
    of apache after 2.0.39 but I can't find a download for that version.Also,
    it sounded like the issues were for WLS 7, not 6.1. Can this work
    with
    2.0.40 or am I wasting my time?
    If I get the mod_wl_20.so from dev2dev I get the "incompatible plugin"
    message that has been mentioned in this group already.
    Any suggestions appreciated,
    -Dominic

  • Using MessagingBridge for WLS6.1-SP3 and MQSeries 5.2

              I am trying to use the MessagingBridge with MQSeries 5.2.
              I have an MDB to consume messages from MQSeries queue. I created
              the MesageingBridge with source (being the MQS queue) and target
              (being WLS queue) but the bridge never channeled the messages from
              MQSeries source queue to WLS destination queue.
              Here are segments from config.xml:
              <JMSServer Name="JMSServer" Targets="myserver">
              <JMSQueue JNDIName="MQ_TARGET_QUEUE" Name="MQS Target Queue" StoreEnabled="default"/>
              </JMSServer>
              <JMSBridgeDestination
              Classpath="c:\MQSeries\ma88\samples\base;c:\MQSeries\ma88\lib\com.ibm.mq.jar;c:\MQSeries\ma88\lib\com.ibm.mqjms.jar;c:\MQSeries\ma88\lib\jms.jar;c:\MQSeries\ma88\lib\jndi.jar;c:\MQSeries\ma88\lib\fscontext.jar;c:\MQSeries\ma88\lib\providerutil.jar;c:\MQSeries\ma88\lib\connector.jar"
              ConnectionFactoryJNDIName="MQSeriesQueueManager"
              ConnectionURL="t3://127.0.0.1:7001"
              DestinationJNDIName="NotifMsgQueue" Name="MQSSourceDestination"/>
              <JMSBridgeDestination
              ConnectionFactoryJNDIName="WLSMQS_Connection_Factory"
              ConnectionURL="t3://127.0.0.1:7001"
              DestinationJNDIName="MQ_TARGET_QUEUE" Name="WLSTargetDestination"/>
              <MessagingBridge AsyncEnabled="true" DurabilityEnabled="true"
              Name="MQSeries Messaging Bridge" QOSDegradationAllowed="false"
              QualityOfService="Duplicate-okay"
              SourceDestination="MQS Source Destination" Started="true"
              TargetDestination="WLSTargetDestination" Targets="myserver"/>
              <StartupClass
              Arguments="QManager=QM_de8u5p,QMJNDIName=MQSeriesQueueManager,QManagerHost=127.0.0.1,
              QManagerPort=1414,NotificationsQueue=AppNotifQueue,NQJNDIName=NotifMsgQueue"
              ClassName="com.wbiex.MQSeriesStartup" FailureIsFatal="false"
              Name="MQSeriesStartup" Targets="myserver"/>
              Note: The MDB was able to access and consume messages off the MQSeries NotifMsgQueue
              queue
              without the bridge .
              Thank you very much for your help.
              

    First of all, CR081414_61sp3.jar is not supposed to be put in
              the CLASSPATH. It contains the adapter files you need to
              run the bridge. You don't need it anyway because CR081511_61sp3.jar
              contains the newer version of the adapter files. You need to put
              CR081414_61sp3.jar to your WLS CLASSPATH, and also extract the a
              adapter files (*.rar) and put them in the directory where your
              config.xml gets the adapters for deployment.
              Did you put all necessary MWSeries stuff in the WLS CLASSPATH
              and PATH. I am sure you have done something there to make
              your startup class work. Just make sure you have all of them.
              Them are listed in "Using Foreign JMS Providers with WebLogic Server".
              By the way, what is the error you got? Did you look at the server
              log?
              You can also turn on bridge debugging.
              -Dweblogic.Debug.DebugMessagingBridgeStartup=true
              -Dweblogic.Debug.DebugMessagignBridgeRuntime=true
              Debugging information will show up in the server log by default.
              Dongbo
              Jim Allen wrote:
              >
              > Thanks Dongbo,
              > I got both patches CR081511_61sp3.jar and CR081404_61sp3.jar
              > and added them to WLS CLASSPATH.
              > The connectionURLs for both source and target destinations are
              > the same because I am using WLS JNDI which is located in same
              > server. I have startup class that creates MQSeries connection
              > factory and a queue and binds them to WLS JNDI tree.
              > I also removed the MQSereis jars from AdapterClassPath but
              > still the Bridge is not working.
              >
              > Please help !! thanks very much again
              >
              > Dongbo Xiao <[email protected]> wrote:
              > >Something in your configuration looks wrong. The connectionURL
              > >you have for both the MQSeries bridge destination and WLS bridge
              > >destination are the same, which cannot be right. Another thing
              > >is that it is not recommended to put MQSeries stuff in AdapterClassPath.
              > >You have to have MQSeries stuff in the CLASSPATH and PATH for
              > >the WLS server that the bridge is running on.
              > >
              > >Take a look at the "Using Foreign JMS Providers with WebLogic Server
              > >"
              > >Tom recommended to you.
              > >
              > >Also you need to get the latest patches for 6.1SP3.
              > >
              > >Hope this helps.
              > >Dongbo
              > >
              > >
              > >Jim Allen wrote:
              > >>
              > >> I am trying to use the MessagingBridge with MQSeries 5.2.
              > >> I have an MDB to consume messages from MQSeries queue. I created
              > >> the MesageingBridge with source (being the MQS queue) and target
              > >> (being WLS queue) but the bridge never channeled the messages from
              > >> MQSeries source queue to WLS destination queue.
              > >> Here are segments from config.xml:
              > >>
              > >> <JMSServer Name="JMSServer" Targets="myserver">
              > >> <JMSQueue JNDIName="MQ_TARGET_QUEUE" Name="MQS Target Queue"
              > >StoreEnabled="default"/>
              > >> </JMSServer>
              > >> <JMSBridgeDestination
              > >> Classpath="c:\MQSeries\ma88\samples\base;c:\MQSeries\ma88\lib\com.ibm.mq.jar;c:\MQSeries\ma88\lib\com.ibm.mqjms.jar;c:\MQSeries\ma88\lib\jms.jar;c:\MQSeries\ma88\lib\jndi.jar;c:\MQSeries\ma88\lib\fscontext.jar;c:\MQSeries\ma88\lib\providerutil.jar;c:\MQSeries\ma88\lib\connector.jar"
              > >> ConnectionFactoryJNDIName="MQSeriesQueueManager"
              > >> ConnectionURL="t3://127.0.0.1:7001"
              > >> DestinationJNDIName="NotifMsgQueue" Name="MQSSourceDestination"/>
              > >> <JMSBridgeDestination
              > >> ConnectionFactoryJNDIName="WLSMQS_Connection_Factory"
              > >> ConnectionURL="t3://127.0.0.1:7001"
              > >> DestinationJNDIName="MQ_TARGET_QUEUE" Name="WLSTargetDestination"/>
              > >> <MessagingBridge AsyncEnabled="true" DurabilityEnabled="true"
              > >> Name="MQSeries Messaging Bridge" QOSDegradationAllowed="false"
              > >> QualityOfService="Duplicate-okay"
              > >> SourceDestination="MQS Source Destination" Started="true"
              > >> TargetDestination="WLSTargetDestination" Targets="myserver"/>
              > >> <StartupClass
              > >> Arguments="QManager=QM_de8u5p,QMJNDIName=MQSeriesQueueManager,QManagerHost=127.0.0.1,
              > >> QManagerPort=1414,NotificationsQueue=AppNotifQueue,NQJNDIName=NotifMsgQueue"
              > >> ClassName="com.wbiex.MQSeriesStartup" FailureIsFatal="false"
              > >> Name="MQSeriesStartup" Targets="myserver"/>
              > >>
              > >> Note: The MDB was able to access and consume messages off the MQSeries
              > >NotifMsgQueue
              > >> queue
              > >> without the bridge .
              > >>
              > >> Thank you very much for your help.
              

  • Bridge between JCAPS 5.1.3 and JCAPS6 using STC JMS

    Hi
    Would be glad if someone could help me configure Glassfish (that we use developing applications in JCAPS6) to use STC JMS. Do not really know how to setup the JMS Resources to access the message servers that we have configured in JCAPS 5.1.3. I try to use connectionURL property but glassfish does not like it, I get a warning in the log "The method setConnectionURL is not present in the class : com.sun.messaging.jms.ra.ManagedConnection"
    Br

    hi faldo,
    which connection url have you tried?
    are you talking about repository based projects?
    we are doing this by adding a"Unified JMS Ressource"server to the "Caps 6 environment" (bridge to STCMS ICAN 505)
    and pointing this ressource to "stcms://somehost:8888"
    regards chris

  • CGIServlet differences between WLS 6.1 sp2 and sp4?

    Hi all,
    I am currently facing a problem with CGI binaries via CGIServlet on WLS 6.1
    sp4. The web.xml file has been configured correctly as follows:
    -------- start of web.xml -----------
    <servlet>
    <servlet-name>CGIServlet</servlet-name>
    <servlet-class>weblogic.servlet.CGIServlet</servlet-class>
    <init-param>
    <param-name>cgiDir</param-name>
    <param-value>/web/bea6.1sp2/wlserver6.1/config/ngwapp/applications/NGWWebApp
    /cgi-bin</param-value>
    </init-param>
    <init-param>
    <param-name>*.pl</param-name>
    <param-value>/web/perl5/bin/perl5.00405</param-value>
    </init-param>
    <init-param>
    <param-name>*.cgi</param-name>
    <param-value>/web/perl5/bin/perl5.00405</param-value>
    </init-param>
    </servlet>
    <servlet-mapping>
    <servlet-name>CGIServlet</servlet-name>
    <url-pattern>/cgi-bin/*</url-pattern>
    </servlet-mapping>-------- end of web.xml ---------
    When a call is made to http://.../cgi-bin/dialogserver , this results in a
    404-File Not Found error.
    The contents of the cgi-bin directory have not been altered and I did not
    face this problem earlier when I was using sp2.
    It only happened after I upgraded to sp4. Can anyone help?
    best rgds,
    steven.

    Steven,
    The CGIServlet for WebLogic will not run a CGI that doesn't have an extension.
    Just add and extension to your executable and it should run fine.
    jeff
    "Steven" <[email protected]> wrote:
    Hi all,
    I am currently facing a problem with CGI binaries via CGIServlet on WLS
    6.1
    sp4. The web.xml file has been configured correctly as follows:
    -------- start of web.xml -----------
    <servlet>
    <servlet-name>CGIServlet</servlet-name>
    <servlet-class>weblogic.servlet.CGIServlet</servlet-class>
    <init-param>
    <param-name>cgiDir</param-name>
    <param-value>/web/bea6.1sp2/wlserver6.1/config/ngwapp/applications/NGWWebApp
    /cgi-bin</param-value>
    </init-param>
    <init-param>
    <param-name>*.pl</param-name>
    <param-value>/web/perl5/bin/perl5.00405</param-value>
    </init-param>
    <init-param>
    <param-name>*.cgi</param-name>
    <param-value>/web/perl5/bin/perl5.00405</param-value>
    </init-param>
    </servlet>
    <servlet-mapping>
    <servlet-name>CGIServlet</servlet-name>
    <url-pattern>/cgi-bin/*</url-pattern>
    </servlet-mapping>-------- end of web.xml ---------
    When a call is made to http://.../cgi-bin/dialogserver , this results
    in a
    404-File Not Found error.
    The contents of the cgi-bin directory have not been altered and I did
    not
    face this problem earlier when I was using sp2.
    It only happened after I upgraded to sp4. Can anyone help?
    best rgds,
    steven.

  • How to setup thunderbolt bridge between two macbook Pro (retina and 2011 )?

    I have a new 13" MB Pro retina and want to use the thunderbolt bridge btween the 13" and the 15" MB pro 2011.
    Somehow I cannot do anything with this, and on both laptops it shows the the Thunderbolt slots as "Inactive". I have connected the the two laptops via the new Thunderbolt cable.
    I looked around and there is no documentation on how to make this happen. The documentations are very thin or non existent.
    I want to use this mechanism to transfer my data from my old MB pro to the new retina one.
    your help is greatly appreciated.
    Amir

    unfortunately the option to select thunderbolt/firewire never comes up.
    It directly goes to the options from where to transfer and then upcon clicking on it. It keeps on looking with the spinner icon showing and it never finds the other computer.
    It does see it through the wiresless but not through thunderbolt.
    The more I look to make this happen the more I am convinved that this feature is not fully baked and does not really work as the documentation on "Thunderbolt bridge" setup is next to none existent and only one perons through macrumors has supposedly managed this. It is really a shame as I was looking forward to use this new capability.
    All the best,

  • Keep-alive message bridge connection

    Hi,
    I have setup messaging bridge between WLS 10.3.0.0 and a JBoss Messaging queque, after about 4 hours of inactivity in a queue bridge was disconneted, is there any way to configure keep-alive connection in WLS bridge ?
    Thanks,
    Lukasz

    You can try to set the IdleTimeMaximum setting on your bridge configuration to a very large number. It specifies the maximum amount of time, in seconds, that a messaging bridge instance remains idle.
    In “asynchronous” mode, this is the longest amount of time a messaging bridge instance stays idle before it checks the sanity of its connection to the source. In “synchronous” mode, this is the amount of time the messaging bridge can block on a receive call if no transaction is involved.
    -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

Maybe you are looking for

  • Yoga 3 Pro DirectX/Direct 3D Error

    I have a Yoga Pro 3 which routinely crashes a few minutes into Neverwinter game with the following error: Fatal Error: Direct3D driver returned error code (DXGI_ERROR_DEVICE_REMOVED) while checking sync query Technical Details: sync query 0 0x15ddf78

  • Facing Problem while adding Azure Project to existing C# web application

    Hi, I have a web application with 5 projects under one Solution. I want to publish this web application on Windows Azure, for that I have tried to add Windows Azure Cloud Service Project but this option is not appear in option list. But when I create

  • Cost Estimate using Commercial Price 3 of BOM item

    Dear Experts, I am trying to create a cost estimate for certain materials using ABC costing variant. The objective is that the cost estimate should pick up Commercial price 3 from the material masters of the BOM item and then calculate cost estimate

  • Question about file preparation for print from Photoshop

    I need to figure out the best method for saving for print from Photoshop. Here are the things that are confusing me: Problem: When I create a design in Photoshop, I'm left with a few options on how to save my document. I would like to know which of t

  • Question about suming two columns from different tables in Subquery?

    Hello everyone, I have a subquery that works great for getting the total SUM of a Billing table, but I also need to add to that SUM the total surcharges or additional charges from a separate table.  I tried this by doing something like so: (SELECT SU