|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Port is not Listening |
« View previous topic :: View next topic » |
Author |
Message
|
agrawalamit166 |
Posted: Thu Sep 17, 2015 6:54 am Post subject: Port is not Listening |
|
|
 Voyager
Joined: 17 Aug 2009 Posts: 78 Location: NY, US
|
Hi,
I am using IIB 10.0.0.1 version,
I create one flow SOAPINPUT --- ComputeNode --- SOAP Reply
It works fine with HTTP (do not check "Use HTTPS" properties on SOAPInput Node)
With checked "Use HTTPS" checkbox, i am able to deploy bar file on EG2, but i could not see LISTENING PORT 7880 through netstat command.
Below is SOAPUI error message after invoking HTTPS URL:
Code: |
Thu Sep 17 09:46:32 CDT 2015:ERROR:org.apache.http.conn.HttpHostConnectException: Connection to https://localhost:7880 refused
|
I defined the EG's properties explicitlySetPortNumber = 7880
Code: |
C:\Program Files\IBM\IIB\10.0.0.1\server\bin>mqsireportproperties BROKER_NAME -e EG2 -o HTTPSConnector -a
HTTPSConnector
uuid='HTTPSConnector'
userTraceLevel='trace'
traceLevel='trace'
userTraceFilter='trace'
traceFilter='trace'
port='0'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests='0'
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay='true'
explicitlySetPortNumber='7880'
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
integratedWindowsAuthentication=''
iwaTimeoutSeconds='300'
serverName=''
corsEnabled='false'
corsAllowOrigins='*'
corsAllowCredentials='false'
corsExposeHeaders='Content-Type'
corsMaxAge='-1'
corsAllowMethods='GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS'
corsAllowHeaders='Accept,Accept-Language,Content-Language,Content-Type'
algorithm=''
clientAuth='true'
keystoreFile=''
keystorePass=''
keystoreType=''
truststoreFile=''
truststorePass=''
truststoreType=''
sslProtocol='SSL'
ciphers=''
keypass=''
keyAlias=''
sslSessionTimeout=''
crlFile=''
propagateClientCert=''
sessionCacheSize=''
|
Here is the netstat command:
Code: |
C:\>netstat -anp tcp | find ":7800"
TCP 0.0.0.0:7800 0.0.0.0:0 LISTENING
C:\>netstat -anp tcp | find ":7880"
C:\>
|
7800 is different EG's HTTP port, which I can see.
7880 is EG2 HTTPS's port
Thanks,
Amit |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Sep 17, 2015 7:01 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
did you restart the EG after setting the properties? _________________ 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 |
|
 |
agrawalamit166 |
Posted: Thu Sep 17, 2015 7:08 am Post subject: |
|
|
 Voyager
Joined: 17 Aug 2009 Posts: 78 Location: NY, US
|
Thanks for response,
Yes, I have restarted EG2 (IIB Server) and even broker (IIB Node) as well, but still not able to see the port in netstat.
I have even tried to change HTTPS port number to other HTTPS port, but could not able to make call.
Regards,
Amit |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 17, 2015 7:15 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
agrawalamit166 wrote: |
Yes, I have restarted EG2 (IIB Server) and even broker (IIB Node) as well, but still not able to see the port in netstat. |
In the mqsireportproperties for EG2 does it show the URL in your SOAPInput node registered with the HTTPConnector or the HTTPSConnector? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
agrawalamit166 |
Posted: Thu Sep 17, 2015 7:25 am Post subject: |
|
|
 Voyager
