ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » URL for HTTP Input flow

Post new topic  Reply to topic Goto page Previous  1, 2
 URL for HTTP Input flow « View previous topic :: View next topic » 
Author Message
jefflowrey
PostPosted: Wed Apr 02, 2008 6:36 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

mrgate wrote:
mgk wrote:
I can cannot telnet to the port, then either you are blocked by a firewall or the broker is not listening. To determine this you can issue "netstat -a" to see if the listener is listening.


from the reslut of mqsireport command, we can clearly see that broker is listening on port.


No.

We can see the port that the bipHttpListener will use, if it starts up correctly.

That doesn't mean that it is started up correctly.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
abhishekpreddy
PostPosted: Thu Apr 03, 2008 12:27 am    Post subject: Reply with quote

Apprentice

Joined: 02 May 2007
Posts: 49

Hey if you have a Http node in your flows , and if you restart your broker you can check the Event log if you are on windows or the sys logs on Unix to check if the Httplistner is running , if it is up if would give the message like

(HTTPListener)[3856]BIP3132I: The HTTP Listener has started listening on port '7080' for 'http' connections. If you dont get this then check the registry settings of the broker for the port number of your http listener or using the mqsireportproperties command.

Check using netstat if the port is being used by some other application , if so then either turn the other application down , or change the default port of ur broker to some other value and do a restart and check if its listening
Back to top
View user's profile Send private message
marcin.kasinski
PostPosted: Thu Apr 03, 2008 12:52 am    Post subject: Reply with quote

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

abhishekpreddy wrote:

Check using netstat if the port is being used by some other application


I think the port is not used by any application because telnet failed.
_________________
Marcin
Back to top
View user's profile Send private message Visit poster's website
jfry
PostPosted: Thu Apr 03, 2008 5:35 am    Post subject: Reply with quote

Apprentice

Joined: 31 Mar 2008
Posts: 32

I tried the "netstat -a" and did not see anything in there for prot 7080. I also looked at the Windows Event Viewer and the only log I see that has anything to do with "listening" is:

The Listener 'LISTENER.TCP' has started. ProcessId(1456).

The Listener process has started.

None.

I still cannot telnet to localhost 7080.

Also, when I look at the Listeners for my Queue Manager in MQ Explorer, I only see one defined as follows:

Listener name: LISTENER.TCP
Control: Queue manager
Status: Running
Xmit protocol: TCP
Port: 1414
all other fields are blank.

Does this look correct and should I have more listeners than just this one, say one that is listening on port 7080?

Thanks.
Back to top
View user's profile Send private message
marcin.kasinski
PostPosted: Thu Apr 03, 2008 6:11 am    Post subject: Reply with quote

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

We are talking about broker HTTP listener.
You are talking about QMGR MQ listener.
These are totally different things.
_________________
Marcin
Back to top
View user's profile Send private message Visit poster's website
jfry
PostPosted: Thu Apr 03, 2008 6:15 am    Post subject: Reply with quote

Apprentice

Joined: 31 Mar 2008
Posts: 32

OK....Any other ideas as to why the broker HTTP listener isn't listening? From all of the above posts, it seems that the broker is configured correctly to listen on port 7080 (mqsireport command) but is not actually doing so (netstat -a and telnet test). A firewall issue would not prevent the broker from listening correct? So what would cause it to not even "start"?
Back to top
View user's profile Send private message
marcin.kasinski
PostPosted: Thu Apr 03, 2008 6:28 am    Post subject: Reply with quote

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

Restart broker , show here event log and mqsilist output with your dev flows.
_________________
Marcin
Back to top
View user's profile Send private message Visit poster's website
jfry
PostPosted: Thu Apr 03, 2008 6:35 am    Post subject: Reply with quote

Apprentice

Joined: 31 Mar 2008
Posts: 32

Event logs from broker restart:

**************************
( Local_Broker ) The WebSphere Message Brokers service has started at version '6003'; process ID 3724.

