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 » problem in Httpinput node

Post new topic  Reply to topic
 problem in Httpinput node « View previous topic :: View next topic » 
Author Message
sahamidas
PostPosted: Sun May 20, 2012 4:06 am    Post subject: problem in Httpinput node Reply with quote

Novice

Joined: 03 Mar 2012
Posts: 17

Hi,
I want, send data from web application to WMB(v 7.0.1).
web App : http://localhost:7080/Test.php
in WMB :
HTTP input node----> MQ OutPut
Path Suffix Http input node : http://localhost:7080/
I dont use HTTPS
but , i get this error :
--------------------------------------------------------------------------------
( MB7BROKER.HTTPListener ) An exception occurred while starting the servlet engine connector. Exception text is 'HTTP Listener LifecycleException: Protocol handler start failed: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind at org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1529) at com.ibm.broker.httplistener.ConnectorWrapper.start(ConnectorWrapper.java:165) at com.ibm.broker.httplistener.TomcatWrapper.startInsecureHTTPConnector(TomcatWrapper.java:304) at com.ibm.broker.httplistener.HTTPListenerManager.ensureServletContainer(HTTPListenerManager.java:296) at com.ibm.broker.httplistener.HTTPListenerManager.run(HTTPListenerManager.java:152) at java.lang.Thread.run(Thread.java:736) '

There are many possible causes of this error. Common causes are:
1: The SSL keystoreFile does not exist or could not be found at the location specified in the 'keystoreFile' property or in the default location of: (<home directory of user-id running the broker>\.keystore)
2: The SSL keystoreFile was found but was accessed with an incorrect password.
3: The SSL key alias in the keystore has a password that is different from the keystore password.
However, this may be an internal error, possibly due to a faulty installation. A review of the exception text may indicate a solution.

Stop the broker and if the exception text does not allow you to solve the problem then you should contact your IBM support center.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Sun May 20, 2012 5:20 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

What did you configure on the broker at all?

What did you configure on the HTTPInput node in the flow you deployed?
Back to top
View user's profile Send private message
sahamidas
PostPosted: Sun May 20, 2012 9:02 pm    Post subject: Reply with quote

Novice

Joined: 03 Mar 2012
Posts: 17

I set this config:

aphachii : localhost:7080
webapp: http://localhost/Test.php?Name=name1
Httpinput node : path suffix --> http://localhost:7080/ and message domain : Blob and other property is defult
MQOutput node : Queue name--> XML_OUT and other property is defult
mqsichangeproperties MB7BROKER -b httplistener -o HTTPListener -n startListener -v true
Back to top
View user's profile Send private message
smdavies99
PostPosted: Sun May 20, 2012 11:01 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Did you (do one or more of the following)

1) Confirm that something is indeed listening on port 7080?
2) try telnetting to that port?
3) Deploy and use the HTTP Samples?
_________________
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
View user's profile Send private message
sahamidas
PostPosted: Mon May 21, 2012 7:22 pm    Post subject: Reply with quote

Novice

Joined: 03 Mar 2012
Posts: 17

1) I think Ok , but not ensure
2) yes,Telnet is OK
3) NO
Back to top
View user's profile Send private message
smdavies99
PostPosted: Mon May 21, 2012 10:25 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Are you going to deply the samples as your next step?
It would prove that the problem is either in your configuration or in your code.
_________________
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
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 » problem in Httpinput node
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.