Posted: Wed Jan 16, 2008 8:29 am Post subject: What occurs when I do a "refresh security(*) type(ssl)&
Master
Joined: 03 Nov 2004 Posts: 211
I have a question regarding the command "refresh security(*) type(ssl)". Sometimes when I issue this command it takes an incredibly long time to return control back to me. I was wondering what is occurring as a result of this command. Do all my ssl enabled channels have to stop and restart as a result.
Joined: 06 Jan 2004 Posts: 378 Location: Nowhere near a queue manager
I don't know what ALL is happening behind the scenes, but I do know that all connected SSL channels will be terminated. That is probably why you see the delay in getting control back. It's also why REFRESH SECURITY TYPE(SSL) offers no real advantage over a queue manager restart, in my opinion.
Joined: 06 Jan 2004 Posts: 378 Location: Nowhere near a queue manager
jefflowrey wrote:
bbburson wrote:
why REFRESH SECURITY TYPE(SSL) offers no real advantage over a queue manager restart, in my opinion.
It presumably doesn't interrupt NON ssl channels.
It presumably doesn't interrupt applications with BINDINGS connections.
True enough. My myopic view sees all/most of our clients connecting with SSL and if they're all going to get knocked off and have to reconnect anyway then I might as well restart the queue manager. To me this is quite different from the other use of REFRESH SECURITY which re-reads the system password and group files and does not disrupt any already-connected clients.
By "interrupt" are you implying it is not a graceful stop/start of the ssl channels but rather more like a stop force? In my case the refresh took so long that I thought it was hung so I suspect that the channels are being allowed to quiesce gracefully.
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