The WebSphere Message Brokers service executable has been started.
**************************
( Local_Broker.IVR ) Execution Group started: process '5632'; thread '1924'; additional information: brokerName ''Local_Broker''; executionGroupUUID ''26a9ae10-1901-0000-0080-b673a46d7ef0''; executionGroupLabel ''IVR''; defaultExecutionGroup 'true'; queueManagerName ''Local_Que_Mgr''; trusted 'false'; dataSourceName ''DEFLOCDB''; userId ''Isjaf''; migrationNeeded 'false'; brokerUUID ''868ca310-1901-0000-0080-b673a46d7ef0''; filePath ''d:\IBM\MQSI\6.0''; workPath ''C:\Documents and Settings\All Users\Application Data\IBM\MQSI''; ICU Converter Path ''''.

The execution Group has started using process '5632' and thread '1924' and will now start processing messages.
***************************
( Local_Broker.IVR ) Publish/Subscribe subscriptions recovery started.

The Publish/Subscribe broker is recovering subscriptions from the broker's database.

This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
***************************
( Local_Broker.IVR ) Publish/Subscribe state recovery completed.

Recovery of the Publish/Subscribe state from the broker's database is complete.

This message is for information only. No action is required.
***************************

mqsilist for my flows:

d:\IBM\MQSI\6.0>mqsilist -a Local_Broker -e IVR
BIP8131I: MessageFlow: IvrDentalBenefitsDev

BIP8071I: Successful command completion.

***************************

I hope that is what you were looking for. Thanks.
Back to top
View user's profile Send private message
abhishekpreddy
PostPosted: Thu Apr 03, 2008 6:46 am    Post subject: Reply with quote

Apprentice

Joined: 02 May 2007
Posts: 49

Hey Just a silly question , but does the flow which you deploy have a Http Node in it
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Apr 03, 2008 6:51 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

jfry wrote:
OK....Any other ideas as to why the broker HTTP listener isn't listening? From all of the above posts, it seems that the broker is configured correctly to listen on port 7080 (mqsireport command) but is not actually doing so (netstat -a and telnet test). A firewall issue would not prevent the broker from listening correct? So what would cause it to not even "start"?


Have you tried explicitly starting the broker's listener? IIRC it doesn't auto start when the broker does by default.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jfry
PostPosted: Thu Apr 03, 2008 6:57 am    Post subject: Reply with quote

Apprentice

Joined: 31 Mar 2008
Posts: 32

abhishekpreddy wrote:
Hey Just a silly question , but does the flow which you deploy have a Http Node in it


It starts with an HTTP Input node.

How do I explicitly start the broker's listener?
Back to top
View user's profile Send private message
jfry
PostPosted: Thu Apr 03, 2008 7:06 am    Post subject: Reply with quote

Apprentice

Joined: 31 Mar 2008
Posts: 32

Not sure what happened but it is now listening on port 7080. I didn't do anything other than recreate and redeploy the BAR file, restart the broker, etc. about 50 times.

THANK YOU to all of you for your help!!!
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Apr 03, 2008 7:07 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

jfry wrote:
How do I explicitly start the broker's listener?


Maybe you don't. Maybe I'm wrong. It does happen.

$64,000 question - is biphttplistener actually running? If not, are you convinced your flow deployed correctly?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jfry
PostPosted: Thu Apr 03, 2008 7:19 am    Post subject: Reply with quote

Apprentice

Joined: 31 Mar 2008
Posts: 32

I would assume it deployed correctly because it is responding with the data that I am expecting and it is creating the trace files I was wanting.
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Apr 03, 2008 7:23 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

jfry wrote:
I would assume it deployed correctly because it is responding with the data that I am expecting and it is creating the trace files I was wanting.


I think our posts sort of crossed in the mail. My question was directed to the state before it started working.

Clearly now it's listening, all is indeed well & all is indeed deployed.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » URL for HTTP Input flow
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.