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 » biplistener - running but not listening?

Post new topic  Reply to topic
 biplistener - running but not listening? « View previous topic :: View next topic » 
Author Message
international
PostPosted: Fri Dec 15, 2006 3:26 am    Post subject: biplistener - running but not listening? Reply with quote

Apprentice

Joined: 19 Jun 2006
Posts: 37

Hello.
I'm unable to send http requests to the biphttplistener because it doesn't appear to be listening on the specified port.
I've set the http listener port to be 7151. Running mqsireportproperties shows the following:

HTTPConnector=''
uuid='HTTPConnector'
port='7151'

I have deployed a flow with an HTTPInput node. The Open Input count on SYSTEM.BROKER.WS.INPUT is 1. There is a biphttplistener running against the broker.
However, if I run a netstat, there is no evidence of anything listening to port 7151. Also, as expected, if I try to make an http request to that port (either via a browser window or via an HTTPRequest node) I get a "server not found" socket error.
I've stopped and started the broker twice - since that seems to be the magic number - to no avail. Worringly, when looking through the startup messages in the syslog, I can't find the normal message about "HTTP Listener started" (even though the biphttplistener does get started).

Have I missed something or does this look like a bug of some sort?

cheers
Tony

P.S. WBIMB v6 CSD2 AIX.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Dec 15, 2006 4:53 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Stop your broker.

If you see a bipHttpListener process running, kill it.

If you see any dataflow engine processess running, kill those.

Confirm that 7151 is not being used by anything else.

Start the broker again. Wait for messages about "Pub/Sub recovery completed" to show up for all Execution Groups. When those appear, you know everything has completed startup. See if there's anything about bipHttpListener starting up.

Is this a new installation, or an existing installation that had previously worked?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
international
PostPosted: Fri Dec 15, 2006 6:32 am    Post subject: Reply with quote

Apprentice

Joined: 19 Jun 2006
Posts: 37

Yes I've done all that.
This used to work. When it did, the syslog indicated successful startup of the HTTP Listener. It all started going pear shaped when I changed a url, recycled twice etc...!
Interestingly, I have just enabled the SSL Connector, just to see what would happen. The syslog had a message that the HTTPListener had started listening on port 7201 for https, and netstat shows that something is now listening on the https port - 7201. However, the http port (7151) is still unused.
I then killed biphttplistener. Upon restart of the biphttplistener process, the syslog again had a message that the HTTPListener was listening on port 7201 for https, but there wasn't the expected companion message saying it was listening on port 7151 for http. Netstat confirmed this.
Just for the hell of it, I then recycled the broker twice (all processes). Upon second restart, the situation was the same (syslog and netstat show https port being listened on, http port not being listened on).

There isn't an enableNonSSLConnector flag that I don't know about is there???
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Dec 15, 2006 6:42 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Did you deploy a flow with an HTTPInput node that is *not* using HTTPS?

I think, that, since the option on the node is a boolean, that it's one or the other, not both.

You could add another HTTPInput node to the same flow that doesn't have the checkbox checked.

It might not like having the same URL, though.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
international
PostPosted: Fri Dec 15, 2006 6:56 am    Post subject: Reply with quote

Apprentice

Joined: 19 Jun 2006
Posts: 37

I'm only deploying nodes for http, no https. I enabled the SSL connector purely on a "what if" basis.
I'm currently buttering up the unix guys in the hope of a recycle of the box...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » biplistener - running but not listening?
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.