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 » webservice + biphttplistener problem

Post new topic  Reply to topic
 webservice + biphttplistener problem « View previous topic :: View next topic » 
Author Message
vmurali_au
PostPosted: Mon May 16, 2005 11:38 pm    Post subject: webservice + biphttplistener problem Reply with quote

Voyager

Joined: 26 Mar 2004
Posts: 76

I have developed a simple http flow which has a HTTP Request node which forwards the request to "http://localhost:7070/svc1"
I also has a webserbice flow running with HTTP Input node property set to "/svc1".
While creating the broker i specified the Http Listener port as 7070 and i could see the 'biphttplistener" process running.

But when i apss the Input xml message i'm getting the error tht the webservice "/svc1" is not found in the localhost portno 7070. I'm also getting socket communications Connect() error.

I want to know how to check whether the webservice is available. I tried doing atelnet to port 7070 but the conection was refused, and also "netstat -an" command didnot list the port "7070" as listening.

Can i modify the broker again and give a new port number?.
Back to top
View user's profile Send private message
mgk
PostPosted: Tue May 17, 2005 3:34 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

You can use mqsichangebroker t-P o change the httplistener port. If you want to try to see if a connection to your web service is possible, try telneting to the port. Make sure the port is open and not blocked by a firewall
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue May 17, 2005 4:00 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

The port doesn't actually get opened until you deploy a flow with an HTTPInput node in it to the broker.

Are you sure the flow deployed correctly?

Try restarting the broker.

Also, as mgk said - make sure there aren't firewall rules in effect.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
vmurali_au
PostPosted: Tue May 17, 2005 6:30 am    Post subject: Reply with quote

Voyager

Joined: 26 Mar 2004
Posts: 76

No i have deployed the HTTP Input message flow in the broker. There is no firewall issue also because i'm testing this flow in my local developement PC.

After i deployed the flow to Broker, i dd a telnet to port 7070. But the connection was refused. Also as i mentioned before there is no reference of port 7070 in the "netstat -an" output. But i could see the portno 7070 value mentioned in the windows regisrty.

I guess due to some issues biphttplistener is not responding to requests.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue May 17, 2005 6:36 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

If the port is not open in netstat, then the biphttpservice is not listening properly. I know for a fact that the port does not get opened unless there is a flow actively deployed.

Again, make sure that the flow deployed successfully!

Does the Broker Domain show that it is deployed and running?

Are there any errors in the Event Log?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
vmurali_au
PostPosted: Thu May 26, 2005 3:19 am    Post subject: Problem Solved Reply with quote

Voyager

Joined: 26 Mar 2004
Posts: 76

The problem was solved

When i went through logs, I found i was getting some saxon & xerces parsing errors in the Event Log.
I had placed my own saxon & xerces jars in the CLASSPATH and also had TomCat 5.0 installed separately.

I removed the aboves jars from the CLASSPATH and unistalled Tomcat too. Now i restarted the broker. Now Event Log says "HttpListener was started successfully on port 7070"

I think the problem was with the incompatiable jars in the CLASSPATH.

Thanks for the help.
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 » webservice + biphttplistener problem
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.