| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Soap Input Node in MB V6.1, Different for Windows and AIX ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| Veera B |
 Posted: Wed Jun 12, 2013 11:11 pm Post subject: Soap Input Node in MB V6.1, Different for Windows and AIX ? |
 |
|
Voyager
Joined: 16 Jan 2013
Posts: 76
|
Hi ALL,
Having a problem of setting Port Number to EG, containing Soap Input node, in AIX. MB V6.1.
But the strange thing is, before trying to test in AIX, i tested in development box, which is windows. It was so simple, just used ,
mqsichangeproperties TEST -e exgro -o HTTPSConnector -n explicitlySetPortNumber -v 7777
mqsireload EGName.
But the same procedure in AIX is not working, even after trying for hours, re-deploy, restart flow, restart broker ... etc
can you pls suggest what else i need to do in AIX to set port .. |
|
| Back to top |
|
 |
| Esa |
| Posted: Wed Jun 12, 2013 11:29 pm Post subject: Re: Soap Input Node in MB V6.1, Different for Windows and AI |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Dear Veera B,
Please stop using the phrase "is not working". Instead, describe precisely what happens. What error messages you get or how you otherwise determine that you have a problem. What gets written in broker or system logs.
Are you sure some other application is not already using the port? Did you run netstat? |
|
| Back to top |
|
|
| Veera B |
| Posted: Wed Jun 12, 2013 11:45 pm Post subject: |
|
|
Voyager
Joined: 16 Jan 2013
Posts: 76
|
Hi Esa,
Ok, comment noted. The situation is, i am setting port number explicitly for an EG, I run the command mqsichange properties, mqsireload and even restart broker.
even after all this when i try mqsireportproperties, i get 0 returned as the port number.
also, if i run netstat -an|grep 8080. i can see a process is already listening on this port.
but this port 8080 is also the broker wide http listener... but I need my webservice also to use this port...
if i try to use this port with out explicitly setting to EG, I get ...
<html><head><title>WebSphere Message Brokers error report</title></head>
<body><h1>HTTP Status 404 - Resource Not Found</h1>
URI /INQ does not map to any message flow in broker MQD4BRK<p>
<h3>WebSphere Event Broker 6102</h3></body></html>
pls suggest.. |
|
| Back to top |
|
|
| goffinf |
| Posted: Wed Jun 12, 2013 11:50 pm Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
| Veera B wrote: |
Hi Esa,
Ok, comment noted. The situation is, i am setting port number explicitly for an EG, I run the command mqsichange properties, mqsireload and even restart broker.
even after all this when i try mqsireportproperties, i get 0 returned as the port number.
also, if i run netstat -an|grep 8080. i can see a process is already listening on this port.
but this port 8080 is also the broker wide http listener... but I need my webservice also to use this port...
if i try to use this port with out explicitly setting to EG, I get ...
<html><head><title>WebSphere Message Brokers error report</title></head>
<body><h1>HTTP Status 404 - Resource Not Found</h1>
URI /INQ does not map to any message flow in broker MQD4BRK<p>
<h3>WebSphere Event Broker 6102</h3></body></html>
pls suggest.. |
Are you sure your broker wide HTTP listener port is 8080 and not 7080 ?
Fraser. |
|
| Back to top |
|
|
| Veera B |
| Posted: Thu Jun 13, 2013 12:08 am Post subject: |
|
|
Voyager
Joined: 16 Jan 2013
Posts: 76
|
Yes, Pretty Sure. because if i run the below command i get 8080...
mqsireportproperties SomeBRK -b httplistener -o HTTPConnector -n port |
|
| Back to top |
|
|
| cociu_2012 |
| Posted: Thu Jun 13, 2013 12:21 am Post subject: |
|
|
Acolyte
Joined: 06 Jan 2012
Posts: 72
|
| Veera B wrote: |
Hi Esa,
Ok, comment noted. The situation is, i am setting port number explicitly for an EG, I run the command mqsichange properties, mqsireload and even restart broker.
even after all this when i try mqsireportproperties, i get 0 returned as the port number.
also, if i run netstat -an|grep 8080. i can see a process is already listening on this port.
but this port 8080 is also the broker wide http listener... but I need my webservice also to use this port...
if i try to use this port with out explicitly setting to EG, I get ...
<html><head><title>WebSphere Message Brokers error report</title></head>
<body><h1>HTTP Status 404 - Resource Not Found</h1>
URI /INQ does not map to any message flow in broker MQD4BRK<p>
<h3>WebSphere Event Broker 6102</h3></body></html>
pls suggest.. |
HTTP port is one per server:
| Code: |
mqsireportproperties <broker_name> -b httplistener -o HTTPConnector -r
HTTPConnector
uuid='HTTPConnector'
address=''
port='7081'
|
, and you can change it.
On the other hand, SOAP port is related to EG. In order to have this port enabled, you must have a SOAP Flow deployed on the EG in question. I'm not sure if you can have a soap port, same as the http port. Check info center, it has to contain this information.
I belive the error you've posted above is quite descriptive. |
|
| Back to top |
|
|
| Veera B |
| Posted: Thu Jun 13, 2013 1:53 am Post subject: |
|
|
Voyager
Joined: 16 Jan 2013
Posts: 76
|
| cociu_2012 wrote: |
| Veera B wrote: |
Hi Esa,
but this port 8080 is also the broker wide http listener... but I need my webservice also to use this port...
if i try to use this port with out explicitly setting to EG, I get ...
<html><head><title>WebSphere Message Brokers error report</title></head>
<body><h1>HTTP Status 404 - Resource Not Found</h1>
URI /INQ does not map to any message flow in broker MQD4BRK<p>
<h3>WebSphere Event Broker 6102</h3></body></html>
pls suggest.. |
HTTP port is one per server:
| Code: |
mqsireportproperties <broker_name> -b httplistener -o HTTPConnector -r
HTTPConnector
uuid='HTTPConnector'
address=''
port='7081'
|
, and you can change it.
On the other hand, SOAP port is related to EG. In order to have this port enabled, you must have a SOAP Flow deployed on the EG in question. I'm not sure if you can have a soap port, same as the http port. Check info center, it has to contain this information.
I belive the error you've posted above is quite descriptive. |
Yes, I know the error message "URI /INQ does not map to any message flow in broker ... " is very descriptive ...
but that is not the exact problem ... the exact problem is, EG not taking the explicit port number being set, no matter how much i try ... even broker restart  (and many more things similar  ) |
|
| Back to top |
|
|
| Tech1621 |
| Posted: Thu Jun 13, 2013 1:54 am Post subject: Re: Soap Input Node in MB V6.1, Different for Windows and AI |
|
|
Novice
Joined: 29 May 2013
Posts: 23
|
| Veera B wrote: |
Hi ALL,
Having a problem of setting Port Number to EG, containing Soap Input node, in AIX. MB V6.1.
But the strange thing is, before trying to test in AIX, i tested in development box, which is windows. It was so simple, just used ,
mqsichangeproperties TEST -e exgro -o HTTPSConnector -n explicitlySetPortNumber -v 7777
mqsireload EGName.
But the same procedure in AIX is not working, even after trying for hours, re-deploy, restart flow, restart broker ... etc
can you pls suggest what else i need to do in AIX to set port .. |
I think you should use this command .. it may help..
mqsireportproperties 'BROKER NAME' -e 'Execution Group name' -o HTTPConnector -n port
to check the port number..
_________________
Anything is easy if you believe in yourself.. |
|
| Back to top |
|
|
| Esa |
| Posted: Thu Jun 13, 2013 1:58 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Applications cannot share a TCP/IP port number on the same machine. This applies to all platforms.
So if the broker wide listener is using 8080, no other application can run it. Not even your execution group.
If your flow needs to listen to that port, make it use the broker wide listener. |
|
| Back to top |
|
|
| McueMart |
| Posted: Thu Jun 13, 2013 2:13 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| So you are trying to explicitly set it to use port 7777 for the EG SOAP HTTPS listener. Have you used netstat to check this port isnt already in use? |
|
| Back to top |
|
|
| Veera B |
| Posted: Thu Jun 13, 2013 6:31 am Post subject: |
|
|
Voyager
Joined: 16 Jan 2013
Posts: 76
|
| Esa wrote: |
Applications cannot share a TCP/IP port number on the same machine. This applies to all platforms.
So if the broker wide listener is using 8080, no other application can run it. Not even your execution group.
If your flow needs to listen to that port, make it use the broker wide listener. |
How to achieve this ? I mean how to make my flow listen to broker wide listener ?
I tried to use 8080( broker wide listener ) along with /url, thinking its broker wide and i dont need to set explicitly,but its not accepting that also ... i am getting "URI /INQ does not map to any message flow in broker " error |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jun 13, 2013 6:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Migrate to MB v8.
Then you can change whether the SOAP nodes use the EG listener or the bipHTTPListener.
Otherwise, at v6.1, you have to manage this complexity yourself, where all SOAP flows use the EG level listener and each EG must use separate ports and you must either use the proxy servlet or manually configure an additional HTTP service that knows how to provide one endpoint to all of those EGs.
Again, migrate to v8. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
