MQseries Queue depth

Hello,
I am using JMS for accessing MQseries. Can anyone tell me asto how can i find the current depth and maximum depth of a queue using the JMS calls.? I am using IBM java classes for JMS.my MQseries verion is 5.2
Thanks
Joe Cherian

I'm afraid that the JMS spec, for some bizarre reason, do not have any APIs for getting the depth of a queue. So, the only way to find the depth of a queue in JMS is to create a browser and browse every message in the queue, and count them. This is quite a neat solution as long as you only have a few messages. If you have thousands you will spend all your time browsing queues not processing them.
Also I believe there is also a bug in MQ 5.2 and JMS whereby if you do not browse ALL the messages, but stop halfway through instead, then you will not release some resource that MQ uses. After xx number of doing this ( depends on your maximum open handles for the queue manager ) MQ dies. So if you ARE going to browse an MQ 5.2 queue, browse all of it.
The way around it we are using is to have JMS adapters for our app, and having mutant/hybrid MQ adapters as well, which use JMS for nearly everything, including transactional gets and puts, and has an MQ queue manager for getting the MQ Series queue depth natively. Not ideal, but it allows us to use JCA/XA etc with MQ Series. I have no idea how you get the max depth of a queue, unless you can find it in the api docs then you may have to use a native call.

Similar Messages

MDB on MQSeries queue undeployment

I just started testing MDBs listening on MQSeries queues. WLS 6.1 and MQ 5.1. I followed
the instructions in the BEA foreign JMS providers white paper, deployed the MDBs,
queued messages and things seemed to work. But shutting down the server revealed
that the undeployment of each MDB was slow. Slower than SSBs or MDBs listening on
BEA queues. Would appreciate any suggestions about what it could be. Thanks.

I just started testing MDBs listening on MQSeries queues. WLS 6.1 and MQ 5.1. I followed
the instructions in the BEA foreign JMS providers white paper, deployed the MDBs,
queued messages and things seemed to work. But shutting down the server revealed
that the undeployment of each MDB was slow. Slower than SSBs or MDBs listening on
BEA queues. Would appreciate any suggestions about what it could be. Thanks.

Oracle 8i and MQseries queues

Is there any possibility to access MQSeries queues using 8i AQ packages routines? I have to read some data from MQS and insert it into Oracle on Win2k and wonder if I need any additional MQ interfaces.
Best regards,
Tomek.

Hi Brajesh,
Have you ever set up communication between Oracle 9i and MQSeries?
Now I'm trying to read MQ messages using Oracle AQ and Messaging Gateway.
When I'm starting MGW agent i get error message: 'bad native queue' in log file.
Agent is still running and reachable.
Is it possible that i need local MQ queue manager?
Could you please help me with this?
Regards,
Tomek.

Throttling MDB performance running against MQSeries queue

I have an unusual requirement for an application. We have a non-transactional MQSeries queue that is bound as a foreign JMS destination in client mode (thanks to the folks on the forum who helped me configure that!).
          The problem is that the cluster that we are running our application on has limited capacity and I need to make sure that the MDB that will be listening to the queue does not surpass a certain TPS limit (say, 1 TPS). This article explains how to throttle performance using a separate execute thread -- http://e-docs.bea.com/wls/docs81/perform/AppTuning.html#1105201
          However, this requires you to set the MDB's "dispatch-policy' attribute to the lower priority queue in ejb-jar.xml. However, the documentation on this attribute -- http://edocs.beasys.com/wls/docs81/ejb/DDreference-ejb-jar.html#1113605 -- indicates that this attribute is only honoured if the source queue is transactional in nature.
          What to do? A transactional queue is a hard sell to our infrastructure folks. Can I use the extended transactional client and have this work?
          FYI - using the max-beans-in-free-pool does not do a sufficiently good job of limiting performance.
          Any other ideas?

another possibility might be the following scenario:
          create a local jms-destination, maybe with a jdbc-store.
          then use the weblogic bridge to transfer messages into the local jms-queue.
          at this point you can configure flow-control for the connection factory
          to limit transferred messages.
          the problem in this case is, that unprocessed messages have to be stored
          on the application server or in the database.
          but maybe this can help you.
          --Klaas
          gbrail schrieb:
          > As the doc describes, your MDB's "onMessage" method is invoked by a thread created by MQ. That means we have no control over it, or how fast it runs. I don't know of any "throttling" features in MQ either that would help.
          >
          > The only (ugly!) suggestion I can think of is that you should set "max-beans-in-free-pool" to 1 and periodically "sleep" in your onMessage method so that you don't get messages too fast!
          >
          > (And even if you were able to use a separate execute queue, or a transactional queue, you still could potentially get messages more than once per second, so you might still need to sleep anyway.)