Joined: 17 Aug 2009 Posts: 78 Location: NY, US
|
Where can i check URL Associated with SOAPInput ( Flow has the URL details, As i can invoke, when i uncheck "use HTTPS" checkbox)
Here is HTTP Connector details:
Code: |
C:\Program Files\IBM\IIB\10.0.0.1\server\bin>mqsireportproperties BROKER_NAME -e EG2 -o HTTPConnector -a
HTTPConnector
uuid='HTTPConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='0'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests='0'
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay='true'
explicitlySetPortNumber=''
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
integratedWindowsAuthentication=''
iwaTimeoutSeconds='300'
serverName=''
corsEnabled='false'
corsAllowOrigins='*'
corsAllowCredentials='false'
corsExposeHeaders='Content-Type'
corsMaxAge='-1'
corsAllowMethods='GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS'
corsAllowHeaders='Accept,Accept-Language,Content-Language,Content-Type'
BIP8071I: Successful command completion.
|
Here is EG Details:
Code: |
C:\Program Files\IBM\IIB\10.0.0.1\server\bin>mqsireportproperties BROKER_NAME -e EG2 -o ExecutionGroup -r
ExecutionGroup
uuid='9d554f74-5e1d-4df9-b748-7bdb732aa68c'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
label='IB10Srv1'
unnamedUserTraceLevel='none'
unnamedTraceLevel='none'
processorArchitecture='64'
consoleMode='on'
traceNodeLevel='on'
activeUserExitList=''
inactiveUserExitList=''
shortDesc=''
longDesc=''
injectionMode='Disabled'
httpNodesUseEmbeddedListener='true'
soapNodesUseEmbeddedListener='true'
threadLocalProxyNameManagers='false'
BIP8071I: Successful command completion.
|
|
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 17, 2015 7:28 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
use -r not -a at the end of the command _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
agrawalamit166 |
Posted: Thu Sep 17, 2015 7:48 am Post subject: |
|
|
 Voyager
