| Author |
Message
|
| mqhelpless |
 Posted: Sun Oct 23, 2005 9:30 pm Post subject: Security Exit - MQXCC_CLOSE_CHANNEL |
 |
|
Apprentice
Joined: 13 Jul 2005
Posts: 33
|
| I'm working on security exit and has encountered the problem. The security exit is suppose to authenticate the users on both side. Thus there is an exchange of keys. When everything goes smoothly, i.e. the keys exchanged are correct etc, the channel will be brought up once the security exit authentication passes through. My problem arise when the keys exchanged are incorrect. In this case, the authentication fails, and in my security exit program, I called a "MQXCC_CLOSE_CHANNEL" for the ExitResponse when the authentication fails. The problem is when I later changed to the correct keys and tried to bring the channel up again, the channel fails to come up. I need to end the queue manager and restart it before I can bring the channel up. Does anyone has any idea why it is behaving as such? |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Sun Oct 23, 2005 10:04 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| the channel fails to come up |
if so, then there are messages in the amq* logs. what are the messages (check logs at both ends)?
what is the channel status after the exchange failed (from both ends)
what is the channel status when trying to reinitiate the connection (from both ends)?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Oct 23, 2005 10:14 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi mqhelpless,
Checked out this link and feel that your MQXCC_CLOSE_CHANNEL is doing what its supposed to do.....closing the Queue manager...
http://middleware.its.state.nc.us/middleware/Documentation/en_US/htm/csqzaw09/csqzaw091x.htm
| Code: |
exitResponse
public int exitResponse
Set by the exit to indicate the action that WebSphere MQ classes for Java should take next. Valid values are:
MQXCC_CLOSE_CHANNEL
Set by any exit to indicate that the connection to the queue manager should be closed. |
Regards |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Sun Oct 23, 2005 10:44 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| closing the Queue manager |
it is closing the connection to the queuemanager. anyway, the channel should be restartable without the need to restart the queuemanager. or am i wrong?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| mqhelpless |
| Posted: Sun Oct 23, 2005 10:52 pm Post subject: |
|
|
Apprentice
Joined: 13 Jul 2005
Posts: 33
|
After trying to close the channel in my code using MQXCC_CLOSE_CHANNEL, I see that there is a message from the system indicating system channel was ended "ABNORMALLY".
In general, how do you guys handle situations when the authentication fails? MQXCC_CLOSE_CHANNEL, MQXCC_SUPPRESS_FUNCTION or ? |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Oct 23, 2005 10:59 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Oh sorry ! I realise what u meant.....
Yes the QM will be running, only the connection needs to be set up again...
Are u doing that mqhelpless ?? Or are u being forced to restart the QM also ?? |
|
| Back to top |
|
|
| mqhelpless |
| Posted: Sun Oct 23, 2005 11:00 pm Post subject: |
|
|
Apprentice
Joined: 13 Jul 2005
Posts: 33
|
| Logically, I would think that restarting the channel will be sufficient. But my current situation requires me to "RESTART THE QMANAGER" which is illogical. Thus, I am of the view that something is wrong with the codes but I am not sure how to rectify this issue. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Oct 23, 2005 11:04 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Logically, dont u think that we need to see ur code then  |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Sun Oct 23, 2005 11:28 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
and - in addition - i would like to see the error messages that are created from the start and the related channel status FROM BOTH ENDS
one (maybe simple) reason could be the receiver remaining "stopped" instead of "inactive". who knows.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| mqhelpless |
| Posted: Mon Oct 24, 2005 12:18 am Post subject: |
|
|
Apprentice
Joined: 13 Jul 2005
Posts: 33
|
| Hi guys, thanks for all the input! I've managed to resolve the issue. It was not because of MQXCC_CLOSE_CHANNEL, but an oversight of mine that causes the channel to be improperly started. Speficially, I did not call a destructor to clear a previous result resulting in the error. Soory for the trouble and thanks once again for all the inputs!!! |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Oct 24, 2005 1:09 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
could you please tell us what exactly did you overlook?
otherwise the thread is useless for people that maybe overlooking the same and are searching here for solutions.
Thanks.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Oct 24, 2005 1:24 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
| And please mark the topic as solved which really helps when we search....just go edit your first post in the topic for the same..... |
|
| Back to top |
|
|
|
|