Configuring an MDB to an MQSeries Queue

I want complete details as to how to configure an MDB to an MQSeries Queue.


From the JMS FAQ at http://e-docs.bea.com/wls/docs70/faq/jms.html
          Q. How do I integrate non-WebLogic JMS providers with WLS?
          A. Refer to the white paper, "Using Foreign JMS Providers with WebLogic
          Server" (jmsproviders.pdf) on
          http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          for a discussion on integrating MQ Series, IBus MessageServer, Fiorano,
          and SonicMQ.
          Or google search this newsgroup for "MQ".
          Tom
          Ranjit wrote:
          > I want complete details as to how to configure an MDB to an MQSeries Queue.

Changing Queue Depth Setting for the MS Software iSCSI Initiator

Hello all,
I am trying to better understand how queue depth for iSCSI works in Windows. Is there a place to adjust max queue depth for an initiator? Also what is the current default? Is it per session or per LUN?
We are working on improving performance and the array we are using supports up to 32QD per volume. We want to make sure we aren't near that limit on the host side as well. We are running server 2012 R2
Thanks in advance!

It's been a while since I've dealt with this, but if I recall correctly, the queue depth on the SAN and the queue depth on the server are two completely separate things. In general, if you are getting a queue depth of 2 or 3 on Windows, it generally
means you need to start looking at making some changes in your environment.
Your best bet is to talk with your SAN vendor about storage settings. They have most likely run all the benchmarks necessary to know which specific settings, if any, should be changed according to the type of usage you are going to have on the array.
And if they haven't you might want to consider a different SAN vendor.
. : | : . : | : . tim

JNDI Newbe questions : Connecting to MQSeries queue using JMS

Hi.
I'm trying to make a connection to a MQseries cueue using JMS and as I understand it I have to look some things up in a JNDI server.
Right now I'm using the IBM Websphere test environment inluded in Visual Age for Java but later this aplication will be deployed on a Webphere 3.5 server.
Question 1 : (code grabbed from an example)
queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("QueueConnectionFactory");
queue = (Queue) jndiContext.lookup(queueName);
When i run an lookup on from my initial context I take it that it tries to search through the JNDI directory which lives within my Websphere Test environment. Ofcourse it doesn't find anything called "QueueConnectionFactory" so: What am I looking for here?
I guess I want to find the MQseries server here right? Firstly I don't know what that one is called (is there a generic name?!) and second i suspect that the MQ server is not registrated in my local JNDI server...
which lead me to Question 2 :
Do I register a remote server in my JNDI directory OR do I try to connect to the real JNDI directry (that might have information on the MQ service) ?

You are looking for the queue manager name in this case. You need a queue manager name and a queue name in you code, you also need define a queue manager and a queue in MQSeries. Then in your WebSphere Test Environment (Or run MQSeries command when you deploy this application, refer to its document) to define the relation between these two pairs of managers and queues. You may actually go to read these two articals and you'll feel much better to do this:
http://www.developer.ibm.com/library/articles/programmer/farrell1.html
http://www.developer.ibm.com/library/articles/programmer/farrell2.html
Hope its helpful. Don't forget my 'dollars' if you feel this info is good for you.
PC

Configuring MDB to receive message from MQSeries Queues bound on WL JNDI

Hi,
I am using weblogic7.0 sp2. I need to configure my MDB to receive message from MQ Series (on a different server). The queue is bound to WL JNDI using a server startup program.
Anyone with experiece, please help.
Thanks,
Fasih

I'd start here:
http://e-docs.bea.com/wls/docs70/faq/index.html
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Registering for a Topic with own stream & queue in Pub/Sub

Hi *.
I'm working with MQSeries 5.3 on WinXP.
I don't know, how to register a subscriber to a topic with the JMS-classes. I found a sample from IBM, but it uses the native (MQ)classes and it does not work, when I try to register an own queue or stream. Everything works fine with system-queues/streams, but I shouldn't work with the defaults in my application.
Does anybody know, where I can find a sample to register a subscriber to a topic, which is based on JMS ?
Thank you very much in advance.
Jo

