Hilde,
Sorry, but I'm new to JMS and haven't used the bind mode yet. The JMSAdmin
tool gives an error message if the client-bind options clash so I would
think that if the script runs successfully you should be okay. However,
there may be some properties which can be overridden in the JMS code.
Nick,
Thanks, that was it!...
Question: Is there anything other than setting the
TRANSPORT(BIND) that needs to be done for the app to
run in the BIND mode (as opposed to CLIENT)? Because I
remember creating the bindings file with BIND in the
past and the developer HAD said that it did not work.
I
Jeff,
>>>Are you using the JMS? In the past I noticed that the JMS
>>>did not support FAIL_IF_QUIESCING. This is one of the
>>>reasons I am not a supporter of JMS.
JMS with WMQ V5.3 does support FAIL_IF_QUIESCING through the use of the
FAILIFQUIESCE connection factory property.
Regards,
Christo
Peter,
Are you using WAS embedded messaging? Or WMQ with WAS as the App Server? Or
WMQ with another App Server?
Regards,
Christopher Frank
Certified I/T Specialist - WebSphere Software
IBM Certified Solutions Expert - Websphere MQ & MQ Integrator
--
Phone: 612
Yes, we are using JMS.
-Original Message-
From: Jeff A Tressler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 31, 2003 2:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING
Are you using the JMS? In the past I noticed that the JMS did not
support FA
Are you using the JMS? In the past I noticed that the JMS did not
support FAIL_IF_QUIESCING. This is one of the reasons I am not
a supporter of JMS.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
Hilde,
Try using the -v option with the JMSAdmin tool. It may give you more
details. I had this error and found it was because I didn't delete the
previous definition, but the -v option should help identify the problem.
Nick
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTEC
Thanks Mike/Peter,
I already had this reference in front of me, but was failing to see the
shortform column. Now I can puzzle together the various options from the
table. I was expecting to find something more akin to the command reference
manual and/or some more examples, but you can't have eve
How to Message Driven Beans (MDBs) and the FAIL_IF_QUIESCING option relate?
The reason I ask is that I was helping an application run through some
testing. One of the things I did was bring down the Queue Manager (endmqm -i
QUEUEMANAGER). The QM came down with no problems.
But when I tried to sta
I am trying to Save XML data as CLOB in Database and later trying to
retrieve CLOB and convert it back to XML
I am able to Save the XML as CLOb successfully using following Code
SAVE THE MESSAGE using
=
DECLARE bContent BLOB;
SET bContent = ASBITSTREAM("Body") ;
INSERT INTO Data
We are on WMQI 5.3 CSD5/Win 2000.
Currently we are using JMS with TRANSPORT(Client)
with no problems.
I would like to use BIND instead. So I changed it as
follows:
echo def qcf(ivtQCF) QMANAGER(QM1) TRANSPORT(BIND) >
ivtsetup.scp
when I tried to create the bindings file I got the
following erro
I really like Peters explaination, I am going to copy it out and put it in
my book to give people who ask!!!
BUTbecause it is so close to New Years Eve I do believe thay my dear
friend Peter has, in the words of our imortal football referre, gone off
side and jumped the gun on celebrating the N
Trigger Interval comes into play whenever a triggered on first queue finds
itself with more than zero messages and the application to be triggered has
not been started yet. In practical terms, the reason for the app not running
is because the app itself abended before it had a chance to open the qu
13 matches
Mail list logo
