| Author |
Message
|
| vald |
 Posted: Wed Nov 21, 2007 5:23 am Post subject: AMQ4063 Error using IBM Websphere MQ Explorer |
 |
|
Novice
Joined: 16 Nov 2007
Posts: 17
|
I'm using Mq 6.0 on an windows XP plateform. I defined two local queue managers on the cluster and they were started OK using IBM Websphere MQ Explorer. Also, I created Listener.TCP controled by queue manager and it is also started.
When I created two channels - 1 sender channel and 1 server channel, they are not started using IBM Websphere MQ Explorer. (AMQ4063).
Then I created a receiver channel. This time I received the message - "The request to start the channel was accepted" (AMQ4008). However, Overall channel status stil says "Inactive". |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Nov 21, 2007 5:37 am Post subject: Re: AMQ4063 Error using IBM Websphere MQ Explorer |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vald wrote: |
| Overall channel status stil says "Inactive". |
What's wrong with that? It's the status I'd expect. 
As to your error message, Mr Google suggests this:
http://www-1.ibm.com/support/docview.wss?uid=swg21107723
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 21, 2007 5:40 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And does this have anything to do with clustering, or is it just posted in the wrong forum?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vald |
| Posted: Wed Nov 21, 2007 6:05 am Post subject: |
|
|
Novice
Joined: 16 Nov 2007
Posts: 17
|
| Vitor wrote: |
| And does this have anything to do with clustering, or is it just posted in the wrong forum? |
I am not sure that it is a "Clustering2 issue. I think it is "MQ distributed communication" issue.
It just that my MQ environment uses a Default cluster. My question is because I am trying to send the message from Java Client to my MQ channel and the server application crashes with reason code 2009.
Then I saw that the status of the channel that I am using is "Inactive" and I assumed that this is wrong. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 21, 2007 6:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vald wrote: |
I am not sure that it is a "Clustering2 issue. I think it is "MQ distributed communication" issue.
It just that my MQ environment uses a Default cluster. |
I'm following your reasoning here, but your problem does seem to be connected to the client connection rather than the cluster. For neatness I'll move it to a more relevant forum.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 21, 2007 6:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vald wrote: |
| [My question is because I am trying to send the message from Java Client to my MQ channel and the server application crashes with reason code 2009. |
2009 is "connection broken". I would check first that your application has the connection in scope when it tries to put the message. If the error doesn't occur all the time, check that the queue manager is not running out of connections and/or resources periodically.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vald |
| Posted: Fri Nov 23, 2007 1:38 am Post subject: |
|
|
Novice
Joined: 16 Nov 2007
Posts: 17
|
| Vitor wrote: |
| vald wrote: |
| [My question is because I am trying to send the message from Java Client to my MQ channel and the server application crashes with reason code 2009. |
2009 is "connection broken". I would check first that your application has the connection in scope when it tries to put the message. If the error doesn't occur all the time, check that the queue manager is not running out of connections and/or resources periodically. |
This error message is appears when my Java Client tries to put the message to the queue that on the same Window machine that client is, but I don't get the same error message when the same client to put the message to the queue that on the remote Linux box. There is IP address as the parameter to client application, so client should not know is the queue is a local or remote. Where am I wrong? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 23, 2007 1:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vald wrote: |
| There is IP address as the parameter to client application, so client should not know is the queue is a local or remote. Where am I wrong? |
Nowhere that I can see - a client is a client is a client.
Given the symptoms you describe, I'd focus on the installation and configuration of the local queue manager (which throws the 2009 errors). The client application is unlikely to be at fault if it can successfully connect to and use another queue manager. Look for resource issues with the queue manager. Also check if the Windoze box has that stupid firewall (or some other less stupid firewall) switched on and blocking the client connections from your app.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vald |
| Posted: Fri Nov 23, 2007 2:53 am Post subject: |
|
|
Novice
Joined: 16 Nov 2007
Posts: 17
|
| Vitor wrote: |
| vald wrote: |
| There is IP address as the parameter to client application, so client should not know is the queue is a local or remote. Where am I wrong? |
Nowhere that I can see - a client is a client is a client.
Given the symptoms you describe, I'd focus on the installation and configuration of the local queue manager (which throws the 2009 errors). The client application is unlikely to be at fault if it can successfully connect to and use another queue manager. Look for resource issues with the queue manager. Also check if the Windoze box has that stupid firewall (or some other less stupid firewall) switched on and blocking the client connections from your app. |
I checked my firewall log and there are a lot of messages like
2007-11-23 10:50:33 DROP UDP ... ... 8201 168 - - - - - - - RECEIVE
in exactly the same time I am testing MQ.
Does it mean that the stupid firewall is blocking the client connections from my app? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 23, 2007 3:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vald wrote: |
I checked my firewall log and there are a lot of messages like
2007-11-23 10:50:33 DROP UDP ... ... 8201 168 - - - - - - - RECEIVE
in exactly the same time I am testing MQ.
Does it mean that the stupid firewall is blocking the client connections from my app? |
Certainly sounds like it! For testing purposes turn it off & see if that helps, remembering to turn it (or something like it) back on.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Nov 23, 2007 4:09 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| vald wrote: |
| Does it mean that the stupid firewall is blocking the client connections from my app? |
isn't that what a firewall is supposed to do? 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 23, 2007 4:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Michael Dag wrote: |
| vald wrote: |
| Does it mean that the stupid firewall is blocking the client connections from my app? |
isn't that what a firewall is supposed to do? |
You should (in theory at least) be able to explain to it that these particular connections should be allowed.
Unless you've gone for the total security option and locked down all access to protect the machine from malicious software or attacks. Or Windoze has decided to protect you from all that badly written, unstable IBM code so you can luxuriate in the badly written, unstable MSoft code.
This is a school of thought that leads to you in the final case walling your machine up in a vault with thick concrete walls with no network or power cables. The machine is completely safe from hackers, viruses and system instabilies caused by upgrades or badly written applications. Obviously there's a trade off with availability....... 
(Note: there may be a trace of bias in my views per pro Windoze. Readers are advised to use their own judgement in weighing my comments......)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| David.Partridge |
| Posted: Tue Nov 27, 2007 12:23 am Post subject: |
|
|
Master
Joined: 28 Jun 2001
Posts: 249
|
>there may be a trace of bias in my views per pro Windoze
Bias? What might lead you to think that 
D. |
|
| Back to top |
|
|
| vald |
| Posted: Wed Nov 28, 2007 10:53 am Post subject: I fixed MQ Error with RC 2009, then I got RC 2033 |
|
|
Novice
Joined: 16 Nov 2007
Posts: 17
|
| Vitor wrote: |
| vald wrote: |
| [My question is because I am trying to send the message from Java Client to my MQ channel and the server application crashes with reason code 2009. |
2009 is "connection broken". I would check first that your application has the connection in scope when it tries to put the message. If the error doesn't occur all the time, check that the queue manager is not running out of connections and/or resources periodically. |
I fixed RC 2009. No wonder - my LISTENER.TCP was not running. Now it is running on the default port 1414, but my client returns MQJE001: Completion Code 2, Reason 2033
Anybody? |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Nov 28, 2007 10:58 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
It has no message to read and it timed out?
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
|
|