Yes, the script is provided by IBM when you install the java for mqseries for websphere MQ. It is under MQ_JAVA_INSTALL_PATH/bin directory called MQJMS_PSQ.mqsc.
I am copying the contents of the file if you want:
* IBM Websphere MQ Support for Java Message Service */ */
* Sample MQSC source defining JMS Publish/Subscribe queues. */
* Installation Verification Test - Setup script */
* Licensed Materials - Property of IBM */
* 5648-C60 5724-B4 5655-F10 */
* (c) Copyright IBM Corp. 1999. All Rights Reserved. */
* US Government Users Restricted Rights - Use, duplication or */
* disclosure restricted by GSA ADP Schedule Contract with IBM Corp.*/
* JMS Publish/Subscribe Administration Queue */
** Create a local queue
DEFINE QLOCAL('SYSTEM.JMS.ADMIN.QUEUE') REPLACE +
DESCR('Websphere MQ - JMS Classes - admin queue') +
* Persistent messages OK
DEFPSIST(YES) +
* Non-Shareable
NOSHARE
* JMS Publish/Subscribe Subscriber Status Queue */
** Create a local queue
DEFINE QLOCAL('SYSTEM.JMS.PS.STATUS.QUEUE') REPLACE +
DESCR('Websphere MQ - JMS Classes - PS status queue') +
* Persistent messages OK
DEFPSIST(YES) +
* Shareable
SHARE DEFSOPT(SHARED)
* JMS Publish/Subscribe Report Queue */
** Create a local queue
DEFINE QLOCAL('SYSTEM.JMS.REPORT.QUEUE') REPLACE +
DESCR('Websphere MQ - JMS Classes - Report queue') +
* Persistent messages OK
DEFPSIST(YES) +
* Shareable
SHARE DEFSOPT(SHARED)
* JMS Publish/Subscribe Subscribers Model Queue */
* Create model queue used by subscribers to create a permanent */
* queue for subsciptions */
* General reply queue */
DEFINE QMODEL('SYSTEM.JMS.MODEL.QUEUE') REPLACE +
DESCR('Websphere MQ - JMS Classes - Model queue') +
* Queue Definition Type
DEFTYPE(PERMDYN) +
* Shareable
SHARE DEFSOPT(SHARED)
* JMS Publish/Subscribe Default Non-Durable Shared Queue */
* Create local queue used as the default shared queue by */
* non-durable subscribers */
** Create a local queue
DEFINE QLOCAL('SYSTEM.JMS.ND.SUBSCRIBER.QUEUE') REPLACE +
DESCR('Websphere MQ - JMS Classes - PS ND shared queue') +
* Persistent messages OK
DEFPSIST(YES) +
* Shareable
SHARE DEFSOPT(SHARED) +
* Maximum queue depth
MAXDEPTH(100000)
* JMS Publish/Subscribe Default Non-Durable Shared Queue for */
* ConnectionConsumer functionality */
* Create local queue used as the default shared queue by */
* non-durable connection consumers */
** Create a local queue
DEFINE QLOCAL('SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE') REPLACE +
DESCR('Websphere MQ - JMS Classes - PS ND CC shared q') +
* Persistent messages OK
DEFPSIST(YES) +
* Shareable
SHARE DEFSOPT(SHARED) +
* Maximum queue depth
MAXDEPTH(100000)
* JMS Publish/Subscribe Default Durable Shared Queue */
* Create local queue used as the default shared queue by durable */
* subscribers */
** Create a local queue
DEFINE QLOCAL('SYSTEM.JMS.D.SUBSCRIBER.QUEUE') REPLACE +
DESCR('Websphere MQ - JMS Classes - PS D shared queue') +
* Persistent messages OK
DEFPSIST(YES) +
* Shareable
SHARE DEFSOPT(SHARED) +
* Maximum queue depth
MAXDEPTH(100000)
* JMS Publish/Subscribe Default Durable Shared Queue for */
* ConnectionConsumer functionality */
* Create local queue used as the default shared queue by durable */
* connection consumers */
** Create a local queue
DEFINE QLOCAL('SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE') REPLACE +
DESCR('Websphere MQ - JMS Classes - PS D CC shared q') +
* Persistent messages OK
DEFPSIST(YES) +
* Shareable
SHARE DEFSOPT(SHARED) +
* Maximum queue depth
MAXDEPTH(100000)

