| Author |
Message
|
| rohittom |
 Posted: Tue Oct 05, 2010 9:16 pm Post subject: Broker Http Listener Port |
 |
|
Novice
Joined: 15 Apr 2008
Posts: 15
|
Hi,
I am configuring Http Listener port for the broker.
Here are the commands i gave:-
mqsichangeproperties EAIDVBR1_BROKER -b httplistener -o HTTPListener -n enableSSLConnector -v false -
mqsichangeproperties EAIDVBR1_BROKER -b httplistener -o HTTPConnector -n port -v 7080
The Listener port seems to have configured however i see the following:-
Output of $ netstat -a|grep 7080
f100020001070808 dgram 0 0 0 f100020000ed9400 0 f10002000023a580
I would like to see something like:-
tcp 0 0 *.7083 *.* LISTEN
Output of mqsireportproperties EAIDVBR1_BROKER -b httplistener -o HTTPConnector -n port -a -r
HTTPConnector=''
uuid='HTTPConnector'
port='7080'
Have i done something wrong?
Please help!! |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Oct 05, 2010 10:54 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you restarted the broker.
btw, you commands shown :-
1) Please use [ code ] tags for the examples. They make the post much easier to follow.
2) Your example shows setting it to 7080 not 7083. Any reason why?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| rohittom |
| Posted: Wed Oct 06, 2010 5:29 am Post subject: |
|
|
Novice
Joined: 15 Apr 2008
Posts: 15
|
Yes i have recycled the broker.
No specific reason i gave 7080.
7083 is the default port, i just explicitely mentioned 7080
Thanks, |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 06, 2010 6:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| The bipHTTPlistener will not start until you deploy a flow that has an HTTPInput node in it. |
|
| Back to top |
|
|
| rohittom |
| Posted: Wed Oct 06, 2010 10:21 am Post subject: |
|
|
Novice
Joined: 15 Apr 2008
Posts: 15
|
I changed the port number to 7083.
Deployed the flow with Http Nodes. I can see biphttplistener up
ps -ef|grep biphttplistener
mqsiadm 364712 368852 0 13:12:43 - 0:03 biphttplistener EAIDVBR1_BROKER
However,
netstat -a | grep 7083 doesnt fetch anyhthing.
Output of
mqsireportproperties EAIDVBR1_BROKER -b httplistener -o HTTPConnector -n port -a -r
HTTPConnector=''
uuid='HTTPConnector'
port='7083'
Any clue? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 06, 2010 10:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| restart the broker a couple of times. |
|
| Back to top |
|
|
| rohittom |
| Posted: Wed Oct 06, 2010 10:46 am Post subject: |
|
|
Novice
Joined: 15 Apr 2008
Posts: 15
|
| I did 3 to 4 times still the same thing |
|
| Back to top |
|
|
| rohittom |
| Posted: Wed Oct 06, 2010 11:11 am Post subject: |
|
|
Novice
Joined: 15 Apr 2008
Posts: 15
|
I found what was missing:-
mqsichangeproperties EAIDVBR1_BROKER -b httplistener -o HTTPListener -n startListener -v true
I didnt gave start command to start the listner.
However still an issue, when i give this command, it thows the following error:-
BIP2051E: Broker EAIDVBR1_BROKER (UUID 1c24799e-2801-0000-0080-c23e40f76be4) could not process an internal configuration message to completion, the problem was caused by 'httplistener'.
The configuration message could not be processed and was rejected.
Use the inserts within this message to determine the cause of the problem. Correct the broker's configuration and redeploy using the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy application. Contact your IBM support center if you are unable to resolve the problem.
BIP2087E: Broker EAIDVBR1_BROKER was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP2051E: Broker EAIDVBR1_BROKER (UUID 1c24799e-2801-0000-0080-c23e40f76be4) could not process an internal configuration message to completion, the problem was caused by 'Change : HTTPListener : startListener'.
The configuration message could not be processed and was rejected.
Use the inserts within this message to determine the cause of the problem. Correct the broker's configuration and redeploy using the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy application. Contact your IBM support center if you are unable to resolve the problem. |
|
| Back to top |
|
|
|
|
