| Author |
Message
|
| jefflowrey |
 Posted: Sat Apr 16, 2005 1:34 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If it's complaining about Bindings mode, why is it saying
| Quote: |
[4/15/05 10:58:34:653 EDT] 3d41aea9 MQQueueConnec E WMSG0902E: The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set.
|
?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Apr 16, 2005 7:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
Possibly poor phrasing of the error message or a broader hint to the transactional client ?
In the start up sequence it states clearly that only the embedded client has been installed. This would not allow 2 phase commit and bindings mode.
Now if the JNDI setup is made for bindings I expect that he might get this kind of error.
Thanks
 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Apr 17, 2005 12:06 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The comment about the embedded messaging client is a lot more likely to be spurious than the message about the WebSphere MQ JMS Binders being disabled.
In my experience.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Apr 17, 2005 4:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
I'd fully agree with you but for the fact that this is WAS 5.1 and not 5.0
I have not sufficient knowledge of WAS 5.1 to discard those startup messages...
And I have found that subsequent error messages (since 5.0) were not always very clear... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Apr 18, 2005 3:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
I'd fully agree with you but for the fact that this is WAS 5.1 and not 5.0
I have not sufficient knowledge of WAS 5.1 to discard those startup messages...
And I have found that subsequent error messages (since 5.0) were not always very clear... |
I've seen the message about Embedded Messaging Client on WAS servers, and WTE servers where MQ worked fine.
Unfortunately, I don't have access to any of those environments right now to see what's different.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 18, 2005 5:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
If he has WebSphere MQ installed on his machine he did not follow any of the installation manuals for WAS hence the MQ_INSTALL_ROOT problem.
I suggest this is a case of
a) specify the exact environment and desired effect no use of us speculating...
b) hit the manuals and install MQ correctly within WAS.
 |
|
| Back to top |
|
|
|
|