Receiving binary IDOC via Queue and convert it to XML-IDOC

Hello,
we are focusing the following scenario:
We receive an plain, binary IDOC in a MQSeries Queue. We want to pick it, transform it and place it into R/3 (of course using XI 3.0). Afterwards the other way around.
I know the Howto for the ABAP mapping from XML-Idoc to plain IDOC. This may also work for our scenario. Do you agree?
The other way around is more difficult. I assume that - since the IDOC adapter resides in the ABAP stack - we cannot re-use an existant adapter module in the JMS adapter. Right?
I heared about JCO capabilities of "xmlizing" Idocs - but did not find hints within the javadoc. Anyway, would this really be the preferred way - writing an user exit for the adapter using JCO - to handle this? There must be a way to do it better, must it not?
How did you guys face this problem - I think its a common one...
Any starting points for a discussion are appreciated....
Greets,
helge

Hi Helge,
For the conversion of the incoming flat message, one could imagine a similar ABAP mapping as the one described for the XML->flat message conversion. The function module IDX_IDOC_TO_XML could be a good starting point for your search.
To perform conversions in the Java stack (e.g. in an adapter module) might be a quite complex task since you first have to get the IDoc metadata. And there you cannot reuse existing function modules.
Best regards
Joachim

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

Does the priority queue always work?

Hi
I have a 8Mbp of wan link which sometime gets saturated and I have shaped average this to 8Mbps but i am running vocie on this WAN link and have defined priority for voice with 850kbps under voice class. My question is when the link is not fully utilized, Will the packets from priority queue are always dequeued first as compared to packets sent from from other queus or will the QoS will not do anything here since the link utilization is lot less than what is sepecified in shape average. I am asking this to confirm if the priority queue always help to overcome the issue of jitter if either the link is saturated or not?
Thanks

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
You describe PQ and shaping, but the former is usually a part of doing QoS on L2/L3 switches, and the latter on routers. What device(s) and their IOS versions and the WAN media are you working with?
On "routers", interfaces generally have FIFO tx-rings, only when they overflow, are packets placed in CBWFQ queues. Within CBWFQ, LLQ will be dequeued first, but such packets might have already been queued behind other non-LLQ traffic within the interface tx-ring. (NB: for routers, with tx-rings, when supporting VoIP, you may want to minimize the size of the tx-ring.)
Shapers, in my experience, are "interesting". First, I believe many shapers don't account for L2 overhead, but provider CIRs often do. So unless you shape slower than the nomimal CIR rate, you can send faster than the available bandwidth. (Often I've found shaping 10 to 15% slower allows for average L2 overhead.)
Second, shapers work on averages over time intervals. For VoIP, you'll often want to insure the shaper is using a small Tc, otherwise it will allow FIFO bursts. (I've found a Tc of 10ms seems to support VoIP fairly well.)
Third, I suspect some shapers might have their own queues between the interface and the defined policy queues. If they do, unknown what their queuing organization is or their supported queuing depths. If this is the case, makes it difficult to engineer QoS.
Whenever possible, I've found it beneficial to work to avoid using shapers especially for timing sensitive traffic, like VoIP. In your case, I would suggest, if possible, obtaining 10 Mbps of WAN bandwidth and somewhere passing the traffic through a physical 10 Mbps interface, with a QoS policy.
But to more directly answer your question, PQ (or LQ) will dequeue its packets next compared to other "peer" queues. This should always help VoIP for delay and jitter, but there's more involved whether this is necessary and/or whether it's helpful enough when necessary.
You ask about when a link is saturated, but a link is 100% saturated everytime a packet is being transmitted. Often link usage is represented in percentages of usage of possible maximum transmission rate over some time period, but when it comes to QoS, 100% utilization might be just fine while 1% utilization is not. Much, much more information, about your situation, might be needed to offer truly constructive recommendations.

