| Author |
Message
|
| warrenpage |
 Posted: Tue Sep 03, 2002 11:11 am Post subject: Yeah.. |
 |
|
Acolyte
Joined: 19 Feb 2002
Posts: 56
Location: Australia
|
I got some Broker/Config Mgr out of sync messages after I installed and had to (chose to) delete/recreate both my broker and config Mgr.
** I did find a fix that CSD3 has which works for us... Yay
Under CSD2 - calling a Function from "EVALed ESQL" used to recycle the broker (that's right - it didn't throw an exception - it recycled the broker) .. Now it seems to work.. We may install it afterall.. ** |
|
| Back to top |
|
 |
| pfaulkner |
| Posted: Tue Sep 03, 2002 12:54 pm Post subject: |
|
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
| I am pretty sure I', running SP2 on both my Broker (AIX) and ConfigMgr(NT) but how do I check for sure (on either platform)? |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Sep 03, 2002 1:07 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
search for memo.ptf file on your system. This file should tell you what CSD level you are at!
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| hopfe_de |
| Posted: Fri Nov 08, 2002 12:59 am Post subject: Problems during install |
|
|
Acolyte
Joined: 03 Mar 2002
Posts: 58
Location: Frankfurt, Germany
|
Yesterday we setup a new version of WMQI 2.1 on our WinNT/SP6a box, now i have downloaded the file U200178.exe. After >>Setup is checking your system....... << i get these error-message:
>>> An incompatible WebSphere MQ Integrator product is present on the host system. You must remove the incompatible version before proceeding the install setup.
This setup will now abort! <<< |
|
| Back to top |
|
|
| muralihegde |
| Posted: Fri Nov 08, 2002 2:29 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Hi All,
After applying CSD3 to the broker, what we observed is that the broker has become smarter in processing MRM messages.
Earlier if the total length of the MRM message happens to be N and the input message length is equal to or more than N, then broker would not complain. Only if the input message is shorter than the defined MRM, the broker would throw exception saying message is shorter than expected.
Now, the broker would capture the error if the message length is not exactly equalt to the MRM length. It also throws errors, if the msg is larger than expected... |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Nov 08, 2002 11:02 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Murali,
I guess this will happen only if you have validate option selected in MQInput node? If this is default behavior then it defeats the purpose of "parse on demand/lazy parsing".
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