Joined: 17 Aug 2009 Posts: 78 Location: NY, US
|
HTTPConnector details
Code: |
C:\Program Files\IBM\IIB\10.0.0.1\server\bin>mqsireportproperties BROKER_NAME -e EG2 -o HTTPConnector -r
HTTPConnector
uuid='HTTPConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='0'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests='0'
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay='true'
explicitlySetPortNumber=''
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
integratedWindowsAuthentication=''
iwaTimeoutSeconds='300'
serverName=''
corsEnabled='false'
corsAllowOrigins='*'
corsAllowCredentials='false'
corsExposeHeaders='Content-Type'
corsMaxAge='-1'
corsAllowMethods='GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS'
corsAllowHeaders='Accept,Accept-Language,Content-Language,Content-Type'
BIP8071I: Successful command completion.
|
HTTPSConnector details
Code: |
C:\Program Files\IBM\IIB\10.0.0.1\server\bin>mqsireportproperties BROKER_NAME -e EG2 -o HTTPSConnector -r
HTTPSConnector
uuid='HTTPSConnector'
userTraceLevel='trace'
traceLevel='trace'
userTraceFilter='trace'
traceFilter='trace'
port='0'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests='0'
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay='true'
explicitlySetPortNumber='7880'
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
integratedWindowsAuthentication=''
iwaTimeoutSeconds='300'
serverName=''
corsEnabled='false'
corsAllowOrigins='*'
corsAllowCredentials='false'
corsExposeHeaders='Content-Type'
corsMaxAge='-1'
corsAllowMethods='GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS'
corsAllowHeaders='Accept,Accept-Language,Content-Language,Content-Type'
algorithm=''
clientAuth='true'
keystoreFile=''
keystorePass=''
keystoreType=''
truststoreFile=''
truststorePass=''
truststoreType=''
sslProtocol='SSL'
ciphers=''
keypass=''
keyAlias=''
sslSessionTimeout=''
crlFile=''
propagateClientCert=''
sessionCacheSize=''
BIP8071I: Successful command completion.
C:\Program Files\IBM\IIB\10.0.0.1\server\bin>
|
|
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 17, 2015 7:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
The URL is the combination of the hostname of the broker machine, the HTTP/HTTPS port the EG SOAP Listener(or bipHTTPListener, if you've told the EG to use that) and then the SOAP url on the SOAPInput node.
Your mqsireportpropertis shows the explicitlySetPortNumber. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
agrawalamit166 |
Posted: Thu Sep 17, 2015 8:16 am Post subject: |
|
|
 Voyager
Joined: 17 Aug 2009 Posts: 78 Location: NY, US
|
Just wanted to share more details:
I unchecked "use HTTPs" checkbox, deployed the code and run netstat command, it shows:
Code: |
C:\>netstat -anp tcp | find ":78"
TCP 0.0.0.0:7800 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7801 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7802 0.0.0.0:0 LISTENING
|
I again checked "use HTTPs" checkbox, deployed the code and run netstat command, it shows:
Code: |
C:\>netstat -anp tcp | find ":78"
TCP 0.0.0.0:7800 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7801 0.0.0.0:0 LISTENING
TCP 127.0.0.1:7802 127.0.0.1:62879 TIME_WAIT
|
i am referring 7802 port |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 17, 2015 8:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Ok.
So your HTTPSConnector isn't running.
Or you need to netstat -tnlp _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
agrawalamit166 |
Posted: Thu Sep 17, 2015 10:08 am Post subject: |
|
|
 Voyager
Joined: 17 Aug 2009 Posts: 78 Location: NY, US
|
I run following command:
Code: |
C:\>netstat -tnlp
Displays protocol statistics and current TCP/IP network connections.
NETSTAT [-a] [-b] [-e] [-f] [-n] [-o] [-p proto] [-r] [-s] [-t] [interval]
-a Displays all connections and listening ports.
-b Displays the executable involved in creating each connection or
listening port. In some cases well-known executables host
multiple independent components, and in these cases the
sequence of components involved in creating the connection
or listening port is displayed. In this case the executable
name is in [] at the bottom, on top is the component it called,
and so forth until TCP/IP was reached. Note that this option
can be time-consuming and will fail unless you have sufficient
permissions.
-e Displays Ethernet statistics. This may be combined with the -s
option.
-f Displays Fully Qualified Domain Names (FQDN) for foreign
addresses.
-n Displays addresses and port numbers in numerical form.
-o Displays the owning process ID associated with each connection.
-p proto Shows connections for the protocol specified by proto; proto
may be any of: TCP, UDP, TCPv6, or UDPv6. If used with the -s
option to display per-protocol statistics, proto may be any of:
IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6.
-r Displays the routing table.
-s Displays per-protocol statistics. By default, statistics are
shown for IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, and UDPv6;
the -p option may be used to specify a subset of the default.
-t Displays the current connection offload state.
interval Redisplays selected statistics, pausing interval seconds
between each display. Press CTRL+C to stop redisplaying
statistics. If omitted, netstat will print the current
configuration information once.
|
I believe the above mentioned command is for Linux not for Window. I have IIB on window.
Also It might be possible that HTTPSConnector is not running, because i tried to deploy HTTPS flow on multiple EGs, but i could not see https listening port through netstat command.
Please let me know, how to validate and start HTTPSConnector.
Regards,
Amit |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 17, 2015 10:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
No, -tnlp is for different versions of netstat than you have.
the -l is supposed to indicate "only show ports that are in LISTEN status.
So, netstat -tnp |grep "LISTEN"
EDit:
well, netstat -tnp|grep /i "listen"
and on windows
netstat -a|find /i "listen" _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Sep 17, 2015 10:16 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
mqjeff wrote: |
No, -tnlp is for different versions of netstat than you have.
the -l is supposed to indicate "only show ports that are in LISTEN status.
So, netstat -tnp |grep "LISTEN" |
'grep' on Windows? Ok, I have a copy of grep.exe but 99.9999% of windows users don't have the luxury of grep when running windows.
I think you might have meant 'find' _________________ 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 |
|
 |
agrawalamit166 |
Posted: Thu Sep 17, 2015 10:21 am Post subject: |
|
|
 Voyager
Joined: 17 Aug 2009 Posts: 78 Location: NY, US
|
I run following command:
Code: |
C:\>netstat -tnp tcp | find "LISTEN"
C:\>netstat -anp tcp | find "LISTEN"
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:623 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1198 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2820 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2822 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4415 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7800 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7801 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:16992 0.0.0.0:0 LISTENING
TCP 0.0.0.0:32434 0.0.0.0:0 LISTENING
TCP 0.0.0.0:42003 0.0.0.0:0 LISTENING
TCP 0.0.0.0:43243 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49157 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49159 0.0.0.0:0 LISTENING
TCP 0.0.0.0:55641 0.0.0.0:0 LISTENING
TCP 0.0.0.0:55644 0.0.0.0:0 LISTENING
TCP 0.0.0.0:57998 0.0.0.0:0 LISTENING
TCP 127.0.0.1:4242 0.0.0.0:0 LISTENING
TCP 127.0.0.1:6500 0.0.0.0:0 LISTENING
TCP 127.0.0.1:6501 0.0.0.0:0 LISTENING
TCP 127.0.0.1:6502 0.0.0.0:0 LISTENING
TCP 127.0.0.1:11884 0.0.0.0:0 LISTENING
TCP 127.0.0.1:54234 0.0.0.0:0 LISTENING
TCP 172.25.13.125:139 0.0.0.0:0 LISTENING
TCP 172.28.85.40:139 0.0.0.0:0 LISTENING
|
Code: |
C:\Program Files\IBM\IIB\10.0.0.1\server\bin>netstat -a|find /i "listen"
TCP 0.0.0.0:135 S223292:0 LISTENING
TCP 0.0.0.0:445 S223292:0 LISTENING
TCP 0.0.0.0:623 S223292:0 LISTENING
TCP 0.0.0.0:1198 S223292:0 LISTENING
TCP 0.0.0.0:2820 S223292:0 LISTENING
TCP 0.0.0.0:2822 S223292:0 LISTENING
TCP 0.0.0.0:4415 S223292:0 LISTENING
TCP 0.0.0.0:7800 S223292:0 LISTENING
TCP 0.0.0.0:7801 S223292:0 LISTENING
TCP 0.0.0.0:8001 S223292:0 LISTENING
TCP 0.0.0.0:16992 S223292:0 LISTENING
TCP 0.0.0.0:32434 S223292:0 LISTENING
TCP 0.0.0.0:42003 S223292:0 LISTENING
TCP 0.0.0.0:43243 S223292:0 LISTENING
TCP 0.0.0.0:49152 S223292:0 LISTENING
TCP 0.0.0.0:49153 S223292:0 LISTENING
TCP 0.0.0.0:49154 S223292:0 LISTENING
TCP 0.0.0.0:49155 S223292:0 LISTENING
TCP 0.0.0.0:49156 S223292:0 LISTENING
TCP 0.0.0.0:49157 S223292:0 LISTENING
TCP 0.0.0.0:49158 S223292:0 LISTENING
TCP 0.0.0.0:49159 S223292:0 LISTENING
TCP 0.0.0.0:55641 S223292:0 LISTENING
TCP 0.0.0.0:55644 S223292:0 LISTENING
TCP 0.0.0.0:57998 S223292:0 LISTENING
TCP 127.0.0.1:4242 S223292:0 LISTENING
|
|
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 17, 2015 10:45 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
I still find it interesting that neither command shows the URL registered with the connector, even when the flow "works" with HTTP not HTTPS.
If this is a change between IIBv9 and IIBv10, then I consider this a retrograde step.
The most common reason for a port not being open is the connector not running, the most common reason for that is that no flow is actually registered with it due to deployment or configuration errors. Checking with the connector via mqsireportproperties is something I encourage my customers to do before telling me my platform isn't working. It's going to be a shame if they've lost this ability. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|
|
 |
Goto page 1, 2 Next |
Page 1 of 2 |
|
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
|
|
|
|