WLS Cluster with Message Driven Beans and MQSeries on more than one Host

          With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
          a MDB can be
          configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
          is started at the same Host that runs the WLS Server too.
          And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
          In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
          Queuemanager.
          A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
          of this Queue.
          If one of the two WLS Servers fails the other WLS Server with the corresponding
          MDB should get the Messages of the
          MQSeries Queue.
          If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
          and the following Exception is thrown:
          <Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
          mdb_deployed
          weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
          exception is:
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
          'btsun1a:TEST'
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
          at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
          I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
          the same Exception when the MDB is deployed.
          The configuration of JMSadmin on both Hosts is the following:
          dis qcf(myQCF2)
          HOSTNAME(btsun1a)
          CCSID(819)
          TRANSPORT(CLIENT)
          PORT(1414)
          TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
          QMANAGER(TEST)
          CHANNEL(JAVA.CHANNEL)
          VERSION(1)
          dis q(myQueue)
          CCSID(819)
          PERSISTENCE(APP)
          TARGCLIENT(JMS)
          QUEUE(MYQUEUE)
          EXPIRY(APP)
          QMANAGER(TEST)
          ENCODING(NATIVE)
          VERSION(1)
          PRIORITY(APP)
          I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
          and a QueueManager on each WLS Server.
          Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?


          With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
          a MDB can be
          configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
          is started at the same Host that runs the WLS Server too.
          And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
          In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
          Queuemanager.
          A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
          of this Queue.
          If one of the two WLS Servers fails the other WLS Server with the corresponding
          MDB should get the Messages of the
          MQSeries Queue.
          If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
          and the following Exception is thrown:
          <Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
          mdb_deployed
          weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
          exception is:
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
          'btsun1a:TEST'
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
          at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
          I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
          the same Exception when the MDB is deployed.
          The configuration of JMSadmin on both Hosts is the following:
          dis qcf(myQCF2)
          HOSTNAME(btsun1a)
          CCSID(819)
          TRANSPORT(CLIENT)
          PORT(1414)
          TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
          QMANAGER(TEST)
          CHANNEL(JAVA.CHANNEL)
          VERSION(1)
          dis q(myQueue)
          CCSID(819)
          PERSISTENCE(APP)
          TARGCLIENT(JMS)
          QUEUE(MYQUEUE)
          EXPIRY(APP)
          QMANAGER(TEST)
          ENCODING(NATIVE)
          VERSION(1)
          PRIORITY(APP)
          I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
          and a QueueManager on each WLS Server.
          Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?

Pl/Sql interaction with MQSeries

Hi,
How do you put/get message from a MQSeries queue i ahve pl/sql procedure which has to connect to a MQSeries queue. It would be great if i can get a code sample
Thanks And Regards
Ravi/Dheeraj

One possibility is to look at MQSeries classes for Java which allows you can communicate with MQSeries via Java. I am currently looking at loading an example into Oracle, then I should be able to call from pl/sql.
My current problem is an unresolved class library reference for MQQueueManager

Configuring MQSeries 5.2 JMS With Weblogic 7.0

Hi :
          Has anyone configured MQ Series 5.2 under weblogic 7.0 ?. I would appreciate
          if you could let me step by step configuration.
          I have tried all the configuration steps in Weblogic 7.0 but still i am
          getting an exception while the MessageBridge is trying to get a connection
          from the Target Destination (in my case MQSeries).
          The exception:
          <Oct 17, 2002 11:17:37 AM PDT> <Error> <Connector> <190006> <Error granting
          connection request.>
          javax.resource.spi.ResourceAllocationException: CreateManagedConnection
          Error: Failed to start the connection
          at
          weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
          ol.java:993)
          at
          weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
          ol.java:1762)
          at
          weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
          ctionPoolManager.java:163)
          at
          weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
          ConnectionManagerImpl.java:25)
          at
          weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseCon
          nectionFactory.java:126)
          at
          weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
          java:733)
          at
          weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:89
          9)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          thanks,
          Balaji.


