Author |
Message
|
MB_Naveen_Kumar |
Posted: Thu Apr 08, 2010 3:28 am Post subject: Https Port issue for many Execution groups |
|
|
Novice
Joined: 25 Mar 2010 Posts: 16
|
Hi ,
I am trying to set https port number to a execution group using mqsichange properties command, but not possible. There is one more execution group associated with the broker for which the command had worked and its https port is working fine. This is the command
C:\Program Files\IBM\MQSI\7.0>mqsichangeproperties broker3 -e AddressSampleProvider -o HTTPSConnector -n port -v 7900
when the above command is run for 2nd execution group i am getting a successful command completion feedback , but when the mqsi report properties command is run its displaying port as 0, and for comfirmation web service also not working. tried restarting the broker many times also..
got a similar post in mqseries for HTTP port issue but didnt work for me as it is HTTPS in mb7...
Can we not associate more execution group in a broker with different Https ports ? how can i solve this ..? |
|
Back to top |
|
 |
maesbrae |
Posted: Thu Apr 08, 2010 4:55 am Post subject: |
|
|
Novice
Joined: 03 Jun 2003 Posts: 12
|
Try the property name -n explicitlySetPortNumber rather than port |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Apr 08, 2010 5:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I agree with what maesbrae said.
Also remember that you can not put two things listening to the same combination of IP address and Port, so each EG is going to have to have a unique set of values for the HTTPSConnector and the HTTPConnector.
See the following technote: http://www-01.ibm.com/support/docview.wss?uid=swg21420032 |
|
Back to top |
|
 |
shaon |
Posted: Mon Jun 17, 2013 5:48 am Post subject: Issue with detemining the port for Execution group in WMB6.1 |
|
|
Newbie
Joined: 17 Jun 2013 Posts: 1
|
I am facing an issue similar to the same posted here .
I am using WMQ v 6.1/WMB 6.1 in Windows XP environment.
I have created a new execution group but after deploying the flow the following
mqsireportproperties CXIP_BRK -e LOCAL_PERFT -o HTTPConnector -n port
"0"
The following are the steps i have tried
Step 1: USed the following commands to set the Port number
(1)mqsichangeproperties CXIP_BRK -e LOCAL_PERF -o HTTPConnector -n explicitlySetPortNumber -v 7803
(2)mqsichangeproperties CXIP_BRK -e LOCAL_PERF -o HTTPSConnector -n port -v 7805
Neither of them worked
Step 2:-
----------
Checked with netstat -b to check the usage of Ports for the EGs..This EG was not reflected neither could i test the same.
Step 3:-
-------------
Restarted the EGs , as it didnt work restarted the Broker as well but neither did the Same work.
Step 4: Checked the EventVwr nothing was depicted.
-----------
I am unable to test a web service as it gives the error "Socket connection refused" in this EG..
Please can you help me out with any solution on the same.
Thanks in advance . |
|
Back to top |
|
 |
Vitor |
Posted: Mon Jun 17, 2013 6:04 am Post subject: Re: Issue with detemining the port for Execution group in WM |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
shaon wrote: |
I am facing an issue similar to the same posted here . |
But not the same because:
shaon wrote: |
I am using WMQ v 6.1/WMB 6.1 in Windows XP environment. |
The OP is using WMBv7, which has different port handling.
I have created a new execution group but after deploying the flow the following
shaon wrote: |
mqsireportproperties CXIP_BRK -e LOCAL_PERFT -o HTTPConnector -n port |
I'm assuming the difference in EG name is a typo?
What kind of node does the flow have? SOAPInput or HTTPInput?
shaon wrote: |
The following are the steps i have tried
Step 1: USed the following commands to set the Port number
(1)mqsichangeproperties CXIP_BRK -e LOCAL_PERF -o HTTPConnector -n explicitlySetPortNumber -v 7803
(2)mqsichangeproperties CXIP_BRK -e LOCAL_PERF -o HTTPSConnector -n port -v 7805
Neither of them worked |
Does it work with the default port?
shaon wrote: |
----------
Checked with netstat -b to check the usage of Ports for the EGs..This EG was not reflected neither could i test the same. |
What do you mean by this? You won't see the EG in a netstat, just the in-use port _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|