| Author |
Message
|
| Rahul999 |
 Posted: Mon Sep 20, 2010 2:09 am Post subject: SSL Error not captured be Message Broker logs(mqsi) |
 |
|
Centurion
Joined: 14 Mar 2007
Posts: 134
|
Hi All,
We are making a webservice call from our flows using HTTP SSL.
when there is an SSL error (like certificate chaining or Certificate expiry), it is not captured by mqsi logs(broker logs on AIX server), what could be the reason for that. Is it a normal behaviour? mqsi logs doesnt capture the information about SSL errors??
Our environment - Message Broker V6.1.0.8
OS - AIX.
Regards |
|
| Back to top |
|
 |
| mvarghese |
| Posted: Mon Sep 20, 2010 3:05 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
if your QMGR also using same cert,then it should be in amqerror logs.
Otherwise check ur cert using keytool commands
Normally should maintained a process docs which have all list cert expiry time , so u came to know well in advance..which all servers ssl cert going to expire.
If you want to check trace file, try put trace of biphttplistener and Execution group.
_________________
Jain Varghese |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Sep 20, 2010 4:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mvarghese wrote: |
if your QMGR also using same cert,then it should be in amqerror logs.
Otherwise check ur cert using keytool commands |
The queue manager configuration has absolutely nothing to do with the use of SSL by the HTTPRequest node.
| mvarghese wrote: |
Normally should maintained a process docs which have all list cert expiry time , so u came to know well in advance..which all servers ssl cert going to expire.
If you want to check trace file, try put trace of biphttplistener and Execution group. |
The biphttplistener has absolutely nothing to do with the use of SSL by the HTTPRequest node.
The logging or failure to log of SSL exceptions by the HTTP or SOAP request nodes is fairly dependent on the coding of the flow that is invoking SOAPRequest or HTTPRequest. |
|
| Back to top |
|
|
| mvarghese |
| Posted: Mon Sep 20, 2010 4:40 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
I agreed...for the webservice request. ...he can call within broker another flow or external provider ..In case any HTTP input node using related to his flow.....any case.if he should get a response ..so httlistener trace some extend can help ..that only I thought.
Jeff, is it able to get SSL specific details in his broker user log....by /etc/syslog.conf
user.* - instead of user.info in
_________________
Jain Varghese
Last edited by mvarghese on Mon Sep 20, 2010 5:12 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Sep 20, 2010 4:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mvarghese wrote: |
| I agreed...for the webservice request. ...he can call within broker another flow or external provider...any case.if he should get a response ..so httlistener trace some extend can help ..that only I thought. |
The HTTPRequest node does not use the bipHttpListener process.
| mvarghese wrote: |
| Jeff, is it able to get SSL specific details in his broker user log.... |
It DEPENDS on how the flow is coded. |
|
| Back to top |
|
|
|
|
