| Author |
Message
|
| mqjeff |
 Posted: Fri Nov 06, 2015 12:24 pm Post subject: |
 |
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| mqjeff wrote: |
| zhaider wrote: |
| Yes, I'm still getting the page not found error. |
An MQ queue manager never returns that error. |
And a broker (which the OP is trying to contact) doesn't either. |
... you mean a broker HTTP listener won't respond to a request with a 404 ... ?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
 |
| zhaider |
| Posted: Sun Nov 08, 2015 10:30 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
| Vitor wrote: |
| mqjeff wrote: |
| zhaider wrote: |
| Yes, I'm still getting the page not found error. |
An MQ queue manager never returns that error. |
And a broker (which the OP is trying to contact) doesn't either.
I keep trying to tell the OP that he's not got the problem he thinks he has, but he doesn't believe me. |
I do believe you. I'm just not sure, how can I debug it? Can you get me a sample app that works correctly? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Nov 08, 2015 10:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
I think what Vitor is trying to let you know is that you may have a bad port or a malformed URL or conflicting URLS...
Can you give us the output of
mqsireportproperties <broker> -e <eg> -o HTTPSConnector -r for all brokers and execution groups on the machine where the port matches the port you are trying to reach?
If none is configured you are running into a config problem:
The port number is wrong
The SSL setup of your eg is wrong preventing the eg from opening the SSL port after deployment of your flow...
Your flow never deployed to the eg and is the only flow requiring SSL, as such the eg never opened the SSL port.
Your flow is deployed but the URL does not match the request URL and this is why you receive the 404...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zhaider |
| Posted: Sun Nov 08, 2015 11:01 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
| fjb_saper wrote: |
I think what Vitor is trying to let you know is that you may have a bad port or a malformed URL or conflicting URLS...
Can you give us the output of
mqsireportproperties <broker> -e <eg> -o HTTPSConnector -r for all brokers and execution groups on the machine where the port matches the port you are trying to reach?
If none is configured you are running into a config problem:
The port number is wrong
The SSL setup of your eg is wrong preventing the eg from opening the SSL port after deployment of your flow...
Your flow never deployed to the eg and is the only flow requiring SSL, as such the eg never opened the SSL port.
Your flow is deployed but the URL does not match the request URL and this is why you receive the 404...
Have fun |
Will post the output as soon as I get to work tomorrow. But I think this command did return the correct HTTPS port when I ran earlier. |
|
| Back to top |
|
|
| zhaider |
| Posted: Wed Nov 11, 2015 4:39 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
| zhaider wrote: |
| fjb_saper wrote: |
I think what Vitor is trying to let you know is that you may have a bad port or a malformed URL or conflicting URLS...
Can you give us the output of
mqsireportproperties <broker> -e <eg> -o HTTPSConnector -r for all brokers and execution groups on the machine where the port matches the port you are trying to reach?
If none is configured you are running into a config problem:
The port number is wrong
The SSL setup of your eg is wrong preventing the eg from opening the SSL port after deployment of your flow...
Your flow never deployed to the eg and is the only flow requiring SSL, as such the eg never opened the SSL port.
Your flow is deployed but the URL does not match the request URL and this is why you receive the 404...
Have fun |
Will post the output as soon as I get to work tomorrow. But I think this command did return the correct HTTPS port when I ran earlier. |
Here is the command output:
| Code: |
C:\Program Files\IBM\MQSI\9.0.0.0\jre17\lib\security>mqsireportproperties SOAUBL
Broker -e Ofam -o HTTPSConnector -r
HTTPSConnector
uuid='HTTPSConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='trace'
port='7963'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
explicitlySetPortNumber='7963'
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
algorithm=''
clientAuth='true'
keystoreFile='C:\Program Files (x86)\IBM\source\WebSphere MQ 7.5.0.5\jre\jre\b
in\SOAUBLBroker.jks'
keystorePass='********'
keystoreType='JKS'
truststoreFile=''
truststorePass='********'
truststoreType=''
sslProtocol='SSLv3'
ciphers=''
keypass='********'
keyAlias=''
sslSessionTimeout=''
crlFile=''
propagateClientCert=''
Connector
port='7963'
type='Embedded'
URLRegistration
url='/OFAMWebEx'
outstandingRequests='0'
outstandingTimeoutRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='SOAP Input'
URLRegistration
url='/TemperatureConverter/TemperatureConverter'
outstandingRequests='0'
UsedBySOAPNNodes='TRUE'
UsedByHTTPNNodes='FALSE'
nodeLabel='SOAP Input'
BIP8071I: Successful command completion. |
|
|
| Back to top |
|
|
| zhaider |
| Posted: Wed Nov 11, 2015 4:48 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
Okay, one more thing I may not be quite accurate in describing the issue. I actually got the Page can't be displayed. message with the following description in the browser:
Make sure TLS, TLS1.0, are enabled on your browser.
And when I checked the Event Viewer I got the following error:
| Code: |
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 40. |
Now I think that it could be an issue with a certificate so I got my self a self signed certificate from http://www.selfsignedcertificate.com/ and only used the certificate to configure the SSL again. Now again, the browser replied with Page can't be displayed but with the following description:
•Make sure the web address is correct.
•Look for the page with your search engine.
•Refresh the page in a few minutes.
Now the following errors appeared in the Event viewer:
| Code: |
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 50. The Windows SChannel error state is 1114.
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 823. |
Did I make any improvements or actually made the problem worse, any idea?[/code] |
|
| Back to top |
|
|
| zhaider |
| Posted: Thu Nov 12, 2015 5:50 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2015
Posts: 40
|
| zhaider wrote: |
Okay, one more thing I may not be quite accurate in describing the issue. I actually got the Page can't be displayed. message with the following description in the browser:
Make sure TLS, TLS1.0, are enabled on your browser.
And when I checked the Event Viewer I got the following error:
| Code: |
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 40. |
Now I think that it could be an issue with a certificate so I got my self a self signed certificate from http://www.selfsignedcertificate.com/ and only used the certificate to configure the SSL again. Now again, the browser replied with Page can't be displayed but with the following description:
•Make sure the web address is correct.
•Look for the page with your search engine.
•Refresh the page in a few minutes.
Now the following errors appeared in the Event viewer:
| Code: |
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 50. The Windows SChannel error state is 1114.
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 823. |
Did I make any improvements or actually made the problem worse, any idea?[/code] |
anyone? |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Thu Nov 12, 2015 6:41 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
| zhaider wrote: |
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 50. The Windows SChannel error state is 1114.
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 823.
|
What does your research on the TLS and SChannel errors reported lead to? |
|
| Back to top |
|
|
|
|