Hi Dongbo:
          It worked, as you have said it was configuration problem of the PATH
          variable in my end.
          thanks,
          Balaji.
          "Dongbo Xiao" <[email protected]> wrote in message
          news:[email protected]...
          > Your configuration looks fine except that you are not recommended to
          > put MQSeries stuff in the AdapterClasspath attribute. Instead, the
          > following is what you should do according to the doc.
          >
          > Before starting WebLogic Server:
          >
          > Supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.
          >
          > Include the PATH of any native code required by the provider's
          > client-side libraries in the WebLogic Server system PATH. (This variable
          > may vary depending on your operating system.)
          >
          > You can also check the Messaging Bridge part of the following doc:
          >
          >
          http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          >
          > If the bridge still does not work after you correctly set everything,
          > you need to check all the values that you set for the attributes
          > (ConnectionURL
          > and etc)of the JMSBridgeDestination corresponding to the MQSeries queue.
          > Make sure
          > you can access MQSeries with those values from a client.
          >
          > It should work. Most commonly seen problems are configuration problems
          > or
          > environment problems.
          >
          > Good luck.
          > Dongbo
          >
          > Balaji Venkataraman wrote:
          > >
          > > Hi Dongbo: Please find herewith the information requested by you.
          > >
          > > Related Properties from Config.xml:
          > >
          > > <Application Deployed="true" Name="jms-xa-adp"
          > > Path="C:\bea\weblogic700\server\lib" TwoPhase="true">
          > > <ConnectorComponent Name="jms-xa-adp" Targets="adminserver"
          > > URI="jms-xa-adp.rar"/>
          > > </Application>
          > >
          > > JMS Related Entries:
          > >
          > > <JMSBridgeDestination ConnectionFactoryJNDIName="ediJMSFactory"
          > > DestinationJNDIName="MQ_WEBEDI_TO_OPUSTX"
          > > Name="MQSourceDestination"/>
          > > <JMSBridgeDestination
          > > Classpath="c:\Program
          > > Files\IBM\MQSeries\Java\samples\base;c:\Program
          > > Files\IBM\MQSeries\java\lib\com.ibm.mq.jar;c:\Program
          > > Files\IBM\MQSeries\java\lib\com.ibm.mqjms.jar;c:\Program
          > > Files\IBM\MQSeries\java\lib\jms.jar;c:\Program
          > > Files\IBM\MQSeries\java\lib\jndi.jar;c:\Program
          > > Files\IBM\MQSeries\java\lib\fscontext.jar;c:\Program
          > > Files\IBM\MQSeries\java\lib\providerutil.jar;c:\Program
          > > Files\IBM\MQSeries\java\lib\connector.jar;"
          > > ConnectionFactoryJNDIName="mqXAQCF"
          > > ConnectionURL="file://c:\bea\wlsmq" DestinationJNDIName="mqQ"
          > >
          InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
          > > Name="MQTargetDestination"/>
          > > <JMSConnectionFactory AllowCloseInOnMessage="true"
          > > JNDIName="ediJMSFactory" Name="ediJMSFactory"
          > > Targets="adminserver" UserTransactionsEnabled="true"
          > > XAConnectionFactoryEnabled="true" XAServerEnabled="true"/>
          > > <JMSFileStore Directory="filestore" Name="MyJMSFile Store"/>
          > > <JMSServer Name="MyJMSServer" Store="MyJMSFile Store"
          > > Targets="adminserver">
          > > <JMSQueue DeliveryModeOverride="Persistent"
          > > JNDIName="MQ_WEBEDI_TO_OPUSTX" Name="OpusQueue"
          > > StoreEnabled="true"/>
          > > </JMSServer>
          > >
          > > Message Bridge:
          > >
          > > <MessagingBridge Name="MyMessaging Bridge"
          > > SourceDestination="MQSourceDestination"
          > > TargetDestination="MQTargetDestination" Targets="adminserver"/>
          > >
          > > thanks,
          > > Balaji.
          > >
          > > "Dongbo Xiao" <[email protected]> wrote in message
          > > news:[email protected]...
          > > >
          > > > Please send your configuration for the source bridge destination,
          > > > target bridge destination and the bridge itself.
          > > >
          > > > Dongbo
          > > >
          > > > Balaji Venkataraman wrote:
          > > > >
          > > > > Hi :
          > > > >
          > > > > Has anyone configured MQ Series 5.2 under weblogic 7.0 ?. I would
          > > appreciate
          > > > > if you could let me step by step configuration.
          > > > >
          > > > > I have tried all the configuration steps in Weblogic 7.0 but still i
          am
          > > > > getting an exception while the MessageBridge is trying to get a
          > > connection
          > > > > from the Target Destination (in my case MQSeries).
          > > > >
          > > > > The exception:
          > > > > <Oct 17, 2002 11:17:37 AM PDT> <Error> <Connector> <190006> <Error
          > > granting
          > > > > connection request.>
          > > > > javax.resource.spi.ResourceAllocationException:
          CreateManagedConnection
          > > > > Error: Failed to start the connection
          > > > > at
          > > > >
          > >
          weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
          > > > > ol.java:993)
          > > > > at
          > > > >
          > >
          weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
          > > > > ol.java:1762)
          > > > > at
          > > > >
          > >
          weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
          > > > > ctionPoolManager.java:163)
          > > > > at
          > > > >
          > >
          weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
          > > > > ConnectionManagerImpl.java:25)
          > > > > at
          > > > >
          > >
          weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseCon
          > > > > nectionFactory.java:126)
          > > > > at
          > > > >
          > >
          weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
          > > > > java:733)
          > > > > at
          > > > >
          > >
          weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:89
          > > > > 9)
          > > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          > > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          > > > >
          > > > > thanks,
          > > > > Balaji.
          > >
          > > <?xml version="1.0" encoding="UTF-8"?>
          > > 
          > > <Domain ConfigurationVersion="7.0.0.0" Name="edixml">
          > > <Application Deployed="true" Name="DefaultWebApp"
          > > Path=".\applications" StagedTargets="" TwoPhase="false">
          > > <WebAppComponent Name="DefaultWebApp" Targets="adminserver"
          URI="DefaultWebApp"/>
          > > </Application>
          > > <Application Deployed="true" Name="certificate"
          > > Path=".\applications" StagedTargets="" TwoPhase="false">
          > > <WebAppComponent Name="certificate" Targets="adminserver"
          URI="certificate.war"/>
          > > </Application>
          > > <Application Deployed="true" Name="jms-xa-adp"
          > > Path="C:\bea\weblogic700\server\lib" TwoPhase="true">
          > > <ConnectorComponent Name="jms-xa-adp" Targets="adminserver"
          URI="jms-xa-adp.rar"/>
          > > </Application>
          > > <ApplicationManager Name="edixml"/>
          > > <Cluster ClusterAddress="208.193.6.143:7001,208.193.6.143:8001"
          > > MulticastAddress="237.0.0.4" MulticastPort="7777"
          Name="edixmlcluster"/>
          > > <EmbeddedLDAP
          > > Credential="{3DES}iLJIRpiJCbQYHvktF5nq32XqGBhWLQpLEcMRXP+KJi0="
          Name="edixml"/>
          > > <FileRealm Name="wl_default_file_realm"/>
          > > <JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
          > > Name="OracleDBPool"
          > >
          Properties="user=webedi7;password=webedi7;dll=ocijdbc8;protocol=thin"
          > > Targets="adminserver" TestConnectionsOnReserve="true"
          > > TestTableName="numberblockmaster"
          URL="jdbc:oracle:thin:@192.168.222.6:1521:ora8"/>
          > > <JDBCTxDataSource JNDIName="OracleTxDS" Name="OracleTxDS"
          PoolName="OracleDBPool"/>
          > > <JMSBridgeDestination ConnectionFactoryJNDIName="ediJMSFactory"
          > > DestinationJNDIName="MQ_WEBEDI_TO_OPUSTX"
          Name="MQSourceDestination"/>
          > > <JMSBridgeDestination
          > > Classpath="c:\Program
          Files\IBM\MQSeries\Java\samples\base;c:\Program
          Files\IBM\MQSeries\java\lib\com.ibm.mq.jar;c:\Program
          Files\IBM\MQSeries\java\lib\com.ibm.mqjms.jar;c:\Program
          Files\IBM\MQSeries\java\lib\jms.jar;c:\Program
          Files\IBM\MQSeries\java\lib\jndi.jar;c:\Program
          Files\IBM\MQSeries\java\lib\fscontext.jar;c:\Program
          Files\IBM\MQSeries\java\lib\providerutil.jar;c:\Program
          Files\IBM\MQSeries\java\lib\connector.jar;"
          > > ConnectionFactoryJNDIName="mqXAQCF"
          > > ConnectionURL="file://c:\bea\wlsmq" DestinationJNDIName="mqQ"
          > >
          InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
          Name="MQTargetDestination"/>
          > > <JMSConnectionFactory AllowCloseInOnMessage="true"
          > > JNDIName="ediJMSFactory" Name="ediJMSFactory"
          > > Targets="adminserver" UserTransactionsEnabled="true"
          > > XAConnectionFactoryEnabled="true" XAServerEnabled="true"/>
          > > <JMSFileStore Directory="filestore" Name="MyJMSFile Store"/>
          > > <JMSServer Name="MyJMSServer" Store="MyJMSFile Store"
          Targets="adminserver">
          > > <JMSQueue DeliveryModeOverride="Persistent"
          > > JNDIName="MQ_WEBEDI_TO_OPUSTX" Name="OpusQueue"
          StoreEnabled="true"/>
          > > </JMSServer>
          > > <JTA Name="edixml"/>
          > > <JTARecoveryService Name="primary"/>
          > > <JTARecoveryService Name="secondary"/>
          > > <Log FileName=".\wl-domain.log" Name="edixml"/>
          > > <MessagingBridge Name="MyMessaging Bridge"
          > > SourceDestination="MQSourceDestination"
          > > TargetDestination="MQTargetDestination" Targets="adminserver"/>
          > > <MigratableTarget Cluster="edixmlcluster"
          > > Name="primary (migratable)"
          > > Notes="This is a system generated default migratable target for
          a server. Do not delete manually." UserPreferredServer="primary"/>
          > > <MigratableTarget Cluster="edixmlcluster"
          > > Name="secondary (migratable)"
          > > Notes="This is a system generated default migratable target for
          a server. Do not delete manually." UserPreferredServer="secondary"/>
          > > <PasswordPolicy Name="wl_default_password_policy"/>
          > > <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          > > <SNMPAgent Name="edixml"/>
          > > <Security GuestDisabled="false" Name="edixml"
          > > PasswordPolicy="wl_default_password_policy"
          > > Realm="wl_default_realm" RealmSetup="true"/>
          > > <SecurityConfiguration
          > >
          Credential="{3DES}du0wFpH35kta7XFhGk6UV2mve7IhavFhAJ8uSzz1W4Gt2i9CV4PDWSLsnb
          6nJjMiej2UAIGHrmT3RGIQG1sn9R0xaYz1STwV" Name="edixml"/>
          > > <Server ListenAddress="208.193.6.143" ListenPort="9001"
          > > Name="adminserver" NativeIOEnabled="true"
          ServerVersion="7.0.0.0">
          > > <COM Name="adminserver"/>
          > > <ExecuteQueue Name="default" ThreadCount="15"/>
          > > <IIOP Name="adminserver"/>
          > > <JTAMigratableTarget Cluster="" Name="adminserver"
          UserPreferredServer="adminserver"/>
          > > <KernelDebug Name="adminserver"/>
          > > <Log FileName=".\adminserver\adminserver.log"
          Name="adminserver"/>
          > > <SSL Enabled="true" HostnameVerificationIgnored="true"
          > > ListenPort="9002" Name="adminserver"
          > > ServerCertificateChainFileName="ca.pem"
          > > ServerCertificateFileName="democert.pem"
          ServerKeyFileName="demokey.pem"/>
          > > <ServerDebug Name="adminserver"/>
          > > <ServerStart Name="adminserver"/>
          > > <WebServer DefaultWebApp="DefaultWebApp"
          > > LogFileName=".\adminserver\access.log" LoggingEnabled="true"
          Name="adminserver"/>
          > > </Server>
          > > <Server Cluster="edixmlcluster" JTARecoveryService="primary"
          > > ListenAddress="208.193.6.143" ListenPort="7001" Name="primary"
          > > NativeIOEnabled="true" ServerVersion="7.0.0.0">
          > > <COM Name="primary"/>
          > > <ExecuteQueue Name="default" ThreadCount="15"/>
          > > <IIOP Name="primary"/>
          > > <JTAMigratableTarget Cluster="edixmlcluster" Name="primary"
          UserPreferredServer="primary"/>
          > > <KernelDebug Name="primary"/>
          > > <Log Name="primary"/>
          > > <SSL Name="primary"/>
          > > <ServerDebug Name="primary"/>
          > > <ServerStart Name="primary"/>
          > > <WebServer Name="primary"/>
          > > </Server>
          > > <Server Cluster="edixmlcluster" JTARecoveryService="secondary"
          > > ListenAddress="208.193.6.143" ListenPort="8001" Name="secondary"
          > > NativeIOEnabled="true" ServerVersion="7.0.0.0">
          > > <COM Name="secondary"/>
          > > <ExecuteQueue Name="default" ThreadCount="15"/>
          > > <IIOP Name="secondary"/>
          > > <JTAMigratableTarget Cluster="edixmlcluster" Name="secondary"
          UserPreferredServer="secondary"/>
          > > <KernelDebug Name="secondary"/>
          > > <Log Name="secondary"/>
          > > <SSL Name="secondary"/>
          > > <ServerDebug Name="secondary"/>
          > > <ServerStart Name="secondary"/>
          > > <WebServer Name="secondary"/>
          > > </Server>
          > > </Domain>

MQseries Queue depth

Similar Messages

Maybe you are looking for